usb toshiba 80 GB detachable HD not getting mounted, not getting creted any device file

Bug #109563 reported by dd
2
Affects Status Importance Assigned to Milestone
hal (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: hal

Feisty Fawn U-7.04: password protection in the detachable HD is disabled. When it was enabled I tried it on my laptop (Acer). It was giving the same problem. Then I disabled the password protection from a MSW-XP box, after that I could use it with my laptop. Then I created a ReiserFS partition on it. And is using it with my laptop with the same Feisty Fawn 7.04. With my desktop, again it is giving problem, though password is disabled, and FS is Reiser. The output of 'lsusb' is:

Bus 003 Device 008: ID 0930:0b06 Toshiba Corp.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 003: ID 0461:4d15 Primax Electronics, Ltd
Bus 001 Device 001: ID 0000:0000

The Primax thing is my USB mouse, that is working properly. The output of dmesg is:
[ 429.810119] usb 3-5: new high speed USB device using ehci_hcd and address 5
[ 429.943083] usb 3-5: configuration #1 chosen from 1 choice
[ 429.943317] scsi3 : SCSI emulation for USB Mass Storage devices
[ 429.943550] usb-storage: device found at 5
[ 429.943554] usb-storage: waiting for device to settle before scanning
[ 432.119783] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 434.941962] usb-storage: device scan complete
[ 434.942814] scsi 3:0:0:0: CD-ROM Toshiba USB 2.0 CD-ROM 1.15 PQ: 0 ANSI: 0
[ 440.548890] usb 3-5: reset high speed USB device using ehci_hcd and address 5
[ 450.784140] usb 3-5: reset high speed USB device using ehci_hcd and address 5
[ 462.526013] usb 3-5: reset high speed USB device using ehci_hcd and address 5
[ 468.265077] usb 3-5: reset high speed USB device using ehci_hcd and address 5
[ 474.004143] usb 3-5: reset high speed USB device using ehci_hcd and address 5
[ 474.160286] sr1: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
[ 474.160427] sr 3:0:0:0: Attached scsi CD-ROM sr1
[ 474.160511] sr 3:0:0:0: Attached scsi generic sg3 type 5
[ 973.283142] sr1: CDROM not ready. Make sure there is a disc in the drive.
[ 973.286384] sr1: CDROM not ready. Make sure there is a disc in the drive.
[ 1323.378394] usb 3-5: USB disconnect, address 5
[ 1408.749019] usb 3-6: new high speed USB device using ehci_hcd and address 8
[ 1408.882014] usb 3-6: configuration #1 chosen from 1 choice
[ 1408.882373] scsi4 : SCSI emulation for USB Mass Storage devices
[ 1408.882589] usb-storage: device found at 8
[ 1408.882592] usb-storage: waiting for device to settle before scanning
[ 1413.880869] usb-storage: device scan complete
[ 1413.881697] scsi 4:0:0:0: CD-ROM Toshiba USB 2.0 CD-ROM 1.15 PQ: 0 ANSI: 0
[ 1419.487769] usb 3-6: reset high speed USB device using ehci_hcd and address 8
[ 1429.722979] usb 3-6: reset high speed USB device using ehci_hcd and address 8
[ 1441.456901] usb 3-6: reset high speed USB device using ehci_hcd and address 8
[ 1447.195964] usb 3-6: reset high speed USB device using ehci_hcd and address 8
[ 1452.939045] usb 3-6: reset high speed USB device using ehci_hcd and address 8
[ 1453.094070] sr1: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
[ 1453.094209] sr 4:0:0:0: Attached scsi CD-ROM sr1
[ 1453.094310] sr 4:0:0:0: Attached scsi generic sg3 type 5

So, it is getting it alright. But I cannot access or use it.

ProblemType: Bug
Architecture: i386
Date: Tue Apr 24 15:02:02 2007
DistroRelease: Ubuntu 7.04
Package: hal 0.5.8.1-4ubuntu12
PackageArchitecture: i386
SourcePackage: hal
Uname: Linux mahammad 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

Revision history for this message
dd (paagol) wrote :
Revision history for this message
dd (paagol) wrote :

Still having the problem.

This is the 'lsusb' output after I attached it.

<<<
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 0461:4d15 Primax Electronics, Ltd
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 006: ID 0930:0b06 Toshiba Corp.
Bus 001 Device 001: ID 0000:0000
>>>

This is the 'dmesg' part after I attached it.

