Auto mount does not work for USB drive

[robotgenius]

The problem:

        USB drive not automounting. The same USB drive does mount on another PC with Edgy installed.

Details:

        When I plug the USB drive in, a new device is created in /dev (sdb and sdb1 to be exect). I can even mount this device manually using mount (and specifying the type as vfat), but the device does not automount. On a second edgy machine, when I plug the device in, not only is the /dev device created, but the device is automounted in /media as SEA_DISC, and an icon appears on the desktop. I believe this is all done with a program called gnome-mount, but I am unfamiliar with this command.

System setup:

OS: Ubuntu Feisty beta
Motherboard: Intel DG965ss with Pentium D
Hard drive: Seagate 750GB USB drive
Other: No cards plugged into board, no other USB devices attached (using onboard network and video)

I am willing to perform further tests if instructed to do any.

[Rom13ain (rom13ain)]

I'm having the same problems with my external hard drive. It was auto mounted in Edgy but doesn't work with the latest version of Feisty (updated beta).

Yet, my USB key auto mounts well. I noticed that we are experiencing these difficulties with nearly the same external hard disk.

So it might come from the drivers?

OS : Ubuntu Fiesty Fawn Beta
PC : Laptop Toshiba
Hard Drive : Seagate 500GB USB

[ElVirolo (elvirolo-gmail)]

I have exactly the same problem with a "generic" 250 GB USB drive.

[Jakub Grobelny (groblus)]

Problem still occurs, with latest Kubuntu 7.04 - devices are added to /dev but are not automounted (kde shows dialog informing about a new device but the drives are not mounted)
the device is a usb harddrive - 80GB
hope it gets fixed

[blekos (ilias)]

I have an external HD 120GB, connected with usb to my laptop (sony vaio vgn-sz3xp). When I had Kubuntu 6.10 the drive was automounted correctly. Upgrading to 7.04 automount (for the HD) does not work correctly anymore. A usb toggle I have (2gb Transcend) automounts correctly.
Steps taken to correct the error
1. Formated the external HD!!
2. In windows run chkdsk /f /r (no errors found)

3. Started linux and connect the external HD, I get the message "open in new window" , "do nothing" etc.
4. i choose "open in new window" , but nothing happens!!!
5. Doing fdisk -l and my external HD is there but not mounted...
6. I create a mount point in /etc/fstab
7. I Do a sudo ntfsfix /dev/sdb1
I get:
Mounting volume... OK
Processing of $MFT and $MFTMirr completed successfully.
NTFS volume version is 3.1.
Setting required flags on partition... OK
Going to empty the journal ($LogFile)... OK
NTFS partition /dev/sdb1 was processed successfully.
8. I do a sudo mount -t ntfs-3g /dev/sdb1 /media/dat -o force
I get:
WARNING: Dirty volume mount was forced by the 'force' mount option.

A voila the HD is mounted.
Same problem was encountered in my PC with a friends external HD.

I also run Kubuntu 6.10 from live CD, and both my external HD and that of my friend was automount and their contents displayed correctly.
Please advice.

[blekos (ilias)]

I've downloaded both Kubuntu 7.04 & Ubuntu 7.04. I started my pc with Kubuntu live cd and after everything was loaded I turned off my external usb HD. Again I had the same problem (see above).
I followed the same procedure, only that time I had Ubuntu live cd to start with. Guess what... my external USB HD was discovered AND mounted correctly (could read but not mount due to live cd restrictions).
I will try to install ubuntu in my pc as well and see what happens. Maybe there is a module or something that is not loaded with kubuntu.
I'd like to see a solution to this problem, since having an external storage device is quite useful especially when you use it for backup reasons.

[blekos (ilias)]

sorry, I meant turnd ON my external HD and NOT turned off.

[blekos (ilias)]

I just finished installing ubuntu-desktop. Again I have the same problem. A pop-up window informs me that the external HD cannot be mounted because it was not properly removed from a Windows session and suggests to ntfsfix, reboot twice in WIndows or force mount... Remeber that when I run the Ubuntu live cd no such message appeared, but my external HD was mounted correctly. Will re-installing (K)ubuntu solve the problem?

