eSata HD not being auto-detected after recent upgrade

Bug #909806 reported by Robbt on 2011-12-29
46
This bug affects 8 people
Affects Status Importance Assigned to Milestone
dbus (Ubuntu)
Undecided
Unassigned

Bug Description

Basically I'm running Precise Pangolin 12.04 alpha and just today my eSata drive started not being detected by Nautilus or dmesg upon plugging it in or not. Previously it always showed up and when I connected to it via USB it appeared immediately. So something recent in terms of the dbus monitoring etc caused this. I then ran rescan-scsi-bus.sh and it was found and showed up in Nautilus. The hardware is a HP Laptop with a eSata/USB port. I could get more specific but I just wanted to note this bug in case it can be identified.

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/909806/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Fabio Marconi (fabiomarconi) wrote :

Assigned to dbus
---
Ubuntu Bug Squad volunteer triager
http://wiki.ubuntu.com/BugSquad

affects: ubuntu → dbus (Ubuntu)
tags: added: precise regression-update
Robbt (robbt) wrote :

This seemed to go away and then happened again. I am able to get Ubuntu to detect my hard drive by running this command.

apt-get install scsitools
sudo rescan-scsi-bus.sh

It is then detected and mountable. Before this nothing is showing up in dmesg to indicate the drive exists or that dbus noticed it being plugged or unplugged.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in dbus (Ubuntu):
status: New → Confirmed
Saša Teković (hseagle2015) wrote :

I'm having the exact same problem (although on Ubuntu 11.10). When I connect my HDD drive to eSATA port nothing happens. There are no information in dmesg or fdisk. Interestingly, if I connect my HDD before turning the computer on, the disk is recognized and mounted automatically.

After executing 'sudo rescan-scsi-bus' the hard drive is recognized, but I'd really like to see a better solution for this problem, especially since everything worked correctly on Ubuntu 11.04.

I have the same problem in Ubuntu 13.04. Running sudo rescan-scsi-bus makes me use the drive. Also in ubuntu 12.04 sometimes I noticed this problem, but in Ubuntu 13.04 this problem is present all the time. I also noticed that connecting it while using Win 7 and then reboot to ubuntu leaves the drive recognized, and after then unplugging/plugging the drive works...
I was writing this comment after I installed scsitools, run rescan-scsi-bus, saw that the drive was recognized, mounted and umounted it, let it go in powersave mode, when suddenly the drive waked up on his own. It never did something like this. Maybe cause of scsitools?

tags: added: raring
Brian Murray (brian-murray) wrote :

Michele it would be help if you were to try debugging this issue using the command 'ubuntu-bug storage' in a terminal as this will run some local tests on your system and create a new bug report for you. Please let me know that new bug number. Thanks!

tags: added: regression-release
removed: regression-update

Ok, strangely after I installed scsitools Ubuntu started to see the disk properly. I don't know why, but I will run some tests and if I'll see that the problem comes back I'll open a new bug.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers