jaszypoo

Thanks graywolf

I'm trying to remove one disk for the mean time (not replace) due to it throwing a ton of smart errors. Disk1(/sdc) is the problematic drive. I've read the following FAQ: http://lime-technology.com/wiki/index.php/FAQ_remove_drive. Logged in via telnet but I get the following: -bash: initconfig: command not found Am I missing something? I'm running 5.0-rc15a. Thanks in advance. syslog.txt smart_sdc.txt

So far I've noticed the rebuild slows down at a crawl when the 500gb is spinning. When all the reads are done on the Blue, speed picks up dramatically. The faulty green drive also led to slower speeds. Also swapped out the faulty drive. I tried preclearing the drive for the hell of it but never got far...only one hour in. RMAing it. Preclearing two new 2TB greens. One to replace the 500gb, the other as another drive in the array. Edit: rebuild done. now parity checking while preclearing two other drives. I will mark this as solved unless something changes. Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

rebuild still ongoing. 6mb/s at about 81%. No errors but still somewhat slow. *knock on wood* Thanks for the heads up on SimpleFeatures. So it's another plug-in all together? Well if that's the case then I'm 100% sure I don't have it. I only had cache_dirs and unMenu as plug-ins. Oops. I meant config/plugins and /extra, not config/ itself. Sorry!

That's a good option to consider. I was originally using a CX430. Upped to an extra TX650 v1 lying around. Maybe ill try a different line of molex connectors next time around. Rebuild is still ongoing...at a crawl. No write errors yet. If simplefeatures is part of unmenu, then I'm def. sure its disabled. My go file is stock and /config and /extra folders have been temporarily renamed to something else. Thanks for the tip. My plan is to, assuming rebuild is complete, add a couple of drives and preclear them first via a supermicro sas2lp card and breakout cable. Then replace the older drives with the precleared ones. Then preclear the older drives to further stress test them. 500gb blue will be out the door and replaced with another new 2tb. Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

Disk3 was rebuild successfully. Disk1 is now problematic. Both drives in question are in a 5x3 supermicro cage powered by the same two molex connectors. rebuilding and waiting it out.

I just got home. Rebuild was complete. Was going to do a parity check afterwards but I noticed disk1 had hundreds of thousands of errors. I kid you not. So I took the array offline. Now disk1 is red balled. Goodness, going to have to RMA this one too? Syslog was huge. took a snippet. mostly write errors. https://dl.dropboxusercontent.com/u/5332835/unraid/syslog-may14.txt What should I do now? Try rebuilding disk1 and OR swap it out with another new drive? (+ parity check afterwards) edit: formatting edit: Decided to try rebuilding disk1. Will update if anything changes.

Thank you for the reply. I'll try turning off the mover script or unassign the cache drive all together. Could it really be cause though? There's nothing to be moved. Cache is empty. No one else is accessing the shares. Just the fact the script is being invoked (and skipped) during rebuild can cause some hiccups? I'll take a look when I get home. Thanks again