[blekos (ilias)]

I deleted my linux partions (had kept a backup of important data).
I installed Ubuntu (7.04)
my external HD is correcly mounted.
I installed the ntfs mount utility in order to read and write both to internal and external devices. Can read/ write to all my ntfs devices.
I install Kubuntu-desktop using
sudo aptitude install kubuntu-desktop

I logged in to KDE. Turned on my external HD and... the same thing again. A window pop's up and ask me if i want to see the contents etc. I chose yes. But nothing happens. I switch back to GNOME and my external HD is there.

I tend to believe that it my be some kind of process or has to do with the ntfs configuration tool.

At the moment I'm using KDE and when I want to access my external HD i switch to GNOME (quite frustrating all this back and forth).

Need to mention that a couple of times when I directly logged in GNOME and then switched to KDE my external HD appeared mounted...

[dnh (dnh)]

I have the same problem on Kubuntu 7.04, but not with all devices.

It works fine with a Sandisk USB-stick, an Apple Ipod nano or an external harddrive by Western Digital. It does not work with an external harrdrive by Maxtor, though I can mount manually using "pmount-hal /dev/sda1" . I had no problems on Kubuntu 6.10.

[Phil Richards (news-derived-software)]

Same problem: I have a Seagate 250Gb external hard disk, udev correctly creates the entry in /dev, but nothing appears in /media (which, under 6.10, it did).
The filesystem type is vfat.

I have a "udevcontrol log_priority=debug" daemon.log for the attach if that is useful to anybody. It shows that udev is doing its stuff, and ends with:
Apr 25 20:28:17 derisoft NetworkManager: <debug info>^I[1177529297.690776] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/storage_serial_Seagate_External_Drive_SG062016817_0_0').
Apr 25 20:28:17 derisoft NetworkManager: <debug info>^I[1177529297.736672] nm_hal_device_added (): New device added (hal udi is '/org/freedesktop/Hal/devices/volume_part1_size_250056705024').

[blekos (ilias)]

Bought a new external WD 320GB HD (MYBOOK). It works out of the box...!!!

[Michael Wood (x3n)]

Again a Seagate external hard disk.

I can mount it fine via command line, but it doesn't auto mount as it used to in edgy.

OS: Clean install of Feisty

[rothchild (marc-rothera)]

Please can we get this bug fixed?

I've just updated my laptop from Dapper to Feisty as I was having such a great experience with it on my desktop and I've backed up my home folder to my 320gb Seagate USB drive and now it won't auto mount in KDE (my 2gb USB pendrive works fine) so I have a lovely clean Feisty install but I can't bring back my files as they are all trapped on the drive.

This is the sort of stuff that sends people back to windoze and as such should be marked as a critical bug IMO.

Cheers
Child

[robotgenius (misc-robotgenius)]

Hello-

    I am the original poster of this bug. FYI, although the bug isn't
fixed, there is an easy workaround if you want to get your files on the
system. Just mount by hand like this "sudo mount -t vfat /dev/sd<drive
letter>1 /media/<drive name>", where you replace the drive letter with a, b,
c, etc depending what drive letter the drive was given, and drive name with
a folder you have created in /media. It isn't a pretty way to do things,
but it works.

                        see you
                            -Jim

----- Original Message -----
From: "rothchild" <email address hidden>
To: <email address hidden>
Sent: Monday, May 21, 2007 11:57 AM
Subject: [Bug 102097] Re: Auto mount does not work for USB drive

> Please can we get this bug fixed?
>
> I've just updated my laptop from Dapper to Feisty as I was having such a
> great experience with it on my desktop and I've backed up my home folder
> to my 320gb Seagate USB drive and now it won't auto mount in KDE (my 2gb
> USB pendrive works fine) so I have a lovely clean Feisty install but I
> can't bring back my files as they are all trapped on the drive.
>
> This is the sort of stuff that sends people back to windoze and as such
> should be marked as a critical bug IMO.
>
> Cheers
> Child
>
> --
> Auto mount does not work for USB drive
> https://bugs.launchpad.net/bugs/102097
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[rothchild (marc-rothera)]

Thanks Robotgenius

I actually used the tip above of calling "pmount-hal /dev/sdb" and that worked ok but as you say it isn't pretty. I'm really trying to get a bunch of my mates to migrate over to ubuntu and this sort of stuff will put them off straight away, if it doesn't work first time it doesn't work at all in their minds. So if we are going to address the number one bug on this tracker (Microsoft's dominance) things like this can not happen.

Have we worked out if this is a KDE bug or something at a lower level?

Cheers
Child

[raintheory (raintheory)]

Seagate here as well. 250GB

However, not only will the drive not mount as NTFS or HFS+ (tried both), when I boot into windows I get an error saying the drive needs formatted!

I replicated this problem 3(!) times. Twice on my laptop and once on my desktop (both feisty).

I formatted the drive as EXT3 and it showed up in Ubuntu, but again when I went into windows with it (using an EXT3 driver as I have done numerous times before with other disks), I get a similar error about the disk and need to reformat.

Frustrating. Luckily I was able to recover the files that were on the disk the first time.

For now I do not trust using the Seagate in Ubuntu.

[rothchild (marc-rothera)]

This bug is infact a complete show stopper for me as I have just clocked that I cannot write to my external drive from Feisty using either pmount or sudo mount. I'm going to have to migrate back to dapper in order to use my hardware properly this is a bad thing.

Can someone with the power mark this bug as needing fixing or please tell me how to mount the drive so I can write to it?

Cheers
Child

[Xwang (xwang1976)]

I can confirm that Kubuntu 7.04 does not automatically mount external NTFS drive.
The /dev/sdb1 is correctly created, but I have to manually give this command pmount-hal /dev/sdb1 in order to mount it.
Can you fix it, please?
Xwang

[rothchild (marc-rothera)]

In response to Duncan Lithgow's recent email request I can confirm that USB auto-mounting is still not working using the Gusty Tribe4 i386 live cd, what's more it appears that the live cd doesn't have pmount installed by default so mounting it that way is not a solution.

My drive is formated FAT32, it is still being seen by HAL but not mounted:

ubuntu@ubuntu:~$ fdisk -l
Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot Start End Blocks Id System
/dev/sdb1 * 1 38913 312568641 c W95 FAT32 (LBA)

You may also be interested in some of the info contained in this thread: http://kubuntuforums.net/forums/index.php?topic=3085063.0

Which demonstrates a bit more of quite how broken *ubuntu is with regards to mounting USB hard-drives (and of course exposes what an ignorant noob I am too ;-))

If there is any other info I can supply that will help then please let me know as I need to see this bug fixed.

Cheers
Child

[rothchild (marc-rothera)]

Some update

