On Friday 11 January 2002 03.48, dep wrote:
idea as to what the business about / not being fsck-able means would be appreciated -- you don't suppose that that's the change in the mk_initrd, so that ext3 could be run on the / partition, do you? /etc/fstab looks fine, everything still ext2.
No, I don't think the new mk_initrd has anything to do with it. Looking at the script /etc/rc.d/boot (I assume you have suse's default. I haven't looked at what other dists do) it tries to do a mount -o remount,ro /, and if that fails you get the error you talk about. So for some reason it can't be remounted read only. Though why that is needs detective work. One thought that occurs to me is that some process has been started that holds / so it can't be remounted. I have a faint recollection from several dists ago that / was usually ro,defaults in /etc/fstab so fsck can run, but I could be wrong about this. Maybe (and I'm just guessing here) SuSE rewrote the scripts to get a nicer fstab, and something's not working. It could be some other reason why it can't remount, but without access to your system all I can do is guess. regards Anders