on boot: fsck.reiserfs /dev/hda3 failed (status 0x10)
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
on boot: fsck.reiserfs /dev/hda3 failed (status 0x10)
SuSE 9.0, been running maybe a year with no problems, used YaST to install BIND and DHCP stuff, had DHCP working fine, had done nothing with BIND yet.
Rebooted and got message that fsck of / had failed, filesystem not clean, run fsck manually. Running fsck runs fsck.reiserfs, shows no corruption, so I reboot, get same error.
Looking more closely at boot messages, I see that it ran a check prior to this during boot and said that filesystem was clean, then a few lines later it does it again and says it's not clean. In between there's a message saying modprobe can't load (or find?) module sysfs, but I don't know if that's normal or not. Not clear if that's a cause or just a symptom.
Ran fsck.reiserfs --check and it looks clean, also tried --fix-fixable with no change. Not sure I want to do a --rebuild-tree unless absolutely necessary.
Based on recommendation from other messages I've run across, also tried setting fstab for / to 0 0 but it still behaves the same.
A co-worker suggests that a problem with an LVM volume on the box may cause boot problems, so he recommends commenting out that volume in the fstab and see if the box boots. I'll try that tonight, look for fixes on LVM if it boots OK.
No luck, commenting out LVM volume didn't help. Also ran fsck on /usr (also reiserfs), still same results on boot. Expect I'll have to go learn the boot process and find out why it checks / twice, fails second time. Any help would be welcome!
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
From my experience I'd advise a backup of all data you still can reach. I could not save my system (and tried too late for the data) under the same conditions (ReiserFS on LVM)
OK, I got fed up with screwing around with it and saved everything I needed onto another physical drive and then torched the boot drive, installed SuSE 10.0 on it also. Now I just have to re-figure out how to automount the LVM volume on boot, and learn how to use syslog-ng to remote log my firewall box instead of syslogd that I was using before.
Distribution: openSuSE Tumbleweed-KDE, Mint 21, MX-21, Manjaro
Posts: 4,629
Rep:
Quote:
Originally posted by ahedler OK, I ... saved everything I needed onto another physical drive and then torched the boot drive, installed SuSE 10.0 on it also.
Yeah, I know the feeling
Quote:
Originally posted by ahedler Now I just have to re-figure out how to automount the LVM volume on boot, ...
Huh? Usually SuSE does that for you long since (version SuSE 6.n)?!? Perhaps you didn't choose "Expert Mode" during install, but that's false modesty . When you do that you get a screen with options to manage LVM, Raid and all the physical layout mountpoints of your drives, it lets you integrate existing / old system layouts including LVM no further worries necessary...
Quote:
Originally posted by ahedler and learn how to use syslog-ng to remote log my firewall box instead of syslogd that I was using before.
Can't help you there, no personal experience on this field.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.