billy_rud10

That won't wipe out the data on disks 1-3, right? After the parity rebuild is completed I can add a new 'disk4' and copy the contents to it from the external backup then do a parity resync?

So it looks like I was able to recover everything but one file from disk4. What's the next step? Install a new 1TB disk4 and let parity sync then replace parity with the 3TB and let it rebuild?

I set disk4 back to the parity drive and started the array so that I can copy all the contents to an external. Not sure what to do after that since I essentially have two disks that are failed (parity and disk4), so far everything has copied except one file (currently at 1184/1602 files)

Unfortunately the copy keeps dying after those errors

The last parity check was 2-3 months ago. The failed disk had a head that was scratching the platter.

Okay well it doesn't appear to be working, I've attached the newest syslog. Edit: Just to add to this, ata6 is sdf which is the old parity disk (now set to disk4) syslog.txt

I confirmed the disks were not spinning, once I reverted back to the old GUI it started to work

Yes, I run multiple addons but none of them are currently running (verified with ps). Heres a syslog of what happens when I press start: Dec 28 13:37:05 Tower emhttp: shcmd (8954): /usr/local/sbin/set_ncq sdd 1 &> /dev/null Dec 28 13:37:05 Tower kernel: mdcmd (7): set md_num_stripes 1280 Dec 28 13:37:05 Tower kernel: mdcmd (: set md_write_limit 768 Dec 28 13:37:05 Tower kernel: mdcmd (9): set md_sync_window 384 Dec 28 13:37:05 Tower kernel: mdcmd (10): set spinup_group 0 0 Dec 28 13:37:05 Tower kernel: mdcmd (11): set spinup_group 1 28 Dec 28 13:37:05 Tower kernel: mdcmd (12): set spinup_group 2 26 Dec 28 13:37:05 Tower kernel: mdcmd (13): set spinup_group 3 22 Dec 28 13:37:05 Tower kernel: mdcmd (14): set spinup_group 4 14 Dec 28 13:37:05 Tower emhttp: shcmd (8955): /usr/local/sbin/set_ncq sda 1 &> /dev/null Dec 28 13:37:05 Tower emhttp: shcmd (8956): /usr/local/sbin/set_ncq sdb 1 &> /dev/null Dec 28 13:37:05 Tower emhttp: shcmd (8957): /usr/local/sbin/set_ncq sdc 1 &> /dev/null Dec 28 13:37:05 Tower emhttp: shcmd (8958): /usr/local/sbin/set_ncq sdf 1 &> /dev/null Dec 28 13:37:05 Tower emhttp: shcmd (8959): /usr/local/sbin/set_ncq sde 1 &> /dev/null Dec 28 13:37:05 Tower emhttp: Spinning up all drives... Dec 28 13:37:05 Tower emhttp: shcmd (8960): /usr/sbin/hdparm -S0 /dev/sde &> /dev/null Dec 28 13:37:05 Tower emhttp: swap_dsbl copy not complete Dec 28 13:37:05 Tower emhttp: shcmd (8961): :>/etc/samba/smb-shares.conf Dec 28 13:37:05 Tower kernel: mdcmd (15): spinup 0 Dec 28 13:37:05 Tower kernel: mdcmd (16): spinup 1 Dec 28 13:37:05 Tower kernel: mdcmd (17): spinup 2 Dec 28 13:37:05 Tower kernel: mdcmd (18): spinup 3 Dec 28 13:37:05 Tower kernel: mdcmd (19): spinup 4 Dec 28 13:37:05 Tower emhttp: Restart SMB... Dec 28 13:37:05 Tower emhttp: shcmd (8962): killall -HUP smbd Dec 28 13:37:05 Tower emhttp: shcmd (8963): ps axc | grep -q rpc.mountd Dec 28 13:37:05 Tower emhttp: _shcmd: shcmd (8963): exit status: 1 Dec 28 13:37:05 Tower emhttp: shcmd (8964): rmmod md-mod |& logger Dec 28 13:37:05 Tower emhttp: shcmd (8965): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger Dec 28 13:37:05 Tower kernel: md: unRAID driver removed Dec 28 13:37:05 Tower emhttp: shcmd (8966): udevadm settle Dec 28 13:37:05 Tower kernel: md: unRAID driver 2.1.6 installed Dec 28 13:37:05 Tower emhttp: Device inventory: Dec 28 13:37:05 Tower emhttp: ST31000340NS_9QJ5N0M4 (sda) 976762584 Dec 28 13:37:05 Tower emhttp: ST31000340NS_9QJ6A5JL (sdb) 976762584 Dec 28 13:37:05 Tower emhttp: ST31000340NS_9QJ6C06Y (sdc) 976762584 Dec 28 13:37:05 Tower emhttp: ST3000DM001-1CH166_W1F41GL0 (sdd) 2930266584 Dec 28 13:37:05 Tower emhttp: ST3400620NS_5QH0BZMZ (sde) 390711384 Dec 28 13:37:05 Tower emhttp: ST31000340NS_9QJ686TM (sdf) 976762584 Dec 28 13:37:05 Tower kernel: mdcmd (1): import 0 8,48 2930266532 ST3000DM001-1CH166_W1F41GL0 Dec 28 13:37:05 Tower kernel: md: import disk0: [8,48] (sdd) ST3000DM001-1CH166_W1F41GL0 size: 2930266532 Dec 28 13:37:05 Tower kernel: md: disk0 wrong Dec 28 13:37:05 Tower kernel: mdcmd (2): import 1 8,0 976762552 ST31000340NS_9QJ5N0M4 Dec 28 13:37:05 Tower kernel: md: import disk1: [8,0] (sda) ST31000340NS_9QJ5N0M4 size: 976762552 Dec 28 13:37:05 Tower kernel: mdcmd (3): import 2 8,16 976762552 ST31000340NS_9QJ6A5JL Dec 28 13:37:05 Tower kernel: md: import disk2: [8,16] (sdb) ST31000340NS_9QJ6A5JL size: 976762552 Dec 28 13:37:05 Tower kernel: mdcmd (4): import 3 8,32 976762552 ST31000340NS_9QJ6C06Y Dec 28 13:37:05 Tower kernel: md: import disk3: [8,32] (sdc) ST31000340NS_9QJ6C06Y size: 976762552 Dec 28 13:37:05 Tower kernel: mdcmd (5): import 4 8,80 976762552 ST31000340NS_9QJ686TM Dec 28 13:37:05 Tower kernel: md: import disk4: [8,80] (sdf) ST31000340NS_9QJ686TM size: 976762552 Dec 28 13:37:05 Tower kernel: md: disk4 replaced Dec 28 13:37:05 Tower kernel: mdcmd (6): import 5 0,0 Dec 28 13:37:05 Tower emhttp: shcmd (8967): /usr/local/sbin/emhttp_event driver_loaded Dec 28 13:37:05 Tower emhttp_event: driver_loaded Dec 28 13:37:05 Tower emhttp: shcmd (8968): rmmod md-mod |& logger Dec 28 13:37:05 Tower emhttp: shcmd (8969): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger Dec 28 13:37:05 Tower kernel: md: unRAID driver removed Dec 28 13:37:05 Tower emhttp: shcmd (8970): udevadm settle Dec 28 13:37:05 Tower kernel: md: unRAID driver 2.1.6 installed Dec 28 13:37:05 Tower emhttp: Device inventory: Dec 28 13:37:05 Tower emhttp: ST31000340NS_9QJ5N0M4 (sda) 976762584 Dec 28 13:37:05 Tower emhttp: ST31000340NS_9QJ6A5JL (sdb) 976762584 Dec 28 13:37:05 Tower emhttp: ST31000340NS_9QJ6C06Y (sdc) 976762584 Dec 28 13:37:05 Tower emhttp: ST3000DM001-1CH166_W1F41GL0 (sdd) 2930266584 Dec 28 13:37:05 Tower emhttp: ST3400620NS_5QH0BZMZ (sde) 390711384 Dec 28 13:37:05 Tower emhttp: ST31000340NS_9QJ686TM (sdf) 976762584 Dec 28 13:37:05 Tower kernel: mdcmd (1): import 0 8,48 2930266532 ST3000DM001-1CH166_W1F41GL0 Dec 28 13:37:05 Tower kernel: md: import disk0: [8,48] (sdd) ST3000DM001-1CH166_W1F41GL0 size: 2930266532 Dec 28 13:37:05 Tower kernel: md: disk0 wrong Dec 28 13:37:05 Tower kernel: mdcmd (2): import 1 8,0 976762552 ST31000340NS_9QJ5N0M4 Dec 28 13:37:05 Tower kernel: md: import disk1: [8,0] (sda) ST31000340NS_9QJ5N0M4 size: 976762552 Dec 28 13:37:05 Tower kernel: mdcmd (3): import 2 8,16 976762552 ST31000340NS_9QJ6A5JL Dec 28 13:37:05 Tower kernel: md: import disk2: [8,16] (sdb) ST31000340NS_9QJ6A5JL size: 976762552 Dec 28 13:37:05 Tower kernel: mdcmd (4): import 3 8,32 976762552 ST31000340NS_9QJ6C06Y Dec 28 13:37:05 Tower kernel: md: import disk3: [8,32] (sdc) ST31000340NS_9QJ6C06Y size: 976762552 Dec 28 13:37:05 Tower kernel: mdcmd (5): import 4 8,80 976762552 ST31000340NS_9QJ686TM Dec 28 13:37:05 Tower kernel: md: import disk4: [8,80] (sdf) ST31000340NS_9QJ686TM size: 976762552 Dec 28 13:37:05 Tower kernel: md: disk4 replaced Dec 28 13:37:05 Tower kernel: mdcmd (6): import 5 0,0 Dec 28 13:37:05 Tower emhttp: shcmd (8971): /usr/local/sbin/emhttp_event driver_loaded Dec 28 13:37:05 Tower emhttp_event: driver_loaded Dec 28 13:37:07 Tower emhttp: shcmd (8972): rmmod md-mod |& logger Dec 28 13:37:07 Tower emhttp: shcmd (8973): modprobe md-mod super=/boot/config/super.dat slots=6 |& logger Dec 28 13:37:07 Tower kernel: md: unRAID driver removed Dec 28 13:37:07 Tower emhttp: shcmd (8974): udevadm settle Dec 28 13:37:07 Tower kernel: md: unRAID driver 2.1.6 installed Dec 28 13:37:07 Tower emhttp: Device inventory: Dec 28 13:37:07 Tower emhttp: ST31000340NS_9QJ5N0M4 (sda) 976762584 Dec 28 13:37:07 Tower emhttp: ST31000340NS_9QJ6A5JL (sdb) 976762584 Dec 28 13:37:07 Tower emhttp: ST31000340NS_9QJ6C06Y (sdc) 976762584 Dec 28 13:37:07 Tower emhttp: ST3000DM001-1CH166_W1F41GL0 (sdd) 2930266584 Dec 28 13:37:07 Tower emhttp: ST3400620NS_5QH0BZMZ (sde) 390711384 Dec 28 13:37:07 Tower emhttp: ST31000340NS_9QJ686TM (sdf) 976762584 Dec 28 13:37:07 Tower kernel: mdcmd (1): import 0 8,48 2930266532 ST3000DM001-1CH166_W1F41GL0 Dec 28 13:37:07 Tower kernel: md: import disk0: [8,48] (sdd) ST3000DM001-1CH166_W1F41GL0 size: 2930266532 Dec 28 13:37:07 Tower kernel: md: disk0 wrong Dec 28 13:37:07 Tower kernel: mdcmd (2): import 1 8,0 976762552 ST31000340NS_9QJ5N0M4 Dec 28 13:37:07 Tower kernel: md: import disk1: [8,0] (sda) ST31000340NS_9QJ5N0M4 size: 976762552 Dec 28 13:37:07 Tower kernel: mdcmd (3): import 2 8,16 976762552 ST31000340NS_9QJ6A5JL Dec 28 13:37:07 Tower kernel: md: import disk2: [8,16] (sdb) ST31000340NS_9QJ6A5JL size: 976762552 Dec 28 13:37:07 Tower kernel: mdcmd (4): import 3 8,32 976762552 ST31000340NS_9QJ6C06Y Dec 28 13:37:07 Tower kernel: md: import disk3: [8,32] (sdc) ST31000340NS_9QJ6C06Y size: 976762552 Dec 28 13:37:07 Tower kernel: mdcmd (5): import 4 8,80 976762552 ST31000340NS_9QJ686TM Dec 28 13:37:07 Tower kernel: md: import disk4: [8,80] (sdf) ST31000340NS_9QJ686TM size: 976762552 Dec 28 13:37:07 Tower kernel: md: disk4 replaced Dec 28 13:37:07 Tower kernel: mdcmd (6): import 5 0,0 Dec 28 13:37:07 Tower emhttp: shcmd (8975): /usr/local/sbin/emhttp_event driver_loaded Dec 28 13:37:07 Tower emhttp_event: driver_loaded

Well I ticked the checkbox and hit start, all it did was reload the page, nothing is happening on the server.

So one of the disks in my unraid server just failed (red/disabled). All the disks in the server are currently 1TB, including parity. I have a 3TB I've been meaning to replace the parity with so now seems like the time to do it with the swap-disable feature found on the wiki. If I'm understanding this correctly all I need to do is install the new disk, switch the parity to the new 3TB and then switch disk 4(the previous failed disk) to the current parity? When doing that I see the following: http://i.imgur.com/paaQcWk.png

Guess it's just a matter of figuring out what I want. I have a dozen spare drives (1TB/2TB) that I want to put to use eventually. I guess the deciding factor is really how external enclosures will play into this when it comes time to expand. If Unraid plays nice with USB 3.0 then I'll go with the mitx setup, if it doesn't then I'll look into an matx setup for the extra expansion slots so that I can use eSata. The reason I'm concerned about the USB3/esata connection is that I will need to use an external enclosure (towerraid jbod) one day due to capacity (unless drive prices drop considerably). Way to many decisions.. I remember why I stopped building computers now...

Thanks Gary, I'm still up the air about a case (thinking the LI PC-A04B due to the drive space). I'm also thinking another motherboard that can support 2 expansion cards for esata would be better.

Thanks for the feedback. While checking if I could cut the cost back a little bit I found the following: Case: LIAN LI PC-A04B - http://www.newegg.com/Product/Product.aspx?Item=N82E16811112316 Motherboard: ASUS A85XM-A - http://www.newegg.com/Product/Product.aspx?Item=N82E16813131972 CPU: AMD Athlon X2 340 - http://www.newegg.com/Product/Product.aspx?Item=N82E16819113330 Looks like I can cut back $77 if I go with those, downside is less USB 3.0 slots and a bigger case (4" taller and longer).

I'm currently using an HP N40L as my Unraid server which has been working well for over a year but I think I need a little more processing power due to plex transcoding. Current specs Machine: HP N40L Ram: 4GB Drives: 5x 1TB and an esata 450gb for cache Addons Plex SabNZBd Sickbeard CouchPotato Budget: $450 Drive Requirements: 6+ 3.5" with the ability to expand (maybe with a JBOD enclosure?) Case: Lian Li PC-Q25B - http://www.newegg.com/Product/Product.aspx?Item=N82E16811112339 PSU: SILVERSTONE ST45SF - http://www.newegg.com/Product/Product.aspx?Item=N82E16817256063 Motherboard: ASUS H87I-PLUS - http://www.newegg.com/Product/Product.aspx?Item=N82E16813132032 CPU: Intel Pentium G3220 - http://www.newegg.com/Product/Product.aspx?Item=N82E16819116950 RAM: Crucial Ballistix 8GB (2 x 4GB) - http://www.newegg.com/Product/Product.aspx?Item=N82E16820148560 I'm open to suggestions regarding all the components listed above.

$160 per drive, I'm not able to find them on sale for less than 100/ea. I already replied to your PM.