On 06/13/2010 11:14 PM, Thomas Johnston wrote:
> Tony,
>
> Thanks for the reply. I'm sorry, but I am not a very sophisticated
> Linux user. Could you be a little detailed with your answers?
>
> I have tried to Google how to boot in single user mode without much
> luck. So far I have found two things:
> (1) one website calls changing the run level to 1 entering 'single user' mode
> (2) a second says to hold down the "shift" key at beginning of the
> boot sequence. I tried this and was presented with the option to boot
> several different kernels (and each kernel had a recovery mode
> option). At the bottom of the screen it sasy: "Press enter to boot
> the selected OS, 'e' to edit the commands before booting or 'c' for a
> command-line." If I highlight the latest kernel (Ubuntu, with Linux
> 2.6.32-22-generic (recovery mode) and press 'e', I get several more
> options, one of which is: linux /boot/vmlinuz-2.6.32.-22-generic
> root=UUID=long alpha-numeric string ro single. I highlighted this
> option and pressed "ctrl-x" to boot it. I then get a recovery menu
> which has various options: resume, clean, dpkg, failsafeX, grub,
> netroot, root
>
> I am in the ballpark of what you were suggesting I do?
Yes you are in the ball park. Please see yesterday E-mail to Hai
Yi about going into Grub and then 'drop to root shell'.
With most versions of *nix you can get into the single user
mode during the boot up procedure. *buntu has made it easy
with Grub and the 'Recover' mode.
Once you are in single user mode (root) then you should do
an 'fsck /home' to insure the partition is clean. Once it is
it should then be able to be mounted as read/write (which is
the error you where having).
Tony
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech
