| View previous topic :: View next topic |
| Author |
Message |
stevem
n00b
Joined: 22 Oct 2003
Posts: 17
Location: Ottawa, ON, Canada
|
 Posted: Sat Oct 25, 2003 3:09 am Post subject: new install - reiserfs partition problems at boot |
 |
|
Hey folks,
Hopefully someone will be able to point me in the right direction. I've searched the forums, but haven't seen anyone else with this particular issue:
Every single time I boot, I get the following:
| Code: | Reiserfs super block in block 16 on 0x303 of format 3.6 with standard journal
Blocks (total/free) 29752380/28422177 by 4096 bytes
Filesystem is NOT cleanly umounted
Partition /dev/hda3 is mounted with write permissions cannot check
* Fsck could not correct all errors, manual repair needed |
Then I get the option to enter the root password to fix it up, or ctrl-d to continue normal boot. When I continue normal boot, the system comes up with no other issues.
Any help appreciated.
Steve |
|
| Back to top |
|
 |
deepthought
Guru
Joined: 04 Apr 2003
Posts: 321
Location: icbm://5131''N:0710''E
|
| Posted: Sat Oct 25, 2003 11:31 am Post subject: |
|
|
You might want to search the WWW on howto repair broken reiser filesystems.
In general, login in single user mode (as stated in the error message) and run reiserfsck; it will tell you what to do.
Regards,
Alexander
_________________
Out of loyalty to its disregarded comrades, this message feels free to ignore the reader.
Registered Linux User #317705 |
|
| Back to top |
|
|
caslca
Tux's lil' helper
Joined: 24 Aug 2003
Posts: 85
|
| Posted: Sat Oct 25, 2003 2:47 pm Post subject: |
|
|
or just boot off the cd, as soon as u get the prompt, run reiserfsck
If that says that it can't repair until u rebuild the tree, run:
reiserfsck --rebuild-tree /dev/hda1 (or whatever your partition is) |
|
| Back to top |
|
|
mike4148
l33t
Joined: 09 Sep 2003
Posts: 641
|
| Posted: Sat Oct 25, 2003 4:41 pm Post subject: |
|
|
Actually, it shouldn't be a filesystem corruption problem. reiserfsck is failing (which Gentoo assumes is because of
filesystem problems) because the root filesystem is mounted read/write instead of read-only, which is what it is supposed to
be on boot. I just wish I had some idea of why this is happening.... Did you install with ACCEPT_KEYWORDS="~x86"
(maybe it's a flaky unstable version of the boot scripts or mount)? Maybe you could try another emerge sync followed by
emerge -u system (i.e., maybe it's a problem with some stable version of the boot scripts).
One more thing to check -- make sure that the mount options for your root filesystem (in /etc/fstab) contain either noatime
or defaults (nothing else is needed for an ordinary configuration; noatime makes things a little faster, but both work). For
example, here's my line:
| Code: | | /dev/hdc3 / reiserfs noatime 0 0 |
In particular, make sure that the options do not contain "rw". I'm not sure, but that might break the read-only mount at
boot. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Installing Gentoo
