Topic: SOLVED- GParted - fsck Progress
Hi folks, I have a situation I hope you can help with. I did a stupid thing and incorrectly replaced a bad drive in a RAID5 array (LSI 9260-8i) . I didn't remove and replace it correctly and probably corrupted the stripe. I went back and replaced the drive correctly but the files were not accessible afterwards. I decided to boot systemrescuecd and run an fsck check from GParted GUI before I consider the data lost. I'm not much of a Linux admin which is why I used the GUI. The file system is ext4 and just under 12TB so I expected the fsck to take a long time. I'm at 36hrs and it's still chugging along. The task manager shows the PID using ~50% CPU with RSS around 200MIB. The command the GUI ran was "e2fsck -f -y -v -C 0 /dev/sdb1"
There was a progress bar but when I opened another window it stopped refreshing and is blank. I'm guessing it's because CPU is busy and not refreshing the screen.
1) I can let the fsck run a week or more if needed. At what point do I kill the process?
2) Would killing the process and restarting cause further corruption?
3) Is there a CLI command that could give insight into the current operations without killing it?