August 21, 201213 yr Hi, I was in the process of swapping out my disk4 out without losing parity as per the instructions here: http://lime-technology.com/forum/index.php?topic=2591.0 I have done this before but today, I had to re-do the command because I did not set the block size to 2048k which means it would take forever. Upon re-entering the command, I made the typo and set the disk2 instead of disk 4. In panic, I rushed over to the box and shut it down manually. Upon boot-up, I can tell it was making writes to the parity, disk 3 and disk 2 and it took a while for the array to be ready. So how can I recover from this? I don't have data in disk 4 but I definitely have some at disk2. Any help would certainly be appreciated. syslog-2012-08-21.txt
August 21, 201213 yr Author just checked and it's still "trying" to stop the array. I've attached a syslog capture. syslog-2012-08-21_b.txt
August 21, 201213 yr Author I managed to issue a reboot command and now it's doing a parity check: Uploaded with ImageShack.us Here's what I'm gonna do, I'm gonna re-do the swap out with disk4 since there is no data on it anyways without losing parity and minimize my issues. Any comments on how should I fix the remaining unformatted disk with data after that?
Archived
This topic is now archived and is closed to further replies.