USB/Firewire Mass Storage Drive doesnt properly mount

[justin420]

When hot-plugging a Seagate USB/Firewire 500GB External HD no icon shows up on the desktop, but syslog says everything is ok. Here the syslog entries related to the drive that doesnt show up with the little icon on the desktop. This drive is formatted with FAT32

Jul 15 09:45:11 Justin kernel: [ 2426.527286] ieee1394: sbp2: Logged into SBP-2 device
Jul 15 09:45:11 Justin kernel: [ 2426.527361] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Jul 15 09:45:11 Justin kernel: [ 2426.529949] scsi 4:0:0:0: Direct-Access Seagate ST3500641A 4.07 PQ: 0 ANSI: 0
Jul 15 09:45:11 Justin kernel: [ 2426.531467] SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
Jul 15 09:45:11 Justin kernel: [ 2426.532774] sdc: Write Protect is off
Jul 15 09:45:11 Justin kernel: [ 2426.532782] sdc: Mode Sense: 10 00 00 00
Jul 15 09:45:11 Justin kernel: [ 2426.535266] sdc: got wrong page
Jul 15 09:45:11 Justin kernel: [ 2426.535275] sdc: assuming drive cache: write through
Jul 15 09:45:11 Justin kernel: [ 2426.536740] SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
Jul 15 09:45:11 Justin kernel: [ 2426.538050] sdc: Write Protect is off
Jul 15 09:45:11 Justin kernel: [ 2426.538057] sdc: Mode Sense: 10 00 00 00
Jul 15 09:45:11 Justin kernel: [ 2426.540521] sdc: got wrong page
Jul 15 09:45:11 Justin kernel: [ 2426.540528] sdc: assuming drive cache: write through
Jul 15 09:45:11 Justin kernel: [ 2426.540534] sdc: sdc1
Jul 15 09:45:11 Justin kernel: [ 2426.572871] sd 4:0:0:0: Attached scsi disk sdc
Jul 15 09:45:11 Justin kernel: [ 2426.572940] sd 4:0:0:0: Attached scsi generic sg4 type 0

I also have a Seagate FreeAgent Pro 500GB USB/Firewire External HD that when either using usb or firewire it mounts properly and a little icon is placed on the desktop. Here is the syslog for the Seagate FreeAgent Drive Pro. This drive is formatted with NTFS

Jul 15 09:55:22 Justin kernel: [ 3037.774373] scsi7 : SBP-2 IEEE-1394
Jul 15 09:55:23 Justin kernel: [ 3038.798564] ieee1394: sbp2: Logged into SBP-2 device
Jul 15 09:55:23 Justin kernel: [ 3038.799553] ieee1394: sbp2: Node 0-00:1023: Max speed [S400] - Max payload [2048]
Jul 15 09:55:23 Justin kernel: [ 3038.809413] scsi 7:0:0:0: Direct-Access Seagate FreeAgentPro FW4 120R PQ: 0 ANSI: 4
Jul 15 09:55:23 Justin kernel: [ 3038.812599] SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
Jul 15 09:55:23 Justin kernel: [ 3038.814781] sdc: Write Protect is off
Jul 15 09:55:23 Justin kernel: [ 3038.816195] sdc: cache data unavailable
Jul 15 09:55:23 Justin kernel: [ 3038.819175] SCSI device sdc: 976773168 512-byte hdwr sectors (500108 MB)
Jul 15 09:55:23 Justin kernel: [ 3038.821186] sdc: Write Protect is off
Jul 15 09:55:23 Justin kernel: [ 3038.822673] sdc: cache data unavailable
Jul 15 09:55:23 Justin kernel: [ 3038.822687] sdc: sdc1
Jul 15 09:55:23 Justin kernel: [ 3038.834125] sd 7:0:0:0: Attached scsi disk sdc
Jul 15 09:55:23 Justin kernel: [ 3038.834210] sd 7:0:0:0: Attached scsi generic sg4 type 0
Jul 15 09:55:24 Justin kernel: [ 3039.408521] NTFS volume version 3.1.

Here is an output of sudo lspci and lsusb.

justin@Justin:~$ sudo lspci && sudo lsusb
Password:
00:00.0 Host bridge: Intel Corporation 82850 850 (Tehama) Chipset Host Bridge (MCH) (rev 02)
00:01.0 PCI bridge: Intel Corporation 82850 850 (Tehama) Chipset AGP Bridge (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 04)
00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 04)
00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 (rev 04)
00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #1) (rev 04)
00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus (rev 04)
00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB (Hub #2) (rev 04)
01:00.0 VGA compatible controller: nVidia Corporation NV40 [GeForce 6800 GS] (rev a1)
02:09.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
02:0a.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
02:0a.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
02:0a.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 63)
02:0a.3 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80)
02:0b.0 Multimedia video controller: Conexant CX23880/1/2/3 PCI Video and Audio Decoder (rev 05)
02:0c.0 Multimedia audio controller: Creative Labs SB Live! EMU10k1 (rev 08)
02:0c.1 Input device controller: Creative Labs SB Live! Game Port (rev 08)
02:0d.0 Network controller: Broadcom Corporation BCM4318 [AirForce One 54g] 802.11g Wireless LAN Controller (rev 02)
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 003: ID 046d:08b2 Logitech, Inc. QuickCam Pro 4000
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
Bus 002 Device 001: ID 0000:0000
Bus 005 Device 002: ID 2001:f103 D-Link Corp. [hex]
Bus 005 Device 001: ID 0000:0000
Bus 004 Device 001: ID 0000:0000
Bus 001 Device 002: ID 0bc7:0004 X10 Wireless Technology, Inc. X10 Receiver
Bus 001 Device 001: ID 0000:0000
justin@Justin:~$ uname -a
Linux Justin 2.6.20-16-generic #2 SMP Thu Jun 7 20:19:32 UTC 2007 i686 GNU/Linux
justin@Justin:~$

If any other information is needed please let me know, as I really would like to get this issue solved. Thanks in advance.

[Tommy Trussell (tommy-trussell)]

I noticed your bug because I'm having a problem with a Firewire/ieee1394 drive, but I just switched to a new MyBook because I'm hoping it will be more reliable. So far so good....

I'm noticing your dmesg and uname -- are you using a custom kernel?

Does the drive work properly and/or show different messages when you boot from the stock kernel and/or use an Ubuntu live CD?

Also, have you tried the USB port to see if it works?

ALSO, I had a problem with my Western Digital MyBook Premium Edition because it turns out the FIREWIRE CABLE that comes in the box is defective, and using it apparently destroyed BOTH Firewire ports on the drive. Call the manufacturer immediately. If they confirm you're affected, get a replacement cable and DON'T use the one that came in the box anywhere.

If you have another machine and a different Firewire cable you can confirm whether the ports work at all. In my case, the USB port continued working. However, since I had paid a premium for the Firewire model, I exchanged the drive at the store where I bought it, and have not had any trouble with the new one (though I DID NOT use the Firewire cable in the box!!!).

Hope that helps.

[unggnu (unggnu)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #126825 so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug.
Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

[Fabián Rodríguez (magicfab)]

Issues described are a result of this drive going to auto-sleep.

Changing duplicate marking to Bug #193154.