July 9, 20178 yr Hi, I was transferring 1.5TB of data disk to disk using midnight commander when the system hung at 97%! The console was locked WebGui hung nothing I could do except hit the power button! :-( on reboot I cancelled the parity check as I have 1.5TB (ish) of data which is the same on 2 disks and I have started Midnight commander again to replace only of file size differs. My question is where do I stand with parity? what should I do now? Many Thanks
July 10, 20178 yr Community Expert You should run a parity check since there could be sync errors due to the unclean shutdown.
July 10, 20178 yr Author I have manually deleted the duplicate files on the source disk now the copy has finished, is it ok to run a parity check now? I am wondering if it will rebuild the files I have just deleted? Cheers
July 10, 20178 yr Yes, run your parity check. You can expect it will find some sync errors, so you should run in correcting mode. Better to run at a time array will be pretty quiet, as parity check will be generating a lot of I/O to all disks. I'd be concerned about your hard server crash. That is not normal, even with a large copy.
July 10, 20178 yr 13 hours ago, mbc0 said: is it ok to run a parity check now? I am wondering if it will rebuild the files I have just deleted? This sounds like you have a misunderstanding of how parity works. I suggest reading the link in bjp999's sig about what is parity, this wiki article and if you have more questions, ask. Parity does NOT have any of your files individually protected, it only recreates an entire disk, full, empty, formatted, unformatted, corrupt, whatever. You need to have a basic understanding of what is and isn't protected by parity so you don't mess up and think parity is going to save you.
July 10, 20178 yr Author ok, yes it makes sense now, it was a half asleep question I am afraid, thanks for the clarification! The reason for the crash was a 5 year old SSD that has now twice disappeared as an unassigned device, the first time I wondered if it was cable related but a week later after connecting to new power & sata cables it has done it again, so time to leave it out of the server
Archived
This topic is now archived and is closed to further replies.