Cloning through SDS Mirror, boot failure
From: Tony Howat (t.howat_at_linst.ac.uk)
Date: 05/20/04
- Previous message: Jamie Garofalo: "Crontab RC error in log file"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 20 May 2004 14:42:41 +0100 To: sunmanagers@sunmanagers.org
Dear Managers,
I am attempting to clone a Solaris 9 SDS mirrored bootdisk system
running on a V120 to another V120. To achieve this I am breaking the
mirror to target 1 on the source system :
metadetach -f d30 d20
metadetach -f d31 d21
metadetach -f d32 d22
metadetach -f d33 d23
metadetach -f d34 d24
metadetach -f d35 d25
then I pull target 1 and insert it into the destination as target zero.
Booting produces the following output....
So, I insert the disk from the source system into the destination system
and boot :
ok boot disk1
Boot device: /pci@1f,0/pci@1/scsi@8/disk@1,0 File and args:
SunOS Release 5.9 Version Generic_112233-08 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
Cannot mount root on /pseudo/md@0:0,30,blk fstype ufs
panic[cpu0]/thread=140a000: vfs_mountroot: cannot mount root
0000000001409970 genunix:vfs_mountroot+70 (0, 0, 0, 200, 1456da8, 0)
%l0-3: 000000000144a800 000000000144a800 0000000000002000
0000000001495a18
%l4-7: 0000000001493400 0000000001411be8 000000000144b000
000000000144e000
0000000001409a20 genunix:main+98 (1409ba0, f00618b8, 1409ec0, 33267c,
2000, 500)
%l0-3: 0000000000000001 0000000000000000 0000000001412c90
0000000078002000
%l4-7: 000000000140a000 0000000000334000 000000000149b0d8
0000000001062dd0
skipping system dump - no dump device configured
rebooting...
Oops. The same happens if I have the disk in the t0 slot.
It appears to be getting some way through and actually loading the
kernel since the errors refer to md. I'm a little stumped.
I'm using metadetach to break the mirror, is that correct? I'm starting
to think that perhaps that mounting the root partition on the broken
mirror, editing the /etc/vfstab to use non SDS mounts, then moving it to
the second system and reconfiguring SDS on the second system would be
the way to go.
Nevertheless I don't quite understand why it won't boot? I've done
similar on 280R's and the only step I'm not doing is the disks part to
sort out fiber channel IDs, but the V120 disks aren't FC.
To rebuild a mirror on the source server after each attempt at cloning,
I use :
metadb -d -f /dev/dsk/c0t1d0s6
metadetach -f d30 d20
metadetach -f d31 d21
metadetach -f d32 d22
metadetach -f d33 d23
metadetach -f d34 d24
metadetach -f d35 d25
metaclear d20
metaclear d21
metaclear d22
metaclear d23
metaclear d24
metaclear d25
then:
prtvtoc /dev/rdsk/c0t0d0s2 | fmthard -s - /dev/rdsk/c0t1d0s2
metadb -a -f -c2 /dev/dsk/c0t0d0s6 /dev/dsk/c0t1d0s6
metainit d20 1 1 c0t1d0s0
metainit d21 1 1 c0t1d0s1
metainit d22 1 1 c0t1d0s3
metainit d23 1 1 c0t1d0s4
metainit d24 1 1 c0t1d0s5
metainit d25 1 1 c0t1d0s7
metattach d30 d20
metattach d31 d21
metattach d32 d22
metattach d33 d23
metattach d34 d24
metattach d35 d25
installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t1d0s0
Advice would be appreciated.
-- Tony Howat UNIX Network Administrator University Of The Arts, London _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagers
- Previous message: Jamie Garofalo: "Crontab RC error in log file"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|