October 30, 201015 yr Author Rebuild on Secondary IDE port here's hoping. Started Stop will take the array off-line. Data-Rebuild in progress. Cancel will stop Data-Rebuild. WARNING: canceling Data-Rebuild will leave the array unprotected! Total size: 1,953,514,552 KB Current position: 333,332 (0.0%) Estimated speed: 3,015 KB/sec Estimated finish: 10795.3 minutes
October 30, 201015 yr Are you using "round" IDE cables? or Are you using 80 conductor flat IDE cables? (They usually have a gray a blue, and a black connector) or Are you using a 40 conductor IDE cable (They are sometimes used for CD drives)
October 31, 201015 yr Author First I used an 80 conductor, then I switched to a round cable, then I switched to another (new) 80 conductor cable. When the rebuild went all the way to 99.9% I did have drive 6 on cable select on slave on a 80 conductor but with no master on the chain. Fixed that. (doh!) But the last time I ran it I think I was on a round cable - and I had fixed the master situation it failed much earlier. When it fails it seems to fill up ram as well - the command free shows available ram shrinking... So far rebuild looks ok no errors on drive 6: FREE results in: total used free shared buffers cached Mem: 3082580 240956 2841624 0 5064 150536 -/+ buffers/cache: 85356 2997224 Swap: 0 0 0 Disk status Model / Serial No. Temperature Size Free Reads Writes Errors parity WDC_WD20EADS-00S_WD-WCAVY0864163 38°C 1,953,514,552 - 622,564 68 0 disk1 WDC_WD5000AAKS-2_WD-WCAS82451651 34°C 488,386,552 44,390,284 616,718 7 0 disk2 ST3500641AS_3PM1YPT7 37°C 488,386,552 73,378,604 643,951 7 0 disk3 WDC_WD20EADS-00S_WD-WCAVY0878118 39°C 1,953,514,552 8,128,452 635,394 7 0 disk4 ST3500641AS_3PM0LCW6 39°C 488,386,552 122,091,392 648,034 8 0 disk5 WDC_WD20EARS-00M_WD-WCAZA0985379 24°C 1,953,514,552 1,933,671,552 33 653,269 0 disk6 ST3500841A_3PM079GN 29°C 488,386,552 245,981,228 566,774 7 0 disk7 ST3200822A_3LJ3BJ39 26°C 195,360,952 2,922,704 277,860 7 0 disk8 ST3200822A_3LJ3A3Z8 25°C 195,360,952 4,284,900 276,712 7 0 disk9 Maxtor_6Y200P0_Y65GPWPE 20°C 199,148,512 56,608,624 352,094 7 0 disk10 ST3200822A_4LJ22G0B 27°C 195,360,952 56,558,920 281,123 8 0 Command area Started Stop will take the array off-line. Data-Rebuild in progress. Cancel will stop Data-Rebuild. WARNING: canceling Data-Rebuild will leave the array unprotected! Total size: 1,953,514,552 KB Current position: 140,342,580 (7.1%) Estimated speed: 13,303 KB/sec Estimated finish: 2269.7 minutes
October 31, 201015 yr Round cables are not able to handle the higher data rates of most drives. They might look good, but they usually do not meet specs. Using the slave connector with nothing on the master is also a recipe for bad communications to a disk. (Always use the connector on the end of the cable first, then add the additional drive to the connector in the middle. Your syslog showed the drive being set to a PIO4 mode. That usually indicates the communications could not be established at a higher rate. I'm glad your re-construction is progressing. Let's hope your luck continues.
October 31, 201015 yr Author Thanks Joe and all for the help. Shall keep posting updates. No errors so far - (Im going to sleep now) Started Stop will take the array off-line. Data-Rebuild in progress. Cancel will stop Data-Rebuild. WARNING: canceling Data-Rebuild will leave the array unprotected! Total size: 1,953,514,552 KB Current position: 318,677,072 (16.3%) Estimated speed: 18,666 KB/sec Estimated finish: 1459.6 minutes
October 31, 201015 yr Started Stop will take the array off-line. Data-Rebuild in progress. Cancel will stop Data-Rebuild. WARNING: canceling Data-Rebuild will leave the array unprotected! Total size: 1,953,514,552 KB Current position: 318,677,072 (16.3%) Estimated speed: 18,666 KB/sec Estimated finish: 1459.6 minutes If you don't use 80 conductor cable for all IDE disks, maybe you should have because it is mandatory for UDMA mode 2 and up and 80 conductor cable has better interference prevention. settle down in PIO only slow down data I/O speed that also affect parity check/data-rebuild. once you rebuild disk5, you should try to resolve PIO issue, if you can't then it might be better migrating to SATA. Because too many signal lines in parallel data bus in IDE created interference problem that preventing higher clock speed for greater data throughput. Latest I/O spec such as SATA or Infiniband that used in high-end data center or cluster machine both are using serial data transportation, although serial data bus has smaller data transport size compared with parallel bus but overall throughput could be compensated through higher clock speed. SATA1 (1.5Gps), SATA2 (3Gbps) and SATA3 (6Gbps).
October 31, 201015 yr Author Ok I see errors on the console: Model / Serial No. Temperature Size Free Reads Writes Errors parity WDC_WD20EADS-00S_WD-WCAVY0864163 33°C 1,953,514,552 - 3,413,252 68 0 disk1 WDC_WD5000AAKS-2_WD-WCAS82451651 * 488,386,552 44,390,284 1,622,671 7 0 disk2 ST3500641AS_3PM1YPT7 * 488,386,552 73,378,604 1,646,663 7 0 disk3 WDC_WD20EADS-00S_WD-WCAVY0878118 33°C 1,953,514,552 8,128,452 3,434,350 7 0 disk4 ST3500641AS_3PM0LCW6 * 488,386,552 122,091,392 1,656,459 8 0 disk5 WDC_WD20EARS-00M_WD-WCAZA0985379 23°C 1,953,514,552 1,933,671,552 33 3,454,416 0 disk6 ST3500841A_3PM079GN 0°C 488,386,552 245,981,228 1,499,779 7 27,914,208 disk7 ST3200822A_3LJ3BJ39 * 195,360,952 2,922,704 386,597 7 0 disk8 ST3200822A_3LJ3A3Z8 * 195,360,952 4,284,900 385,027 7 0 disk9 Maxtor_6Y200P0_Y65GPWPE * 199,148,512 56,608,624 494,906 7 0 disk10 ST3200822A_4LJ22G0B * 195,360,952 56,558,920 391,190 8 0 ----------------------- Result of FREE - I keep checking this because I sometimes see the memory usage go way up on my old server with 512Mb I think it used up all the memory at one point. total used free shared buffers cached Mem: 3082580 2364000 718580 0 9756 2263756 -/+ buffers/cache: 90488 2992092 Swap: 0 0 0 ------------------------ Speed is still up and we are over 50% done Started Stop will take the array off-line. Data-Rebuild in progress. Cancel will stop Data-Rebuild. WARNING: canceling Data-Rebuild will leave the array unprotected! Total size: 1,953,514,552 KB Current position: 1,067,332,920 (54.6%) Estimated speed: 26,035 KB/sec Estimated finish: 567.1 minutes msg10-31.txt sys10-31.txt
October 31, 201015 yr Author Is there a key to reading the MSG.log? I am technical enough (to be dangerous ) to understand some of the stuff but I see many mentions of PIO - I do have 4 old 200gig IDE PATA drives hooked up to a promise controller - that are probably not using 80 conductor cables. I did notice a pause when I started up the unraid software on server - where it ran through all the drives, then the log flashed real fast across the screen and the login came up. Is MSGS the same as what flashes on the screen when UNRAID boots up? Should I have the Bios have Plug and play OS? What do these things mean: 1. Found IT8712F chip at 0xd00, revision 7 it87: in3 is VCC (+5V) it87: in7 is VCCH (+5V Stand-By) ACPI: I/O resource it87 [0xd05-0xd06] conflicts with ACPI region ECRE [0xd00-0xd1f] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver 2. IDE controller (0x10de:0x0053 rev 0xf3) amd74xx 0000:00:0f.0: BIOS didn't set cable bits correctly. Enabling workaround. amd74xx 0000:00:0f.0: not 100% native mode: will probe irqs later
October 31, 201015 yr Author ERROR count looks like it has stabilized rebuild continues - what does this mean? Model / Serial No. Temperature Size Free Reads Writes Errors parity WDC_WD20EADS-00S_WD-WCAVY0864163 32°C 1,953,514,552 - 4,142,919 68 0 disk1 WDC_WD5000AAKS-2_WD-WCAS82451651 * 488,386,552 44,390,284 1,622,671 7 0 disk2 ST3500641AS_3PM1YPT7 * 488,386,552 73,378,604 1,646,663 7 0 disk3 WDC_WD20EADS-00S_WD-WCAVY0878118 32°C 1,953,514,552 8,128,452 4,164,080 7 0 disk4 ST3500641AS_3PM0LCW6 * 488,386,552 122,091,392 1,656,459 8 0 disk5 WDC_WD20EARS-00M_WD-WCAZA0985379 23°C 1,953,514,552 1,933,671,552 33 4,184,930 0 disk6 ST3500841A_3PM079GN 0°C 488,386,552 245,981,228 1,499,779 7 27,914,208 disk7 ST3200822A_3LJ3BJ39 * 195,360,952 2,922,704 386,597 7 0 disk8 ST3200822A_3LJ3A3Z8 * 195,360,952 4,284,900 385,027 7 0 disk9 Maxtor_6Y200P0_Y65GPWPE * 199,148,512 56,608,624 494,906 7 0 disk10 ST3200822A_4LJ22G0B * 195,360,952 56,558,920 391,190 8 0 Command area Started Stop will take the array off-line. Data-Rebuild in progress. Cancel will stop Data-Rebuild. WARNING: canceling Data-Rebuild will leave the array unprotected! Total size: 1,953,514,552 KB Current position: 1,301,055,716 (66.6%) Estimated speed: 26,744 KB/sec Estimated finish: 405.4 minutes
October 31, 201015 yr disk6 ST3500841A_3PM079GN 0°C 488,386,552 245,981,228 1,499,779 7 27,914,208 I think you better take a look at syslog to find out if system has issues in talking to this disk. looks to me the smart ioctl might have failed that is why temperature is zero degree. meanwhile there are 1,499,779 in read count but there are 27,914,208 in error count, this doesn't add up unless both counters are not in same unit.
October 31, 201015 yr Author Ok guys just got back this is what I see on the console - I will post the logs in a bit Model / Serial No. Temperature Size Free Reads Writes Errors parity WDC_WD20EADS-00S_WD-WCAVY0864163 * 1,953,514,552 - 6,179,754 68 0 disk1 WDC_WD5000AAKS-2_WD-WCAS82451651 * 488,386,552 44,390,284 1,622,671 7 0 disk2 ST3500641AS_3PM1YPT7 * 488,386,552 73,378,604 1,646,663 7 0 disk3 WDC_WD20EADS-00S_WD-WCAVY0878118 * 1,953,514,552 8,128,452 6,201,074 7 0 disk4 ST3500641AS_3PM0LCW6 * 488,386,552 122,091,392 1,656,459 8 0 disk5 WDC_WD20EARS-00M_WD-WCAZA0985379 * 1,953,514,552 1,933,671,552 33 6,224,153 0 disk6 ST3500841A_3PM079GN * 488,386,552 245,981,228 1,499,779 7 27,914,208 disk7 ST3200822A_3LJ3BJ39 * 195,360,952 2,922,704 386,597 7 0 disk8 ST3200822A_3LJ3A3Z8 * 195,360,952 4,284,900 385,027 7 0 disk9 Maxtor_6Y200P0_Y65GPWPE * 199,148,512 56,608,624 494,906 7 0 disk10 ST3200822A_4LJ22G0B * 195,360,952 56,558,920 391,190 8 0 Started Stop will take the array off-line. Data-Rebuild in progress. Cancel will stop Data-Rebuild. WARNING: canceling Data-Rebuild will leave the array unprotected! Total size: 1,953,514,552 KB Current position: 1,953,514,040 (99.9%) Estimated speed: 21,680 KB/sec Estimated finish: 0.0 minutes We are back to being stuck at 99.9% Arrrrgh...
October 31, 201015 yr Author Result of FREE: total used free shared buffers cached Mem: 3082580 2364116 718464 0 9784 2264016 -/+ buffers/cache: 90316 2992264 Swap: 0 0 0 Log files attached. I am backed to the original problem 99.9% done - stuck - what to do next? msgs-10-31-635pm.txt sys-10-31-635pm.zip
October 31, 201015 yr Author GK20 - What am I looking for? I posted the syslog - I have no idea what I am looking for - very confused why its 99.9% done and then stuck. Is there some tool I can run in linux to check if the drive has failed - I am just wasting time with all this cable/port swapping crap? disk6 ST3500841A_3PM079GN 0°C 488,386,552 245,981,228 1,499,779 7 27,914,208 I think you better take a look at syslog to find out if system has issues in talking to this disk. looks to me the smart ioctl might have failed that is why temperature is zero degree. meanwhile there are 1,499,779 in read count but there are 27,914,208 in error count, this doesn't add up unless both counters are not in same unit.
October 31, 201015 yr Well, the tool to tell if a drive has failed is smartctl -d ata -d /dev/sdX or smartctl -d ata -d /dev/hdX where sdX or hdX = the device of disk6. (hdX could be hda, hdb, hdc, etc for IDE drives, od sda, sdb, sdc etc for SATA drives)
October 31, 201015 yr Author Well here's the strange thing - I am able to recover files from drive 6 After a reboot of the server with the rebuild back to 0.0% complete. However same files would not play etc when rebuild was at 99.9%. This makes no sense?? I am going to recover the important stuff before I do anything else. I already do off site backups with a HD in a bank vault for my most critical data - I am thinking maybe I need to rethink what/how I classify critical data. WHY Am I able to read fine off of disk 6 now?
October 31, 201015 yr Author The good news is - I managed to grab the most critical data off of disk 6 - NICE! There are no errors reported on the console for drive 6 yet. Now let me ask you - if there was corruption on the original drive 5 would this manifest it self as errors on drive 6 when you try a rebuild? I do not see how this can happen - but this is not making any sense to me right now. Grasping at straws. BTW the power supply is a 600W Enermax Noisetaker ATX 12V V2 This should be plenty power - and if it were the power supply then I would have drive issues on boot up not at 99.9% of complete on a rebuild? Why is it stopping at 99.9% Do you guys see anything in the log files?
November 1, 201015 yr Author Lets say I get everything I want out of disk 5 and 6 and I want to just get two blank drives - or maybe a blank for 5 and 6 with the data that is still on it. ie forget this damned rebuild. What must I do?
November 1, 201015 yr Author Whats the easiest way to hook up either disk 5 or disk 6 to a win 7 machine and to see what data is recoverable?
November 1, 201015 yr BTW the power supply is a 600W Enermax Noisetaker ATX 12V V2 This should be plenty power - and if it were the power supply then I would have drive issues on boot up not at 99.9% of complete on a rebuild? Why is it stopping at 99.9% According to this web-page at the enermax web-site, your power supply has 2 18Amp 12Volt rails. One is used for the CPU, the other for the disks. You basically have 18Amps available. If you have older drives (and I know you have some) figure on 3 Amps per drive. Figure on an amp or two for the fans. You are right on the edge of stressing that supply past its limits. Multi-rail supplies often only have one rail connected to the molex connectors for the disks. It gives you a false sense of having a 600 Watt power supply. You really are not using much of it, and cannot, because it was designed for power hungry video cards run by game enthusiasts. I'm not saying it is the issue, but it might not be as powerful as you think. I saw the ethernet controller lock up and reset itself in your syslog. Are you sure the re-construction is still in progress? Can you type /root/mdcmd status | strings and post the output? Joe L.
November 1, 201015 yr Author So I am able to grab a lot of files off of disk 6 - some files make the drive generate errors. If I skip these I seem to be ok. I think the drive is failing. How to confirm? Result of /root/mdcmd status | strings cmdOper=status cmdResult=ok sbName=/boot/config/super.dat sbVersion=0.95.3 sbCreated=1266082976 sbUpdated=1288571570 sbEvents=108 sbState=0 sbNumDisks=11 sbSynced=1288431955 sbSyncErrs=0 mdVersion=0.95.4 mdState=STARTED mdNumProtected=11 mdNumDisabled=0 mdDisabledDisk=0 mdNumInvalid=1 mdInvalidDisk=5 mdNumMissing=0 mdMissingDisk=0 mdNumNew=0 mdResync=1953514552 mdResyncPos=4652540 mdResyncPrcnt=0.2 mdResyncFinish=3110.0 mdResyncSpeed=10440 diskNumber.0=0 diskName.0= diskSize.0=1953514552 diskState.0=7 diskModel.0=WDC WD20EADS-00S2B0 diskSerial.0= WD-WCAVY0864163 diskId.0=WDC_WD20EADS-00S2B0_WD-WCAVY0864163 rdevNumber.0=0 rdevStatus.0=DISK_OK rdevName.0=sde rdevSize.0=1953514552 rdevModel.0=WDC WD20EADS-00S rdevSerial.0=WD-WCAVY0864163 rdevId.0=WDC_WD20EADS-00S_WD-WCAVY0864163 rdevNumErrors.0=0 rdevLastIO.0=1288572706 rdevSpinupGroup.0=0 diskNumber.1=1 diskName.1=md1 diskSize.1=488386552 diskState.1=7 diskModel.1=WDC WD5000AAKS-22YGA0 diskSerial.1= WD-WCAS82451651 diskId.1=WDC_WD5000AAKS-22YGA0_WD-WCAS82451651 rdevNumber.1=1 rdevStatus.1=DISK_OK rdevName.1=sda rdevSize.1=488386552 rdevModel.1=WDC WD5000AAKS-2 rdevSerial.1=WD-WCAS82451651 rdevId.1=WDC_WD5000AAKS-2_WD-WCAS82451651 rdevNumErrors.1=0 rdevLastIO.1=1288572706 rdevSpinupGroup.1=0 diskNumber.2=2 diskName.2=md2 diskSize.2=488386552 diskState.2=7 diskModel.2=ST3500641AS diskSerial.2=3PM1YPT7 diskId.2=ST3500641AS_3PM1YPT7 rdevNumber.2=2 rdevStatus.2=DISK_OK rdevName.2=sdf rdevSize.2=488386552 rdevModel.2=ST3500641AS rdevSerial.2=3PM1YPT7 rdevId.2=ST3500641AS_3PM1YPT7 rdevNumErrors.2=0 rdevLastIO.2=1288572706 rdevSpinupGroup.2=0 diskNumber.3=3 diskName.3=md3 diskSize.3=1953514552 diskState.3=7 diskModel.3=WDC WD20EADS-00S2B0 diskSerial.3= WD-WCAVY0878118 diskId.3=WDC_WD20EADS-00S2B0_WD-WCAVY0878118 rdevNumber.3=3 rdevStatus.3=DISK_OK rdevName.3=sdd rdevSize.3=1953514552 rdevModel.3=WDC WD20EADS-00S rdevSerial.3=WD-WCAVY0878118 rdevId.3=WDC_WD20EADS-00S_WD-WCAVY0878118 rdevNumErrors.3=0 rdevLastIO.3=1288572706 rdevSpinupGroup.3=0 diskNumber.4=4 diskName.4=md4 diskSize.4=488386552 diskState.4=7 diskModel.4=ST3500641AS diskSerial.4= 3PM0LCW6 diskId.4=ST3500641AS_3PM0LCW6 rdevNumber.4=4 rdevStatus.4=DISK_OK rdevName.4=sdc rdevSize.4=488386552 rdevModel.4=ST3500641AS rdevSerial.4=3PM0LCW6 rdevId.4=ST3500641AS_3PM0LCW6 rdevNumErrors.4=0 rdevLastIO.4=1288572706 rdevSpinupGroup.4=0 diskNumber.5=5 diskName.5=md5 diskSize.5=1953514552 diskState.5=6 diskModel.5=WDC WD20EARS-00M diskSerial.5=WD-WCAZA0985379 diskId.5=WDC_WD20EARS-00M_WD-WCAZA0985379 rdevNumber.5=5 rdevStatus.5=DISK_INVALID rdevName.5=sdh rdevSize.5=1953514552 rdevModel.5=WDC WD20EARS-00M rdevSerial.5=WD-WCAZA0985379 rdevId.5=WDC_WD20EARS-00M_WD-WCAZA0985379 rdevNumErrors.5=0 rdevLastIO.5=1288572706 rdevSpinupGroup.5=64 diskNumber.6=6 diskName.6=md6 diskSize.6=488386552 diskState.6=7 diskModel.6=ST3500841A diskSerial.6=3PM079GN diskId.6=ST3500841A_3PM079GN rdevNumber.6=6 rdevStatus.6=DISK_OK rdevName.6=hdc rdevSize.6=488386552 rdevModel.6=ST3500841A rdevSerial.6=3PM079GN rdevId.6=ST3500841A_3PM079GN rdevNumErrors.6=128 rdevLastIO.6=1288572706 rdevSpinupGroup.6=32 diskNumber.7=7 diskName.7=md7 diskSize.7=195360952 diskState.7=7 diskModel.7=ST3200822A diskSerial.7=3LJ3BJ39 diskId.7=ST3200822A_3LJ3BJ39 rdevNumber.7=7 rdevStatus.7=DISK_OK rdevName.7=hde rdevSize.7=195360952 rdevModel.7=ST3200822A rdevSerial.7=3LJ3BJ39 rdevId.7=ST3200822A_3LJ3BJ39 rdevNumErrors.7=0 rdevLastIO.7=1288572706 rdevSpinupGroup.7=256 diskNumber.8=8 diskName.8=md8 diskSize.8=195360952 diskState.8=7 diskModel.8=ST3200822A diskSerial.8=3LJ3A3Z8 diskId.8=ST3200822A_3LJ3A3Z8 rdevNumber.8=8 rdevStatus.8=DISK_OK rdevName.8=hdf rdevSize.8=195360952 rdevModel.8=ST3200822A rdevSerial.8=3LJ3A3Z8 rdevId.8=ST3200822A_3LJ3A3Z8 rdevNumErrors.8=0 rdevLastIO.8=1288572706 rdevSpinupGroup.8=128 diskNumber.9=9 diskName.9=md9 diskSize.9=199148512 diskState.9=7 diskModel.9=Maxtor 6Y200P0 diskSerial.9=Y65GPWPE diskId.9=Maxtor_6Y200P0_Y65GPWPE rdevNumber.9=9 rdevStatus.9=DISK_OK rdevName.9=hdg rdevSize.9=199148512 rdevModel.9=Maxtor 6Y200P0 rdevSerial.9=Y65GPWPE rdevId.9=Maxtor_6Y200P0_Y65GPWPE rdevNumErrors.9=0 rdevLastIO.9=1288572706 rdevSpinupGroup.9=1024 diskNumber.10=10 diskName.10=md10 diskSize.10=195360952 diskState.10=7 diskModel.10=ST3200822A diskSerial.10=4LJ22G0B diskId.10=ST3200822A_4LJ22G0B rdevNumber.10=10 rdevStatus.10=DISK_OK rdevName.10=hdh rdevSize.10=195360952 rdevModel.10=ST3200822A rdevSerial.10=4LJ22G0B rdevId.10=ST3200822A_4LJ22G0B rdevNumErrors.10=0 rdevLastIO.10=1288572706 rdevSpinupGroup.10=512
November 1, 201015 yr Author After I took the sys and msgs logs I rebooted the server - it would not even shutdown properly. And then backed up the critical data on disk 6 Now getting secondary datat off of disk 6 When I tried to do a big chunk copy of secondary data drive started to make some noise and console showed errors basically copy failed and console just kept showing more and more errors for disk 6 - then went unresponsive - I had to do a hard boot. Re booted quite slow to get to console. Finally got there - now I am copying secondary data one file at a time. Whats the easiest way to mount this on a Windows 7 machine?
November 1, 201015 yr So I am able to grab a lot of files off of disk 6 - some files make the drive generate errors. If I skip these I seem to be ok. I think the drive is failing. How to confirm? Result of /root/mdcmd status | strings cmdOper=status cmdResult=ok sbName=/boot/config/super.dat sbVersion=0.95.3 sbCreated=1266082976 sbUpdated=1288571570 sbEvents=108 sbState=0 sbNumDisks=11 sbSynced=1288431955 sbSyncErrs=0 mdVersion=0.95.4 mdState=STARTED mdNumProtected=11 mdNumDisabled=0 mdDisabledDisk=0 mdNumInvalid=1 mdInvalidDisk=5 mdNumMissing=0 mdMissingDisk=0 mdNumNew=0 mdResync=1953514552 mdResyncPos=4652540 mdResyncPrcnt=0.2 mdResyncFinish=3110.0 mdResyncSpeed=10440 diskNumber.0=0 diskName.0= diskSize.0=1953514552 diskState.0=7 diskModel.0=WDC WD20EADS-00S2B0 diskSerial.0= WD-WCAVY0864163 diskId.0=WDC_WD20EADS-00S2B0_WD-WCAVY0864163 rdevNumber.0=0 rdevStatus.0=DISK_OK rdevName.0=sde rdevSize.0=1953514552 rdevModel.0=WDC WD20EADS-00S rdevSerial.0=WD-WCAVY0864163 rdevId.0=WDC_WD20EADS-00S_WD-WCAVY0864163 rdevNumErrors.0=0 rdevLastIO.0=1288572706 rdevSpinupGroup.0=0 diskNumber.1=1 diskName.1=md1 diskSize.1=488386552 diskState.1=7 diskModel.1=WDC WD5000AAKS-22YGA0 diskSerial.1= WD-WCAS82451651 diskId.1=WDC_WD5000AAKS-22YGA0_WD-WCAS82451651 rdevNumber.1=1 rdevStatus.1=DISK_OK rdevName.1=sda rdevSize.1=488386552 rdevModel.1=WDC WD5000AAKS-2 rdevSerial.1=WD-WCAS82451651 rdevId.1=WDC_WD5000AAKS-2_WD-WCAS82451651 rdevNumErrors.1=0 rdevLastIO.1=1288572706 rdevSpinupGroup.1=0 diskNumber.2=2 diskName.2=md2 diskSize.2=488386552 diskState.2=7 diskModel.2=ST3500641AS diskSerial.2=3PM1YPT7 diskId.2=ST3500641AS_3PM1YPT7 rdevNumber.2=2 rdevStatus.2=DISK_OK rdevName.2=sdf rdevSize.2=488386552 rdevModel.2=ST3500641AS rdevSerial.2=3PM1YPT7 rdevId.2=ST3500641AS_3PM1YPT7 rdevNumErrors.2=0 rdevLastIO.2=1288572706 rdevSpinupGroup.2=0 diskNumber.3=3 diskName.3=md3 diskSize.3=1953514552 diskState.3=7 diskModel.3=WDC WD20EADS-00S2B0 diskSerial.3= WD-WCAVY0878118 diskId.3=WDC_WD20EADS-00S2B0_WD-WCAVY0878118 rdevNumber.3=3 rdevStatus.3=DISK_OK rdevName.3=sdd rdevSize.3=1953514552 rdevModel.3=WDC WD20EADS-00S rdevSerial.3=WD-WCAVY0878118 rdevId.3=WDC_WD20EADS-00S_WD-WCAVY0878118 rdevNumErrors.3=0 rdevLastIO.3=1288572706 rdevSpinupGroup.3=0 diskNumber.4=4 diskName.4=md4 diskSize.4=488386552 diskState.4=7 diskModel.4=ST3500641AS diskSerial.4= 3PM0LCW6 diskId.4=ST3500641AS_3PM0LCW6 rdevNumber.4=4 rdevStatus.4=DISK_OK rdevName.4=sdc rdevSize.4=488386552 rdevModel.4=ST3500641AS rdevSerial.4=3PM0LCW6 rdevId.4=ST3500641AS_3PM0LCW6 rdevNumErrors.4=0 rdevLastIO.4=1288572706 rdevSpinupGroup.4=0 diskNumber.5=5 diskName.5=md5 diskSize.5=1953514552 diskState.5=6 diskModel.5=WDC WD20EARS-00M diskSerial.5=WD-WCAZA0985379 diskId.5=WDC_WD20EARS-00M_WD-WCAZA0985379 rdevNumber.5=5 rdevStatus.5=DISK_INVALID rdevName.5=sdh rdevSize.5=1953514552 rdevModel.5=WDC WD20EARS-00M rdevSerial.5=WD-WCAZA0985379 rdevId.5=WDC_WD20EARS-00M_WD-WCAZA0985379 rdevNumErrors.5=0 rdevLastIO.5=1288572706 rdevSpinupGroup.5=64 diskNumber.6=6 diskName.6=md6 diskSize.6=488386552 diskState.6=7 diskModel.6=ST3500841A diskSerial.6=3PM079GN diskId.6=ST3500841A_3PM079GN rdevNumber.6=6 rdevStatus.6=DISK_OK rdevName.6=hdc rdevSize.6=488386552 rdevModel.6=ST3500841A rdevSerial.6=3PM079GN rdevId.6=ST3500841A_3PM079GN rdevNumErrors.6=128 rdevLastIO.6=1288572706 rdevSpinupGroup.6=32 diskNumber.7=7 diskName.7=md7 diskSize.7=195360952 diskState.7=7 diskModel.7=ST3200822A diskSerial.7=3LJ3BJ39 diskId.7=ST3200822A_3LJ3BJ39 rdevNumber.7=7 rdevStatus.7=DISK_OK rdevName.7=hde rdevSize.7=195360952 rdevModel.7=ST3200822A rdevSerial.7=3LJ3BJ39 rdevId.7=ST3200822A_3LJ3BJ39 rdevNumErrors.7=0 rdevLastIO.7=1288572706 rdevSpinupGroup.7=256 diskNumber.8=8 diskName.8=md8 diskSize.8=195360952 diskState.8=7 diskModel.8=ST3200822A diskSerial.8=3LJ3A3Z8 diskId.8=ST3200822A_3LJ3A3Z8 rdevNumber.8=8 rdevStatus.8=DISK_OK rdevName.8=hdf rdevSize.8=195360952 rdevModel.8=ST3200822A rdevSerial.8=3LJ3A3Z8 rdevId.8=ST3200822A_3LJ3A3Z8 rdevNumErrors.8=0 rdevLastIO.8=1288572706 rdevSpinupGroup.8=128 diskNumber.9=9 diskName.9=md9 diskSize.9=199148512 diskState.9=7 diskModel.9=Maxtor 6Y200P0 diskSerial.9=Y65GPWPE diskId.9=Maxtor_6Y200P0_Y65GPWPE rdevNumber.9=9 rdevStatus.9=DISK_OK rdevName.9=hdg rdevSize.9=199148512 rdevModel.9=Maxtor 6Y200P0 rdevSerial.9=Y65GPWPE rdevId.9=Maxtor_6Y200P0_Y65GPWPE rdevNumErrors.9=0 rdevLastIO.9=1288572706 rdevSpinupGroup.9=1024 diskNumber.10=10 diskName.10=md10 diskSize.10=195360952 diskState.10=7 diskModel.10=ST3200822A diskSerial.10=4LJ22G0B diskId.10=ST3200822A_4LJ22G0B rdevNumber.10=10 rdevStatus.10=DISK_OK rdevName.10=hdh rdevSize.10=195360952 rdevModel.10=ST3200822A rdevSerial.10=4LJ22G0B rdevId.10=ST3200822A_4LJ22G0B rdevNumErrors.10=0 rdevLastIO.10=1288572706 rdevSpinupGroup.10=512 You have 11 drives on a 18 Amp supply. You are way past the limits of the power supply even if you only figure 2 amps per drive. (they would need between 22 Amps and 33 Amps) Joe L.
November 1, 201015 yr Author ok shall hook up second power supply to old MB and switch some drives to second power supply to see if that makes problem go away. Can you recommend a single power supply that is more capable?
November 1, 201015 yr ok shall hook up second power supply to old MB and switch some drives to second power supply to see if that makes problem go away. That sure would help. Can you recommend a single power supply that is more capable? Any with a single 12 Volt rail that has a capacity of 35 Amps or more. (Actually, since the motherboard needs some 12Volt power too, better make that 45 Amps or more)
November 1, 201015 yr Author But Joe do you really think this is a power issue? I was able to copy a bunch of files off of disk 6.
Archived
This topic is now archived and is closed to further replies.