usb hard drive not recognized at startup

Asked by buck2202 on 2009-04-28

I have a Seagate FreeAgent 500GB usb hard drive that worked perfectly under Intrepid. It would recognize and mount it on startup if it was already plugged in, or automatically mount it if I plugged it in while the system was on.

Since upgrading to Jaunty, the drive is no longer mounted on startup. The lsusb command always shows that it is present, but blkid / fdisk -l don't show any information on it. Configuring fstab with the mounting information has no effect, and I can't mount it manually since the computer doesn't recognize it as disk space.

If I disconnect/reconnect the device after the system starts up, it works properly.

I've tried the drive on a different computer (also running Jaunty), and it mounts normally under both circumstances (present at startup, or plugged in later).

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
Steve
Solved:
2009-04-28
Last query:
2009-04-28
Last reply:
2009-04-28
buck2202 (buck2202) said : #1

kernel.log extract for unsuccessful loading (already connected at startup):
kernel: [ 2.244021] usb 1-2: new high speed USB device using ehci_hcd and address 2
kernel: [ 2.390447] usb 1-2: configuration #1 chosen from 1 choice
and then onto other things..

kernel.log extract for successful loading (connected after startup):
kernel: [12867.692532] usb 1-2: new high speed USB device using ehci_hcd and address 4
kernel: [12867.839570] usb 1-2: configuration #1 chosen from 1 choice
kernel: [12867.922260] Initializing USB Mass Storage driver...
kernel: [12867.924207] scsi4 : SCSI emulation for USB Mass Storage devices
kernel: [12867.932272] usbcore: registered new interface driver usb-storage
kernel: [12867.932281] USB Mass Storage support registered.
kernel: [12867.944296] usb-storage: device found at 4
kernel: [12867.944302] usb-storage: waiting for device to settle before scanning
kernel: [12872.941494] usb-storage: device scan complete
kernel: [12872.943135] scsi 4:0:0:0: Direct-Access Seagate FreeAgent 102C PQ: 0 ANSI: 4
kernel: [12881.792954] sd 4:0:0:0: [sdd] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
kernel: [12881.794184] sd 4:0:0:0: [sdd] Write Protect is off
kernel: [12881.794190] sd 4:0:0:0: [sdd] Mode Sense: 1c 00 00 00
kernel: [12881.794195] sd 4:0:0:0: [sdd] Assuming drive cache: write through
kernel: [12881.796060] sd 4:0:0:0: [sdd] 976773168 512-byte hardware sectors: (500 GB/465 GiB)
kernel: [12881.799199] sd 4:0:0:0: [sdd] Write Protect is off
kernel: [12881.799206] sd 4:0:0:0: [sdd] Mode Sense: 1c 00 00 00
kernel: [12881.799210] sd 4:0:0:0: [sdd] Assuming drive cache: write through
kernel: [12881.799219] sdd: sdd1
kernel: [12882.023156] sd 4:0:0:0: [sdd] Attached SCSI disk
kernel: [12882.023305] sd 4:0:0:0: Attached scsi generic sg4 type 0

buck2202 (buck2202) said : #2

Just as a note, both of my computers are running clean installs of Jaunty. The non-working one with the amd64 version, the working one with i386.

Add usb_storage to /etc/modules - It should fix it. Bug 364933 is about this. If adding the module fixes it, can you please add a comment in there saying that you're experiencing it too, and that it's AMD64 (nobody in there is on AMD64 yet, I think).

It's odd that it works fine on another system. Wonder if there's a hardware difference for those of us who have it not working.

peter b (b1pete) said : #4

Steven, pls take a look at #344406 too.

regards,
peter b

peter b (b1pete) said : #5

I'm v sorry, it should have been Steven and David.

my apologies.
peter b

buck2202 (buck2202) said : #6

Thanks Steven Susbauer, that solved my question.