mountall proc/bus/usb could not be mounted

Bug #499100 reported by Christopher
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: mountall

I get the message 'mountall proc/bus/usb could not be mounted', or something close (messages are only briefly visible) when booting, restarting and shutting down. It doesn't seem to affect any of my USB devices or the functioning of the system, other than an extended boot time.

Lucid -9.

ProblemType: Bug
Architecture: i386
CheckboxSubmission: 986216097b0334da1f111f9962302c03
CheckboxSystem: 00d1e28d54c476aae7445d64a6399859
Date: Mon Dec 21 10:58:45 2009
DistroRelease: Ubuntu 10.04
Package: mountall 1.1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-9.13-generic
SourcePackage: mountall
Tags: lucid
Uname: Linux 2.6.32-9-generic i686

Revision history for this message
Christopher (soft-kristal) wrote :
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Please attach your /etc/fstab

Changed in mountall (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Christopher (soft-kristal) wrote :

Just to add to the issue, Segmentation Fault is sometimes the first thing I see on boot up. Nothing else on the screen, just that.

Revision history for this message
Pablo Marchant (pamarca) wrote :

I seem to be having this same problem. However, it seems to be related to a somewhat more serious problem. After getting this mountall message, or after getting this "Segmentation Fault" message on boot (the only thing shown right after grub, the boot process doesn't complete), I am asked to manually run fsck and dropped to a root terminal. Once, I even got an error saying "This shouldn't happen. Data will be lost!"

In the root terminal, I run "fsck /dev/sda1" which repairs a lot of errors in my ext4 filesystem. After that, I can boot normally.

Revision history for this message
Christopher (soft-kristal) wrote :

So far, the boot process is delayed, but not stopped by the 'Segmentation fault' message. I haven't timed it yet, but I'm pretty sure my Karmic partition boots faster than Lucid Alpha.

Revision history for this message
Johan Kiviniemi (ion) wrote :

You both might have broken hardware. Please investigate that possibility. Running memtest86+ for a few hours would be a good start.

Revision history for this message
Johan Kiviniemi (ion) wrote :

Cristopher,

As for usbfs not mounting:

linux (2.6.32-6.7) lucid; urgency=low

  * [Config] disable CONFIG_USB_DEVICEFS

I don’t know enough about usbfs to say why it was disabled, and the changelog message isn’t helpful either.

Revision history for this message
Christopher (soft-kristal) wrote :

memtest+ locked up at 53% for almost an hour before I gave up. As to USB devices, they are all working properly, including the ones on root hubs, both USB and a four port PCIMIA card.

The Segmentation fault is not occurring in Karmic on the same laptop, different partition, nor is any other error.

Most of these issues occurred after a UFW update locked and would not continue. I left it running all night and finally force quit the update manager.

I'm wondering if a format and re-install is in order. I don't keep anything important on this partition. I use the Gparted live CD for major surgery.

Revision history for this message
Pablo Marchant (pamarca) wrote :

I just runned memtest once, and it went fine. I'll leave it now overnight to see how it goes.

Also, when I get just the segmentation fault message, boot completes. I was just lacking patience before.

Revision history for this message
Pablo Marchant (pamarca) wrote :

Memtest results after running overnight: Pass, 7 Fail, 0

Revision history for this message
Christopher (soft-kristal) wrote :

I have no choice other than a format and re-installation. After this morning's update, my network was flaky and I rebooted. I have no terminal access at all.

Now all I get in any boot mode is a fast-scrolling message which looks like:

mountall: /proc/bus/usb canceled by user, or something to that effect. It's scolling so fast that it's blurry. Only a ctrl+alt+delete stops the process.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote : Re: [Bug 499100] Re: mountall error message on boot and shutdown

On Tue, 2009-12-22 at 20:00 +0000, Christopher wrote:

> mountall: /proc/bus/usb canceled by user, or something to that effect.
> It's scolling so fast that it's blurry. Only a ctrl+alt+delete stops the
> process.
>
Yeah, uploaded a fix for that a couple of hours ago ;-)

Scott
--
Scott James Remnant
<email address hidden>

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Please test mountall 2.1 (now in lucid)

summary: - mountall error message on boot and shutdown
+ mountall proc/bus/usb could not be mounted
Revision history for this message
Christopher (soft-kristal) wrote :

Can you tell me if there is a way to get into a terminal? I just have my Karmic partition available.

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote : Re: [Bug 499100] Re: mountall proc/bus/usb could not be mounted

On Tue, 2009-12-22 at 20:35 +0000, Christopher wrote:

> Can you tell me if there is a way to get into a terminal? I just have my
> Karmic partition available.
>
init=/sbin/sulogin always works.

Scott
--
Scott James Remnant
<email address hidden>

Revision history for this message
Christopher (soft-kristal) wrote :

I can't stop the scrolling and enter a terminal command. I can stop the scrolling with FN+ScrLk, but I as soon as I type something, the scrolling starts anew.

Is there a way to break the cycle? I can wait until the weekend to reformat and reinstall Lucid on my test partition, but that's a tad drastic.

The only thing working in Lucid is memtest+, which I just ran. 8 tests, no errors.

Revision history for this message
Javier Cabezas (javier-cabezas) wrote :

I am still getting the "proc/bus/usb could not be mounted " message with mountall 0.2.1 and cannot get to GDM

Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Marking as invalid. usbfs is not available in Ubuntu's kernel

Changed in mountall (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.