Hi: I have a Suse 9.1 box that has suddenly broke. It gets stuck with a message that I need to check the filesystem, but as you will see, there is apparently nothing wrong with the filesystem: The booting stops here and the following is a log of what I've done to fix it, without success: ... Loading console font lat9w-16.psfu -m trivial CK ... done fsck failed. Please repair manually and reboot. The root filesystem is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount,rw / Attention: Only CONTROL-D will reboot the system in this maintenance mode. Shutdown or reboot will not work. Give root password for login: # mount /dev/sda2 on / type reiserfs (rw,acl,user_xattr) /dev/sda2 on / type reiserfs (rw,acl,user_xattr) # fsck /dev/sda2 fsck 1.34 (25-Jul-2003) reiserfsck 3.6.13 (2003 www.namesys.com) ... Partition /dev/sda2 is mounted with write permissions, cannot check it fsck.reiserfs /dev/sda2 failed (status 0x10). Run manually! # mount -n -o remount,ro / # fsck /dev/sda2 fsck 1.34 (25-Jul-2003) reiserfsck 3.6.13 (2003 www.namesys.com) ... Partition /dev/sda2 is mounted with write permissions, cannot check it fsck.reiserfs /dev/sda2 failed (status 0x10). Run manually! # mount /dev/sda2 on / type reiserfs (rw,acl,user_xattr) /dev/sda2 on / type reiserfs (rw,acl,user_xattr) Ok, so we see that the system tells me it is RO and I should check, but it is really RW and I can't check. Nor can I remount it RO. And there is the strange fact that mount shows it mounted twice. So I run the rescue system from CD: Rescue login: root Rescue:~# fsck /dev/sda2 ... reiserfsck --check started ... Replaying journal.. Reiserfs journal '/dev/sda2' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished Comparing bitmaps..finished Checking semantics tree: finished No corruptions found There are on the filesystem: Leaves 78819 Internal nodes 522 Directories 22794 Other files 303921 Data block pointers 9007004 (1123 of them are zero) Safe link 0 ... Reiserfsck finished Rescue:~# So that's it. There appears to be nothing wrong. Furthermore, I can mount it from the rescue and all the directories appear to be their, and the files in a few of the dirs I browsed. How to get Suse to stop getting stuck? And why does it say it's mounted ro when it is really rw? Thanks for assistance. -- ____________________________________ Christopher R. Carlen Principal Laser/Optical Technologist Sandia National Laboratories CA USA crcarle@sandia.gov
On Fri, 2005-01-28 at 08:35 -0800, Christopher Carlen wrote:
Hi:
I have a Suse 9.1 box that has suddenly broke. It gets stuck with a message that I need to check the filesystem, but as you will see, there is apparently nothing wrong with the filesystem:
# mount /dev/sda2 on / type reiserfs (rw,acl,user_xattr) /dev/sda2 on / type reiserfs (rw,acl,user_xattr)
is /dev/sda2 listed twice in /etc/fstab?
On Friday 28 January 2005 06:35, Christopher Carlen wrote:
Hi:
I have a Suse 9.1 box that has suddenly broke. It gets stuck with a message that I need to check the filesystem, but as you will see, there is apparently nothing wrong with the filesystem:
The booting stops here and the following is a log of what I've done to fix it, without success:
... Loading console font lat9w-16.psfu -m trivial CK ... done fsck failed. Please repair manually and reboot. The root filesystem is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount,rw / Attention: Only CONTROL-D will reboot the system in this maintenance mode. Shutdown or reboot will not work.
So that's it. There appears to be nothing wrong. Furthermore, I can mount it from the rescue and all the directories appear to be their, and the files in a few of the dirs I browsed.
How to get Suse to stop getting stuck?
And why does it say it's mounted ro when it is really rw?
Thanks for assistance. -- ____________________________________ Christopher R. Carlen Principal Laser/Optical Technologist Sandia National Laboratories CA USA crcarle@sandia.gov
Hello Christopher, I had the exact same problem not too long ago and with a little help from the list I solved it. There is a thread that you need to see. In Konqueror do this: gg:lists site:lists.suse.com suse-linux-e "Booting Problem" to see the complete thread. Here is the text of the one marked [SOLVED] that had the solution for me: There were two problems. On the second harddrive hdb5 was always being recognized by fsck as a swap partition (which it originally was) even though I would reformat it as other partitions. So finally I deleted it and rebooted, still into the same problem. So I checked my external firewire drive. Fsck failed on /dev/sda1; said there was no such device, so I deleted the entry in /etc/fstab, rebooted and I am now back in business! Thank You Anders and Patrick, Bruce, C.Richard, Sid, peter, ptilopteri and Carl! Success at last! I couldn't done it without you! Jerome I hope this helps, Jerome
The Friday 2005-01-28 at 08:35 -0800, Christopher Carlen wrote:
So that's it. There appears to be nothing wrong. Furthermore, I can mount it from the rescue and all the directories appear to be their, and the files in a few of the dirs I browsed.
How to get Suse to stop getting stuck?
I'd guess there is something wrong in the fstab file. Probably you have listed some partition with the wrong filesystem, or it is no longer there.
And why does it say it's mounted ro when it is really rw?
On the contrary, it complains that it is mounted rw, and thus refuses to check it. You mounted it rw your self first thing - see:
Partition /dev/sda2 is mounted with write permissions, cannot check it ______________________________________^^^^^
_write_ permissions, ie, RW.
fsck.reiserfs /dev/sda2 failed (status 0x10). Run manually! # mount /dev/sda2 on / type reiserfs (rw,acl,user_xattr) /dev/sda2 on / type reiserfs (rw,acl,user_xattr) ________________________________^^
It seems you have a double entry for sda2. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The Friday 2005-01-28 at 08:35 -0800, Christopher Carlen wrote:
So that's it. There appears to be nothing wrong. Furthermore, I can mount it from the rescue and all the directories appear to be their, and the files in a few of the dirs I browsed.
How to get Suse to stop getting stuck?
I'd guess there is something wrong in the fstab file. Probably you have listed some partition with the wrong filesystem, or it is no longer there.
Yes, I disconnected the drive with that partition.
And why does it say it's mounted ro when it is really rw?
On the contrary, it complains that it is mounted rw, and thus refuses to check it. You mounted it rw your self first thing - see:
Partition /dev/sda2 is mounted with write permissions, cannot check it
______________________________________^^^^^
_write_ permissions, ie, RW.
No, that was the ouput from fsck, which correctly says that the /dev/sda2 partition is mounted RW. What I was complaining about is the fact that the startup scripts reported that the partition was mounted RO, so that it could be checked. See: ... fsck failed. Please repair manually and reboot. The root filesystem is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount,rw / Attention: Only CONTROL-D will reboot the system in this maintenance mode. Shutdown or reboot will not work. Give root password for login: This is normally what happens when a root filesystem is inconsistent when booting, and so the boot scripts correctly halt the system and request the user to manually run fsck, which must be done with the problem partition mounted RO. That is what I tried to do, thinking that there really was a problem, and that the problem partition was RO. But the / was actually mounted RW. *I* did not mount / RW. The *boot scripts* did, and then incorrectly reported that it was RO and needed checking.
fsck.reiserfs /dev/sda2 failed (status 0x10). Run manually! # mount /dev/sda2 on / type reiserfs (rw,acl,user_xattr) /dev/sda2 on / type reiserfs (rw,acl,user_xattr)
________________________________^^
It seems you have a double entry for sda2.
No, it was something else. See my other reply. Thanks for your input and interest. Good day! -- _____________________ Christopher R. Carlen crobc@sbcglobal.net SuSE 9.1 Linux 2.6.5
The Saturday 2005-01-29 at 17:31 -0800, Chris Carlen wrote:
And why does it say it's mounted ro when it is really rw?
On the contrary, it complains that it is mounted rw, and thus refuses to check it. You mounted it rw your self first thing - see:
Partition /dev/sda2 is mounted with write permissions, cannot check it
______________________________________^^^^^
_write_ permissions, ie, RW.
No, that was the ouput from fsck, which correctly says that the /dev/sda2 partition is mounted RW. What I was complaining about is the fact that the startup scripts reported that the partition was mounted RO, so that it could be checked. See:
... fsck failed. Please repair manually and reboot. The root filesystem is currently mounted read-only. To remount it read-write do: bash# mount -n -o remount,rw / Attention: Only CONTROL-D will reboot the system in this maintenance mode. Shutdown or reboot will not work. Give root password for login:
It seemed to me that you had typed mount command, at what I thought was the "bash# " prompt. My mistake.
This is normally what happens when a root filesystem is inconsistent when booting, and so the boot scripts correctly halt the system and request the user to manually run fsck, which must be done with the problem partition mounted RO. That is what I tried to do, thinking that there really was a problem, and that the problem partition was RO.
Yes, that's correct. It is done by '/etc/init.d/boot.rootfsck', which on success remounts "/" RW. However, now that I think, on every occasion I had this problem with a reiserfs, I had to reboot from the rescue CD; from HD it was impossible to fsck.
But the / was actually mounted RW. *I* did not mount / RW. The *boot scripts* did, and then incorrectly reported that it was RO and needed checking.
Funny. Ah.... perhaps... an idea. On a second phase, it is the job of '/etc/init.d/boot.localfs' to check the rest of the partitions, and when it runs, "/" is already RW, I think - yes, it is: case "$1" in start) # rootfs is mounted rw, lvm et al should be up now Then it runs fsck, and if the error is greater than 3, it does this: ... echo "fsck failed. Please repair manually and reboot. The root" echo "file system is currently mounted read-only. To remount it" echo "read-write do:" echo echo " bash# mount -n -o remount,rw /" That's the message you saw, isn't it? But at that point root is RW, and that matches what you saw. This second script is wrong. There are two mistakes: one is to wrongly report the RO status (because the script is derived from the first one). The other is misleading you to think that the root filesystem is faulty, when it is some other partition. Ah! I see it clear, it happened to me as well when I deleted a partition and forgot to remove it from the fstab file. I got the same error as you did.
No, it was something else. See my other reply.
Yes, I saw it. It matches what I said on my first paragraph: |> I'd guess there is something wrong in the fstab file. Probably you have |> listed some partition with the wrong filesystem, or it is no longer |> there.
Thanks for your input and interest.
Welcome :-) -- Cheers, Carlos Robinson
Carlos E. R. wrote:
Funny.
Ah.... perhaps... an idea.
On a second phase, it is the job of '/etc/init.d/boot.localfs' to check the rest of the partitions, and when it runs, "/" is already RW, I think - yes, it is:
case "$1" in start) # rootfs is mounted rw, lvm et al should be up now
Then it runs fsck, and if the error is greater than 3, it does this:
... echo "fsck failed. Please repair manually and reboot. The root" echo "file system is currently mounted read-only. To remount it" echo "read-write do:" echo echo " bash# mount -n -o remount,rw /"
That's the message you saw, isn't it? But at that point root is RW, and that matches what you saw.
This second script is wrong. There are two mistakes: one is to wrongly report the RO status (because the script is derived from the first one). The other is misleading you to think that the root filesystem is faulty, when it is some other partition.
Ah!
I see it clear, it happened to me as well when I deleted a partition and forgot to remove it from the fstab file. I got the same error as you did.
Carlos E. R., you are brilliant!!! Thanks for the reply. I had almost forgotten about this problem, since I got my system working again by putting fs_passno=0 for the extra HD. Once I put it back in the system I think it doesn't matter. I am very happy you thought about the script, and looked at it. I had suspected there was really a bug, since we agree it should not have behaved this way. So this is actually quite serious. It should be reported to Suse. I would say that responsibility should be mine. I will make a note of it. Unfortunately, now I am deep into experiments with DVD burning, for the first time. Hopefully I won't forget about this issue. Good day! -- ____________________________________ Christopher R. Carlen Principal Laser/Optical Technologist Sandia National Laboratories CA USA crcarle@sandia.gov
The Tuesday 2005-02-01 at 17:20 -0800, Christopher Carlen wrote:
This second script is wrong. There are two mistakes: one is to wrongly report the RO status (because the script is derived from the first one). The other is misleading you to think that the root filesystem is faulty, when it is some other partition.
Ah!
I see it clear, it happened to me as well when I deleted a partition and forgot to remove it from the fstab file. I got the same error as you did.
Carlos E. R., you are brilliant!!! Thanks for the reply. I had almost forgotten about this problem, since I got my system working again by putting fs_passno=0 for the extra HD. Once I put it back in the system I think it doesn't matter.
I'll put that comment on a golden frame, and show it to prospective employers :-p
I am very happy you thought about the script, and looked at it. I had suspected there was really a bug, since we agree it should not have behaved this way.
I like detecting problems. This one I can not solve, I'm not a good script programmer. Not even a Linux programmer. But investigating problems is like a good game of... whatever. And to tell you the truth, I have looked at that script several times, but I never noticed there were two of them till today. Pure chance.
So this is actually quite serious. It should be reported to Suse.
At least a nuisance.
I would say that responsibility should be mine.
Good, I browse very little, I use a modem :-)
I will make a note of it. Unfortunately, now I am deep into experiments with DVD burning, for the first time. Hopefully I won't forget about this issue.
Point them to this thread, they should be reading the list on paid time.
Good day!
Yap, I'm closing for the day. I was watching a movie and it has just finished. -- Cheers, Carlos Robinson
Christopher Carlen wrote:
Hi:
I have a Suse 9.1 box that has suddenly broke. It gets stuck with a message that I need to check the filesystem, but as you will see, there is apparently nothing wrong with the filesystem:
The booting stops here and the following is a log of what I've done to fix it, without success:
Thanks folks who responded. The /dev/sda2 was not in /etc/fstab twice. Rather, there was an IDE drive /dev/hda1 that was the last line in the file, which was causing the problem. Why is that? I disconnected the drive temporarily. It appears that with the /etc/fstab reading: /dev/hda1 /data1 ext3 noauto,user,acl,user_xattr 1 2 then the system gave the problem described. Changing to: /dev/hda1 /data1 ext3 noauto,user,acl,user_xattr 0 0 fixed it, and makes the system not care if the drive is conencted or not. Thanks. -- _____________________ Christopher R. Carlen crobc@sbcglobal.net SuSE 9.1 Linux 2.6.5
The Saturday 2005-01-29 at 17:25 -0800, Chris Carlen wrote:
then the system gave the problem described. Changing to:
/dev/hda1 /data1 ext3 noauto,user,acl,user_xattr 0 0
fixed it, and makes the system not care if the drive is conencted or not.
It was trying to fsck it. The 0 dissables it. Interesting. -- Cheers, Carlos Robinson
participants (5)
-
Carlos E. R. -
Chris Carlen -
Christopher Carlen -
lee fellows -
Susemail