aRTee Posted February 26, 2003 Report Share Posted February 26, 2003 I have a weird problem in that I have the mdk9.1rc1 root partition mounted at boot on /alt but since I installed mdk9.1rc1 it stops at the fsck and tells me I should update fsck and that the version I have is not compatible or so. I can't boot to 9.0 anymore, until I step in and comment the line in the /etc/fstab out where the /dev/hda9 is mounted on /alt After booting, I can issue the correct command and mount the partition (guess then it doesn't check the filesystem or so) without any problem. Does anyone else have this problem? (and yes, I checked but found no updated version of fsck) Quote Link to comment Share on other sites More sharing options...
Cannonfodder Posted February 26, 2003 Report Share Posted February 26, 2003 How did you install 9.1? Do an upgrade to 9? Might want to detail this one and reportit to http://qa.mandrakesoft.com as a bug.. I did a search for fsck and didn't see any bugs on it so that means it may be unique.. Quote Link to comment Share on other sites More sharing options...
Guest ndeb Posted February 27, 2003 Report Share Posted February 27, 2003 aRTee, I have exactly the same problem. Here's the situation: mdk-9.0 has e2fsprogs-1.27ea mdk-9.1rc1 has e2fsprogs-1.32 It so happens that v1.32 supports some new features not supported by v1.27ea. Naturally, a filesystem generated by v1.32 cannot be checked/repaired by v1.27ea. The workaround is this: 1. Linux lets u login as root after complaining about the incompatibility. U can change the /etc/fstab file by commenting out the relevant lines. 2. After u reboot, linux will reboot and this time it will boot fine. 3. Now, u can uncomment the entries in fstab and mount these partitions. Note that mounting is allowed but not running fsck. 4. Before reboot, do not forget to comment out the same lines in fstab !! Quote Link to comment Share on other sites More sharing options...
aRTee Posted February 27, 2003 Author Report Share Posted February 27, 2003 ndeb, your solution is exactly what I did; except for the uncommenting again; I just leave the # in the /etc/fstab and issue mount /dev/hda9 -t ext3 /alt whenever I want to read from it. What puzzles me is why it's not complaining about /home which is also ext3.... but maybe it doesn't check that at boot..? Anyway, thank you for figuring out why this happens (and which programs make it so),... guess I can close my bugreport now... Quote Link to comment Share on other sites More sharing options...
Guest ndeb Posted February 27, 2003 Report Share Posted February 27, 2003 I just leave the # in the /etc/fstab and issue mount /dev/hda9 -t ext3 /alt Thats a neat idea. I will start using that too.What puzzles me is why it's not complaining about /home which is also ext3.... but maybe it doesn't check that at boot..?Well, its not about ext2 or ext3 since in my case the partitions are ext2. Its about which partition needs to checked. It so happens that it is not trying to check /home so there is no problem with it. But it is trying to check / and running into problems. Also, see http://e2fsprogs.sourceforge.net/ where it says: This release has fixes a few bugs over the previous releases. In particular if you wish to experiment with the new htree directories feature in the 2.5 (or 2.4 kernels using the backport patches) you should upgrade to this version of e2fsprogs.Could this be the cause ? Quote Link to comment Share on other sites More sharing options...
aRTee Posted February 27, 2003 Author Report Share Posted February 27, 2003 Thanks for searching more answers. I guess you´re right, so I´ll have to cancel my bugreport/bugfixrequest... Quote Link to comment Share on other sites More sharing options...
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.