<<<
[ 3813.123804] usb 1-6: new high speed USB device using ehci_hcd and address 4
[ 3813.256808] usb 1-6: configuration #1 chosen from 1 choice
[ 3813.825197] usbcore: registered new interface driver libusual
[ 3813.853781] Initializing USB Mass Storage driver...
[ 3813.853940] scsi2 : SCSI emulation for USB Mass Storage devices
[ 3813.854054] usbcore: registered new interface driver usb-storage
[ 3813.854058] USB Mass Storage support registered.
[ 3813.854327] usb-storage: device found at 4
[ 3813.854330] usb-storage: waiting for device to settle before scanning
[ 3818.850666] usb-storage: device scan complete
[ 3818.851509] scsi 2:0:0:0: CD-ROM Toshiba USB 2.0 CD-ROM 1.15 PQ: 0 ANSI: 0
[ 3824.457204] usb 1-6: reset high speed USB device using ehci_hcd and address 4
[ 3834.691595] usb 1-6: reset high speed USB device using ehci_hcd and address 4
[ 3846.424970] usb 1-6: reset high speed USB device using ehci_hcd and address 4
[ 3852.163213] usb 1-6: reset high speed USB device using ehci_hcd and address 4
[ 3857.901831] usb 1-6: reset high speed USB device using ehci_hcd and address 4
[ 3858.063683] sr1: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
[ 3858.063823] sr 2:0:0:0: Attached scsi CD-ROM sr1
[ 3858.063910] sr 2:0:0:0: Attached scsi generic sg3 type 5
[ 3935.249367] usb 1-6: USB disconnect, address 4
[ 4044.079307] usb 1-5: new high speed USB device using ehci_hcd and address 6
[ 4044.224334] usb 1-5: configuration #1 chosen from 1 choice
[ 4044.224591] scsi3 : SCSI emulation for USB Mass Storage devices
[ 4044.224815] usb-storage: device found at 6
[ 4044.224819] usb-storage: waiting for device to settle before scanning
[ 4049.222732] usb-storage: device scan complete
[ 4049.223564] scsi 3:0:0:0: CD-ROM Toshiba USB 2.0 CD-ROM 1.15 PQ: 0 ANSI: 0
[ 4054.833227] usb 1-5: reset high speed USB device using ehci_hcd and address 6
[ 4065.071649] usb 1-5: reset high speed USB device using ehci_hcd and address 6
[ 4076.812627] usb 1-5: reset high speed USB device using ehci_hcd and address 6
[ 4082.555243] usb 1-5: reset high speed USB device using ehci_hcd and address 6
[ 4088.297860] usb 1-5: reset high speed USB device using ehci_hcd and address 6
[ 4088.454963] sr1: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
[ 4088.455106] sr 3:0:0:0: Attached scsi CD-ROM sr1
[ 4088.455193] sr 3:0:0:0: Attached scsi generic sg3 type 5

>>>

But, it is not automounted, as it usually happens with USB devices, neither I can mount it myself, because I don't get any device file added.

Revision history for this message
dd (paagol) wrote :

A 512 MB detachable stick (with VFAT) is getting automounted, and the device it is getting attached to is /dev/sdc. The two HD-s are /dev/sda and /dev/sdb.

This toshiba 80 GB detachable HD was first giving the same problem with my Acer laptop, when it was password protection enabled, and then I made it off with an MSW-XP machine, and made the whole thing one single ReiserFS partition. And now it is working fine with the laptop. But, it is not working with the desktop.

Where exactly is the problem?

Revision history for this message
dd (paagol) wrote :

Actually, the problem was neither in the desktop machine, nor in the USB HD. It got solved in the most curious of ways. One guy told me to try the HD not in the USB port on the front panel, but on the back of the cabinet, he said he has seen this happen. I did it, and that very moment it got connected and mounted. I don't know why. Maybe the amount of current supplied to the USB port in the front panel was inadequate for this high-speed USB HD. And I browsed the documentation of the motherboard. It is not there too, about any difference in the amount of electricity. But it happened. And maybe, because the current was inadequate, it was taking very very long for 'dmesg' to report the drive and its specification.

Pasting the 'dmesg' portion here, if it is of any help to anybody:

[ 724.672031] usb 3-3: new high speed USB device using ehci_hcd and address 4
[ 724.805010] usb 3-3: configuration #1 chosen from 1 choice
[ 724.950485] usbcore: registered new interface driver libusual
[ 724.966149] Initializing USB Mass Storage driver...
[ 724.966297] scsi2 : SCSI emulation for USB Mass Storage devices
[ 724.966410] usbcore: registered new interface driver usb-storage
[ 724.966415] USB Mass Storage support registered.
[ 724.966665] usb-storage: device found at 4
[ 724.966669] usb-storage: waiting for device to settle before scanning
[ 729.963824] usb-storage: device scan complete
[ 729.964650] scsi 2:0:0:0: CD-ROM Toshiba USB 2.0 CD-ROM 1.15 PQ: 0 ANSI: 0
[ 729.966150] scsi 2:0:0:1: Direct-Access Toshiba USB 2.0 Ext. HDD 1.15 PQ: 0 ANSI: 0
[ 730.020711] sr1: scsi3-mmc drive: 52x/52x cd/rw xa/form2 cdda tray
[ 730.020866] sr 2:0:0:0: Attached scsi CD-ROM sr1
[ 730.020952] sr 2:0:0:0: Attached scsi generic sg3 type 5
[ 730.023495] SCSI device sdc: 156250072 512-byte hdwr sectors (80000 MB)
[ 730.024574] sdc: Write Protect is off
[ 730.024578] sdc: Mode Sense: 0b 00 00 08
[ 730.024583] sdc: assuming drive cache: write through
[ 730.025705] SCSI device sdc: 156250072 512-byte hdwr sectors (80000 MB)
[ 730.026572] sdc: Write Protect is off
[ 730.026577] sdc: Mode Sense: 0b 00 00 08
[ 730.026579] sdc: assuming drive cache: write through
[ 730.026586] sdc: sdc1
[ 730.052996] sd 2:0:0:1: Attached scsi disk sdc
[ 730.053082] sd 2:0:0:1: Attached scsi generic sg4 type 0
[ 730.826216] ReiserFS: sdc1: found reiserfs format "3.6" with standard journal
[ 730.826869] ReiserFS: sdc1: using ordered data mode
[ 730.833859] ReiserFS: sdc1: journal params: device sdc1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
[ 730.837014] ReiserFS: sdc1: checking transaction log (sdc1)
[ 730.920128] ReiserFS: sdc1: Using r5 hash to sort names

And, 'lsusb' shows it as:

Bus 003 Device 004: ID 0930:0b06 Toshiba Corp.

Revision history for this message
Martin Pitt (pitti) wrote :

Right, this seems to be an electrical problem then; in your first dmesg outputs there were a lot of bus resets, which usually happen if the device gets into an undefined state (common for brownout).

Changed in hal:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.