bennyboi Posted September 19, 2016 Share Posted September 19, 2016 Guys, I have had my server running for two years, but all of a sudden i am getting read-only file system errors. I have ran reiserfsck on all the drives and apparently the SB is damaged on all. I am wary of doing anything as i did it on one disk and lost all of my data. (yes i followed the unpaid guide) please could someone advise. Thanks Ben Quote Link to comment
JorgeB Posted September 19, 2016 Share Posted September 19, 2016 What was the command you used to run reiserfsck on say disk1? Quote Link to comment
bennyboi Posted September 19, 2016 Author Share Posted September 19, 2016 What was the command you used to run reiserfsck on say disk1? reiserfsck --rebuild-tree /dev/sdd/ As per the instructions. Thanks Ben Quote Link to comment
Squid Posted September 19, 2016 Share Posted September 19, 2016 The instructions usually state to run it against /dev/md1 but I'd wait for Johnnie to pipe back in before doing anything else as he is one of the resident experts Sent from my SM-T560NU using Tapatalk Quote Link to comment
JorgeB Posted September 19, 2016 Share Posted September 19, 2016 Those are not the instructions, you have to use the md device, e.g., for disk1: reiserfsck --check /dev/md1 https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later Quote Link to comment
JorgeB Posted September 19, 2016 Share Posted September 19, 2016 If the disks are unassigned or you don't care about maintaining parity you can use the sd* identifier but you have to specify the partition, e.g.: reiserfsck --check /dev/sdd1 Quote Link to comment
bennyboi Posted September 19, 2016 Author Share Posted September 19, 2016 Those are not the instructions, you have to use the md device, e.g., for disk1: reiserfsck --check /dev/md1 https://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later Im such an idiot... i can't read! Thanks guys... Why would all SB's corrupt though? is this going to be an on going issue? Quote Link to comment
JorgeB Posted September 19, 2016 Share Posted September 19, 2016 It's normal to get the superblock error if running reiserfsck using the sd* identifier without the partition, like you did. Also don't forget to always start with reiserfsck --check, only use the other options if told by reiserfsck. Quote Link to comment
bennyboi Posted September 19, 2016 Author Share Posted September 19, 2016 It's normal to get the superblock error if running reiserfsck using the sd* identifier without the partition, like you did. Also don't forget to always start with reiserfsck --check, only use the other options if told by reiserfsck. Johhnie you are a legend i believe it is fixed. thank you so much Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.