Yesterday I upgraded one of my feisty boxen to gutsy (as usb automount doesn't work on either I may as well have the newer version to see what is going on and gutsy is due soon) upon installation / upgrade yesterday I was able to mount my drive with 'pmount-hal sdb1' and read from it.

I noticed that in todays update there were some hal related packages so I decided to try my drive again, firstly no automagic but secondly (and perhaps more seriously) I now get an error when issuing the pmount command.

:~$ fdisk -l

Disk /dev/sdb: 320.0 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x170a8ae2

   Device Boot Start End Blocks Id System
/dev/sdb1 * 1 38913 312568641 c W95 FAT32 (LBA)

:~$ pmount-hal sdb1
process 5387: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
libhal.c 1122 : Couldn't allocate D-BUS message
process 5387: arguments to dbus_message_new_method_call() were incorrect, assertion "_dbus_check_is_valid_path (path)" failed in file dbus-message.c line 1074.
This is normally a bug in some application using the D-Bus library.
libhal.c 1122 : Couldn't allocate D-BUS message
Error: given UDI is not a mountable volume

Child

[rothchild (marc-rothera)]

I followed the guide here: https://wiki.ubuntu.com/DebuggingRemovableDevices

And posted my results here: https://bugs.launchpad.net/ubuntu/+bug/130367

I'm now having trouble with USB Keys as well as the removable drive - feels like ubuntu is going backwards in terms of 'just works' :-(

This is on a bang up to date Gutsy install

Child

[rothchild (marc-rothera)]

All is well (for me at least), USB automounting now working properly for both hard-drive and pendrives.

Thankyou Ubuntu Devs

Child

[Phil Richards (news-derived-software)]

Sadly, I've still got the problem.

I know *where* the problem is in my case, but no idea how to fix it :-(
(See https://bugs.launchpad.net/ubuntu/+source/udev/+bug/118292)

It comes down to vol_id not recognising a vfat partition: the device entry is created, and I can mount it by hand:
$ sudo mount -o ro -t vfat /dev/sdg1 /mnt
works fine.

But, /sbin/vol_id shows:
$ vol_id /dev/sdg1
/dev/sdg1: unknown volume type

Of course, the system *can* recognise the partition properly if you use a different command:
$ blkid /dev/sdg1
/dev/sdg1: LABEL="SEA_DISK" UUID="0000-0ED4" TYPE="vfat"

So as 118292 says, it's a udev (vol_id) bug (possibly under Ubuntu).

I am somewhat loath to do the workarounds suggested (especially rewriting vol_id as a shell script), but unless somebody decides to fix it "properly", I don't see much choice.
I've been living with this bug since Feisty broke Edgy, and Gutsy is no better (yet :-), but it's a bit of a pain...

[Phil Richards (news-derived-software)]

Ok, having read the vol_id source code, and dumped out my header for /dev/sdg1 (my external disk) I think I have an idea what the problem is:

The SEAGATE drive I have has a single partition over its 250Gb. This has a sector size of 0x2000 (according to the disk header).

vol_id internally sanity checks the allowed sector sizes for a FAT* disk to be one of: 0x200, 0x400, 0x800, or 0x1000.

This check fails. The partition is therefore rejected as a FAT volume.

Simple fix would be to add 0x2000 as a valid sector size...

[Dan Lenski (lenski)]

I can confirm this bug as well. I have tried a USB-IDE enclosure, a thumb drive, two different cameras in UMS mode, and an MP3 player in UMS mode. They mostly have vfat filesystems, though I have tried ext3 as well. *ALL* of them automount just fine under Edgy.

If I run "udevmonitor -e" while inserting my Kingston DataTraveler 1gb flash drive, with one ext3 partition and one vfat partition, it reports that correctly:

UDEV [1191447365.558892] add /block/sdb/sdb2 (block)
UDEV_LOG=3
ACTION=add
DEVPATH=/block/sdb/sdb2
SUBSYSTEM=block
SEQNUM=2829
MINOR=18
MAJOR=8
PHYSDEVPATH=/devices/pci0000:00/0000:00:13.2/usb1/1-6/1-6:1.0/host6/target6:0:0/6:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
UDEVD_EVENT=1
DEVTYPE=partition
ID_VENDOR=Kingston
ID_MODEL=DataTraveler_2.0
ID_REVISION=1.00
ID_SERIAL=Kingston_DataTraveler_2.0_0000015955-0:0
ID_SERIAL_SHORT=0000015955
ID_TYPE=disk
ID_INSTANCE=0:0
ID_BUS=usb
ID_PATH=pci-0000:00:13.2-usb-0:6:1.0-scsi-0:0:0:0
ID_FS_USAGE=filesystem
ID_FS_TYPE=vfat
ID_FS_VERSION=FAT32
ID_FS_UUID=46E1-B3BA
ID_FS_UUID_ENC=46E1-B3BA
ID_FS_LABEL=
ID_FS_LABEL_ENC=
ID_FS_LABEL_SAFE=
DEVNAME=/dev/sdb2
DEVLINKS=/dev/disk/by-id/usb-Kingston_DataTraveler_2.0_0000015955-0:0-part2 /dev/disk/by-path/pci-0000:00:13.2-usb-0:6:1.0-scsi-0:0:0:0-part2 /dev/disk/by-uuid/46E1-B3BA

UDEV [1191447365.598111] add /block/sdb/sdb1 (block)
UDEV_LOG=3
ACTION=add
DEVPATH=/block/sdb/sdb1
SUBSYSTEM=block
SEQNUM=2828
MINOR=17
MAJOR=8
PHYSDEVPATH=/devices/pci0000:00/0000:00:13.2/usb1/1-6/1-6:1.0/host6/target6:0:0/6:0:0:0
PHYSDEVBUS=scsi
PHYSDEVDRIVER=sd
UDEVD_EVENT=1
DEVTYPE=partition
ID_VENDOR=Kingston
ID_MODEL=DataTraveler_2.0
ID_REVISION=1.00
ID_SERIAL=Kingston_DataTraveler_2.0_0000015955-0:0
ID_SERIAL_SHORT=0000015955
ID_TYPE=disk
ID_INSTANCE=0:0
ID_BUS=usb
ID_PATH=pci-0000:00:13.2-usb-0:6:1.0-scsi-0:0:0:0
ID_FS_USAGE=filesystem
ID_FS_TYPE=ext3
ID_FS_VERSION=1.0
ID_FS_UUID=9c19c221-e338-49a7-9614-df76a4b940e2
ID_FS_UUID_ENC=9c19c221-e338-49a7-9614-df76a4b940e2
ID_FS_LABEL=Xubuntu
ID_FS_LABEL_ENC=Xubuntu
ID_FS_LABEL_SAFE=Xubuntu
DEVNAME=/dev/sdb1
DEVLINKS=/dev/disk/by-id/usb-Kingston_DataTraveler_2.0_0000015955-0:0-part1 /dev/disk/by-path/pci-0000:00:13.2-usb-0:6:1.0-scsi-0:0:0:0-part1 /dev/disk/by-uuid/9c19c221-e338-49a7-9614-df76a4b940e2 /dev/disk/by-label/Xubuntu

Also, dbus-monitor seems to be sending out signals to Gnome to mount the two new partitions:

signal sender=:1.4 -> dest=(null destination) path=/org/gnome/GnomeVFS/Daemon; interface=org.gnome.GnomeVFS.Daemon; member=DriveConnectedSignal
   struct {
      int32 8
      int32 3
      array [
      ]
      string "/dev/sdb2"
      string ""
      string "Kingston DataTraveler 2.0"
      string "gnome-dev-removable-usb"
      string "/org/freedesktop/Hal/devices/volume_uuid_46E1_B3BA"
      boolean true
      boolean true
      boolean false
   }
signal sender=:1.4 -> dest=(null destination) path=/org/gnome/GnomeVFS/Daemon; interface=org.gnome.GnomeVFS.Daemon; member=DriveConnectedSignal
   struct {
      int32 9
      int32 3
      array [
      ]
      string "/dev/sdb1"
      string ""
      string "Kingston DataTraveler 2.0 (2)"
      string "gnome-dev-removable-usb"
      string "/o...

[Tanker Bob (tankerbob)]

I also have this problem on Kubuntu Gutsy installed clean. I posted details at http://ubuntuforums.org/showthread.php?t=594421. I'll repeat some of that here for convenience and add a few things.

Short description is that no USB removable FAT file system will automount in my Kubuntu Gutsy. I have a USB external FAT hard drive, several flash sticks, and a USB card reader. The USB external hard drive connects directly to the motherboard port, the sticks and card reader through a hub. My USB printer, Bluetooth stick, and camera have no problems with auto mounting, and the Bluetooth connects through the USB hub. It is only USB removable storage devices with FAT file systems that don't auto mount.

I have tried adding the USB HD to /etc/fstab at its usually assigned address, but Kubuntu also tries to create a drive out of the 1K marker for the extended partition on another ext3 internal hard drive. It seems that whatever is next in line, be it the USB HD's entry (usually sdd or sdi) or the floppy drive (fd0), that bogus partition captures other devices' entries. The other mounts on that other disk are hda1, hda5 (only entry in the extended partition), and hda3 (linux swap partition). I can manually create the mounting for the USB drive only if the 1K extended partition marker doesn't steal the mounting point. At the moment it is squatting on the floppy's mounting point, but the floppy works fine. I finally solved this by putting the USB HD in fstab by name rather than address. No problems with the internal NTFS volume loading.

My initial workaround for the flash sticks and cards uses Dolphin''s Storage Media, which notes the insertion of the sticks/cards/USB HD even though they are not mounted. Opening the stick/card/HD in Dolphin correctly automatically mounts the devices. This gets pretty annoying of one is swapping sticks or cards a lot. I can also see all the inserted devices using "lsusb" when they are not auto mounted. The problem is not one of detecting the devices--all are detected immediately upon insertion, just not auto mounted.

Then I discovered that if I used Dolphin to mount the sticks and cards that I commonly use, but giving them custom mounting point names and checking the auto mount box in the mounting dialog allows the devices to be automounted after that, even after restarts. The mounting points in /media are recreated upon insertion. Devices that didn't go through this process still do not automount, though.

Running 'dmesg | grep usb' produces the following new lines after plugging in a USB stick:

[117008.216420] usb-storage: device found at 14
[117008.216422] usb-storage: waiting for device to settle before scanning
[117013.205095] usb-storage: device scan complete

Running 'udevmonitor --udev' while plugging in a USB flash stick gives:

UDEV [1194051580.440807] add /devices/pci0000:00/0000:00:0b.1/usb1/1-2/1-2.4/1-2.4.1 (usb)
UDEV [1194051580.443599] add /class/usb_endpoint/usbdev1.16_ep00 (usb_endpoint)
UDEV [1194051580.460611] add /devices/pci0000:00/0000:00:0b.1/usb1/1-2/1-2.4/1-2.4.1/1-2.4.1:1.0 (usb)
UDEV [1194051580.466864] add /class/scsi_host/host10 (scsi_host)
UDEV [1194051580.467364] a...

[Tanker Bob (tankerbob)]

My OS crashed big time today, taking the \ partition down with it. I had to rebuild the \ partition from scratch, but my \home partition survived relatively intact. After a complete reinstall, the USB automounting problem remained unchanged. That was a bit disappointing.

[Dominic Webb (dominic-webb)]

I can confirm multiple Gutsy (network upgraded from Fiesty) machines have problems with multiple usb sticks and card readers, that worked under Fiesty without issue.

A simple, but not user friendly solution is:

sudo mount -t vfat /dev/{sdb1 or such like} /media/{dir_of_choice}

Typical error seems to say "mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program or other error In some cases useful info is found in syslog - try dmesg | tail or so"

Have tried removing (then adding back in) the "usefree" option in gconf-editor.

Seems that auto mounting in Gutsy(Fiesty as well ?) has gone completely belly up!

[steph_Z (polariscorp)]

kubuntu gutsy -> confirmed on my 3 computers with fresh install

shame a bug like this this is still here

... how can bug n°1 be erased with such a bug.........

[Endolith (endolith)]

Looks like every person here has a different problem. :-)

I also have lost auto-mounting for one external Seagate drive but not the other, ever since the Feisty upgrade, and have posted my troubleshooting information here:

https://bugs.launchpad.net/ubuntu/+bug/163386

Please help me troubleshoot this. I've been waiting for help on this since April.

[Atlanx (atlanx)]

If I plug in my 250Gig FAT formated USB-Drive from Lacie it get automounted under Gutsy Gibbon.
But if I plug in my My_Book(NTFS formated) from WD it will not get automounted. The difference between this two drives is that the
MyBook starts automatically if it detects an connection over usb.

If I start the MyBook BEVOR I plug the USB cable in it will get automounted, too!!!

[Paul Dufresne (paulduf)]

Could be linked to bug #235134, but not sure at all, this bug here being relatively old.

[Freon (freongrr)]

I know nobody has commented on this bug in a while, but I still have the problem...
Here is the content of /var/log/message
No error... I can mount it manually...

I tried formatting the drive and it DID solve the problem. But now that it's broken again I don't want to do that every couple of day...

Feb 25 17:11:16 xps kernel: [ 680.464188] usb 7-1: new high speed USB device using ehci_hcd and address 5
Feb 25 17:11:16 xps kernel: [ 680.599346] usb 7-1: configuration #1 chosen from 1 choice
Feb 25 17:11:16 xps kernel: [ 680.604434] scsi6 : SCSI emulation for USB Mass Storage devices
Feb 25 17:11:21 xps kernel: [ 685.621133] scsi 6:0:0:0: Direct-Access WD 2500BEV External 1.05 PQ: 0 ANSI: 4
Feb 25 17:11:21 xps kernel: [ 685.647334] sd 6:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
Feb 25 17:11:21 xps kernel: [ 685.648226] sd 6:0:0:0: [sdb] Write Protect is off
Feb 25 17:11:21 xps kernel: [ 685.648954] sd 6:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
Feb 25 17:11:21 xps kernel: [ 685.649852] sd 6:0:0:0: [sdb] Write Protect is off
Feb 25 17:11:22 xps kernel: [ 685.649875] sdb: sdb1
Feb 25 17:11:22 xps kernel: [ 685.703608] sd 6:0:0:0: [sdb] Attached SCSI disk
Feb 25 17:11:22 xps kernel: [ 685.703818] sd 6:0:0:0: Attached scsi generic sg2 type 0

[Freon (freongrr)]

Unloading "ehci_hcd" to disable the High Speed mode did the trick.
Here is the new log.

Feb 25 17:23:24 xps kernel: [ 1406.985032] usb 4-1: new full speed USB device using uhci_hcd and address 3
Feb 25 17:23:24 xps kernel: [ 1407.148585] usb 4-1: configuration #1 chosen from 1 choice
Feb 25 17:23:24 xps kernel: [ 1407.152644] scsi9 : SCSI emulation for USB Mass Storage devices
Feb 25 17:23:29 xps kernel: [ 1412.161203] scsi 9:0:0:0: Direct-Access WD 2500BEV External 1.05 PQ: 0 ANSI: 4
Feb 25 17:23:29 xps kernel: [ 1412.168090] sd 9:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
Feb 25 17:23:29 xps kernel: [ 1412.173110] sd 9:0:0:0: [sdb] Write Protect is off
Feb 25 17:23:29 xps kernel: [ 1412.178102] sd 9:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
Feb 25 17:23:29 xps kernel: [ 1412.183100] sd 9:0:0:0: [sdb] Write Protect is off
Feb 25 17:23:29 xps kernel: [ 1412.183126] sdb: sdb1
Feb 25 17:23:29 xps kernel: [ 1412.224396] sd 9:0:0:0: [sdb] Attached SCSI disk
Feb 25 17:23:29 xps kernel: [ 1412.224619] sd 9:0:0:0: Attached scsi generic sg2 type 0

But it's still a bug. Why can the drive be *auto* mounted in high speed mode?

[Joe Kuan (yetanotherstupidsignup)]

Please check whether you have the package usbmount installed. Usbmount is a package that works with udev to automount usb devices. If you got it installed, then check /etc/usbmount/usbmount.conf to make sure it includes vfat filesystem. Usbmount's default configuration for filesystem support only includes ext2 and ext3.

http://joekuan.wordpress.com/2009/03/03/troubleshooting-on-usbmount/

Hope this helps

[Thomas Hotz (thotz-deactivatedaccount)]

Your Ubuntu version is EOL. Can you retest this with a supported Ubuntu version please?

[Launchpad Janitor (janitor)]

[Expired for hal (Ubuntu) because there has been no activity for 60 days.]