February 2, 201115 yr My Hardware: Asus P5KPL-CM Intel Celeron DUAL-CORE E1200 Corsair XMS2 TWIN2X2048-6400C4 2GB 2X1GB INTEL pci-E Gigabit PC Power & Cooling Silencer 610W SYBA SD-SA2PEX-2IR PCI Express SATA II SYBA SD-SATA150R PCI SATA 4xHitachi_HUA72101 3xWDC_WD10EACS 1xWDC_WD7500AACS I replaced syba cards with SASLP-MV8, everything is fine.Upgraded from Unraid 4.6 to 4.7b. Added WDC_WD20EARS drive (jumper off), started new preclear script.Unraid frozen in the middle of it, nothing seams to work, power off button.After restart one disk shows unformatted.Plug the disk in Windows machine and i can copy all the data no problem.Plug it back in the "tower' still shows unformatted.Run "initconfig" Unraid clear the disk and everything is OK. Revered back to Unraid 4.6. Run precleardisk on 2TB disk (with jumper on).unraid freezes syslog file used all memory. Check the disk with WD diag software - it reports OK. Now i was moving large number of files (data) with mc directly on the tower, mc stops telling me there is incomplete file meanwhile unraid puts red dot on the disk I'm reading from.Red dot still on but mc keeps coping files. What do I test to determine whats wrong. Got to go to work, post more later. Please help. thanks.
February 2, 201115 yr Post a syslog and run a memtest for at least overnight. Start there and if memetest passes an overnight run then we can go from there.
February 3, 201115 yr Author Damn i did not noticed max file size for attachments and my message did not post. Here we go again.Memtest run for 25 passes- NO errors. Please find attached partial syslog (complete was 20MB).Even though the disk was marked red (disabled) mc was still coping files and the disk was and still is accessible on network(after restarting unraid the disk is still marked red).2TB WD disk I was not able to preclear due to unraid freezing(crashing) did preclear on a spare machine. syslog-2011-02-02-partial.txt
February 3, 201115 yr Author Me again. Here is syslog from today after restarting the server.The disk I was reading from is marked red but still accessible on a network. syslog-2011-02-03.txt
February 4, 201115 yr The red disk is being emulated by the remaining data disks plus parity. If your log is too big please use zip to compress it and post the compressed copy.
February 4, 201115 yr Author What do you want me to compress 750MB syslog, because that was the first one i was able to save.Next one i have is 20MB and last one is 70kB. Did you even look at ones I did posted or did you read the problems I'm having?
February 4, 201115 yr The 20MB one will likely show the problem. With compression you will be able to post it. Post them all.
February 4, 201115 yr Author Here is 20MB one.Here is part one(had to split it).Part two in next post. My mistake the BIG one is 1.46GB p.s. These are rar files had to rename to zip. syslog-2011-02-02.part001.zip syslog-2011-02-02.part002.zip
February 4, 201115 yr Author Winrar. Like I said these are rar files. Had to rename it because I could not attach rar files.
February 4, 201115 yr ata3/disk4 is the problem. Check the cabling to that drive. Reseat all of the connectors. If that does not fix it, try a different cable and power connector, then try a different SATA port. You need to isolate where the problem is. You may have a bad disk, but more likely it is a cable problem.
February 4, 201115 yr Author Well, I've removed red doted WD 750GB drive. Plugged it in windows machine, run WD diagnostics with no errors. After a reboot windows did not see the drive (could still see it in bios). After a second reboot (was going to run WD diagnostics under DOS) drive does not show in bios. It spins up but does not list in bios-toasted. Replaced it with precleard (on different machine) and rebuilding data now. After preclearing the script reported following errors: Disk has been precleared successfully. SMART error count differences detected after pre-clear note, some "raw" values may change, but not be indication of a problem. 58c58 <7 seek_Error_Rate 0x002e 200 200 000 Old.age Always - 0 >7 seek_Error_Rate 0x002e 100 253 000 Old.age Always - 0 63c63 <193 Load_Cycle_Count 0x0032 200 200 000 Old.age Always - 446 >193 Load_Cycle_Count 0x0032 200 200 000 Old.age Always - 447
February 4, 201115 yr Those aren't errors. They are normal. Do you have the latest pre-clear script? It presents the results in a less confusing manner.
February 4, 201115 yr Always update the preclear_disk.sh before you start your preclear cycles. The version your using is at least 3 weeks old, and around 7 versions behind. Without the final SMART report for the drive we have no idea how the drive is actually doing. We only know a few values have changed. The new version takes the guess work out and makes it so any user should be able to tell how their drive is doing.
February 4, 201115 yr Author My bad with old version, but I do not want to preclear it again if I can avoid it. So do you think my problems (starting with "unformatted" drive which I could read in windows) was caused by that WD 750 that went bad?
February 4, 201115 yr Author Damn, I've tried that 750 drive again on windows and now it seams to be OK. WD diagnostics report -pass (quick test at least) I got to check my cables and power connector.
February 4, 201115 yr The new pre-clear exercises the drive with the same torture test. If the drive is bad it will eventually fail a pre-clear. If your using the same cables to attach the new drive then it was probably a loose connector. Locking SATA cables from monoprice are a good and cheap investment. http://www.monoprice.com/products/product.asp?c_id=102&cp_id=10226&cs_id=1022602&p_id=2887&seq=1&format=2
February 4, 201115 yr Author Good idea on the cables (i do use them) but how am i going to use these on Supermicro SASLP-MV8?
Archived
This topic is now archived and is closed to further replies.