Thank you for submitting this bug and taking the time to help make
Ubuntu better. Please assist us in gathering information about this bug
by performing the following steps:
1) Unplug the problematic device from the USB port, and restart your computer.
2) Login to Ubuntu, and wait until all startup processes have completed
(usually less than a minute, but more if you have a lot of programs scheduled
to run on startup) A good indication this process is complete is that CPU is
idling without significant (20%+ load)
3) Start a terminal, and run the following command:
"sudo udevadm monitor --e >> ~/Desktop/udevadm_monitor-e.log"
Leave this terminal running, as it is logging some stuff for us.
4) Make sure the hard drive is powered, then plug it back into your USB port.
5) Immediately start a NEW instance of the terminal, and enter the following
commands, one at a time:
"cp /var/log/dmesg ~/Desktop/dmesg.log"
"cp /var/log/kern.log ~/Desktop/kern.log"
"uname - a >> ~/Desktop/VersionInfo.log"
"lsb_release -a >> ~/Desktop/VersionInfo.log"
"lsusb -v > ~/Desktop/lsusb-v.log"
"lspci -vvnn > ~/Desktop/lspci-vvnn.log"
6) Close the terminal you just entered these commands into.
7) Stop udevadm by selecting the first terminal and holding "ctrl+c". You can
now close this terminal.
8) Attach the following text files to this bug report as separate attachments
(they are all on the desktop). Please don't compress them into a single file,
as it makes them very difficult to triage from launchpad:
VersionInfo.log
dmesg.log
kern.log
lspci-vvnn.log
lsusb-v.log
udevadm_monitor-e.log
8) You can go ahead and delete the logs after you have uploaded them all to
launchpad.
Thanks in advance! After this, our developers should have enough
information to properly diagnose your problem.
** Changed in: linux (Ubuntu)
Sourcepackagename: None => linux
Status: New => Incomplete
--
Maxtor DiamondMax 10 model 6L200R0 PATA 133 HDD, 3.5 Series external HDD not
detected by Ubuntu.
https://bugs.launchpad.net/bugs/310034
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
