fmdump is not helping much: r...@host:~# fmdump -eV TIME CLASS fmdump: /var/fm/fmd/errlog is empty
comparing that screenshot to the output of cfgadm is interesting - looks like the controller(s): r...@host:~# cfgadm -v Ap_Id Receptacle Occupant Condition Information When Type Busy Phys_Id sata4/0::dsk/c4t0d0 connected configured ok Mod: ST3250310NS FRev: SN06 SN: 9SF06CZZ unavailable disk n /devices/p...@0,0/pci15d9,1...@5:0 sata4/1::dsk/c4t1d0 connected configured ok Mod: ST3250310NS FRev: SN06 SN: 9SF06BC8 unavailable disk n /devices/p...@0,0/pci15d9,1...@5:1 sata5/0 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci15d9,1...@5,1:0 sata5/1::dsk/c7t1d0 connected configured ok Mod: WDC WD10EACS-00D6B0 FRev: 01.01A01 SN: WD-WCAU40244615 unavailable disk n /devices/p...@0,0/pci15d9,1...@5,1:1 sata6/0 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci15d9,1...@5,2:0 sata6/1 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci15d9,1...@5,2:1 sata7/0 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@4:0 sata7/1 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@4:1 sata7/2::dsk/c5t2d0 connected configured ok Mod: WDC WD7500AYYS-01RCA0 FRev: 30.04G30 SN: WD-WCAPT0376631 unavailable disk n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@4:2 sata7/3::dsk/c5t3d0 connected configured ok Mod: WDC WD7500AYYS-01RCA0 FRev: 30.04G30 SN: WD-WCAPT0350798 unavailable disk n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@4:3 sata7/4::dsk/c5t4d0 connected configured ok Mod: WDC WD7500AYYS-01RCA0 FRev: 30.04G30 SN: WD-WCAPT0403574 unavailable disk n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@4:4 sata7/5::dsk/c5t5d0 connected configured ok Mod: WDC WD7500AYYS-01RCA0 FRev: 30.04G30 SN: WD-WCAPT0312592 unavailable disk n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@4:5 sata7/6::dsk/c5t6d0 connected configured ok Mod: WDC WD7500AYYS-01RCA0 FRev: 30.04G30 SN: WD-WCAPT0399779 unavailable disk n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@4:6 sata7/7::dsk/c5t7d0 connected configured ok Mod: WDC WD7500AYYS-01RCA0 FRev: 30.04G30 SN: WD-WCAPT0441660 unavailable disk n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@4:7 sata8/0::dsk/c6t0d0 connected configured ok Mod: WDC WD7500AYYS-01RCA0 FRev: 30.04G30 SN: WD-WCAPT1000344 unavailable disk n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@6:0 sata8/1 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@6:1 sata8/2 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@6:2 sata8/3 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@6:3 sata8/4 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@6:4 sata8/5 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@6:5 sata8/6 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@6:6 sata8/7 empty unconfigured ok unavailable sata-port n /devices/p...@0,0/pci10de,3...@a/pci1033,1...@0/pci11ab,1...@6:7 On Wed, Mar 11, 2009 at 2:40 PM, Blake <blake.ir...@gmail.com> wrote: > I'm attaching a screenshot of the console just before reboot. The > dump doesn't seem to be working, or savecore isn't working. > > On Wed, Mar 11, 2009 at 11:33 AM, Blake <blake.ir...@gmail.com> wrote: >> I'm working on testing this some more by doing a savecore -L right >> after I start the copy. >> >> BTW, I'm copying to a raidz2 of only 5 disks, not 16 (the chassis >> supports 16, but isn't fully populated). >> >> So far as I know, there is no spinup happening - these are not RAID >> controllers, just dumb SATA JBOD controllers, so I don't think they >> control drive spin in any particular way. Correct me if I'm wrong, of >> course. >> >> >> >> On Wed, Mar 11, 2009 at 11:23 AM, Marc Bevand <m.bev...@gmail.com> wrote: >>> The copy operation will make all the disks start seeking at the same time >>> and >>> will make your CPU activity jump to a significant percentage to compute the >>> ZFS checksum and RAIDZ parity. I think you could be overloading your PSU >>> because of the sudden increase in power consumption... >>> >>> However if you are *not* using SATA staggered spin-up, then the above theory >>> is unlikely because spinning up consumes much more power than when seeking. >>> So, in a sense, a successful boot proves your PSU is powerful enough. >>> >>> Trying reproducing the problem by copying data on a smaller number of disks. >>> You tried 2 and 16. Try 8. >>> >>> -marc >>> >>> _______________________________________________ >>> zfs-discuss mailing list >>> zfs-discuss@opensolaris.org >>> http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >>> >> > _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
