wazkaren

Thanks.

It seems I was hasty on shutting down my system. It wasn't actually locked up, I have a bad drive and I think it was retrying to read or write the disk. Seeing these errors: » reallocated_sector_ct=12000 » reported_uncorrect=1081 » current_pending_sector=52736 » offline_uncorrectable=52736 » ata_error_count=1081 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 40938 284536536 I assume at this point the only thing to do is replace the drive and let it rebuild? Is there anyway to tell if any files are corrupted after the rebuild completes and system is back up and running?

It's been a few years since I've been to this forum and I'm not sure where to start looking. My unraid server has been running without issue for several years. Last night it locked up. When I restarted the server a parity check started and has found 8 errors so far. Can someone point me to info on this website on how to deal with parity errors? I'm thinking that I now have one or more files on my server that are now corrupted. Before I ask specific questions I wanted to do some catching up but there is a lot of info on this site. Is there a faq that deals with parity errors? Thanks, Greg

Turns out I'm not really awake yet. I double checked and the array WAS started when I checked to see if the files are there. Glad I listened to you guys and did not start a rebuild. I still can't figure out what's wrong the the drive though. Smart test passes

Ok, thanks. My current processor is not 64-bit. I'm looking into upgrading so I can move to the latest version of unRaid

Thanks. I did replace the drive 2 weeks ago so bad cabling does seem likely. When I checked the contents of the drive the array was stopped (I checked from a the shell). The drive is assigned to it's slot so I'm puzzled as to why the rebuild button is missing? I will double check the cabling and reboot. And thanks for the warning about not rebuilding the parity disk. Thanks, Greg

I have a drive that has been disabled (red ball). But it appears to be healthy, no smart errors, and data appears intact on the drive. I understand that once the drive is red balled I have to rebuild the array. But there is no option to do a parity rebuild, only start/stop array and reboot. I'm not sure what to do next. Any thoughts? I attached the syslog Thanks, Greg syslog-2017-01-28.txt