Re: Memorex TravelDrive not automounting on FC6 x86_64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



At 10:53 PM -0700 5/25/07, Raymond C. Rodgers wrote:
>I originally posted this cry for help almost a week ago under the "Re:
>usb stick, can't mount" thread, but there hasn't been the slightest hint
>of a response; I'm taking the view point that that thread is considered
>dead without a resolution. I'm hoping that someone will notice my new
>thread and be able to help.
>
>The quick summary of the issue is that my USB 1 GB Memorex TravelDrive
>used to auto-mount perfectly under FC6 x86_64 up until a couple weeks
>ago, when it suddenly stopped. I am able to manually mount it using
>mount or pmount command line tools, but oddly the drive continues to
>auto-mount perfectly at work under FC5 i386, on another machine here at
>home running FC6 i386 that hasn't been updated in several months, and of
>course gets mounted properly under Windows 2000 & XP. I've toggled all
>of the auto-mount settings under Removable Drives and Media, but the
>problem remains that when I plug the TravelDrive into the problem
>machine while in FC6 x86_64, the drive gets mounted and unmounted within
>the span of half a second. No error messages appear, no warnings, nothing.
>
>I'm attaching the dmesg output from both the working FC6 i386 machine
>and the FC6 x86_64 non-working machine. The only significant difference
>I think I've seen is that the i386 machine appears to be using USB 1.1
>to access the TravelDrive (admittedly though a hub) where as the x86_64
>machine is using 2.0. The TravelDrive supports both, and it operates
>normally when manually mounted through mount/pmount on the "non-working"
>64 bit machine.
>
>Could a kernel update have broken this? Does anyone have an idea how to
>fix the problem? Like I said, I can manually mount it but that's a bit
>of a pain...
>
>Thank you,
>Raymond
>
>Linux version 2.6.19-1.2895.fc6 (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxx)
>(gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Wed Jan 10 19:28:18
>EST 2007
>BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
> BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000004fff0000 (usable)
> BIOS-e820: 000000004fff0000 - 000000004fff3000 (ACPI NVS)
> BIOS-e820: 000000004fff3000 - 0000000050000000 (ACPI data)
> BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
> BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
> BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
>383MB HIGHMEM available.
>896MB LOWMEM available.
>found SMP MP-table at 000f5410
>Using x86 segment limits to approximate NX protection
 ...
>usb 1-2.3: new full speed USB device using uhci_hcd and address 6
>usb 1-2.3: not running at top speed; connect to a high speed hub
>usb 1-2.3: configuration #1 chosen from 1 choice
>scsi1 : SCSI emulation for USB Mass Storage devices
>usb-storage: device found at 6
>usb-storage: waiting for device to settle before scanning
>scsi 1:0:0:0: Direct-Access     Memorex  TD Classic 003B  PMAP PQ: 0 ANSI:
>0 CCS
>SCSI device sdb: 2007040 512-byte hdwr sectors (1028 MB)
>sdb: Write Protect is off
>sdb: Mode Sense: 23 00 00 00
>sdb: assuming drive cache: write through
>SCSI device sdb: 2007040 512-byte hdwr sectors (1028 MB)
>sdb: Write Protect is off
>sdb: Mode Sense: 23 00 00 00
>sdb: assuming drive cache: write through
> sdb: sdb1
>sd 1:0:0:0: Attached scsi removable disk sdb
>sd 1:0:0:0: Attached scsi generic sg1 type 0
>usb-storage: device scan complete

AFAICT the x86 one looks OK.  The memory stick is connected to an external
High-speed (USB 1.1) hub.


>Linux version 2.6.20-1.2948.fc6 (brewbuilder@xxxxxxxxxxxxxxxxxxxxxxxxxxxx)
>(gcc version 4.1.1 20070105 (Red Hat 4.1.1-51)) #1 SMP Fri Apr 27 19:18:54
>EDT 2007
>Command line: ro root=/dev/VolGroup00/LogVol00 rhgb quiet
>BIOS-provided physical RAM map:
 ...
>AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ stepping 01
 ...
>usb 2-6: new high speed USB device using ehci_hcd and address 2
>usb 2-6: configuration #1 chosen from 1 choice
>Initializing USB Mass Storage driver...
>scsi4 : SCSI emulation for USB Mass Storage devices
>usb-storage: device found at 2
>usb-storage: waiting for device to settle before scanning
>usbcore: registered new interface driver usb-storage
>USB Mass Storage support registered.
>scsi 4:0:0:0: Direct-Access     Memorex  TD Classic 003B  PMAP PQ: 0 ANSI:
>0 CCS
>SCSI device sdc: 2007040 512-byte hdwr sectors (1028 MB)
>sdc: Write Protect is off
>sdc: Mode Sense: 23 00 00 00
>sdc: assuming drive cache: write through
>SCSI device sdc: 2007040 512-byte hdwr sectors (1028 MB)
>sdc: Write Protect is off
>sdc: Mode Sense: 23 00 00 00
>sdc: assuming drive cache: write through
> sdc: sdc1
>sd 4:0:0:0: Attached scsi removable disk sdc
>sd 4:0:0:0: Attached scsi generic sg2 type 0
>usb-storage: device scan complete

AFAICT the x64 one also looks OK.  The memory stick is connected to a
High-speed (USB 1.1) hub.

ISTM that the problem is after the USB part of things.  Look at other logs,
such as /var/log/messages, /var/log/audit/audit.log if you have one, or
maybe /var/log/secure.

I assume that you are plugging the device after booting?
-- 
____________________________________________________________________
TonyN.:'                       <mailto:tonynelson@xxxxxxxxxxxxxxxxx>
      '                              <http://www.georgeanelson.com/>


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux