December 28, 201312 yr 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
December 28, 201312 yr I haven't actually done the procedure myself, but from what I can see, you are good to go. You may want to wait for someone who actually has first hand experience, but if it were me, I'd go ahead.
December 28, 201312 yr 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 Everything looks like you are about to start the swap-disabled-disk process. You'll need to check the checkbox and press start. It will take some number of hours for the initial copy to occur as unRAID will need to write the entire 3TB drive. Even if it can reach 100MB/s that will be 6GB per minute. (3000GB / 6 = 500 minutes, or 8.33 hours ) It might take a bit longer if you cannot reach 100MB/s sustained read/write speed. Diring this initial time I seem to remember others reporting the array is off-line and not usable. I remember trying it long ago on a 4.X release and the array was usable during the copy. You'll have to let us know what it does for you. It may not respond on the web-management console at all during this initial copy. (you'll have to let us know) Once the initial copy of parity is complete, the array should come back online as the failed disk is re-constructed. Again, it will take about the same time, although it might be less since the target drive is a 1TB drive. Joe L. Good luck and report back every once in a while.
December 28, 201312 yr Author Well I ticked the checkbox and hit start, all it did was reload the page, nothing is happening on the server.
December 28, 201312 yr Well I ticked the checkbox and hit start, all it did was reload the page, nothing is happening on the server. Are you running any add-ons? At least one makes it impossible to partition a disk. Regardless, there are probably clues in the syslog. Attach a copy of your syslog to your next post.
December 28, 201312 yr Author 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
December 28, 201312 yr 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 Even if not running, some replace system libraries with different versions. Also, some features do not work with the "improved" GUI Best to revert to entirely clean/stock unRAID... You do seem to have at least one entry in the syslog showing the copy is in progress... Are you sure that the disks are not spinning? (I would leave it alone for about 8-10 hours and assume it is...) As I said earlier, you'll probably see nothing on the web-interface for some time. Joe L.
December 28, 201312 yr Author Even if not running, some replace system libraries with different versions. Also, some features do not work with the "improved" GUI Best to revert to entirely clean/stock unRAID... You do seem to have at least one entry in the syslog showing the copy is in progress... Are you sure that the disks are not spinning? (I would leave it alone for about 8-10 hours and assume it is...) As I said earlier, you'll probably see nothing on the web-interface for some time. Joe L. I confirmed the disks were not spinning, once I reverted back to the old GUI it started to work
December 28, 201312 yr Author 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
December 28, 201312 yr 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) Well, ata6 is showing a lot of un-readable sectors (media errors) as you attempt to copy from it to the new parity disk it is constantly re-trying to read the un-readable sectors. Did you perform periodic parity checks? (They might have detected the un-readable sectors) So... basically, the copy is working.... but having difficulty. What symptoms did the disk that failed exhibit? Joe L.
December 29, 201312 yr Author The last parity check was 2-3 months ago. The failed disk had a head that was scratching the platter.
December 29, 201312 yr The last parity check was 2-3 months ago. The failed disk had a head that was scratching the platter. That is a pretty clear indication of failure. About all you can do is to let the copy continue, as slowly as it might be. (Might also try copying any "precious" files off the emulated failed disk to another disk.) Joe L.
December 29, 201312 yr Author That is a pretty clear indication of failure. About all you can do is to let the copy continue, as slowly as it might be. (Might also try copying any "precious" files off the emulated failed disk to another disk.) Joe L. Unfortunately the copy keeps dying after those errors
December 29, 201312 yr It looks like disk4 is lost. There are many Windows and Linux recovery options you can try. Try SystemRescueCD for a live disk. It sounds like the disk is toast; however.
December 29, 201312 yr Author 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)
December 30, 201312 yr Author 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?
December 30, 201312 yr Set new config, Utils->New Config. Assign the data disks as desired. You can leave out disk 4. Assign the new 3T parity drive and start the array.
December 30, 201312 yr Author Set new config, Utils->New Config. Assign the data disks as desired. You can leave out disk 4. Assign the new 3T parity drive and start the array. 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?
December 30, 201312 yr A New Config won't cause any changes to your data drives -- and since you're currently without parity, it's far easier to do this to migrate up to a larger parity drive. Just set the New Config; then let it do an initial parity sync; then do a parity check when it's finished to confirm all went well. Then you can add any new disks you want, and copy the data you recovered back to the array.
Archived
This topic is now archived and is closed to further replies.