Uh oh. Experiencing the same symptoms. Slow rebuild and unresponsive UI. Getting this: May 14 04:00:01 Tower logger: mover started May 14 04:00:01 Tower logger: skipping */ May 14 04:00:01 Tower logger: mover finished May 14 06:00:01 Tower logger: mover started May 14 06:00:01 Tower logger: skipping */ May 14 06:00:01 Tower logger: mover finished May 14 07:52:36 Tower kernel: mdcmd (22): spindown 2 May 14 08:00:01 Tower logger: mover started May 14 08:00:01 Tower logger: skipping */ May 14 08:00:01 Tower logger: mover finished May 14 10:00:01 Tower logger: mover started May 14 10:00:01 Tower logger: skipping */ May 14 10:00:01 Tower logger: mover finished May 14 12:00:01 Tower logger: mover started May 14 12:00:01 Tower logger: skipping */ May 14 12:00:01 Tower logger: mover finished May 14 13:12:43 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen May 14 13:12:43 Tower kernel: ata1.00: failed command: READ DMA EXT May 14 13:12:43 Tower kernel: ata1.00: cmd 25/00:00:c7:98:02/00:04:7f:00:00/e0 tag 0 dma 524288 in May 14 13:12:43 Tower kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) May 14 13:12:43 Tower kernel: ata1.00: status: { DRDY } May 14 13:12:43 Tower kernel: ata1: hard resetting link May 14 13:12:53 Tower kernel: ata1: softreset failed (device not ready) May 14 13:12:53 Tower kernel: ata1: hard resetting link May 14 13:13:02 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) May 14 13:13:02 Tower kernel: ata1.00: configured for UDMA/133 May 14 13:13:02 Tower kernel: ata1: EH complete May 14 13:13:33 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen May 14 13:13:33 Tower kernel: ata1.00: failed command: READ DMA EXT May 14 13:13:33 Tower kernel: ata1.00: cmd 25/00:00:c7:a4:02/00:04:7f:00:00/e0 tag 0 dma 524288 in May 14 13:13:33 Tower kernel: res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) May 14 13:13:33 Tower kernel: ata1.00: status: { DRDY } May 14 13:13:33 Tower kernel: ata1: hard resetting link May 14 13:13:43 Tower kernel: ata1: softreset failed (device not ready) May 14 13:13:43 Tower kernel: ata1: hard resetting link May 14 13:13:53 Tower kernel: ata1: softreset failed (device not ready) May 14 13:13:53 Tower kernel: ata1: hard resetting link May 14 13:14:03 Tower kernel: ata1: link is slow to respond, please be patient (ready=0) May 14 13:14:09 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) May 14 13:14:09 Tower kernel: ata1.00: configured for UDMA/133 May 14 13:14:09 Tower kernel: ata1: EH complete edit: wrong screenie. Anything odd in the log snippet? Heading to work. Hopefully just a hiccup.

Same drive - rebuild failed. Sata cable replaced, Same drive - rebuild failed. Sata cable replaced, New 2TB drive - rebuild going at 50MB/s right off the bat! Looks like it was the drive. Hope the rebuild goes through without any problems. Thanks again everyone for the help! RMA the drive ASAP. Edit: But first, preclearing the new drive.

I've been monitoring the speed of the rebuild and it has been up to 10MB/s now. However, just now I noticed all activity halted. Here's an updated syslog. Disk3 (dev/sdf) is throwing errors and is now RED. Under maintenance mode, I took the array offline and powered it down. About to head off to work (running late ). What should I do now? Replace Disk3 with another 2TB? Edit: When I get home, I'm thinking to stop the array, unassign dev/sdf, start the array, stop the array, try again and reassign dev/sdf and commence rebuilding again. Am I right to assume the smart report on the drive is OK? syslog-may132013-update1.txt

Thanks for the quick reply! Forgot to mention that I've already reverted to a stock go file and temporarily renamed my plug-ins folders to something else. Good to know that this seems normal. Rebuild speed is up to 5-6 MB/s. Could be better. Will update if anything changes.

Hello! System specs: AMD Sempron 140 AM3 CPU ASUS M4A785T-M/CSM Mobo Corsair 2GB DDR3-1333 Ram Corsair TX650 PSU Unraid 5.0-rc12 - monthly parity checks Parity: 2GB WD Green Cache: 500GB Hitachi Array: 3x2GB WD Green, 1x500GB WD Blue I just recently transplanted my setup into a bigger case (Antec 300 > Zalman MS800) as well as decided to use some 5x3 cages (Supermicro CSE-M35T-1). Only have one powered for now. Ran into some issues. The drive in question (a 2TB Green - sdf) was not originally being detected by unraid. Reseated SATA cables. AHCI enabled in bios (Sata 1-4, Sata 5-6). Finally detected and it shows as orange. Rebuild is going at ~4MB/s. I'm not quite sure what I did wrong. It can't be this slow to rebuild a 2TB drive. 1) Is it the 5x3 cage causing the slow speeds? 2) What could have caused the drive to have its contents invalid - amber/yellow sphere? 3) If the 2TB Green - sdf is dying, can I simply pop in another 2TB in its place and have a go at rebuilding again? Any tips or hints will be greatly appreciated. Thanks! Attached are my syslog and smart status on the drive in question. smart-report-sdf.txt syslog-2013-05-13.txt