dwoods99 Posted February 4, 2013 Share Posted February 4, 2013 As discussed in this thread I started, I am replacing a Supermicro AOC-SAT2-MV8 PCI-X http://lime-technology.com/forum/index.php?topic=25545.msg222274 with the recommended PCI-e x4 Supermicro AOC-SASLP-MV8 controller on an Intel Desktop Mainboard DQ965GF with has a PCI-e x16 slot. I bought two x 3ware CBL-SFF8087OCF-05M 1 Unit of .5M Multi-lane Internal (SFF-8087) Serial ATA Breakout cables, which only go on one way. I connected the 8 plugs into sata backplanes (8 of 10), leaving 4 more drives on the motherboard sata connection (including parity). When I boot up, unRaid is unable to see 7 out 8 drives on sata backplane, so 5 show up in the list while the others say Missing Disk. All 4 on motherboard are found plus just 1 on new controller. If I login I can see the drives with /dev/sd[a-m] appearing fine. It's as if the controller is only seen as 1 port. I know the connections are tight, power is attached. It's as if the PCI-e x16 can't handle the card, is that the case? I am at a loss for what to do next, short of trying on a different motherboard but I still don't have the knowledge to understand if the PCI-e x16 slot should work or not. EDIT1: re-attached proper syslog.txt file syslog.zip Link to comment
dwoods99 Posted February 4, 2013 Author Share Posted February 4, 2013 Can't see any setting in the BIOS screens for INTerrupts, so I can't turn off INT13. Best I could find was turn off Auto mode for video to use internal and not external PCI-E. After reboot I now see 6 drives, 2 on controller which I'm guessing is 1 for each cable group. Next might be to try USB bootup to set the card's bios to .15 as instructed at http://lime-technology.com/forum/index.php?topic=12404.msg117904#msg117904 even though unRaid does boot. Link to comment
dwoods99 Posted February 4, 2013 Author Share Posted February 4, 2013 One thing I forgot to mention was that I also swapped out the PSU 700 Watt for a quieter 450W CoolerMaster. I have no added video so even with 12 drives it should be plenty of room. for power needs. I decided to put back the 700W in order to be certain it wasn't the cause. Now when I boot, unRaid menu does not show up for booting. Uggh! So now it does seem I will need to try the .15 firmware USB boot update. Link to comment
dwoods99 Posted February 4, 2013 Author Share Posted February 4, 2013 After flashing to .15 the system was able to reboot into unRaid. However still only 5 drives known to unRaid. What I don't understand is that the flash update has mdu mvflash -o bios -u 6480b15n.bin mdu restore_cfg smc_n.txt and 6480.txt files shows [ADAPTER CONFIG] #adapter config [bEGIN] [sERIAL_NUMBER]=VA2400WWXX0000000000 [sUBVENDOR_ID]=15D9 [sUBDEVICE_ID]=0500 [sILENT_MODE]=DISABLE [iNT13]=ENABLE [ERROR_STOP]=DISABLE [RAID FEATURE]=DISABLE [RAID5]=DISABLE [sPINUP GROUP]=8 [sPINUP TIME]=0 [DELAY TIME(s)]=5 [END] where the INT13 is enabled but according to the other forum thread, we want it to be DISABLE'd -- so which is it? Same thing for file SMC_N.TXT, the INT13 is ENABLE'd. What now? Link to comment
itimpi Posted February 4, 2013 Share Posted February 4, 2013 The INT 13 setting only affects whether connected drives show up in a boot menu - it is not critical to whether the board functions correctly. Link to comment
itimpi Posted February 4, 2013 Share Posted February 4, 2013 One thing that occurs to me - you suggested earlier that he drives ARE showing up at the Linux level as the relevant /dev/sd? Devices. Is this actually the case? If so the problem might simply be the identity as seen by unRAID has changed. Link to comment
PeterB Posted February 4, 2013 Share Posted February 4, 2013 From what you say, it does seem that all the drives are seen by the O/S, so I guess that you're saying that unRAID doesn't allow you to access them. As Itimpi says, INT13 only controls whether drives on the card can be booted from. Can you be more precise about the CoolerMaster PSU - in particular, is it single 12V rail, or multiple. What is the current rating of the 12V rail supplying the disk drives? I suspect that it is multirail, and doesn't have sufficient current to spin up all 13 drives simultaneaously. Concentrate on getting the system working with 700 watt supply (is that single rail?). Link to comment
dwoods99 Posted February 4, 2013 Author Share Posted February 4, 2013 One thing that occurs to me - you suggested earlier that he drives ARE showing up at the Linux level as the relevant /dev/sd? Devices. Is this actually the case? If so the problem might simply be the identity as seen by unRAID has changed. If you mean identity is which drive it expects to find for Device # NNN, then no. It has what should be there but is missing and there's nothing in the drop-down list to set the device -- nothing in list. Link to comment
dwoods99 Posted February 4, 2013 Author Share Posted February 4, 2013 Can you be more precise about the CoolerMaster PSU - in particular, is it single 12V rail, or multiple. What is the current rating of the 12V rail supplying the disk drives? I suspect that it is multirail, and doesn't have sufficient current to spin up all 13 drives simultaneaously. Concentrate on getting the system working with 700 watt supply (is that single rail?). The 700W is an OCZ from 3-4 years ago, and worked fine with previous controller. Bootup BIOS sees all the drives, so INT13 must be enabled. The 450W is this one and it says "Single +12V Rail", which I don't understand other than I plugged in the motherboard power and 4-pin square. Not sure what multirail implies. I was really hoping this would be a simple controller swap-out and get things back up and running. Link to comment
itimpi Posted February 4, 2013 Share Posted February 4, 2013 At the moment I cannot quite see what might be wrong! It might be useful if you posted the output of ls -l /dev/disk/by-id so we can see exactly what Linux is seeing. Link to comment
dwoods99 Posted February 5, 2013 Author Share Posted February 5, 2013 I switched to another (newer) computer and it's working up to a point. I included 2 images and syslog (upload restriction required putting in zip files) Linux 3.4.11-unRAID. root@Moat:~# ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-ST3000DM001-1CH166_Z1F1QHVN -> ../../sdb lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-ST3000DM001-1CH166_Z1F1QHVN-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA1137613 -> ../../hda lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA1221569 -> ../../sdg lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA1221569-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA1239546 -> ../../sde lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA1239546-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0853254 -> ../../sdf lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA0853254-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA3805888 -> ../../sdj lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA3805888-part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA3806129 -> ../../sdd lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA3806129-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD20EARS-00S8B1_WD-WCAVY5637510 -> ../../sdl lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-WDC_WD20EARS-00S8B1_WD-WCAVY5637510-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD20EARX-00PASB0_WD-WCAZAD279325 -> ../../sdh lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-WDC_WD20EARX-00PASB0_WD-WCAZAD279325-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD20EARX-00PASB0_WD-WCAZAD907189 -> ../../sdi lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-WDC_WD20EARX-00PASB0_WD-WCAZAD907189-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD20EARX-00PASB0_WD-WMAZA9708345 -> ../../sdk lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-WDC_WD20EARX-00PASB0_WD-WMAZA9708345-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 ata-WDC_WD30EZRX-00DC0B0_WD-WCC1T0036740 -> ../../sdc lrwxrwxrwx 1 root root 10 2013-02-05 05:40 ata-WDC_WD30EZRX-00DC0B0_WD-WCC1T0036740-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_ST3000DM001-1CH_Z1F1QHVN -> ../../sdb lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_ST3000DM001-1CH_Z1F1QHVN-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WCAVY5637510 -> ../../sdl lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WCAVY5637510-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA1221569 -> ../../sdg lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA1221569-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA1239546 -> ../../sde lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA1239546-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0853254 -> ../../sdf lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA0853254-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA3805888 -> ../../sdj lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA3805888-part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA3806129 -> ../../sdd lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA3806129-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_WDC_WD20EARX-00_WD-WCAZAD279325 -> ../../sdh lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_WDC_WD20EARX-00_WD-WCAZAD279325-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_WDC_WD20EARX-00_WD-WCAZAD907189 -> ../../sdi lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_WDC_WD20EARX-00_WD-WCAZAD907189-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_WDC_WD20EARX-00_WD-WMAZA9708345 -> ../../sdk lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_WDC_WD20EARX-00_WD-WMAZA9708345-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 scsi-SATA_WDC_WD30EZRX-00_WD-WCC1T0036740 -> ../../sdc lrwxrwxrwx 1 root root 10 2013-02-05 05:40 scsi-SATA_WDC_WD30EZRX-00_WD-WCC1T0036740-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 usb-SanDisk_Cruzer_4C532009511026101360-0:0 -> ../../sda lrwxrwxrwx 1 root root 10 2013-02-05 05:40 usb-SanDisk_Cruzer_4C532009511026101360-0:0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x5000c5004f1029d7 -> ../../sdb lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x5000c5004f1029d7-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x50014ee057c2a44b -> ../../sdf lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x50014ee057c2a44b-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x50014ee057f0eed0 -> ../../sdj lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x50014ee057f0eed0-part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x50014ee0ad469f8d -> ../../sdd lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x50014ee0ad469f8d-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x50014ee20680b538 -> ../../sdh lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x50014ee20680b538-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x50014ee207ccea16 -> ../../sdc lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x50014ee207ccea16-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x50014ee2afb355df -> ../../sdl lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x50014ee2afb355df-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x50014ee2afb3c736 -> ../../sde lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x50014ee2afb3c736-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x50014ee2afb3c7b4 -> ../../sdg lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x50014ee2afb3c7b4-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x50014ee2b1a9e79b -> ../../sdk lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x50014ee2b1a9e79b-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 2013-02-05 05:40 wwn-0x50014ee2b1a9ec3d -> ../../sdi lrwxrwxrwx 1 root root 10 2013-02-05 05:40 wwn-0x50014ee2b1a9ec3d-part1 -> ../../sdi1 root@Moat:~# All HDDs are recognized on web page drop-down list for devices but I need to re-enter the devices since initconfig was necessary. I get as far as device #9 of 11 and then the web slows right down trying to refresh the page. I either lose some devices (Unassigned and no temp shown) or zero size value in drop down list. When (if) I get to #10 it starts to fail or network access practically dies. No matter how many times I initconfig and start over, or reboot, problem happens at device #9 (2TB WD) and #10 (3TB WD). Is there any way to edit/create a file on the flash key to pre-enter the correct values so that going to devices page it will pre-populate with correct values and then I can Start array with good parity? syslog2.zip 05-02-2013_5-35-42_AM.zip 05-02-2013_1-10-18_AM.zip Link to comment
itimpi Posted February 5, 2013 Share Posted February 5, 2013 Just for interest, was that ls command run on the 'old' or the 'new' computer? Regardless, it shows all the drives being shown at the Linux level, so if they are not being picked up correctly at the unRAID level then the problem is something other than the card not working. Link to comment
dwoods99 Posted February 5, 2013 Author Share Posted February 5, 2013 On the new computer. See my modified post with attachments. Link to comment
RobJ Posted February 5, 2013 Share Posted February 5, 2013 Both of those pics show issues, but when I checked the syslog, it clearly shows that the SAS card had crashed, and crashed several more times after that. When it failed, it took down a number of drives with it, and they were quickly disabled by the kernel, which removes them from service until the next boot. A few suggestions: I see you are still running RC8a. While I don't see any fixes listed that obviously would fix your issues, I would still upgrade to RC11, as it does include some fixes and a newer kernel with newer drivers. The driver in question though is mvsas, and it is still the same 0.8.16. Make sure you have the latest BIOS for that SAS card, and the correct BIOS if it has different types of BIOS (I don't have any SAS cards, so can't advise you myself). When you have time, on booting go into the BIOS settings for the motherboard and change the SATA support modes to a native SATA mode, preferably AHCI, anything but the IDE emulation mode that one of the onboard SATA controllers is in. That will allow Disk 6 (WD20EARS with serial ending in 613) full SATA support, and it should operate a little faster (it is currently limited to UDMA/100. Probably not related, but there are some BIOS errors, so you might look into a newer BIOS for your Gigabyte motherboard. DMI says it is currently BIOS F2 06/08/2011. Link to comment
dwoods99 Posted February 6, 2013 Author Share Posted February 6, 2013 Good suggestions, looking into it. Link to comment
dwoods99 Posted February 6, 2013 Author Share Posted February 6, 2013 I updated to 5.0r11 and booted into 4GB limited. Once I got to the devices screen, the slowdown started again on entering device #9 and crashed on device #10 part 1 of 2 Feb 5 17:52:23 Moat emhttp: shcmd (56): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Feb 5 17:52:23 Moat kernel: md: unRAID driver removed Feb 5 17:52:23 Moat emhttp: shcmd (57): udevadm settle Feb 5 17:52:23 Moat kernel: md: unRAID driver 2.1.5 installed Feb 5 17:52:23 Moat kernel: read_file: error 2 opening /boot/config/super.dat Feb 5 17:52:23 Moat kernel: md: could not read superblock from /boot/config/super.dat Feb 5 17:52:23 Moat kernel: md: initializing superblock ... Feb 5 17:52:31 Moat kernel: mdcmd (1): import 0 8,0 2930266532 ST3000DM001-1CH166_Z1F1QHVN Feb 5 17:52:31 Moat kernel: md: import disk0: [8,0] (sda) ST3000DM001-1CH166_Z1F1QHVN size: 2930266532 Feb 5 17:52:31 Moat kernel: md: disk0 new disk Feb 5 17:52:31 Moat kernel: mdcmd (2): import 1 8,112 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZAD279325 Feb 5 17:52:31 Moat kernel: md: import disk1: [8,112] (sdh) WDC_WD20EARX-00PASB0_WD-WCAZAD279325 size: 1953514552 Feb 5 17:52:31 Moat kernel: md: disk1 new disk Feb 5 17:52:31 Moat kernel: mdcmd (3): import 2 8,96 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA1221569 Feb 5 17:52:31 Moat kernel: md: import disk2: [8,96] (sdg) WDC_WD20EARS-00MVWB0_WD-WCAZA1221569 size: 1953514552 Feb 5 17:52:31 Moat kernel: md: disk2 new disk Feb 5 17:52:31 Moat kernel: mdcmd (4): import 3 8,80 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA0853254 Feb 5 17:52:31 Moat kernel: md: import disk3: [8,80] (sdf) WDC_WD20EARS-00MVWB0_WD-WMAZA0853254 size: 1953514552 Feb 5 17:52:31 Moat kernel: md: disk3 new disk Feb 5 17:52:31 Moat kernel: mdcmd (5): import 4 8,64 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA1239546 Feb 5 17:52:31 Moat kernel: md: import disk4: [8,64] (sde) WDC_WD20EARS-00MVWB0_WD-WCAZA1239546 size: 1953514552 Feb 5 17:52:31 Moat kernel: md: disk4 new disk Feb 5 17:52:31 Moat kernel: mdcmd (6): import 5 8,176 1953514552 WDC_WD20EARS-00S8B1_WD-WCAVY5637510 Feb 5 17:52:31 Moat kernel: md: import disk5: [8,176] (sdl) WDC_WD20EARS-00S8B1_WD-WCAVY5637510 size: 1953514552 Feb 5 17:52:31 Moat kernel: md: disk5 new disk Feb 5 17:52:31 Moat kernel: mdcmd (7): import 6 3,0 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA1137613 Feb 5 17:52:31 Moat kernel: md: import disk6: [3,0] (hda) WDC_WD20EARS-00MVWB0_WD-WCAZA1137613 size: 1953514552 Feb 5 17:52:31 Moat kernel: md: disk6 new disk Feb 5 17:52:31 Moat kernel: mdcmd (: import 7 8,32 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3806129 Feb 5 17:52:31 Moat kernel: md: import disk7: [8,32] (sdc) WDC_WD20EARS-00MVWB0_WD-WMAZA3806129 size: 1953514552 Feb 5 17:52:31 Moat kernel: md: disk7 new disk Feb 5 17:52:31 Moat kernel: mdcmd (9): import 8 8,160 1953514552 WDC_WD20EARX-00PASB0_WD-WMAZA9708345 Feb 5 17:52:31 Moat kernel: md: import disk8: [8,160] (sdk) WDC_WD20EARX-00PASB0_WD-WMAZA9708345 size: 1953514552 Feb 5 17:52:31 Moat kernel: md: disk8 new disk Feb 5 17:52:31 Moat kernel: mdcmd (10): import 9 8,144 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3805888 Feb 5 17:52:31 Moat emhttp: shcmd (62): /usr/local/sbin/emhttp_event driver_loaded Feb 5 17:52:31 Moat kernel: md: import disk9: [8,144] (sdj) WDC_WD20EARS-00MVWB0_WD-WMAZA3805888 size: 1953514552 Feb 5 17:52:31 Moat kernel: md: disk9 new disk Feb 5 17:52:31 Moat kernel: mdcmd (11): import 10 0,0 ... Feb 5 17:52:31 Moat kernel: mdcmd (24): import 23 0,0 Feb 5 17:52:31 Moat emhttp_event: driver_loaded Feb 5 17:52:51 Moat kernel: sd 0:0:1:0: [sdf] command f758d0c0 timed out Feb 5 17:52:51 Moat kernel: sd 0:0:7:0: [sdl] command f7467b40 timed out Feb 5 17:52:51 Moat kernel: sd 0:0:0:0: [sde] command f7467a80 timed out Feb 5 17:52:51 Moat kernel: sd 0:0:6:0: [sdk] command f758d780 timed out Feb 5 17:52:51 Moat kernel: sd 0:0:3:0: [sdh] command f3e61000 timed out Feb 5 17:52:51 Moat kernel: sd 0:0:2:0: [sdg] command f74670c0 timed out Feb 5 17:52:51 Moat kernel: sas: Enter sas_scsi_recover_host busy: 6 failed: 6 Feb 5 17:52:51 Moat kernel: sas: trying to find task 0xf741c640 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: aborting task 0xf741c640 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: task 0xf741c640 is aborted Feb 5 17:52:51 Moat kernel: sas: sas_eh_handle_sas_errors: task 0xf741c640 is aborted Feb 5 17:52:51 Moat kernel: sas: trying to find task 0xf7508280 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: aborting task 0xf7508280 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: task 0xf7508280 is aborted Feb 5 17:52:51 Moat kernel: sas: sas_eh_handle_sas_errors: task 0xf7508280 is aborted Feb 5 17:52:51 Moat kernel: sas: trying to find task 0xf7508640 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: aborting task 0xf7508640 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: task 0xf7508640 is aborted Feb 5 17:52:51 Moat kernel: sas: sas_eh_handle_sas_errors: task 0xf7508640 is aborted Feb 5 17:52:51 Moat kernel: sas: trying to find task 0xf7508500 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: aborting task 0xf7508500 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: task 0xf7508500 is aborted Feb 5 17:52:51 Moat kernel: sas: sas_eh_handle_sas_errors: task 0xf7508500 is aborted Feb 5 17:52:51 Moat kernel: sas: trying to find task 0xf741c780 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: aborting task 0xf741c780 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: task 0xf741c780 is aborted Feb 5 17:52:51 Moat kernel: sas: sas_eh_handle_sas_errors: task 0xf741c780 is aborted Feb 5 17:52:51 Moat kernel: sas: trying to find task 0xf75083c0 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: aborting task 0xf75083c0 Feb 5 17:52:51 Moat kernel: sas: sas_scsi_find_task: task 0xf75083c0 is aborted Feb 5 17:52:51 Moat kernel: sas: sas_eh_handle_sas_errors: task 0xf75083c0 is aborted Feb 5 17:52:51 Moat kernel: sas: ata6: end_device-0:1: cmd error handler Feb 5 17:52:51 Moat kernel: sas: ata12: end_device-0:7: cmd error handler Feb 5 17:52:51 Moat kernel: sas: ata5: end_device-0:0: cmd error handler Feb 5 17:52:51 Moat kernel: sas: ata11: end_device-0:6: cmd error handler Feb 5 17:52:51 Moat kernel: sas: ata8: end_device-0:3: cmd error handler Feb 5 17:52:51 Moat kernel: sas: ata7: end_device-0:2: cmd error handler Feb 5 17:52:51 Moat kernel: sas: ata5: end_device-0:0: dev error handler Feb 5 17:52:51 Moat kernel: sas: ata6: end_device-0:1: dev error handler Feb 5 17:52:51 Moat kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 5 17:52:51 Moat kernel: ata5.00: failed command: SMART Feb 5 17:52:51 Moat kernel: ata5.00: cmd b0/d8:00:01:4f:c2/00:00:00:00:00/00 tag 0 Feb 5 17:52:51 Moat kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 5 17:52:51 Moat kernel: ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 5 17:52:51 Moat kernel: ata6.00: failed command: SMART Feb 5 17:52:51 Moat kernel: ata6.00: cmd b0/d8:00:01:4f:c2/00:00:00:00:00/00 tag 0 Feb 5 17:52:51 Moat kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 5 17:52:51 Moat kernel: ata6.00: status: { DRDY } Feb 5 17:52:51 Moat kernel: ata5.00: status: { DRDY } Feb 5 17:52:51 Moat kernel: ata6: hard resetting link Feb 5 17:52:51 Moat kernel: ata5: hard resetting link Feb 5 17:52:55 Moat kernel: sas: ata7: end_device-0:2: dev error handler Feb 5 17:52:55 Moat kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 5 17:52:55 Moat kernel: ata7.00: failed command: SMART Feb 5 17:52:55 Moat kernel: ata7.00: cmd b0/d8:00:01:4f:c2/00:00:00:00:00/00 tag 0 Feb 5 17:52:55 Moat kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 5 17:52:55 Moat kernel: ata7.00: status: { DRDY } Feb 5 17:52:55 Moat kernel: ata7: hard resetting link Feb 5 17:52:55 Moat kernel: sas: ata8: end_device-0:3: dev error handler Feb 5 17:52:55 Moat kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 5 17:52:55 Moat kernel: ata8.00: failed command: SMART Feb 5 17:52:55 Moat kernel: ata8.00: cmd b0/d8:00:01:4f:c2/00:00:00:00:00/00 tag 0 Feb 5 17:52:55 Moat kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 5 17:52:55 Moat kernel: ata8.00: status: { DRDY } Feb 5 17:52:55 Moat kernel: ata8: hard resetting link Feb 5 17:52:55 Moat kernel: sas: ata9: end_device-0:4: dev error handler Feb 5 17:52:55 Moat kernel: sas: ata10: end_device-0:5: dev error handler Feb 5 17:52:55 Moat kernel: sas: ata11: end_device-0:6: dev error handler Feb 5 17:52:55 Moat kernel: ata11.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 5 17:52:55 Moat kernel: ata11.00: failed command: SMART Feb 5 17:52:55 Moat kernel: ata11.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in Feb 5 17:52:55 Moat kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 5 17:52:55 Moat kernel: ata11.00: status: { DRDY } Feb 5 17:52:55 Moat kernel: ata11: hard resetting link Feb 5 17:52:55 Moat kernel: sas: ata12: end_device-0:7: dev error handler Feb 5 17:52:55 Moat kernel: ata12.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Feb 5 17:52:55 Moat kernel: ata12.00: failed command: SMART Feb 5 17:52:55 Moat kernel: ata12.00: cmd b0/d8:00:01:4f:c2/00:00:00:00:00/00 tag 0 Feb 5 17:52:55 Moat kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Feb 5 17:52:55 Moat kernel: ata12.00: status: { DRDY } Feb 5 17:52:55 Moat kernel: ata12: hard resetting link Feb 5 17:52:55 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[0]:rc= 0 Feb 5 17:52:55 Moat kernel: sas: sas_ata_task_done: SAS error 8a Feb 5 17:52:55 Moat kernel: sas: sas_ata_task_done: SAS error 8a Feb 5 17:52:55 Moat kernel: ata5.00: both IDENTIFYs aborted, assuming NODEV Feb 5 17:52:55 Moat kernel: ata5.00: revalidation failed (errno=-2) Feb 5 17:52:55 Moat kernel: mvsas 0000:03:00.0: Phy0 : No sig fis Feb 5 17:52:56 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[1]:rc= 0 Feb 5 17:52:57 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[3]:rc= 0 Feb 5 17:52:57 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[6]:rc= 0 Feb 5 17:52:57 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[7]:rc= 0 Feb 5 17:52:57 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[2]:rc= 0 Link to comment
dwoods99 Posted February 6, 2013 Author Share Posted February 6, 2013 part 2 of 2 Feb 5 17:52:59 Moat kernel: sas: sas_form_port: phy0 belongs to port0 already(1)! Feb 5 17:53:00 Moat kernel: ata5: hard resetting link Feb 5 17:53:00 Moat kernel: ata5.00: configured for UDMA/133 Feb 5 17:53:00 Moat kernel: ata5: EH complete Feb 5 17:53:02 Moat kernel: ata6.00: qc timeout (cmd 0x27) Feb 5 17:53:02 Moat kernel: ata6.00: failed to read native max address (err_mask=0x4) Feb 5 17:53:02 Moat kernel: ata6.00: HPA support seems broken, skipping HPA handling Feb 5 17:53:02 Moat kernel: ata6.00: revalidation failed (errno=-5) Feb 5 17:53:02 Moat kernel: ata6: hard resetting link Feb 5 17:53:03 Moat kernel: ata8.00: qc timeout (cmd 0x27) Feb 5 17:53:03 Moat kernel: ata12.00: qc timeout (cmd 0xec) Feb 5 17:53:03 Moat kernel: ata8.00: failed to read native max address (err_mask=0x4) Feb 5 17:53:03 Moat kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x4) Feb 5 17:53:03 Moat kernel: ata12.00: revalidation failed (errno=-5) Feb 5 17:53:03 Moat kernel: ata8.00: HPA support seems broken, skipping HPA handling Feb 5 17:53:03 Moat kernel: ata12: hard resetting link Feb 5 17:53:03 Moat kernel: ata8.00: revalidation failed (errno=-5) Feb 5 17:53:03 Moat kernel: ata8: hard resetting link Feb 5 17:53:04 Moat kernel: ata11.00: qc timeout (cmd 0x27) Feb 5 17:53:04 Moat kernel: ata11.00: failed to read native max address (err_mask=0x4) Feb 5 17:53:04 Moat kernel: ata11.00: HPA support seems broken, skipping HPA handling Feb 5 17:53:04 Moat kernel: ata11.00: revalidation failed (errno=-5) Feb 5 17:53:04 Moat kernel: ata11: hard resetting link Feb 5 17:53:06 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[1]:rc= 0 Feb 5 17:53:06 Moat kernel: mvsas 0000:03:00.0: Phy1 : No sig fis Feb 5 17:53:06 Moat kernel: ata7.00: qc timeout (cmd 0x27) Feb 5 17:53:06 Moat kernel: ata7.00: failed to read native max address (err_mask=0x4) Feb 5 17:53:06 Moat kernel: ata7.00: HPA support seems broken, skipping HPA handling Feb 5 17:53:06 Moat kernel: ata7.00: revalidation failed (errno=-5) Feb 5 17:53:06 Moat kernel: ata7: hard resetting link Feb 5 17:53:07 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[7]:rc= 0 Feb 5 17:53:07 Moat kernel: sas: sas_ata_task_done: SAS error 8a Feb 5 17:53:07 Moat kernel: sas: sas_ata_task_done: SAS error 8a Feb 5 17:53:07 Moat kernel: ata12.00: both IDENTIFYs aborted, assuming NODEV Feb 5 17:53:07 Moat kernel: ata12.00: revalidation failed (errno=-2) Feb 5 17:53:07 Moat kernel: mvsas 0000:03:00.0: Phy7 : No sig fis Feb 5 17:53:08 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[6]:rc= 0 Feb 5 17:53:08 Moat kernel: sas: sas_ata_task_done: SAS error 8a Feb 5 17:53:08 Moat kernel: sas: sas_ata_task_done: SAS error 8a Feb 5 17:53:08 Moat kernel: ata11.00: both IDENTIFYs aborted, assuming NODEV Feb 5 17:53:08 Moat kernel: ata11.00: revalidation failed (errno=-2) Feb 5 17:53:08 Moat kernel: mvsas 0000:03:00.0: Phy3 : No sig fis Feb 5 17:53:08 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[3]:rc= 0 Feb 5 17:53:08 Moat kernel: mvsas 0000:03:00.0: Phy2 : No sig fis Feb 5 17:53:08 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[2]:rc= 0 Feb 5 17:53:09 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1951:Release slot [0] tag[0], task [f741c000]: Feb 5 17:53:09 Moat kernel: sas: sas_ata_task_done: SAS error 8a Feb 5 17:53:09 Moat kernel: ata6.00: failed to set xfermode (err_mask=0x11) Feb 5 17:53:09 Moat kernel: ata6.00: limiting speed to UDMA/133:PIO3 Feb 5 17:53:09 Moat kernel: sas: sas_form_port: phy1 belongs to port1 already(1)! Feb 5 17:53:12 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1951:Release slot [1] tag[1], task [f741c140]: Feb 5 17:53:12 Moat kernel: sas: sas_ata_task_done: SAS error 8a Feb 5 17:53:12 Moat kernel: ata8.00: failed to set xfermode (err_mask=0x11) Feb 5 17:53:12 Moat kernel: ata8.00: limiting speed to UDMA/133:PIO3 Feb 5 17:53:12 Moat kernel: sas: sas_form_port: phy7 belongs to port7 already(1)! Feb 5 17:53:12 Moat kernel: ata6: hard resetting link Feb 5 17:53:13 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1951:Release slot [2] tag[2], task [f7508640]: Feb 5 17:53:13 Moat kernel: sas: sas_ata_task_done: SAS error 8a Feb 5 17:53:13 Moat kernel: ata7.00: failed to set xfermode (err_mask=0x11) Feb 5 17:53:13 Moat kernel: ata7.00: limiting speed to UDMA/133:PIO3 Feb 5 17:53:13 Moat kernel: sas: sas_form_port: phy2 belongs to port2 already(1)! Feb 5 17:53:13 Moat kernel: ata12: hard resetting link Feb 5 17:53:14 Moat kernel: ata11: hard resetting link Feb 5 17:53:14 Moat kernel: mvsas 0000:03:00.0: Phy3 : No sig fis Feb 5 17:53:14 Moat kernel: ata8: hard resetting link Feb 5 17:53:14 Moat kernel: ata7: hard resetting link Feb 5 17:53:18 Moat kernel: ata6.00: qc timeout (cmd 0xec) Feb 5 17:53:18 Moat kernel: ata6.00: failed to IDENTIFY (I/O error, err_mask=0x5) Feb 5 17:53:18 Moat kernel: ata6.00: revalidation failed (errno=-5) Feb 5 17:53:18 Moat kernel: ata6.00: disabled Feb 5 17:53:18 Moat kernel: ata6: hard resetting link Feb 5 17:53:20 Moat kernel: ata11.00: qc timeout (cmd 0xec) Feb 5 17:53:20 Moat kernel: ata11.00: failed to IDENTIFY (I/O error, err_mask=0x5) Feb 5 17:53:20 Moat kernel: ata11.00: revalidation failed (errno=-5) Feb 5 17:53:20 Moat kernel: ata11.00: disabled Feb 5 17:53:20 Moat kernel: ata11: hard resetting link Feb 5 17:53:20 Moat kernel: ata8.00: qc timeout (cmd 0xef) Feb 5 17:53:20 Moat kernel: ata8.00: failed to set xfermode (err_mask=0x4) Feb 5 17:53:20 Moat kernel: ata8.00: disabled Feb 5 17:53:20 Moat kernel: ata8: hard resetting link Feb 5 17:53:21 Moat kernel: ata7.00: qc timeout (cmd 0xef) Feb 5 17:53:21 Moat kernel: ata7.00: failed to set xfermode (err_mask=0x4) Feb 5 17:53:21 Moat kernel: ata7.00: disabled Feb 5 17:53:21 Moat kernel: ata7: hard resetting link Feb 5 17:53:21 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[1]:rc= 0 Feb 5 17:53:22 Moat kernel: sas: sas_form_port: phy3 belongs to port3 already(1)! Feb 5 17:53:22 Moat kernel: mvsas 0000:03:00.0: Phy1 : No sig fis Feb 5 17:53:22 Moat kernel: ata6: EH complete Feb 5 17:53:22 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[6]:rc= 0 Feb 5 17:53:23 Moat kernel: ata11: EH complete Feb 5 17:53:23 Moat kernel: mvsas 0000:03:00.0: Phy6 : No sig fis Feb 5 17:53:23 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[3]:rc= 0 Feb 5 17:53:23 Moat kernel: ata8: EH complete Feb 5 17:53:24 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[2]:rc= 0 Feb 5 17:53:24 Moat kernel: ata7: EH complete Feb 5 17:53:25 Moat kernel: ata12.00: qc timeout (cmd 0xec) Feb 5 17:53:25 Moat kernel: ata12.00: failed to IDENTIFY (I/O error, err_mask=0x5) Feb 5 17:53:25 Moat kernel: ata12.00: revalidation failed (errno=-5) Feb 5 17:53:25 Moat kernel: ata12.00: disabled Feb 5 17:53:25 Moat kernel: ata12: hard resetting link Feb 5 17:53:27 Moat kernel: sas: sas_form_port: phy6 belongs to port6 already(1)! Feb 5 17:53:28 Moat kernel: drivers/scsi/mvsas/mv_sas.c 1521:mvs_I_T_nexus_reset for device[7]:rc= 0 Feb 5 17:53:28 Moat kernel: ata12: EH complete Feb 5 17:53:28 Moat kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 Feb 5 17:53:28 Moat kernel: sd 0:0:3:0: [sdh] READ CAPACITY(16) failed Feb 5 17:53:28 Moat kernel: sd 0:0:3:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Feb 5 17:53:28 Moat kernel: sd 0:0:3:0: [sdh] Sense not available. Feb 5 17:53:28 Moat kernel: sd 0:0:1:0: [sdf] READ CAPACITY(16) failed Feb 5 17:53:28 Moat kernel: sd 0:0:1:0: [sdf] Result: hostbyte=0x04 driverbyte=0x00 Feb 5 17:53:28 Moat kernel: sd 0:0:1:0: [sdf] Sense not available. Feb 5 17:53:28 Moat kernel: sd 0:0:1:0: [sdf] READ CAPACITY failed Feb 5 17:53:28 Moat kernel: sd 0:0:1:0: [sdf] Result: hostbyte=0x04 driverbyte=0x00 Feb 5 17:53:28 Moat kernel: sd 0:0:1:0: [sdf] Sense not available. Feb 5 17:53:28 Moat kernel: sd 0:0:3:0: [sdh] READ CAPACITY failed Feb 5 17:53:28 Moat kernel: sd 0:0:3:0: [sdh] Result: hostbyte=0x04 driverbyte=0x00 Feb 5 17:53:28 Moat kernel: sd 0:0:3:0: [sdh] Sense not available. Feb 5 17:53:28 Moat kernel: sd 0:0:1:0: [sdf] Asking for cache data failed Feb 5 17:53:28 Moat kernel: sd 0:0:1:0: [sdf] Assuming drive cache: write through Feb 5 17:53:28 Moat kernel: sdf: detected capacity change from 2000398934016 to 0 Feb 5 17:53:28 Moat kernel: sd 0:0:3:0: [sdh] Asking for cache data failed Feb 5 17:53:28 Moat kernel: sd 0:0:3:0: [sdh] Assuming drive cache: write through Feb 5 17:53:28 Moat kernel: sdh: detected capacity change from 2000398934016 to 0 Feb 5 17:53:28 Moat kernel: sd 0:0:2:0: [sdg] READ CAPACITY(16) failed Feb 5 17:53:28 Moat kernel: sd 0:0:2:0: [sdg] Result: hostbyte=0x04 driverbyte=0x00 Feb 5 17:53:28 Moat kernel: sd 0:0:2:0: [sdg] Sense not available. Feb 5 17:53:28 Moat kernel: sd 0:0:2:0: [sdg] READ CAPACITY failed Feb 5 17:53:28 Moat kernel: sd 0:0:2:0: [sdg] Result: hostbyte=0x04 driverbyte=0x00 Feb 5 17:53:28 Moat kernel: sd 0:0:2:0: [sdg] Sense not available. Feb 5 17:53:28 Moat kernel: sdg: detected capacity change from 2000398934016 to 0 Feb 5 17:53:28 Moat kernel: mvsas 0000:03:00.0: Phy7 : No sig fis Feb 5 17:53:28 Moat kernel: mvsas 0000:03:00.0: Phy1 : No sig fis Feb 5 17:53:32 Moat kernel: sas: sas_form_port: phy7 belongs to port7 already(1)! Feb 5 17:53:36 Moat emhttp: shcmd (63): rmmod md-mod |& logger Feb 5 17:53:36 Moat emhttp: shcmd (64): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger Feb 5 17:53:36 Moat kernel: md: unRAID driver removed Feb 5 17:53:36 Moat kernel: md: unRAID driver 2.1.5 installed Feb 5 17:53:36 Moat kernel: read_file: error 2 opening /boot/config/super.dat Feb 5 17:53:36 Moat kernel: md: could not read superblock from /boot/config/super.dat Feb 5 17:53:36 Moat kernel: md: initializing superblock Feb 5 17:53:36 Moat emhttp: shcmd (65): udevadm settle Feb 5 17:53:36 Moat emhttp: Device inventory: Feb 5 17:53:36 Moat emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA1137613 (hda) 1953514584 Feb 5 17:53:36 Moat emhttp: ST3000DM001-1CH166_Z1F1QHVN (sda) 2930266584 Feb 5 17:53:36 Moat emhttp: WDC_WD30EZRX-00DC0B0_WD-WCC1T0036740 (sdb) 2930266584 Feb 5 17:53:36 Moat emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3806129 (sdc) 1953514584 Feb 5 17:53:36 Moat emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA1239546 (sde) 1953514584 Feb 5 17:53:36 Moat emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA0853254 (sdf) 0 Feb 5 17:53:36 Moat emhttp: WDC_WD20EARS-00MVWB0_WD-WCAZA1221569 (sdg) 0 Feb 5 17:53:36 Moat emhttp: WDC_WD20EARX-00PASB0_WD-WCAZAD279325 (sdh) 0 Feb 5 17:53:36 Moat emhttp: WDC_WD20EARX-00PASB0_WD-WCAZAD907189 (sdi) 1953514584 Feb 5 17:53:36 Moat emhttp: WDC_WD20EARS-00MVWB0_WD-WMAZA3805888 (sdj) 1953514584 Feb 5 17:53:36 Moat emhttp: WDC_WD20EARX-00PASB0_WD-WMAZA9708345 (sdk) 1953514584 Feb 5 17:53:36 Moat emhttp: WDC_WD20EARS-00S8B1_WD-WCAVY5637510 (sdl) 1953514584 Feb 5 17:53:36 Moat emhttp: ckmbr: read: Success Feb 5 17:53:36 Moat last message repeated 2 times Feb 5 17:53:36 Moat emhttp: ckmbr: read: Input/output error Feb 5 17:53:36 Moat emhttp: ckmbr: read: Input/output error Feb 5 17:53:36 Moat kernel: mdcmd (1): import 0 8,0 2930266532 ST3000DM001-1CH166_Z1F1QHVN Feb 5 17:53:36 Moat kernel: md: import disk0: [8,0] (sda) ST3000DM001-1CH166_Z1F1QHVN size: 2930266532 Feb 5 17:53:36 Moat kernel: md: disk0 new disk Feb 5 17:53:36 Moat kernel: mdcmd (2): import 1 0,0 Feb 5 17:53:36 Moat kernel: mdcmd (3): import 2 0,0 Feb 5 17:53:36 Moat kernel: mdcmd (4): import 3 0,0 Feb 5 17:53:36 Moat kernel: mdcmd (5): import 4 8,64 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA1239546 Feb 5 17:53:36 Moat kernel: md: import disk4: [8,64] (sde) WDC_WD20EARS-00MVWB0_WD-WCAZA1239546 size: 1953514552 Feb 5 17:53:36 Moat kernel: md: disk4 new disk Feb 5 17:53:36 Moat kernel: sd 0:0:7:0: [sdl] Unhandled error code Feb 5 17:53:36 Moat kernel: sd 0:0:7:0: [sdl] Result: hostbyte=0x04 driverbyte=0x00 Feb 5 17:53:36 Moat emhttp: shcmd (66): /usr/local/sbin/emhttp_event driver_loaded Feb 5 17:53:36 Moat kernel: sd 0:0:7:0: [sdl] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 20 00 Feb 5 17:53:36 Moat kernel: end_request: I/O error, dev sdl, sector 0 Feb 5 17:53:36 Moat kernel: Buffer I/O error on device sdl, logical block 0 Feb 5 17:53:36 Moat kernel: Buffer I/O error on device sdl, logical block 1 Feb 5 17:53:36 Moat kernel: Buffer I/O error on device sdl, logical block 2 Feb 5 17:53:36 Moat kernel: Buffer I/O error on device sdl, logical block 3 Feb 5 17:53:36 Moat kernel: sd 0:0:7:0: [sdl] Unhandled error code Feb 5 17:53:36 Moat kernel: sd 0:0:7:0: [sdl] Result: hostbyte=0x04 driverbyte=0x00 Feb 5 17:53:36 Moat kernel: sd 0:0:7:0: [sdl] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00 Feb 5 17:53:36 Moat kernel: end_request: I/O error, dev sdl, sector 0 Feb 5 17:53:36 Moat kernel: Buffer I/O error on device sdl, logical block 0 Feb 5 17:53:36 Moat kernel: mdcmd (6): import 5 0,0 Feb 5 17:53:36 Moat kernel: mdcmd (7): import 6 3,0 1953514552 WDC_WD20EARS-00MVWB0_WD-WCAZA1137613 Feb 5 17:53:36 Moat kernel: md: import disk6: [3,0] (hda) WDC_WD20EARS-00MVWB0_WD-WCAZA1137613 size: 1953514552 Feb 5 17:53:36 Moat kernel: md: disk6 new disk Feb 5 17:53:36 Moat kernel: mdcmd (: import 7 8,32 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3806129 Feb 5 17:53:36 Moat kernel: md: import disk7: [8,32] (sdc) WDC_WD20EARS-00MVWB0_WD-WMAZA3806129 size: 1953514552 Feb 5 17:53:36 Moat kernel: md: disk7 new disk Feb 5 17:53:36 Moat kernel: sd 0:0:6:0: [sdk] Unhandled error code Feb 5 17:53:36 Moat kernel: sd 0:0:6:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Feb 5 17:53:36 Moat kernel: sd 0:0:6:0: [sdk] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 20 00 Feb 5 17:53:36 Moat kernel: end_request: I/O error, dev sdk, sector 0 Feb 5 17:53:36 Moat kernel: Buffer I/O error on device sdk, logical block 0 Feb 5 17:53:36 Moat kernel: Buffer I/O error on device sdk, logical block 1 Feb 5 17:53:36 Moat kernel: Buffer I/O error on device sdk, logical block 2 Feb 5 17:53:36 Moat kernel: Buffer I/O error on device sdk, logical block 3 Feb 5 17:53:36 Moat kernel: sd 0:0:6:0: [sdk] Unhandled error code Feb 5 17:53:36 Moat kernel: sd 0:0:6:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Feb 5 17:53:36 Moat kernel: sd 0:0:6:0: [sdk] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 08 00 Feb 5 17:53:36 Moat kernel: end_request: I/O error, dev sdk, sector 0 Feb 5 17:53:36 Moat kernel: Buffer I/O error on device sdk, logical block 0 Feb 5 17:53:36 Moat kernel: mdcmd (9): import 8 0,0 Feb 5 17:53:36 Moat kernel: mdcmd (10): import 9 8,144 1953514552 WDC_WD20EARS-00MVWB0_WD-WMAZA3805888 Feb 5 17:53:36 Moat kernel: md: import disk9: [8,144] (sdj) WDC_WD20EARS-00MVWB0_WD-WMAZA3805888 size: 1953514552 Feb 5 17:53:36 Moat kernel: md: disk9 new disk Feb 5 17:53:36 Moat kernel: mdcmd (11): import 10 8,16 2930266532 WDC_WD30EZRX-00DC0B0_WD-WCC1T0036740 Feb 5 17:53:36 Moat kernel: md: import disk10: [8,16] (sdb) WDC_WD30EZRX-00DC0B0_WD-WCC1T0036740 size: 2930266532 Feb 5 17:53:36 Moat kernel: md: disk10 new disk Now looking into any firmware updating I can get installed. Link to comment
RobJ Posted February 6, 2013 Share Posted February 6, 2013 That is exactly what happened in the RC8a syslog, so no improvement so far. You may also want to consider reinstalling in your previous motherboard. Do you happen to have a recent syslog from that setup? Link to comment
dwoods99 Posted February 6, 2013 Author Share Posted February 6, 2013 See first post. The problem was that motherboard would not accept the new sata controller cart, hence my OP about only seeing 1 HDD. Link to comment
dwoods99 Posted February 6, 2013 Author Share Posted February 6, 2013 I've tried firmware .15 and latest .21, tried unRaid 5.0r8a and 5.0r11 but the closest I've managed to get was when I modified BIOS setting for SATA as sata not ide and use AHCI. I was able to get to device 11 and then during the refresh, lots of errors showed up in the log file. The biggest kicker is that it seems to be fighting with the network card because waiting for the web page takes very long, or lose connection and if I am in a telnet session, I can lose connection. When I was streaming music from the other unRaid box, music couldn't stream anymore as though my bandwidth was fighting to talk to the problem server. Is it possible that the sata controller conflicts with the network card? At this point I'm out of ideas and frustrated, thinking it's time to get a different sata controller. Still open to anything else worth trying! Link to comment
joshpond Posted February 6, 2013 Share Posted February 6, 2013 Not going to help you much, but the firmware 0.15 or 0.21 and int13 settings shouldn't be causing your issues. Josh Link to comment
RobJ Posted February 7, 2013 Share Posted February 7, 2013 See first post. I was hoping someone else had already informed you that the attached file (named syslog.txt) in your original post is not a text file nor a syslog, except it does appear to have some syslog lines deeply embedded in html, following some javascript. It looks more like a little web page. I tried but the syslog lines appearing there are only a small excerpt, but not wrapped and not formatted - not readable! Can you try attaching the original syslog again? The problem was that motherboard would not accept the new sata controller cart, hence my OP about only seeing 1 HDD. When you say "would not accept", was that because some of the drives did not appear, or was there some other reason? The biggest kicker is that it seems to be fighting with the network card because waiting for the web page takes very long, or lose connection and if I am in a telnet session, I can lose connection. When I was streaming music from the other unRaid box, music couldn't stream anymore as though my bandwidth was fighting to talk to the problem server. Is it possible that the sata controller conflicts with the network card? In the one syslog I have seen so far, I did not see any network issues, just lots of time delays while the system tried (unsuccessfully) to recover the card and the drives. I think what you were seeing was those repeated timeouts, trying over and over to communicate with the card and each of the drives. At this point I'm out of ideas and frustrated, thinking it's time to get a different sata controller. Still open to anything else worth trying! I'd still like to see a syslog from the first computer (the Intel?) with this card. And perhaps the BIOS update will make the card more compatible with that board? The syslog showed that the mvsas driver reported the cards capabilities as "mvsas: PCI-E x4, Bandwidth Usage: 2.5 Gbps". Could someone else with that card tells us if these numbers are normal, or should they be higher? That might be another indication that the card and the slot and/or the motherboard are not fully compatible. Link to comment
dwoods99 Posted February 7, 2013 Author Share Posted February 7, 2013 ... It looks more like a little web page. I tried but the syslog lines appearing there are only a small excerpt, but not wrapped and not formatted - not readable! Can you try attaching the original syslog again? Done. Edit on first post as zip file. I'd still like to see a syslog from the first computer (the Intel?) with this card. And perhaps the BIOS update will make the card more compatible with that board? I did update the BIOS to that motherboard so it should be up to date. Link to comment
RobJ Posted February 7, 2013 Share Posted February 7, 2013 Unfortunately this syslog has rolled over, starts at a point well after the probable crash of the card and the disabling of its drives. It does look suspiciously like the other syslog though, with all of the drives that have been disabled. I can't say absolutely, but I suspect it had the same trouble with this card as the other board did. If that is so, then it looks like you may have a bad card, and both boards are fine. I did spot one other problem, not that you will want to hear about it! Disk 9 (WD20EARS with serial ending in 888) has a Current_Pending_Sector count of 486, so you will want to deal with that once the other issues are fixed. Sorry. Link to comment
dwoods99 Posted February 7, 2013 Author Share Posted February 7, 2013 Appreciate all the help. I ordered two different controller cards and will return this one as faulty. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.