Maxtor DiamondMax 10 model 6L200R0 PATA 133 HDD, 3.5 Series external HDD not detected by Ubuntu.

[Nate]

The drive works in Windows and Mac OS, and on multiple computers including the Windows partition of the one I have Ubuntu installed on. I tried manually mounting and force mounting through the terminal to no avail. It was safely removed from Windows, so that isn't the problem. There's a full chronology of things I've done at the Ubuntu forums here:

http://ubuntuforums.org/showthread.php?t=1010198

[Patrick Kilgore (patrick-kilgore)]

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.

[Nate (superzero-gmail)]

Sorry it took so long to get all this. I've been really busy with school.

The kern.log file wouldn't upload. I cut and pasted most of it into the attached file here. After the last line, it just repeats the last two lines indefinitely, the only difference being that there are different numbers between the brackets.

[xteejx (xteejx)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue for you. Can you try with the latest Ubuntu release? Thanks in advance.

[xteejx (xteejx)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!