problem with mirrored root - comp.unix.solaris

Hi, I have a problem with S10 1009 and seting up a mirrored root device. Initially I tried during install but one devcie failed after boot. Now I have tried adding but it comlains about EFI label, but I have set it to SMI label on both drives. What is the proper way to make c0t0d0s0 mirrored? pool: rpool state: DEGRADED status: One or more devices could not be used because the label is missing or invalid. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Replace the device using 'zpool replace'. see: http://www.sun.com/msg/ZFS-8000-4J scrub: none requested config: NAME STATE READ WRITE CKSUM rpool DEGRADED 0 0 0 mirror DEGRADED 0 0 0 c0t0d0s0 FAULTED 0 0 0 corrupted data c0t1d0s0 ONLINE 0 0 0 errors: No known data errors /michael

Michael Laajanen <michael_laajanen@yahoo.com> wrote: > What is the proper way to make c0t0d0s0 mirrored? What is the way you're trying now? You haven't shown the commands you're using. It should be a simple "zpool replace". -- Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/

Hi, hume.spamfilter@bofh.ca wrote: > Michael Laajanen <michael_laajanen@yahoo.com> wrote: >> What is the proper way to make c0t0d0s0 mirrored? > > What is the way you're trying now? You haven't shown the commands > you're using. It should be a simple "zpool replace". > /mbash-3.00# zpool clear rpool bash-3.00# zpool replace -f rpool c0t0d0s0 invalid vdev specification the following errors must be manually repaired: /dev/dsk/c0t0d0s0 is part of active ZFS pool rpool. Please see zpool(1M). bash-3.00# zpool detach rpool c0t0d0s0 bash-3.00# zpool status rpool pool: rpool state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 c0t1d0s0 ONLINE 0 0 0 errors: No known data errors /michael

