June 25, 20215 yr I recently had 2 drives fail within hours of each other that seems to have corrupted the filesystem on one of the drives. As expected the rebuild from parity did not fix the file system corruption and left the disk in read-only mode. I restarted the array in maintenance mode and ran reiserfsck --check /dev/md10 . The results were: 13 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Wed Jun 23 11:32:32 2021 ########### I then ran reiserfsck --rebuild-tree /dev/md10. As of today ( 2 days later) it is still running and the last update was Flushing..finished Syncing..finished It has been at this state for at least 8 hours now. I can't get to the web GUI to see if the read/write count on the drive is changing but looking at this for last hour I don't see any change. With the my servers plugin forcing ssl through unraid.net, starting a resiser check kills the gui for me. root@Tower:/proc/30353# cat io rchar: 5155039685281 wchar: 11886923136 syscr: 1258554627 syscw: 3286164 read_bytes: 5136389296128 write_bytes: 10541928448 cancelled_write_bytes: 0 Should kill the process and restart the array and see what it looks like or should I continue to wait it out. This is an 8TB Western Digital but over 2 days for a fsck seems excessive to me. Thanks in advance. And I know I should convert this to XFS but I need to get things working again before starting that process. Tony
Archived
This topic is now archived and is closed to further replies.