I am having intermittent issues. It seems a reboot is the only way to get around it. For instance, I had a USB WinTV PVR connected earlier today. Recently I attempted to connect a 500GB usb drive up and it would not mount. lsusb showed the wintv still connected but the drive not connected. Looking at the drive with fdisk -l gave an IO error. Same with Gparted showed the drive having no partition. Dmesg showed all kinds of errors.
I decided to reboot and it would not shut down. The error message was "could not unmount /var/run and /home.
Device or resource busy. Not all file systems unmounted, 2 left. Cannot finalize remaining systems and devices. Giving up. A hard reset was the only way to get out of the problem.
This has happened off and on for a couple of months now. At first I thought it was motherboard issues. I DID have a defective board, but this one issue remains.
I am using a EVGA X79 Classified motherboard.
Opensuse 12.3, 64bit with KDE
Currently I am using a USB 3.0 port. I don’t recall if this is always a usb 3.0 issue. .
I just did a dmesg and got this: (I’ve seen this before to intermittently.
[10996.410039] hub 5-0:1.0: unable to enumerate USB device on port 2
[10996.660063] hub 5-0:1.0: unable to enumerate USB device on port 2
[10996.866040] hub 5-0:1.0: unable to enumerate USB device on port 2
[10997.072048] hub 5-0:1.0: unable to enumerate USB device on port 2
[10997.410043] hub 5-0:1.0: unable to enumerate USB device on port 2
[10997.616053] hub 5-0:1.0: unable to enumerate USB device on port 2
[10997.822073] hub 5-0:1.0: unable to enumerate USB device on port 2
[10998.028057] hub 5-0:1.0: unable to enumerate USB device on port 2
[10998.410056] hub 5-0:1.0: unable to enumerate USB device on port 2
[10998.660036] hub 5-0:1.0: unable to enumerate USB device on port 2
[10998.866043] hub 5-0:1.0: unable to enumerate USB device on port 2
[10999.072066] hub 5-0:1.0: unable to enumerate USB device on port 2
[10999.410043] hub 5-0:1.0: unable to enumerate USB device on port 2
[10999.660048] hub 5-0:1.0: unable to enumerate USB device on port 2
This is the port that has that usb drive connected and it has been copying data for the last hour. I didn’t realize it had failed again, until just now. lsusb shows the system doesn’t think it is there. arggggg. it copied 465.6gb of 472.9gb.
anybody else have this issue, or ideas on what is going on? Hardware?
(P.S. this is the second time I’ve posted this. THe first time did not seem to take. IF this shows up twice, I apologize and the first one can be deleted.)
Editing afterwards is of no use because all the layout is allready gone then. CODE tags only work as intended when you copy/paste direct from your terminal window in between the CODE tags (or put CODE tags manualy around the copied/pasted text, but allways before posting).
On 06/12/2013 11:16 PM, lshantz wrote:
>
> I am having intermittent issues. It seems a reboot is the only way to
> get around it. For instance, I had a USB WinTV PVR connected earlier
> today. Recently I attempted to connect a 500GB usb drive up and it would
> not mount. lsusb showed the wintv still connected but the drive not
> connected. Looking at the drive with fdisk -l gave an IO error. Same
> with Gparted showed the drive having no partition. Dmesg showed all
> kinds of errors.
>
> I decided to reboot and it would not shut down. The error message was
> "could not unmount /var/run and /home.
> Device or resource busy. Not all file systems unmounted, 2 left. Cannot
> finalize remaining systems and devices. Giving up. A hard reset was the
> only way to get out of the problem.
>
> This has happened off and on for a couple of months now. At first I
> thought it was motherboard issues. I DID have a defective board, but
> this one issue remains.
Not all USB to PCIe converters are designed correctly, and the drivers ehci-hcd,
uhci-hcd, ohci-cd, and xhci-hcd contain a number of special code sections to
handle quirks. Your MB may not be common, and you may have such a problem,
particularly if the port is question is USB 3.0. Usually, the problems that lead
to “unable to enumerate” messages are not intermittent, but some problem may
have locked that particular USB device. In my experience, the Hauppauge WinTV
devices are OK and should not cause the problem when attached to a good hub. If
possible, try a different port.
To debug a driver/port issue, the primary developer would need you to use a
kernel with USB debugging enabled, and it will lead to very large log files. I
think the openSUSE debug kernel has the necessary configuration.