Michael Laajanen <michael_laajanen@yahoo.com> wrote: > /dev/dsk/c0t0d0s0 is part of active ZFS pool rpool. Please see zpool(1M). What does "zdb -l /dev/dsk/c0t0d0s0" say? It looks like the system is confused about the state of the filesystem on the disk (technically, it's correct that the device still has a zpool on it...) The easiest thing to do might be to destroy the zpool on that disk using dd (null the first and last megabyte) and re-fmthard and re-attach it, especially now that you've taken it out of the pool anyway. -- Brandon Hume - hume -> BOFH.Ca, http://WWW.BOFH.Ca/

Hi, hume.spamfilter@bofh.ca wrote: > Michael Laajanen <michael_laajanen@yahoo.com> wrote: >> /dev/dsk/c0t0d0s0 is part of active ZFS pool rpool. Please see zpool(1M). > > What does "zdb -l /dev/dsk/c0t0d0s0" say? It looks like the system is > confused about the state of the filesystem on the disk (technically, it's > correct that the device still has a zpool on it...) > > The easiest thing to do might be to destroy the zpool on that disk > using dd (null the first and last megabyte) and re-fmthard and re-attach > it, especially now that you've taken it out of the pool anyway. > bash-3.00# zdb -l /dev/dsk/c0t0d0s0 -------------------------------------------- LABEL 0 -------------------------------------------- version=15 name='rpool' state=0 txg=4 pool_guid=2255544692981663971 hostid=2159107026 hostname='tango' top_guid=5810209564273531140 guid=2702942121932374796 vdev_tree type='mirror' id=0 guid=5810209564273531140 metaslab_array=24 metaslab_shift=29 ashift=9 asize=73341861888 is_log=0 children[0] type='disk' id=0 guid=2702942121932374796 path='/dev/dsk/c0t0d0s0' devid='id1,sd@n5000000000000000/a' phys_path='/pci@1f,4000/scsi@3/sd@0,0:a' whole_disk=0 children[1] type='disk' id=1 guid=14581663705942102880 path='/dev/dsk/c0t1d0s0' devid='id1,sd@n5000000000000000/a' phys_path='/pci@1f,4000/scsi@3/sd@1,0:a' whole_disk=0 -------------------------------------------- LABEL 1 -------------------------------------------- version=15 name='rpool' state=0 txg=4 pool_guid=2255544692981663971 hostid=2159107026 hostname='tango' top_guid=5810209564273531140 guid=2702942121932374796 vdev_tree type='mirror' id=0 guid=5810209564273531140 metaslab_array=24 metaslab_shift=29 ashift=9 asize=73341861888 is_log=0 children[0] type='disk' id=0 guid=2702942121932374796 path='/dev/dsk/c0t0d0s0' devid='id1,sd@n5000000000000000/a' phys_path='/pci@1f,4000/scsi@3/sd@0,0:a' whole_disk=0 children[1] type='disk' id=1 guid=14581663705942102880 path='/dev/dsk/c0t1d0s0' devid='id1,sd@n5000000000000000/a' phys_path='/pci@1f,4000/scsi@3/sd@1,0:a' whole_disk=0 -------------------------------------------- LABEL 2 -------------------------------------------- version=15 name='rpool' state=0 txg=4 pool_guid=2255544692981663971 hostid=2159107026 hostname='tango' top_guid=5810209564273531140 guid=2702942121932374796 vdev_tree type='mirror' id=0 guid=5810209564273531140 metaslab_array=24 metaslab_shift=29 ashift=9 asize=73341861888 is_log=0 children[0] type='disk' id=0 guid=2702942121932374796 path='/dev/dsk/c0t0d0s0' devid='id1,sd@n5000000000000000/a' phys_path='/pci@1f,4000/scsi@3/sd@0,0:a' whole_disk=0 children[1] type='disk' id=1 guid=14581663705942102880 path='/dev/dsk/c0t1d0s0' devid='id1,sd@n5000000000000000/a' phys_path='/pci@1f,4000/scsi@3/sd@1,0:a' whole_disk=0 -------------------------------------------- LABEL 3 -------------------------------------------- version=15 name='rpool' state=0 txg=4 pool_guid=2255544692981663971 hostid=2159107026 hostname='tango' top_guid=5810209564273531140 guid=2702942121932374796 vdev_tree type='mirror' id=0 guid=5810209564273531140 metaslab_array=24 metaslab_shift=29 ashift=9 asize=73341861888 is_log=0 children[0] type='disk' id=0 guid=2702942121932374796 path='/dev/dsk/c0t0d0s0' devid='id1,sd@n5000000000000000/a' phys_path='/pci@1f,4000/scsi@3/sd@0,0:a' whole_disk=0 children[1] type='disk' id=1 guid=14581663705942102880 path='/dev/dsk/c0t1d0s0' devid='id1,sd@n5000000000000000/a' phys_path='/pci@1f,4000/scsi@3/sd@1,0:a' whole_disk=0 /michael

On Apr 7, 10:15=A0am, Michael Laajanen <michael_laaja...@yahoo.com> wrote: > Hi, > > hume.spamfil...@bofh.ca wrote: > > Michael Laajanen <michael_laaja...@yahoo.com> wrote: > >> /dev/dsk/c0t0d0s0 is part of active ZFS pool rpool. Please see zpool(1= M). > > > What does "zdb -l /dev/dsk/c0t0d0s0" say? =A0It looks like the system i= s > > confused about the state of the filesystem on the disk (technically, it= 's > > correct that the device still has a zpool on it...) > > > The easiest thing to do might be to destroy the zpool on that disk > > using dd (null the first and last megabyte) and re-fmthard and re-attac= h > > it, especially now that you've taken it out of the pool anyway. > > bash-3.00# zdb -l /dev/dsk/c0t0d0s0 > -------------------------------------------- > LABEL 0 > -------------------------------------------- > =A0 =A0 =A0version=3D15 > =A0 =A0 =A0name=3D'rpool' > =A0 =A0 =A0state=3D0 > =A0 =A0 =A0txg=3D4 > =A0 =A0 =A0pool_guid=3D2255544692981663971 > =A0 =A0 =A0hostid=3D2159107026 > =A0 =A0 =A0hostname=3D'tango' > =A0 =A0 =A0top_guid=3D5810209564273531140 > =A0 =A0 =A0guid=3D2702942121932374796 > =A0 =A0 =A0vdev_tree > =A0 =A0 =A0 =A0 =A0type=3D'mirror' > =A0 =A0 =A0 =A0 =A0id=3D0 > =A0 =A0 =A0 =A0 =A0guid=3D5810209564273531140 > =A0 =A0 =A0 =A0 =A0metaslab_array=3D24 > =A0 =A0 =A0 =A0 =A0metaslab_shift=3D29 > =A0 =A0 =A0 =A0 =A0ashift=3D9 > =A0 =A0 =A0 =A0 =A0asize=3D73341861888 > =A0 =A0 =A0 =A0 =A0is_log=3D0 > =A0 =A0 =A0 =A0 =A0children[0] > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0type=3D'disk' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0id=3D0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0guid=3D2702942121932374796 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0path=3D'/dev/dsk/c0t0d0s0' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0devid=3D'id1,sd@n5000000000000000/a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0phys_path=3D'/pci@1f,4000/scsi@3/sd@0,= 0:a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0whole_disk=3D0 > =A0 =A0 =A0 =A0 =A0children[1] > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0type=3D'disk' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0id=3D1 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0guid=3D14581663705942102880 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0path=3D'/dev/dsk/c0t1d0s0' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0devid=3D'id1,sd@n5000000000000000/a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0phys_path=3D'/pci@1f,4000/scsi@3/sd@1,= 0:a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0whole_disk=3D0 > -------------------------------------------- > LABEL 1 > -------------------------------------------- > =A0 =A0 =A0version=3D15 > =A0 =A0 =A0name=3D'rpool' > =A0 =A0 =A0state=3D0 > =A0 =A0 =A0txg=3D4 > =A0 =A0 =A0pool_guid=3D2255544692981663971 > =A0 =A0 =A0hostid=3D2159107026 > =A0 =A0 =A0hostname=3D'tango' > =A0 =A0 =A0top_guid=3D5810209564273531140 > =A0 =A0 =A0guid=3D2702942121932374796 > =A0 =A0 =A0vdev_tree > =A0 =A0 =A0 =A0 =A0type=3D'mirror' > =A0 =A0 =A0 =A0 =A0id=3D0 > =A0 =A0 =A0 =A0 =A0guid=3D5810209564273531140 > =A0 =A0 =A0 =A0 =A0metaslab_array=3D24 > =A0 =A0 =A0 =A0 =A0metaslab_shift=3D29 > =A0 =A0 =A0 =A0 =A0ashift=3D9 > =A0 =A0 =A0 =A0 =A0asize=3D73341861888 > =A0 =A0 =A0 =A0 =A0is_log=3D0 > =A0 =A0 =A0 =A0 =A0children[0] > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0type=3D'disk' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0id=3D0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0guid=3D2702942121932374796 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0path=3D'/dev/dsk/c0t0d0s0' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0devid=3D'id1,sd@n5000000000000000/a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0phys_path=3D'/pci@1f,4000/scsi@3/sd@0,= 0:a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0whole_disk=3D0 > =A0 =A0 =A0 =A0 =A0children[1] > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0type=3D'disk' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0id=3D1 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0guid=3D14581663705942102880 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0path=3D'/dev/dsk/c0t1d0s0' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0devid=3D'id1,sd@n5000000000000000/a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0phys_path=3D'/pci@1f,4000/scsi@3/sd@1,= 0:a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0whole_disk=3D0 > -------------------------------------------- > LABEL 2 > -------------------------------------------- > =A0 =A0 =A0version=3D15 > =A0 =A0 =A0name=3D'rpool' > =A0 =A0 =A0state=3D0 > =A0 =A0 =A0txg=3D4 > =A0 =A0 =A0pool_guid=3D2255544692981663971 > =A0 =A0 =A0hostid=3D2159107026 > =A0 =A0 =A0hostname=3D'tango' > =A0 =A0 =A0top_guid=3D5810209564273531140 > =A0 =A0 =A0guid=3D2702942121932374796 > =A0 =A0 =A0vdev_tree > =A0 =A0 =A0 =A0 =A0type=3D'mirror' > =A0 =A0 =A0 =A0 =A0id=3D0 > =A0 =A0 =A0 =A0 =A0guid=3D5810209564273531140 > =A0 =A0 =A0 =A0 =A0metaslab_array=3D24 > =A0 =A0 =A0 =A0 =A0metaslab_shift=3D29 > =A0 =A0 =A0 =A0 =A0ashift=3D9 > =A0 =A0 =A0 =A0 =A0asize=3D73341861888 > =A0 =A0 =A0 =A0 =A0is_log=3D0 > =A0 =A0 =A0 =A0 =A0children[0] > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0type=3D'disk' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0id=3D0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0guid=3D2702942121932374796 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0path=3D'/dev/dsk/c0t0d0s0' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0devid=3D'id1,sd@n5000000000000000/a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0phys_path=3D'/pci@1f,4000/scsi@3/sd@0,= 0:a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0whole_disk=3D0 > =A0 =A0 =A0 =A0 =A0children[1] > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0type=3D'disk' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0id=3D1 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0guid=3D14581663705942102880 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0path=3D'/dev/dsk/c0t1d0s0' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0devid=3D'id1,sd@n5000000000000000/a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0phys_path=3D'/pci@1f,4000/scsi@3/sd@1,= 0:a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0whole_disk=3D0 > -------------------------------------------- > LABEL 3 > -------------------------------------------- > =A0 =A0 =A0version=3D15 > =A0 =A0 =A0name=3D'rpool' > =A0 =A0 =A0state=3D0 > =A0 =A0 =A0txg=3D4 > =A0 =A0 =A0pool_guid=3D2255544692981663971 > =A0 =A0 =A0hostid=3D2159107026 > =A0 =A0 =A0hostname=3D'tango' > =A0 =A0 =A0top_guid=3D5810209564273531140 > =A0 =A0 =A0guid=3D2702942121932374796 > =A0 =A0 =A0vdev_tree > =A0 =A0 =A0 =A0 =A0type=3D'mirror' > =A0 =A0 =A0 =A0 =A0id=3D0 > =A0 =A0 =A0 =A0 =A0guid=3D5810209564273531140 > =A0 =A0 =A0 =A0 =A0metaslab_array=3D24 > =A0 =A0 =A0 =A0 =A0metaslab_shift=3D29 > =A0 =A0 =A0 =A0 =A0ashift=3D9 > =A0 =A0 =A0 =A0 =A0asize=3D73341861888 > =A0 =A0 =A0 =A0 =A0is_log=3D0 > =A0 =A0 =A0 =A0 =A0children[0] > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0type=3D'disk' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0id=3D0 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0guid=3D2702942121932374796 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0path=3D'/dev/dsk/c0t0d0s0' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0devid=3D'id1,sd@n5000000000000000/a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0phys_path=3D'/pci@1f,4000/scsi@3/sd@0,= 0:a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0whole_disk=3D0 > =A0 =A0 =A0 =A0 =A0children[1] > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0type=3D'disk' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0id=3D1 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0guid=3D14581663705942102880 > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0path=3D'/dev/dsk/c0t1d0s0' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0devid=3D'id1,sd@n5000000000000000/a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0phys_path=3D'/pci@1f,4000/scsi@3/sd@1,= 0:a' > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0whole_disk=3D0 > /michael Hi Michael, The above output looks sane to me so it seems ZFS has an accurate view of these disks. I don't know why disk labels go funky, but it happens. You might overwrite the c0t0d0s0 label with an EFI label, then relabel it back to SMI and confirm the slices are correct. Sometimes wiping out the label and recreating it helps. Then, try re-attaching c0t0d0s0, like this: # zpool attach rpool c0t1d0s0 c0t0d0s0 If this works, don't forget to apply the bootblocks after the c0t0d0s0 disk is completely resilvered. Thanks, cindy

Hi, cindy wrote: > On Apr 7, 10:15 am, Michael Laajanen <michael_laaja...@yahoo.com> > wrote: >> Hi, >> ><snip> >> /michael > > Hi Michael, > > The above output looks sane to me so it seems ZFS has an accurate view > of these disks. > > I don't know why disk labels go funky, but it happens. > > You might overwrite the c0t0d0s0 label with an EFI label, then relabel > it back to SMI and confirm the slices are correct. Sometimes wiping > out > the label and recreating it helps. > > Then, try re-attaching c0t0d0s0, like this: > > # zpool attach rpool c0t1d0s0 c0t0d0s0 > > If this works, don't forget to apply the bootblocks after the c0t0d0s0 > disk > is completely resilvered. > > Thanks, > > cindy Hi again, manage to crash the system disk so I had to jumpstart the server, now I am back with the same issue butt this time c0t0d0s0 is working boot drive. bash-3.00# prtvtoc /dev/rdsk/c0t0d0s0 * /dev/rdsk/c0t0d0s0 partition map * * Dimensions: * 512 bytes/sector * 1093 sectors/track * 2 tracks/cylinder * 2186 sectors/cylinder * 65535 cylinders * 65533 accessible cylinders * * Flags: * 1: unmountable * 10: read-only * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 2 00 0 143255138 143255137 2 5 00 0 143255138 143255137 bash-3.00# prtvtoc /dev/rdsk/c0t1d0s0 * /dev/rdsk/c0t1d0s0 partition map * * Dimensions: * 512 bytes/sector * 1093 sectors/track * 2 tracks/cylinder * 2186 sectors/cylinder * 65535 cylinders * 65533 accessible cylinders * * Flags: * 1: unmountable * 10: read-only * * First Sector Last * Partition Tag Flags Sector Count Sector Mount Directory 0 2 00 0 143255138 143255137 2 5 00 0 143255138 143255137 Below is after c0t1 detached again! bash-3.00# zpool status rpool pool: rpool state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 c0t0d0s0 ONLINE 0 0 0 I have tried label on c0t1d0s0,from SMI -> EFI -> SMI, still the same issue. bash-3.00# zpool attach rpool c0t0d0s0 c0t1d0s0 cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy bash-3.00# zpool create foo c0t1d0s0 bash-3.00# zpool status foo pool: foo state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM foo ONLINE 0 0 0 c0t1d0s0 ONLINE 0 0 0 errors: No known data errors bash-3.00# zpool attach rpool c0t0d0s0 c0t1d0s0 cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy What is the problem, the drive is working as I can create a pool foo! /michael

On Apr 7, 1:14=A0pm, Michael Laajanen <michael_laaja...@yahoo.com> wrote: > Hi, > > > > cindy wrote: > > On Apr 7, 10:15 am, Michael Laajanen <michael_laaja...@yahoo.com> > > wrote: > >> Hi, > > ><snip> > >> /michael > > > Hi Michael, > > > The above output looks sane to me so it seems ZFS has an accurate view > > of these disks. > > > I don't know why disk labels go funky, but it happens. > > > You might overwrite the c0t0d0s0 label with an EFI label, then relabel > > it back to SMI and confirm the slices are correct. Sometimes wiping > > out > > the label and recreating it helps. > > > Then, try re-attaching c0t0d0s0, like this: > > > # zpool attach rpool c0t1d0s0 c0t0d0s0 > > > If this works, don't forget to apply the bootblocks after the c0t0d0s0 > > disk > > is completely resilvered. > > > Thanks, > > > cindy > > Hi again, manage to crash the system disk so I had to jumpstart the > server, now I am back with the same issue butt this time c0t0d0s0 is > working boot drive. > > bash-3.00# prtvtoc /dev/rdsk/c0t0d0s0 > * /dev/rdsk/c0t0d0s0 partition map > * > * Dimensions: > * =A0 =A0 512 bytes/sector > * =A0 =A01093 sectors/track > * =A0 =A0 =A0 2 tracks/cylinder > * =A0 =A02186 sectors/cylinder > * =A0 65535 cylinders > * =A0 65533 accessible cylinders > * > * Flags: > * =A0 1: unmountable > * =A010: read-only > * > * =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0First =A0 =A0 Sector= =A0 =A0Last > * Partition =A0Tag =A0Flags =A0 =A0Sector =A0 =A0 Count =A0 =A0Sector =A0= Mount Directory > =A0 =A0 =A0 =A0 0 =A0 =A0 =A02 =A0 =A000 =A0 =A0 =A0 =A0 =A00 143255138 1= 43255137 > =A0 =A0 =A0 =A0 2 =A0 =A0 =A05 =A0 =A000 =A0 =A0 =A0 =A0 =A00 143255138 1= 43255137 > bash-3.00# prtvtoc /dev/rdsk/c0t1d0s0 > * /dev/rdsk/c0t1d0s0 partition map > * > * Dimensions: > * =A0 =A0 512 bytes/sector > * =A0 =A01093 sectors/track > * =A0 =A0 =A0 2 tracks/cylinder > * =A0 =A02186 sectors/cylinder > * =A0 65535 cylinders > * =A0 65533 accessible cylinders > * > * Flags: > * =A0 1: unmountable > * =A010: read-only > * > * =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0First =A0 =A0 Sector= =A0 =A0Last > * Partition =A0Tag =A0Flags =A0 =A0Sector =A0 =A0 Count =A0 =A0Sector =A0= Mount Directory > =A0 =A0 =A0 =A0 0 =A0 =A0 =A02 =A0 =A000 =A0 =A0 =A0 =A0 =A00 143255138 1= 43255137 > =A0 =A0 =A0 =A0 2 =A0 =A0 =A05 =A0 =A000 =A0 =A0 =A0 =A0 =A00 143255138 1= 43255137 > > Below is after c0t1 detached again! > > bash-3.00# zpool status rpool > =A0 =A0pool: rpool > =A0 state: ONLINE > =A0 scrub: none requested > config: > > =A0 =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > =A0 =A0 =A0 =A0 =A0rpool =A0 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0c0t0d0s0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 0 > > I have tried label on c0t1d0s0,from SMI -> EFI -> SMI, still the same iss= ue. > bash-3.00# zpool attach rpool c0t0d0s0 c0t1d0s0 > cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy > > bash-3.00# zpool create foo c0t1d0s0 > bash-3.00# zpool status foo > =A0 =A0pool: foo > =A0 state: ONLINE > =A0 scrub: none requested > config: > > =A0 =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > =A0 =A0 =A0 =A0 =A0foo =A0 =A0 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0= =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0c0t1d0s0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 0 > > errors: No known data errors > > bash-3.00# zpool attach rpool c0t0d0s0 c0t1d0s0 > cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy > > What is the problem, the drive is working as I can create a pool foo! > > /michael Michael, In the last case, of course, you need to destroy foo before attaching c0t1d0s0, but other than that, I'm stumped. If foo is destroyed, you might retry the zpool attach with the -f option to see if any add'l clues are provided: # zpool attach -f rpool c0t0d0s0 c0t1d0s0 We had a bug where if you tried to attach a disk to create a root pool mirror you would get a overlapping slice message, but I don't recall a device busy problem with zpool attach. Cindy Thanks, Cindy

Hi, cindy wrote: > On Apr 7, 1:14 pm, Michael Laajanen <michael_laaja...@yahoo.com> > wrote: >> Hi, >> >> >> >> cindy wrote: >>> On Apr 7, 10:15 am, Michael Laajanen <michael_laaja...@yahoo.com> >>> wrote: >>>> Hi, >>> <snip> >>>> /michael >>> Hi Michael, >>> The above output looks sane to me so it seems ZFS has an accurate view >>> of these disks. >>> I don't know why disk labels go funky, but it happens. >>> You might overwrite the c0t0d0s0 label with an EFI label, then relabel >>> it back to SMI and confirm the slices are correct. Sometimes wiping >>> out >>> the label and recreating it helps. >>> Then, try re-attaching c0t0d0s0, like this: >>> # zpool attach rpool c0t1d0s0 c0t0d0s0 >>> If this works, don't forget to apply the bootblocks after the c0t0d0s0 >>> disk >>> is completely resilvered. >>> Thanks, >>> cindy >> Hi again, manage to crash the system disk so I had to jumpstart the >> server, now I am back with the same issue butt this time c0t0d0s0 is >> working boot drive. >> >> bash-3.00# prtvtoc /dev/rdsk/c0t0d0s0 >> * /dev/rdsk/c0t0d0s0 partition map >> * >> * Dimensions: >> * 512 bytes/sector >> * 1093 sectors/track >> * 2 tracks/cylinder >> * 2186 sectors/cylinder >> * 65535 cylinders >> * 65533 accessible cylinders >> * >> * Flags: >> * 1: unmountable >> * 10: read-only >> * >> * First Sector Last >> * Partition Tag Flags Sector Count Sector Mount Directory >> 0 2 00 0 143255138 143255137 >> 2 5 00 0 143255138 143255137 >> bash-3.00# prtvtoc /dev/rdsk/c0t1d0s0 >> * /dev/rdsk/c0t1d0s0 partition map >> * >> * Dimensions: >> * 512 bytes/sector >> * 1093 sectors/track >> * 2 tracks/cylinder >> * 2186 sectors/cylinder >> * 65535 cylinders >> * 65533 accessible cylinders >> * >> * Flags: >> * 1: unmountable >> * 10: read-only >> * >> * First Sector Last >> * Partition Tag Flags Sector Count Sector Mount Directory >> 0 2 00 0 143255138 143255137 >> 2 5 00 0 143255138 143255137 >> >> Below is after c0t1 detached again! >> >> bash-3.00# zpool status rpool >> pool: rpool >> state: ONLINE >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> rpool ONLINE 0 0 0 >> c0t0d0s0 ONLINE 0 0 0 >> >> I have tried label on c0t1d0s0,from SMI -> EFI -> SMI, still the same issue. >> bash-3.00# zpool attach rpool c0t0d0s0 c0t1d0s0 >> cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy >> >> bash-3.00# zpool create foo c0t1d0s0 >> bash-3.00# zpool status foo >> pool: foo >> state: ONLINE >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> foo ONLINE 0 0 0 >> c0t1d0s0 ONLINE 0 0 0 >> >> errors: No known data errors >> >> bash-3.00# zpool attach rpool c0t0d0s0 c0t1d0s0 >> cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy >> >> What is the problem, the drive is working as I can create a pool foo! >> >> /michael > > Michael, > > In the last case, of course, you need to destroy foo before > attaching c0t1d0s0, but other than that, I'm stumped. > > If foo is destroyed, you might retry the zpool attach with > the -f option to see if any add'l clues are provided: > > # zpool attach -f rpool c0t0d0s0 c0t1d0s0 > > We had a bug where if you tried to attach a disk to create > a root pool mirror you would get a overlapping slice message, > but I don't recall a device busy problem with zpool attach. > > Cindy > Thanks, > > Cindy Right, I am also stumped! bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy bash-3.00# zpool create foo c0t1d0s0 bash-3.00# zpool status foo pool: foo state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM foo ONLINE 0 0 0 c0t1d0s0 ONLINE 0 0 0 errors: No known data errors bash-3.00# zpool destroy foo bash-3.00# zpool status foo cannot open 'foo': no such pool bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy bash-3.00# cat /etc/release Solaris 10 10/09 s10s_u8wos_08a SPARC Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 16 September 2009 /michael

On Apr 7, 1:54=A0pm, Michael Laajanen <michael_laaja...@yahoo.com> wrote: > Hi, > > > > cindy wrote: > > On Apr 7, 1:14 pm, Michael Laajanen <michael_laaja...@yahoo.com> > > wrote: > >> Hi, > > >> cindy wrote: > >>> On Apr 7, 10:15 am, Michael Laajanen <michael_laaja...@yahoo.com> > >>> wrote: > >>>> Hi, > >>> <snip> > >>>> /michael > >>> Hi Michael, > >>> The above output looks sane to me so it seems ZFS has an accurate vie= w > >>> of these disks. > >>> I don't know why disk labels go funky, but it happens. > >>> You might overwrite the c0t0d0s0 label with an EFI label, then relabe= l > >>> it back to SMI and confirm the slices are correct. Sometimes wiping > >>> out > >>> the label and recreating it helps. > >>> Then, try re-attaching c0t0d0s0, like this: > >>> # zpool attach rpool c0t1d0s0 c0t0d0s0 > >>> If this works, don't forget to apply the bootblocks after the c0t0d0s= 0 > >>> disk > >>> is completely resilvered. > >>> Thanks, > >>> cindy > >> Hi again, manage to crash the system disk so I had to jumpstart the > >> server, now I am back with the same issue butt this time c0t0d0s0 is > >> working boot drive. > > >> bash-3.00# prtvtoc /dev/rdsk/c0t0d0s0 > >> * /dev/rdsk/c0t0d0s0 partition map > >> * > >> * Dimensions: > >> * =A0 =A0 512 bytes/sector > >> * =A0 =A01093 sectors/track > >> * =A0 =A0 =A0 2 tracks/cylinder > >> * =A0 =A02186 sectors/cylinder > >> * =A0 65535 cylinders > >> * =A0 65533 accessible cylinders > >> * > >> * Flags: > >> * =A0 1: unmountable > >> * =A010: read-only > >> * > >> * =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0First =A0 =A0 Sec= tor =A0 =A0Last > >> * Partition =A0Tag =A0Flags =A0 =A0Sector =A0 =A0 Count =A0 =A0Sector = =A0Mount Directory > >> =A0 =A0 =A0 =A0 0 =A0 =A0 =A02 =A0 =A000 =A0 =A0 =A0 =A0 =A00 14325513= 8 143255137 > >> =A0 =A0 =A0 =A0 2 =A0 =A0 =A05 =A0 =A000 =A0 =A0 =A0 =A0 =A00 14325513= 8 143255137 > >> bash-3.00# prtvtoc /dev/rdsk/c0t1d0s0 > >> * /dev/rdsk/c0t1d0s0 partition map > >> * > >> * Dimensions: > >> * =A0 =A0 512 bytes/sector > >> * =A0 =A01093 sectors/track > >> * =A0 =A0 =A0 2 tracks/cylinder > >> * =A0 =A02186 sectors/cylinder > >> * =A0 65535 cylinders > >> * =A0 65533 accessible cylinders > >> * > >> * Flags: > >> * =A0 1: unmountable > >> * =A010: read-only > >> * > >> * =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0First =A0 =A0 Sec= tor =A0 =A0Last > >> * Partition =A0Tag =A0Flags =A0 =A0Sector =A0 =A0 Count =A0 =A0Sector = =A0Mount Directory > >> =A0 =A0 =A0 =A0 0 =A0 =A0 =A02 =A0 =A000 =A0 =A0 =A0 =A0 =A00 14325513= 8 143255137 > >> =A0 =A0 =A0 =A0 2 =A0 =A0 =A05 =A0 =A000 =A0 =A0 =A0 =A0 =A00 14325513= 8 143255137 > > >> Below is after c0t1 detached again! > > >> bash-3.00# zpool status rpool > >> =A0 =A0pool: rpool > >> =A0 state: ONLINE > >> =A0 scrub: none requested > >> config: > > >> =A0 =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > >> =A0 =A0 =A0 =A0 =A0rpool =A0 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 = =A0 =A0 0 > >> =A0 =A0 =A0 =A0 =A0 =A0c0t0d0s0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 > > >> I have tried label on c0t1d0s0,from SMI -> EFI -> SMI, still the same = issue. > >> bash-3.00# zpool attach rpool c0t0d0s0 c0t1d0s0 > >> cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy > > >> bash-3.00# zpool create foo c0t1d0s0 > >> bash-3.00# zpool status foo > >> =A0 =A0pool: foo > >> =A0 state: ONLINE > >> =A0 scrub: none requested > >> config: > > >> =A0 =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > >> =A0 =A0 =A0 =A0 =A0foo =A0 =A0 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 = =A0 =A0 0 > >> =A0 =A0 =A0 =A0 =A0 =A0c0t1d0s0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 > > >> errors: No known data errors > > >> bash-3.00# zpool attach rpool c0t0d0s0 c0t1d0s0 > >> cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy > > >> What is the problem, the drive is working as I can create a pool foo! > > >> /michael > > > Michael, > > > In the last case, of course, you need to destroy foo before > > attaching c0t1d0s0, but other than that, I'm stumped. > > > If foo is destroyed, you might retry the zpool attach with > > the -f option to see if any add'l clues are provided: > > > # zpool attach -f rpool c0t0d0s0 c0t1d0s0 > > > We had a bug where if you tried to attach a disk to create > > a root pool mirror you would get a overlapping slice message, > > but I don't recall a device busy problem with zpool attach. > > > Cindy > > Thanks, > > > Cindy > > Right, I am also stumped! > > bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 > cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy > bash-3.00# zpool create foo c0t1d0s0 > bash-3.00# zpool status foo > =A0 =A0pool: foo > =A0 state: ONLINE > =A0 scrub: none requested > config: > > =A0 =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > =A0 =A0 =A0 =A0 =A0foo =A0 =A0 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0= =A0 0 > =A0 =A0 =A0 =A0 =A0 =A0c0t1d0s0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 =A0= 0 > > errors: No known data errors > bash-3.00# zpool destroy foo > bash-3.00# zpool status foo > cannot open 'foo': no such pool > bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 > cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy > bash-3.00# cat /etc/release > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Solaris 10 10/09 s10s_u8wo= s_08a SPARC > =A0 =A0 =A0 =A0 =A0 =A0 Copyright 2009 Sun Microsystems, Inc. =A0All Righ= ts Reserved. > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Use is subject to lice= nse terms. > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Assembled 16 Sept= ember 2009 > > /michael Michael, I did a google search on zpool attach, rpool, cannot attach, is busy and found two errors conditions: 1. the disks were not specified in the correct order, but this is not your problem 2. this problem was reported with an Areca controller and I didn't see a resolution reported. Works fine on my t2000 running identical bits as you: # cat /etc/release Solaris 10 10/09 s10s_u8wos_08a SPARC Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. Use is subject to license terms. Assembled 16 September 2009 # zpool attach rpool c1t0d0s0 c1t1d0s0 Please be sure to invoke installboot(1M) to make 'c1t1d0s0' bootable. # zpool status rpool pool: rpool state: ONLINE status: One or more devices is currently being resilvered. The pool will continue to function, possibly in a degraded state. action: Wait for the resilver to complete. scrub: resilver in progress for 0h0m, 3.41% done, 0h13m to go config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror ONLINE 0 0 0 c1t0d0s0 ONLINE 0 0 0 c1t1d0s0 ONLINE 0 0 0 1.27G resilvered errors: No known data errors

Hi, cindy wrote: > On Apr 7, 1:54 pm, Michael Laajanen <michael_laaja...@yahoo.com> > wrote: >> Hi, >> >> >> >> cindy wrote: >>> On Apr 7, 1:14 pm, Michael Laajanen <michael_laaja...@yahoo.com> >>> wrote: >>>> Hi, >>> Thanks, >>> Cindy >> Right, I am also stumped! >> >> bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 >> cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy >> bash-3.00# zpool create foo c0t1d0s0 >> bash-3.00# zpool status foo >> pool: foo >> state: ONLINE >> scrub: none requested >> config: >> >> NAME STATE READ WRITE CKSUM >> foo ONLINE 0 0 0 >> c0t1d0s0 ONLINE 0 0 0 >> >> errors: No known data errors >> bash-3.00# zpool destroy foo >> bash-3.00# zpool status foo >> cannot open 'foo': no such pool >> bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 >> cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy >> bash-3.00# cat /etc/release >> Solaris 10 10/09 s10s_u8wos_08a SPARC >> Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. >> Use is subject to license terms. >> Assembled 16 September 2009 >> >> /michael > > Michael, > > I did a google search on zpool attach, rpool, cannot attach, is busy > and found two errors conditions: > 1. the disks were not specified in the correct order, but this is not > your problem right > 2. this problem was reported with an Areca controller and I didn't see > a resolution reported. > This is a E450, all Sun gear but the disks are new 15K 73GB Seagates( SEAGATE-ST373455LC-0003) for the root pool. I have 16 300GB drives in the main pool all working fine! > Works fine on my t2000 running identical bits as you: > # cat /etc/release > Solaris 10 10/09 s10s_u8wos_08a SPARC > Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. > Use is subject to license terms. > Assembled 16 September 2009 > # zpool attach rpool c1t0d0s0 c1t1d0s0 > Please be sure to invoke installboot(1M) to make 'c1t1d0s0' bootable. > # zpool status rpool > pool: rpool > state: ONLINE > status: One or more devices is currently being resilvered. The pool > will > continue to function, possibly in a degraded state. > action: Wait for the resilver to complete. > scrub: resilver in progress for 0h0m, 3.41% done, 0h13m to go > config: > > NAME STATE READ WRITE CKSUM > rpool ONLINE 0 0 0 > mirror ONLINE 0 0 0 > c1t0d0s0 ONLINE 0 0 0 > c1t1d0s0 ONLINE 0 0 0 1.27G resilvered > > errors: No known data errors > The funny thing is that the installer also fail! 0. c0t0d0 <SEAGATE-ST373455LC-0003 cyl 65533 alt 2 hd 2 sec 1093> /pci@1f,4000/scsi@3/sd@0,0 1. c0t1d0 <SEAGATE-ST373455LC-0003 cyl 65533 alt 2 hd 2 sec 1093> /pci@1f,4000/scsi@3/sd@1,0 2. c2t0d0 <FUJITSU-MAW3300NC-0104-279.40GB> /pci@6,4000/scsi@3/sd@0,0 3. c2t1d0 <FUJITSU-MAW3300NC-0104-279.40GB> /pci@6,4000/scsi@3/sd@1,0 4. c2t2d0 <FUJITSU-MAW3300NC-0104-279.40GB> /pci@6,4000/scsi@3/sd@2,0 5. c2t3d0 <FUJITSU-MAW3300NC-0104-279.40GB> /pci@6,4000/scsi@3/sd@3,0 6. c3t0d0 <FUJITSU-MAW3300NC-0104-279.40GB> /pci@6,4000/scsi@3,1/sd@0,0 7. c3t1d0 <FUJITSU-MAW3300NC-0104-279.40GB> /pci@6,4000/scsi@3,1/sd@1,0 8. c3t2d0 <FUJITSU-MAW3300NC-0104-279.40GB> /pci@6,4000/scsi@3,1/sd@2,0 9. c3t3d0 <FUJITSU-MAW3300NC-0104-279.40GB> /pci@6,4000/scsi@3,1/sd@3,0 10. c4t0d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> /pci@6,4000/scsi@4/sd@0,0 11. c4t1d0 <FUJITSU-MAW3300NC-0104-279.40GB> /pci@6,4000/scsi@4/sd@1,0 12. c4t2d0 <MAXTOR-ATLAS10K5_300SCA-JNZH-279.40GB> /pci@6,4000/scsi@4/sd@2,0 13. c4t3d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> /pci@6,4000/scsi@4/sd@3,0 14. c5t0d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> /pci@6,4000/scsi@4,1/sd@0,0 15. c5t1d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> /pci@6,4000/scsi@4,1/sd@1,0 16. c5t2d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> /pci@6,4000/scsi@4,1/sd@2,0 17. c5t3d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> /pci@6,4000/scsi@4,1/sd@3,0 Fine, I can run without the root pool mirrored and do a dump from the active drive to the standby each night but why does it not work mirrored? /michael

On Apr 7, 2:38=A0pm, Michael Laajanen <michael_laaja...@yahoo.com> wrote: > Hi, > > > > cindy wrote: > > On Apr 7, 1:54 pm, Michael Laajanen <michael_laaja...@yahoo.com> > > wrote: > >> Hi, > > >> cindy wrote: > >>> On Apr 7, 1:14 pm, Michael Laajanen <michael_laaja...@yahoo.com> > >>> wrote: > >>>> Hi, > >>> Thanks, > >>> Cindy > >> Right, I am also stumped! > > >> bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 > >> cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy > >> bash-3.00# zpool create foo c0t1d0s0 > >> bash-3.00# zpool status foo > >> =A0 =A0pool: foo > >> =A0 state: ONLINE > >> =A0 scrub: none requested > >> config: > > >> =A0 =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > >> =A0 =A0 =A0 =A0 =A0foo =A0 =A0 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 = =A0 =A0 0 > >> =A0 =A0 =A0 =A0 =A0 =A0c0t1d0s0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 > > >> errors: No known data errors > >> bash-3.00# zpool destroy foo > >> bash-3.00# zpool status foo > >> cannot open 'foo': no such pool > >> bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 > >> cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy > >> bash-3.00# cat /etc/release > >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Solaris 10 10/09 s10s_u= 8wos_08a SPARC > >> =A0 =A0 =A0 =A0 =A0 =A0 Copyright 2009 Sun Microsystems, Inc. =A0All R= ights Reserved. > >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Use is subject to l= icense terms. > >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Assembled 16 S= eptember 2009 > > >> /michael > > > Michael, > > > I did a google search on zpool attach, rpool, cannot attach, is busy > > and found two errors conditions: > > 1. the disks were not specified in the correct order, but this is not > > your problem > > right > > > 2. this problem was reported with an Areca controller and I didn't see > > a resolution reported. > > This is a E450, all Sun gear but the disks are new 15K 73GB Seagates( > SEAGATE-ST373455LC-0003) for the root pool. > I have 16 300GB drives in the main pool all working fine! > > > > > Works fine on my t2000 running identical bits as you: > > # cat /etc/release > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Solaris 10 10/09 s10s_u8wos= _08a SPARC > > =A0 =A0 =A0 =A0 =A0 =A0Copyright 2009 Sun Microsystems, Inc. =A0All Rig= hts Reserved. > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Use is subject to licen= se terms. > > =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0Assembled 16 Sep= tember 2009 > > # zpool attach rpool c1t0d0s0 c1t1d0s0 > > Please be sure to invoke installboot(1M) to make 'c1t1d0s0' bootable. > > # zpool status rpool > > =A0 pool: rpool > > =A0state: ONLINE > > status: One or more devices is currently being resilvered. =A0The pool > > will > > =A0 =A0 =A0 =A0 continue to function, possibly in a degraded state. > > action: Wait for the resilver to complete. > > =A0scrub: resilver in progress for 0h0m, 3.41% done, 0h13m to go > > config: > > > =A0 =A0 =A0 =A0 NAME =A0 =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > > =A0 =A0 =A0 =A0 rpool =A0 =A0 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 = =A0 =A0 0 > > =A0 =A0 =A0 =A0 =A0 mirror =A0 =A0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 = =A0 =A0 0 > > =A0 =A0 =A0 =A0 =A0 =A0 c1t0d0s0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 > > =A0 =A0 =A0 =A0 =A0 =A0 c1t1d0s0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 =A01.27G resilvered > > > errors: No known data errors > > The funny thing is that the installer also fail! > > =A0 =A0 =A0 =A0 0. c0t0d0 <SEAGATE-ST373455LC-0003 cyl 65533 alt 2 hd 2 s= ec 1093> > =A0 =A0 =A0 =A0 =A0 =A0/pci@1f,4000/scsi@3/sd@0,0 > =A0 =A0 =A0 =A0 1. c0t1d0 <SEAGATE-ST373455LC-0003 cyl 65533 alt 2 hd 2 s= ec 1093> > =A0 =A0 =A0 =A0 =A0 =A0/pci@1f,4000/scsi@3/sd@1,0 > =A0 =A0 =A0 =A0 2. c2t0d0 <FUJITSU-MAW3300NC-0104-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@3/sd@0,0 > =A0 =A0 =A0 =A0 3. c2t1d0 <FUJITSU-MAW3300NC-0104-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@3/sd@1,0 > =A0 =A0 =A0 =A0 4. c2t2d0 <FUJITSU-MAW3300NC-0104-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@3/sd@2,0 > =A0 =A0 =A0 =A0 5. c2t3d0 <FUJITSU-MAW3300NC-0104-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@3/sd@3,0 > =A0 =A0 =A0 =A0 6. c3t0d0 <FUJITSU-MAW3300NC-0104-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@3,1/sd@0,0 > =A0 =A0 =A0 =A0 7. c3t1d0 <FUJITSU-MAW3300NC-0104-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@3,1/sd@1,0 > =A0 =A0 =A0 =A0 8. c3t2d0 <FUJITSU-MAW3300NC-0104-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@3,1/sd@2,0 > =A0 =A0 =A0 =A0 9. c3t3d0 <FUJITSU-MAW3300NC-0104-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@3,1/sd@3,0 > =A0 =A0 =A0 =A010. c4t0d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@4/sd@0,0 > =A0 =A0 =A0 =A011. c4t1d0 <FUJITSU-MAW3300NC-0104-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@4/sd@1,0 > =A0 =A0 =A0 =A012. c4t2d0 <MAXTOR-ATLAS10K5_300SCA-JNZH-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@4/sd@2,0 > =A0 =A0 =A0 =A013. c4t3d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@4/sd@3,0 > =A0 =A0 =A0 =A014. c5t0d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@4,1/sd@0,0 > =A0 =A0 =A0 =A015. c5t1d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@4,1/sd@1,0 > =A0 =A0 =A0 =A016. c5t2d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@4,1/sd@2,0 > =A0 =A0 =A0 =A017. c5t3d0 <HITACHI-HUS103030FL3800-SA1B-279.40GB> > =A0 =A0 =A0 =A0 =A0 =A0/pci@6,4000/scsi@4,1/sd@3,0 > > Fine, I can run without the root pool mirrored and do a dump from the > active drive to the standby each night but why does it not work mirrored? > > /michael Michael, Oh right, the install program create the root pool mirror either, but it probably just calls the zpool attach operation. Something about this disk is not connected properly but I'm not sure how to troubleshoot from here. Maybe the hardware experts on this list can comment. Cindy

On Wed, 7 Apr 2010 13:13:42 -0700 (PDT) cindy <cindy.swearingen@sun.com> wrote: > I did a google search on zpool attach, rpool, cannot attach, is busy > and found two errors conditions: > 1. the disks were not specified in the correct order, but this is not > your problem > 2. this problem was reported with an Areca controller and I didn't see > a resolution reported. I had a similar problem (disk busy on attach) after a V440 crashed. The system has a zpool created from 6 disks on a StorEdge 3320, and after it came back up one of the disks was shown as failed. There was nothing wrong with it, however, as it showed up OK under format and was readable with dd. As in this case, zpool attach (with and without -f) worked, zpool claiming that the disk was in use. I finally managed to solve the problem by exporting the zpool, re-labelling the "failed" disk with fmthard, and then importing the zpool. After this (rather scary, but I had made a backup) sequence the disk attached without problems and re-silvered. My guess is that the crash caused some subtle changes to the disk that made ZFS think it was invalid, but also that it was still in use in the zpool. -- Stefaan A Eeckels -- "Object-oriented programming is an exceptionally bad idea which could only have originated in California." --Edsger Dijkstra

Hi, Stefaan A Eeckels wrote: > On Wed, 7 Apr 2010 13:13:42 -0700 (PDT) > cindy <cindy.swearingen@sun.com> wrote: > >> I did a google search on zpool attach, rpool, cannot attach, is busy >> and found two errors conditions: >> 1. the disks were not specified in the correct order, but this is not >> your problem >> 2. this problem was reported with an Areca controller and I didn't see >> a resolution reported. > > I had a similar problem (disk busy on attach) after a V440 crashed. The > system has a zpool created from 6 disks on a StorEdge 3320, and after > it came back up one of the disks was shown as failed. There was nothing > wrong with it, however, as it showed up OK under format and was > readable with dd. > > As in this case, zpool attach (with and without -f) worked, zpool > claiming that the disk was in use. I finally managed to solve the > problem by exporting the zpool, re-labelling the "failed" disk with > fmthard, and then importing the zpool. After this (rather scary, but I > had made a backup) sequence the disk attached without problems and > re-silvered. > Hmm, you say you exported the pool can that be done while running on the pool(rpool)? > My guess is that the crash caused some subtle changes to the disk that > made ZFS think it was invalid, but also that it was still in use in the > zpool. > I tried this without success. bash-3.00# prtvtoc /dev/rdsk/c0t0d0s0 | fmthard -s - /dev/rdsk/c0t1d0s0 fmthard: New volume table of contents now in place. bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy /michael

On Apr 9, 4:36=A0am, Michael Laajanen <michael_laaja...@yahoo.com> wrote: > Hi, > > > > Stefaan A Eeckels wrote: > > On Wed, 7 Apr 2010 13:13:42 -0700 (PDT) > > cindy <cindy.swearin...@sun.com> wrote: > > >> I did a google search on zpool attach, rpool, cannot attach, is busy > >> and found two errors conditions: > >> 1. the disks were not specified in the correct order, but this is not > >> your problem > >> 2. this problem was reported with an Areca controller and I didn't see > >> a resolution reported. > > > I had a similar problem (disk busy on attach) after a V440 crashed. The > > system has a zpool created from 6 disks on a StorEdge 3320, and after > > it came back up one of the disks was shown as failed. There was nothing > > wrong with it, however, as it showed up OK under format and was > > readable with dd. > > > As in this case, zpool attach (with and without -f) worked, zpool > > claiming that the disk was in use. I finally managed to solve the > > problem by exporting the zpool, re-labelling the "failed" disk with > > fmthard, and then importing the zpool. After this (rather scary, but I > > had made a backup) sequence the disk attached without problems and > > re-silvered. > > Hmm, you say you exported the pool can that be done while running on the > =A0 pool(rpool)? > > > My guess is that the crash caused some subtle changes to the disk that > > made ZFS think it was invalid, but also that it was still in use in the > > zpool. > > I tried this without success. > > bash-3.00# prtvtoc /dev/rdsk/c0t0d0s0 | fmthard -s - /dev/rdsk/c0t1d0s0 > fmthard: =A0New volume table of contents now in place. > bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 > cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy > > /michael- Hide quoted text - > > - Show quoted text - Interesting! Per your second post, bash-3.00# zpool status rpool pool: rpool state: ONLINE scrub: none requested config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 c0t1d0s0 ONLINE 0 0 0 c0t1d0s0 is ONLINE, but in later posts, you are trying to attach it to rpool. Seems that the box is not in production yet. Then you can just jumpstart to reinstall it, specifying mirror in the profile. Victor

Hi, Victor wrote: > On Apr 9, 4:36 am, Michael Laajanen <michael_laaja...@yahoo.com> > wrote: >> Hi, >> >> >> >> Stefaan A Eeckels wrote: >>> On Wed, 7 Apr 2010 13:13:42 -0700 (PDT) >>> cindy <cindy.swearin...@sun.com> wrote: >>>> I did a google search on zpool attach, rpool, cannot attach, is busy >>>> and found two errors conditions: >>>> 1. the disks were not specified in the correct order, but this is not >>>> your problem >>>> 2. this problem was reported with an Areca controller and I didn't see >>>> a resolution reported. >>> I had a similar problem (disk busy on attach) after a V440 crashed. The >>> system has a zpool created from 6 disks on a StorEdge 3320, and after >>> it came back up one of the disks was shown as failed. There was nothing >>> wrong with it, however, as it showed up OK under format and was >>> readable with dd. >>> As in this case, zpool attach (with and without -f) worked, zpool >>> claiming that the disk was in use. I finally managed to solve the >>> problem by exporting the zpool, re-labelling the "failed" disk with >>> fmthard, and then importing the zpool. After this (rather scary, but I >>> had made a backup) sequence the disk attached without problems and >>> re-silvered. >> Hmm, you say you exported the pool can that be done while running on the >> pool(rpool)? >> >>> My guess is that the crash caused some subtle changes to the disk that >>> made ZFS think it was invalid, but also that it was still in use in the >>> zpool. >> I tried this without success. >> >> bash-3.00# prtvtoc /dev/rdsk/c0t0d0s0 | fmthard -s - /dev/rdsk/c0t1d0s0 >> fmthard: New volume table of contents now in place. >> bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 >> cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy >> >> /michael- Hide quoted text - >> >> - Show quoted text - > > Interesting! Per your second post, > > bash-3.00# zpool status rpool > pool: rpool > state: ONLINE > scrub: none requested > config: > > > NAME STATE READ WRITE CKSUM > rpool ONLINE 0 0 0 > c0t1d0s0 ONLINE 0 0 0 > > c0t1d0s0 is ONLINE, but in later posts, you are trying to attach it to > rpool. > > Seems that the box is not in production yet. Then you can just > jumpstart to reinstall it, specifying mirror in the profile. > > Victor The machine is running as NFS server but not yet as NIS server which is still on the old server. I have tried install 2-3 times, and the latest time c0t1 came up as working root drive the previous it was c0t0 that why. Both c0t0 and c0t1 where set as boot drives, but it does not work for some reason. There must be a way to force c0t0d0s0 to start as mirror of c0t1d0s0! /michael

On Apr 10, 12:27=A0am, Michael Laajanen <michael_laaja...@yahoo.com> wrote: > Hi, > > > > Victor wrote: > > On Apr 9, 4:36 am, Michael Laajanen <michael_laaja...@yahoo.com> > > wrote: > >> Hi, > > >> Stefaan A Eeckels wrote: > >>> On Wed, 7 Apr 2010 13:13:42 -0700 (PDT) > >>> cindy <cindy.swearin...@sun.com> wrote: > >>>> I did a google search on zpool attach, rpool, cannot attach, is busy > >>>> and found two errors conditions: > >>>> 1. the disks were not specified in the correct order, but this is no= t > >>>> your problem > >>>> 2. this problem was reported with an Areca controller and I didn't s= ee > >>>> a resolution reported. > >>> I had a similar problem (disk busy on attach) after a V440 crashed. T= he > >>> system has a zpool created from 6 disks on a StorEdge 3320, and after > >>> it came back up one of the disks was shown as failed. There was nothi= ng > >>> wrong with it, however, as it showed up OK under format and was > >>> readable with dd. > >>> As in this case, zpool attach (with and without -f) worked, zpool > >>> claiming that the disk was in use. I finally managed to solve the > >>> problem by exporting the zpool, re-labelling the "failed" disk with > >>> fmthard, and then importing the zpool. After this (rather scary, but = I > >>> had made a backup) sequence the disk attached without problems and > >>> re-silvered. > >> Hmm, you say you exported the pool can that be done while running on t= he > >> =A0 pool(rpool)? > > >>> My guess is that the crash caused some subtle changes to the disk tha= t > >>> made ZFS think it was invalid, but also that it was still in use in t= he > >>> zpool. > >> I tried this without success. > > >> bash-3.00# prtvtoc /dev/rdsk/c0t0d0s0 | fmthard -s - /dev/rdsk/c0t1d0s= 0 > >> fmthard: =A0New volume table of contents now in place. > >> bash-3.00# zpool attach -f rpool c0t0d0s0 c0t1d0s0 > >> cannot attach c0t1d0s0 to c0t0d0s0: c0t1d0s0 is busy > > >> /michael- Hide quoted text - > > >> - Show quoted text - > > > Interesting! Per your second post, > > > bash-3.00# zpool status rpool > > =A0 =A0pool: rpool > > =A0 state: ONLINE > > =A0 scrub: none requested > > config: > > > =A0 =A0 =A0 =A0 =A0NAME =A0 =A0 =A0 =A0STATE =A0 =A0 READ WRITE CKSUM > > =A0 =A0 =A0 =A0 =A0rpool =A0 =A0 =A0 ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0= =A0 0 > > =A0 =A0 =A0 =A0 =A0 =A0c0t1d0s0 =A0ONLINE =A0 =A0 =A0 0 =A0 =A0 0 =A0 = =A0 0 > > > c0t1d0s0 is ONLINE, but in later posts, you are trying to attach it to > > rpool. > > > Seems that the box is not in production yet. =A0Then you can just > > jumpstart to reinstall it, specifying mirror in the profile. > > > Victor > > The machine is running as NFS server but not yet as NIS server which is > still on the old server. > > I have tried install 2-3 times, and the latest time c0t1 came up as > working root drive the previous it was c0t0 that why. > > Both c0t0 and c0t1 where set as boot drives, but it does not work for > some reason. > > There must be a way to force c0t0d0s0 to start as mirror of c0t1d0s0! > > /michael Your can try SVM.

Similiar Articles:

problem with mirrored root - comp.unix.solaris
Hi, I have a problem with S10 1009 and seting up a mirrored root device. Initially I tried during install but one devcie failed after boot. N...

Resetting root password with zfs mirrored root - comp.unix.solaris ...
problem with mirrored root - comp.unix.solaris Resetting root password with zfs mirrored root - comp.unix.solaris ... Install Solaris 10 - without console and without root ...

Solaris 10 on x86: Problems booting off mirror disk - comp.unix ...
Mirror disk' root (hd1,0,a) Error 22: No such partition Press any key to ... for any advise on how to install Solaris. Solaris 10 on x86: Problems booting off mirror ...

Problem with prtvtoc/fmthard - comp.unix.solaris
problem with mirrored root - comp.unix.solaris Problem with prtvtoc/fmthard - comp.unix.solaris problem with mirrored root - comp.unix.solaris Hi, I have a problem with ...

Mirroring: Wait for disks to resynch? - comp.sys.sun.admin ...
problem with mirrored root - comp.unix.solaris Mirroring: Wait for disks to resynch? - comp.sys.sun.admin ... problem with mirrored root - comp.unix.solaris Mirroring ...

wipe free space from HD - comp.unix.programmer
problem with mirrored root - comp.unix.solaris Sometimes wiping out the label and recreating it helps. ... c0t0d0 <SEAGATE-ST373455LC-0003 cyl 65533 alt 2 hd 2 ... problem ...

Bug in SVM or just bad device path? - comp.unix.solaris
problem with mirrored root - comp.unix.solaris Bug in SVM or just bad device path? - comp.unix.solaris problem with mirrored root - comp.unix.solaris... problem with S10 ...

Solaris 10 installation fails with "no disk found". - comp.unix ...
problem with mirrored root - comp.unix.solaris Solaris 10 installation fails with "no disk found". - comp.unix ... problem with mirrored root - comp.unix.solaris Solaris ...

jumpstart and hostid/sysinit problem - comp.unix.solaris ...
ZFS Version Upgrade ? - comp.unix.solaris jumpstart and hostid/sysinit problem - comp.unix.solaris ... Jumpstart problem with mirrored root - comp.unix.solaris ...

Confused: Single User Mode and LVM Maint. mode - comp.sys.hp.hpux ...
problem with mirrored root - comp.unix.solaris Confused: Single User Mode and LVM Maint. mode - comp.sys.hp.hpux ... problem with mirrored root - comp.unix.solaris It ...

Trouble with ZFS mounts - comp.unix.solaris
problem with mirrored root - comp.unix.solaris Hi, I have a problem with S10 1009 and seting up a ... Tag Flags Sector Count Sector Mount ... some subtle changes to the ...

Solaris 10 10/09 zpool upgrade - comp.unix.solaris
problem with mirrored root - comp.unix.solaris > bash-3.00# zpool attach rpool c0t0d0s0 ... etc/release Solaris 10 10/09 ... ZFS Version Upgrade ? - comp.unix.solaris ...

Jumpstart - NFS server not responding still trying - eventually ...
problem with mirrored root - comp.unix.solaris... is running as NFS server but not yet as NIS server which is still ... but it does not work ... unix.solaris Solaris 10 ...

Solaris 10 b69 autofs problem - comp.unix.solaris
Resetting root password with zfs mirrored root - comp.unix.solaris ... problem with mirrored root - comp.unix.solaris... with S10 1009 and seting up a mirrored root ...

error: timeout waiting for ARP/RARP packet - comp.unix.solaris ...
3 Replies 416 Views (page loaded in 0.068 seconds) Similiar Articles: error: timeout waiting for ARP/RARP packet - comp.unix.solaris ... problem with mirrored root ...

problem with mirrored root - comp.unix.solaris | Computer Group
Hi, I have a problem with S10 1009 and seting up a mirrored root device. Initially I tried during install but one devcie failed after boot. N...

Jumpstart problem with mirrored root - Der Keiler UNIX: The source ...
Hi. I'm attempting to install Solaris 10 onto a mirrored device using Jumpstart but am experiencing a few problems. The server is a Sun Fire V125 and the version of ...

7/30/2012 1:37:19 PM