On Fri, Nov 03, 2006 at 01:37:52PM +0100, Santiago Vila wrote: > On Wed, 19 Jul 2006, Thomas Schwinge wrote: > > > I was hit by the same issue and it was because of /boot/grub/menu.lst > > containing ``--read-only'' on ext2fs.static's line. This had probably > > been added when auto-detecting an existing Debian GNU/Hurd installation > > by the Debian etch installer. > > Oops, yes, there was a --read-only in menu.lst. Yesterday I removed > that and tried again (using the mini iso by Philip Charles) and everything > worked smoothly. > > I still have to check it properly using crosshurd (will need some sort of > hack, > because netbase does not want to be installed due to broken dependencies). > > We should probably check that the current debian installer for etch > does not create such wrong grub entries when auto-detecting a Hurd > install.
The problem is that we had also reports of computers hanging at the e2fsck phase on bootup, namely when we call "fsysopts / --update --readonly" in /libexec/rc *and* the file system has not been clealy unmounted. It turned out those issues can be fixed by removing that entry from the file and adding --read-only to ext2fs.static's line. So I am really not sure how to fix that, or what the problem is in the first place. Maybe it helps if check for a read-only file system before the fsysopts and only --update it if it is really read-only. Michael PS: FWIW, I think I've got bitten by this exact bug as well the last time I tried crosshurd two weeks ago or so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
