Boot process stops

[Jook_roberts]

Anyone having this problem? My boot process quits with only this on screen:

mount: mount point /proc/bus/usb does not exist
mountall: mount /proc/bus/usb [586] terminated with status 32
mountall: filesystem could not be mounted /proc/bus/usb

I ran yesterday's update, now I can't boot up.

[Snowhog]

Re: Boot process stops

Did you have a USB thumbdrive/HD attached when you did the update? If you did, plug it back in and boot.

[timek718]

Re: Boot process stops

I had something similar happen today. I thought it was mischief from updates. Turns out I had an error in my fstab. I made some changes a day or two ago & left out the filesystem type for the partition with media files. The error message was init: ureadahead-other main process (xxxx) terminated with status 4. There was a mention of an error with mountall and that partition.

It would seem that Lucid is unforgiving of fstab errors. I couldn't even get to a command line without booting from an old Karmic disk.

I suggest also checking your fstab for errors, even if your specific error messages are different.

[verndog]

Re: Boot process stops

Today for the first time since Jaunty, my Ubuntu system stopped during boot. It started up then just stopped. "alt reisub" had no effect. Power cycle was the only option. Using "nomodeset" booted then froze solid.

The only solution for me was to purge plymouth. Then boot up worked. It was shortly after todays plymouth update that this oocured. There was some nautilus updates that I thought were the cause, but now I'm sure its plymouth.

Tomorrow after the new Open Office updates get into the dailies I will zsync my ISO and try again.

[Jook_roberts]

Re: Boot process stops

Hi snowhog

i thought of that to, but no luck.


timek718

You are right about the fstab. I was trying to get the USB working in Virtual Box yesterday. There is a line you can add to the fstab file to enable the USB.

#usbfs
none /proc/bus/usb usbfs devgid=46,devmode=664 0 0

I have no idea what it does. The above works great in Karmic, but totally locks you out in LL. I remarked out the line and life is good again.

Thanks for saving me from myself.

[Jook_roberts]

Re: Boot process stops

Verndog

How do you purge a package form a system that will not boot? I assume you boot into a live CD, but then what do you do?

I got a feeling, with the changes they are making to the boot process, that I will need to know this stuff.

[verndog]

Re: Boot process stops

Verndog

How do you purge a package form a system that will not boot? I assume you boot into a live CD, but then what do you do?

I got a feeling, with the changes they are making to the boot process, that I will need to know this stuff.

Chroot.

Here's the script I use:

mount /dev/sdaX /mnt/
mount --bind /dev /mnt/dev
mount --bind /proc /mnt/proc
mount --bind /sys /mnt/sys
mount --bind /dev/pts /mnt/dev/pts
mount -o bind /etc/resolv.conf /mnt/etc/resolv.conf
chroot /mnt/ /bin/bash

then reverse the process to get out of it:

Crtl+d

umount /mnt/dev/pts
umount /mnt/sys
umount /mnt/proc
umount /mnt/dev
umount /mnt

That 'sdaX' is your partition in question. Also you can create another folder and use that instead of '/mnt'. Its ones choice. This has always worked for me. There has been several variations on choot'ing. Go here for some info on chroot. Follow the links.