Hardware Supermicro X7DAE (AHCI BIOS) dual Intel Woodcrest processors, 6 x Western Digital Raptor SATA drives. I have installed b62 running 64 bit succesfully on a PATA drive. The BIOS is configured to access the SATA drives in native mode using hte AHCI Bios. I have 6 SATA II drives accessed via the Solaris AHCI driver. I have created a ZFS file system across all 6 drives. This works fine until I reboot. ZFS then shows the drives as unvail. This is repeatable. Is this a problem with the device names I have used to create the filesystem? Have I used an alias for the device names that is not valid at boot time? # zpool create -f mtf /dev/dsk/c1t0d0s6 /dev/dsk/c1t1d0s6 /dev/dsk/c1t2d0s6 /dev/dsk/c1t3d0s6 /dev/dsk/c1t4d0s6 /dev/dsk/c1t5d0s6 Dmesg reports the following: Apr 27 09:30:03 weston sata: [ID 663010 kern.notice] /pci at 0,0/pci15d9,8180 at 1f,2 : Apr 27 09:30:03 weston sata: [ID 761595 kern.notice] SATA disk device at port 2 Apr 27 09:30:03 weston sata: [ID 846691 kern.notice] model WDC WD740ADFD-00NL R1 Apr 27 09:30:03 weston sata: [ID 693010 kern.notice] firmware 20.07P20 Apr 27 09:30:03 weston sata: [ID 163988 kern.notice] serial number WD-WM ANS1324283 Apr 27 09:30:03 weston sata: [ID 594940 kern.notice] supported features: Apr 27 09:30:03 weston sata: [ID 981177 kern.notice] 48-bit LBA, DMA, Native Command Queueing, SMART, SMART self-test Apr 27 09:30:03 weston sata: [ID 674233 kern.notice] SATA1 compatible Apr 27 09:30:03 weston sata: [ID 349649 kern.notice] queue depth 32 Apr 27 09:30:03 weston sata: [ID 349649 kern.notice] capacity = 145226112 sec tors Apr 27 09:30:03 weston scsi: [ID 193665 kern.notice] sd3 at ahci0: target 2 lun 0 Apr 27 09:30:03 weston genunix: [ID 936769 kern.notice] sd3 is /pci at 0,0/pci15d9, 8180 at 1f,2/disk at 2,0 Apr 27 09:30:04 weston genunix: [ID 408114 kern.notice] /pci at 0,0/pci15d9,8180 at 1f ,2/disk at 2,0 (sd3) online ........ Apr 27 09:30:04 weston genunix: [ID 408114 kern.notice] /pci at 0,0/pci15d9,8180 at 1f ,2/disk at 5,0 (sd6) online Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: ncrs: 64-bit driver module not found Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: hpfc: 64-bit driver module not found Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: adp: 64-bit driver module not found Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: mscsi: 64-bit drive r module not found Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: i2o_scsi: 64-bit dr iver module not found Apr 27 09:30:04 weston e1000g: [ID 801593 kern.notice] NOTICE: pciex8086,1096 - e1000g[0] : Adapter 1000Mbps full duplex copper link is up. Apr 27 09:30:04 weston scsi: [ID 193665 kern.notice] sd0 at ata0: target 1 lun 0 Apr 27 09:30:04 weston genunix: [ID 936769 kern.notice] sd0 is /pci at 0,0/pci-ide@ 1f,1/ide at 0/sd at 1,0 Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: symhisl: 64-bit dri ver module not found Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: cadp: 64-bit driver module not found Apr 27 09:30:05 weston pseudo: [ID 129642 kern.notice] pseudo-device: pm0 Apr 27 09:30:05 weston genunix: [ID 936769 kern.notice] pm0 is /pseudo/pm at 0 Apr 27 09:30:05 weston pseudo: [ID 129642 kern.notice] pseudo-device: power0 Apr 27 09:30:05 weston genunix: [ID 936769 kern.notice] power0 is /pseudo/power@ 0 Apr 27 09:30:05 weston pseudo: [ID 129642 kern.notice] pseudo-device: devinfo0 Apr 27 09:30:05 weston genunix: [ID 936769 kern.notice] devinfo0 is /pseudo/devi nfo at 0 Apr 27 09:30:08 weston rootnex: [ID 349649 kern.notice] iscsi0 at root Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] iscsi0 is /iscsi Apr 27 09:30:08 weston rootnex: [ID 349649 kern.notice] xsvc0 at root: space 0 o ffset 0 Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] xsvc0 is /xsvc at 0,0 Apr 27 09:30:08 weston pseudo: [ID 129642 kern.notice] pseudo-device: pseudo1 Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] pseudo1 is /pseudo/zcons nex at 1 Apr 27 09:30:08 weston pcplusmp: [ID 803547 kern.info] pcplusmp: asy (asy) insta nce 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 1 Apr 27 09:30:08 weston isa: [ID 202937 kern.notice] ISA-device: asy0 Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] asy0 is /isa/asy at 1,3f8 Apr 27 09:30:08 weston pcplusmp: [ID 444295 kern.info] pcplusmp: asy (asy) insta nce #1 vector 0x3 ioapic 0x2 intin 0x3 is bound to cpu 1 Apr 27 09:30:08 weston isa: [ID 202937 kern.notice] ISA-device: asy1 Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] asy1 is /isa/asy at 1,2f8 Apr 27 09:30:08 weston pseudo: [ID 129642 kern.notice] pseudo-device: nvidia255 Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] nvidia255 is /pseudo/nvi dia at 255 Apr 27 09:30:08 weston npe: [ID 236367 kern.notice] PCI Express-device: pci8086, 244e at 1e, pci_pci0 Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] pci_pci0 is /pci at 0,0/pci 8086,244e at 1e Apr 27 09:30:08 weston genunix: [ID 773945 kern.notice] UltraDMA mode 2 selected Apr 27 09:30:08 weston last message repeated 1 time Apr 27 09:30:08 weston pcplusmp: [ID 444295 kern.info] pcplusmp: pciex8086,1096 (e1000g) instance #1 vector 0x31 ioapic 0xff intin 0xff is bound to cpu 0 Apr 27 09:30:08 weston genunix: [ID 773945 kern.notice] UltraDMA mode 2 selected Apr 27 09:30:08 weston last message repeated 1 time Apr 27 09:30:08 weston pcplusmp: [ID 803547 kern.info] pcplusmp: fdc (fdc) insta nce 0 vector 0x6 ioapic 0x2 intin 0x6 is bound to cpu 2 Apr 27 09:30:08 weston isa: [ID 202937 kern.notice] ISA-device: fdc0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: ramdisk102 4 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] ramdisk1024 is /pseudo/r amdisk at 1024 Apr 27 09:30:09 weston pcplusmp: [ID 803547 kern.info] pcplusmp: lp (ecpp) insta nce 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 3 Apr 27 09:30:09 weston isa: [ID 202937 kern.notice] ISA-device: ecpp0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] ecpp0 is /isa/lp at 1,378 Apr 27 09:30:09 weston mac: [ID 469746 kern.info] NOTICE: e1000g1 registered Apr 27 09:30:09 weston e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network C onnection, Driver Ver. 5.1.6 Apr 27 09:30:09 weston fdc: [ID 114370 kern.notice] fd0 at fdc0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] fd0 is /isa/fdc at 1,3f0/fd @0,0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: lockstat0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] lockstat0 is /pseudo/loc kstat at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: llc10 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] llc10 is /pseudo/llc1 at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: lofi0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] lofi0 is /pseudo/lofi at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: dtrace0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] dtrace0 is /pseudo/dtrac e at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: profile0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] profile0 is /pseudo/prof ile at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: systrace0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] systrace0 is /pseudo/sys trace at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: fbt0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] fbt0 is /pseudo/fbt at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: sdt0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] sdt0 is /pseudo/sdt at 0 Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: fasttrap0 Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] fasttrap0 is /pseudo/fas ttrap at 0 Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: fcp0 Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] fcp0 is /pseudo/fcp at 0 Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: fcsm0 Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] fcsm0 is /pseudo/fcsm at 0 Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: lx_systrac e0 Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] lx_systrace0 is /pseudo/ lx_systrace at 0 Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: fssnap0 Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] fssnap0 is /pseudo/fssna p at 0 Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: winlock0 Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] winlock0 is /pseudo/winl ock at 0 Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: rsm0 Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] rsm0 is /pseudo/rsm at 0 Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: pool0 Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] pool0 is /pseudo/pool at 0 Apr 27 09:30:10 weston ipf: [ID 774698 kern.info] IP Filter: v4.1.9, running. Apr 27 09:30:16 weston rpcbind: [ID 489175 daemon.error] Unable to join IPv6 mul ticast group for rpc broadcast FF02::202 Apr 27 09:30:27 weston fmd: [ID 441519 daemon.error] SUNW-MSG-ID: ZFS-8000-CS, T YPE: Fault, VER: 1, SEVERITY: Major Apr 27 09:30:27 weston EVENT-TIME: Fri Apr 27 09:30:27 BST 2007 Apr 27 09:30:27 weston PLATFORM: X7DA8, CSN: 0123456789, HOSTNAME: weston Apr 27 09:30:27 weston SOURCE: zfs-diagnosis, REV: 1.0 Apr 27 09:30:27 weston EVENT-ID: 998d62e7-8a2c-4aa0-8741-b0fa88a61ecb Apr 27 09:30:27 weston DESC: A ZFS pool failed to open. Refer to http://sun.com /msg/ZFS-8000-CS for more information. Apr 27 09:30:27 weston AUTO-RESPONSE: No automated response will occur. Apr 27 09:30:27 weston IMPACT: The pool data is unavailable Apr 27 09:30:27 weston REC-ACTION: Run ''zpool status -x'' and either attach the m issing device or Apr 27 09:30:27 weston restore from backup. This message posted from opensolaris.org
Peter, Can you send the ''zpool status -x'' output after your reboot. I suspect that the pool error is occurring early in the boot and later the devices are all available and the pool is brought into an online state. Take a look at: *6401126 ZFS DE should verify that diagnosis is still valid before solving cases <http://monaco.sfbay/detail.jsp?cr=6401126>* Thanks, George Peter Goodman wrote:> Hardware Supermicro X7DAE (AHCI BIOS) dual Intel Woodcrest processors, 6 x Western Digital Raptor SATA drives. > > I have installed b62 running 64 bit succesfully on a PATA drive. The BIOS is configured to access the SATA drives in native mode using hte AHCI Bios. > I have 6 SATA II drives accessed via the Solaris AHCI driver. I have created a ZFS file system across all 6 drives. This works fine until I reboot. ZFS then shows the drives as unvail. This is repeatable. > > Is this a problem with the device names I have used to create the filesystem? Have I used an alias for the device names that is not valid at boot time? > > > # zpool create -f mtf > /dev/dsk/c1t0d0s6 /dev/dsk/c1t1d0s6 /dev/dsk/c1t2d0s6 /dev/dsk/c1t3d0s6 /dev/dsk/c1t4d0s6 /dev/dsk/c1t5d0s6 > > Dmesg reports the following: > > Apr 27 09:30:03 weston sata: [ID 663010 kern.notice] /pci at 0,0/pci15d9,8180 at 1f,2 > : > Apr 27 09:30:03 weston sata: [ID 761595 kern.notice] SATA disk device at port > 2 > Apr 27 09:30:03 weston sata: [ID 846691 kern.notice] model WDC WD740ADFD-00NL > R1 > Apr 27 09:30:03 weston sata: [ID 693010 kern.notice] firmware 20.07P20 > Apr 27 09:30:03 weston sata: [ID 163988 kern.notice] serial number WD-WM > ANS1324283 > Apr 27 09:30:03 weston sata: [ID 594940 kern.notice] supported features: > Apr 27 09:30:03 weston sata: [ID 981177 kern.notice] 48-bit LBA, DMA, Native > Command Queueing, SMART, SMART self-test > Apr 27 09:30:03 weston sata: [ID 674233 kern.notice] SATA1 compatible > Apr 27 09:30:03 weston sata: [ID 349649 kern.notice] queue depth 32 > Apr 27 09:30:03 weston sata: [ID 349649 kern.notice] capacity = 145226112 sec > tors > Apr 27 09:30:03 weston scsi: [ID 193665 kern.notice] sd3 at ahci0: target 2 lun > 0 > Apr 27 09:30:03 weston genunix: [ID 936769 kern.notice] sd3 is /pci at 0,0/pci15d9, > 8180 at 1f,2/disk at 2,0 > Apr 27 09:30:04 weston genunix: [ID 408114 kern.notice] /pci at 0,0/pci15d9,8180 at 1f > ,2/disk at 2,0 (sd3) online > > ........ > > Apr 27 09:30:04 weston genunix: [ID 408114 kern.notice] /pci at 0,0/pci15d9,8180 at 1f > ,2/disk at 5,0 (sd6) online > Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: ncrs: 64-bit driver > module not found > Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: hpfc: 64-bit driver > module not found > Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: adp: 64-bit driver > module not found > Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: mscsi: 64-bit drive > r module not found > Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: i2o_scsi: 64-bit dr > iver module not found > Apr 27 09:30:04 weston e1000g: [ID 801593 kern.notice] NOTICE: pciex8086,1096 - > e1000g[0] : Adapter 1000Mbps full duplex copper link is up. > Apr 27 09:30:04 weston scsi: [ID 193665 kern.notice] sd0 at ata0: target 1 lun 0 > Apr 27 09:30:04 weston genunix: [ID 936769 kern.notice] sd0 is /pci at 0,0/pci-ide@ > 1f,1/ide at 0/sd at 1,0 > Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: symhisl: 64-bit dri > ver module not found > Apr 27 09:30:04 weston unix: [ID 469452 kern.notice] NOTICE: cadp: 64-bit driver > module not found > Apr 27 09:30:05 weston pseudo: [ID 129642 kern.notice] pseudo-device: pm0 > Apr 27 09:30:05 weston genunix: [ID 936769 kern.notice] pm0 is /pseudo/pm at 0 > Apr 27 09:30:05 weston pseudo: [ID 129642 kern.notice] pseudo-device: power0 > Apr 27 09:30:05 weston genunix: [ID 936769 kern.notice] power0 is /pseudo/power@ > 0 > Apr 27 09:30:05 weston pseudo: [ID 129642 kern.notice] pseudo-device: devinfo0 > Apr 27 09:30:05 weston genunix: [ID 936769 kern.notice] devinfo0 is /pseudo/devi > nfo at 0 > Apr 27 09:30:08 weston rootnex: [ID 349649 kern.notice] iscsi0 at root > Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] iscsi0 is /iscsi > Apr 27 09:30:08 weston rootnex: [ID 349649 kern.notice] xsvc0 at root: space 0 o > ffset 0 > Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] xsvc0 is /xsvc at 0,0 > Apr 27 09:30:08 weston pseudo: [ID 129642 kern.notice] pseudo-device: pseudo1 > Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] pseudo1 is /pseudo/zcons > nex at 1 > Apr 27 09:30:08 weston pcplusmp: [ID 803547 kern.info] pcplusmp: asy (asy) insta > nce 0 vector 0x4 ioapic 0x2 intin 0x4 is bound to cpu 1 > Apr 27 09:30:08 weston isa: [ID 202937 kern.notice] ISA-device: asy0 > Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] asy0 is /isa/asy at 1,3f8 > Apr 27 09:30:08 weston pcplusmp: [ID 444295 kern.info] pcplusmp: asy (asy) insta > nce #1 vector 0x3 ioapic 0x2 intin 0x3 is bound to cpu 1 > Apr 27 09:30:08 weston isa: [ID 202937 kern.notice] ISA-device: asy1 > Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] asy1 is /isa/asy at 1,2f8 > Apr 27 09:30:08 weston pseudo: [ID 129642 kern.notice] pseudo-device: nvidia255 > Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] nvidia255 is /pseudo/nvi > dia at 255 > Apr 27 09:30:08 weston npe: [ID 236367 kern.notice] PCI Express-device: pci8086, > 244e at 1e, pci_pci0 > Apr 27 09:30:08 weston genunix: [ID 936769 kern.notice] pci_pci0 is /pci at 0,0/pci > 8086,244e at 1e > Apr 27 09:30:08 weston genunix: [ID 773945 kern.notice] UltraDMA mode 2 > selected > Apr 27 09:30:08 weston last message repeated 1 time > Apr 27 09:30:08 weston pcplusmp: [ID 444295 kern.info] pcplusmp: pciex8086,1096 > (e1000g) instance #1 vector 0x31 ioapic 0xff intin 0xff is bound to cpu 0 > Apr 27 09:30:08 weston genunix: [ID 773945 kern.notice] UltraDMA mode 2 > selected > Apr 27 09:30:08 weston last message repeated 1 time > Apr 27 09:30:08 weston pcplusmp: [ID 803547 kern.info] pcplusmp: fdc (fdc) insta > nce 0 vector 0x6 ioapic 0x2 intin 0x6 is bound to cpu 2 > Apr 27 09:30:08 weston isa: [ID 202937 kern.notice] ISA-device: fdc0 > Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: ramdisk102 > 4 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] ramdisk1024 is /pseudo/r > amdisk at 1024 > Apr 27 09:30:09 weston pcplusmp: [ID 803547 kern.info] pcplusmp: lp (ecpp) insta > nce 0 vector 0x7 ioapic 0x2 intin 0x7 is bound to cpu 3 > Apr 27 09:30:09 weston isa: [ID 202937 kern.notice] ISA-device: ecpp0 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] ecpp0 is /isa/lp at 1,378 > Apr 27 09:30:09 weston mac: [ID 469746 kern.info] NOTICE: e1000g1 registered > Apr 27 09:30:09 weston e1000g: [ID 766679 kern.info] Intel(R) PRO/1000 Network C > onnection, Driver Ver. 5.1.6 > Apr 27 09:30:09 weston fdc: [ID 114370 kern.notice] fd0 at fdc0 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] fd0 is /isa/fdc at 1,3f0/fd > @0,0 > Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: lockstat0 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] lockstat0 is /pseudo/loc > kstat at 0 > Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: llc10 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] llc10 is /pseudo/llc1 at 0 > Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: lofi0 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] lofi0 is /pseudo/lofi at 0 > Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: dtrace0 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] dtrace0 is /pseudo/dtrac > e at 0 > Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: profile0 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] profile0 is /pseudo/prof > ile at 0 > Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: systrace0 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] systrace0 is /pseudo/sys > trace at 0 > Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: fbt0 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] fbt0 is /pseudo/fbt at 0 > Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: sdt0 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] sdt0 is /pseudo/sdt at 0 > Apr 27 09:30:09 weston pseudo: [ID 129642 kern.notice] pseudo-device: fasttrap0 > Apr 27 09:30:09 weston genunix: [ID 936769 kern.notice] fasttrap0 is /pseudo/fas > ttrap at 0 > Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: fcp0 > Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] fcp0 is /pseudo/fcp at 0 > Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: fcsm0 > Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] fcsm0 is /pseudo/fcsm at 0 > Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: lx_systrac > e0 > Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] lx_systrace0 is /pseudo/ > lx_systrace at 0 > Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: fssnap0 > Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] fssnap0 is /pseudo/fssna > p at 0 > Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: winlock0 > Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] winlock0 is /pseudo/winl > ock at 0 > Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: rsm0 > Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] rsm0 is /pseudo/rsm at 0 > Apr 27 09:30:10 weston pseudo: [ID 129642 kern.notice] pseudo-device: pool0 > Apr 27 09:30:10 weston genunix: [ID 936769 kern.notice] pool0 is /pseudo/pool at 0 > Apr 27 09:30:10 weston ipf: [ID 774698 kern.info] IP Filter: v4.1.9, running. > Apr 27 09:30:16 weston rpcbind: [ID 489175 daemon.error] Unable to join IPv6 mul > ticast group for rpc broadcast FF02::202 > Apr 27 09:30:27 weston fmd: [ID 441519 daemon.error] SUNW-MSG-ID: ZFS-8000-CS, T > YPE: Fault, VER: 1, SEVERITY: Major > Apr 27 09:30:27 weston EVENT-TIME: Fri Apr 27 09:30:27 BST 2007 > Apr 27 09:30:27 weston PLATFORM: X7DA8, CSN: 0123456789, HOSTNAME: weston > Apr 27 09:30:27 weston SOURCE: zfs-diagnosis, REV: 1.0 > Apr 27 09:30:27 weston EVENT-ID: 998d62e7-8a2c-4aa0-8741-b0fa88a61ecb > Apr 27 09:30:27 weston DESC: A ZFS pool failed to open. Refer to http://sun.com > /msg/ZFS-8000-CS for more information. > Apr 27 09:30:27 weston AUTO-RESPONSE: No automated response will occur. > Apr 27 09:30:27 weston IMPACT: The pool data is unavailable > Apr 27 09:30:27 weston REC-ACTION: Run ''zpool status -x'' and either attach the m > issing device or > Apr 27 09:30:27 weston restore from backup. > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20070430/e80d7ac7/attachment.html>
# zpool status -x
pool: mtf
state: UNAVAIL
status: One or more devices could not be opened. There are insufficient
replicas for the pool to continue functioning.
action: Attach the missing device and online it using ''zpool
online''.
see: http://www.sun.com/msg/ZFS-8000-D3
scrub: none requested
config:
NAME STATE READ WRITE CKSUM
mtf UNAVAIL 0 0 0 insufficient replicas
c1t0d0s6 UNAVAIL 0 0 0 cannot open
c1t1d0s6 UNAVAIL 0 0 0 cannot open
c1t2d0s6 UNAVAIL 0 0 0 cannot open
c1t3d0s6 UNAVAIL 0 0 0 cannot open
c1t4d0s6 UNAVAIL 0 0 0 cannot open
c1t5d0s6 UNAVAIL 0 0 0 cannot open
#
This message posted from opensolaris.org
Peter Goodman wrote:> # zpool status -x > pool: mtf > state: UNAVAIL > status: One or more devices could not be opened. There are insufficient > replicas for the pool to continue functioning. > action: Attach the missing device and online it using ''zpool online''. > see: http://www.sun.com/msg/ZFS-8000-D3 > scrub: none requested > config: > > NAME STATE READ WRITE CKSUM > mtf UNAVAIL 0 0 0 insufficient replicas > c1t0d0s6 UNAVAIL 0 0 0 cannot open > c1t1d0s6 UNAVAIL 0 0 0 cannot open > c1t2d0s6 UNAVAIL 0 0 0 cannot open > c1t3d0s6 UNAVAIL 0 0 0 cannot open > c1t4d0s6 UNAVAIL 0 0 0 cannot open > c1t5d0s6 UNAVAIL 0 0 0 cannot open > # > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >Are you able to see the devices with format? I noticed that you have specified slice 6 for these devices does that mean that you have other filesystems on other slices?
Changed to: zpool create -f mtf c1t0d0 c1t1d0 c1t2d0 c1t3d0 c1t4d0 c1t5d0 works fine and the throughput is still the very satisfactory sustained sequential 360MB/s write and 385MB/s read Thanks This message posted from opensolaris.org