August 31, 20178 yr Hi all! I have been having SMART errors with one of my drives (disk 11). I probably should have just replaced it straight away but I instead decided to upgrade a smaller empty drive (disk 7) and start copying the data over from disk 11 via unBALANCE. The reason I did it this way was I figured that if I got all of the data off, I could format disk 11 as XFS so that when I replaced the disk it would be in the correct format. Thinking back, I should have just replaced disk 11 leaving ReiserFS and then replaced disk 7 and done the copy and format. *sigh* unBALANCE was in the middle of the move from disk 11 to disk 7 last night, about 50% through, when the monthly Parity Sync kicked off. I am disappointed that I didn't even think of the monthly parity check when I started the unBALANCE move. This morning, I cannot access the web gui, cannot SSH into the box, and none of my dockers are accessible. I have IPMI so I am able to see that the server has not kernel panic'd. unBALANCE web gui is still accessible though not progressing in its file move. I cannot login to the server even via IPMI (see attached pic). At this point, should I just restart the server? Should I be concerned about any damage to the parity of the array? I should also mentioned that I excluded Drive 11 from all user shares before starting the process since I didnt want any data getting written to it during the move. The new replacement disk for disk 11 will be here today but I assume before anything, I will at the very least need to do a parity check before replacing the drive. Thank you! Edited August 31, 20178 yr by savestheday
Archived
This topic is now archived and is closed to further replies.