pretty much the same version anyone running feisty has I guess: GNU bash, version 3.2.10(1)-release (i486-pc-linux-gnu) Copyright (C) 2005 Free Software Foundation, Inc.
The problem is simple (and there is no need to risk a filesystem). What happens was: - fsck started after a forced reboot (libata is sometimes having trouble... but this is an other reported bug) - fsk should only check unmounted directoryl: everything but / root is unmounted (in my case, that's /var, /usr/, /usr/local, /tmp ). - when checking 'fsck' found things to fix, and because of the default configuration in ubuntu stops there (rather than automatically trying to fix the problem). - fsck stopping causes a start of the maintenance shell, but nothing that was unmounted for the fsck is mounted back. - the maintenance shell missing things in /usr, the show stops here. It was possible for me to fix my disk, but what happened was not something I wished to a less experienced user. Cheers, Laurent 2007/3/14, Sense Hofstede <[EMAIL PROTECTED]>: > What is the version of bash you're using? > Is there anybody else with the same problem? If anybody else has the same > problem, the bug is confirmed. But I don't think anyone want to risk a broken > filesystem to reproduce this bug. > > -- > failure while starting a maintenance shell > https://launchpad.net/bugs/89595 > -- failure while starting a maintenance shell https://launchpad.net/bugs/89595 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
