Am Donnerstag, 27. September 2012 schrieb Filipe Freire:
> Dear All!
> 
> I am having problems getting a stable mount of an extern FREECOM HD on
> debian squeeze.
> 
> Sometimes it mounts and by running
> # blkid -o list -c /dev/null
> 
> get
> 
> /dev/sdb1  vfat    FREECOM HDD /media/FREECOM HDD 13EC-4051
> 
> but it often umounts while copying files and can not mount it again.  Tried
> placing the line in fstab
> 
> UUID=13EC-4051  /media/Ext-HD vfat defaults,auto,exec,users,rw 0 0
> 
> but get
> 
> mount: special device UUID=13EC-4051 does not exist
> 
> also /dev/sdb1 is gone.
[…]
> PS what should be a relevant part from running dmesg is:
> 
> [  193.043620] USB Mass Storage support registered.
> [  194.046020] scsi 8:0:0:0: Direct-Access     Freecom  Hard Drive XS
>  1.00 PQ
> : 0 ANSI: 4
> [  194.046736] sd 8:0:0:0: Attached scsi generic sg2 type 0
> [  194.047446] sd 8:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00
> TB/1.
> 81 TiB)
> [  194.053731] sd 8:0:0:0: [sdb] Write Protect is off
> [  194.053734] sd 8:0:0:0: [sdb] Mode Sense: 38 00 00 00
> [  194.060095] sd 8:0:0:0: [sdb] No Caching mode page present
> [  194.060099] sd 8:0:0:0: [sdb] Assuming drive cache: write through
> [  194.073837] sd 8:0:0:0: [sdb] No Caching mode page present
> [  194.073840] sd 8:0:0:0: [sdb] Assuming drive cache: write through
> [  194.090570]  sdb: sdb1
> [  194.105295] sd 8:0:0:0: [sdb] No Caching mode page present
> [  194.105298] sd 8:0:0:0: [sdb] Assuming drive cache: write through
> [  194.105300] sd 8:0:0:0: [sdb] Attached SCSI disk
> [  195.430432] FAT-fs (sdb1): utf8 is not a recommended IO charset for FAT
> filesystems, filesystem will be case sensitive!
> [  291.152427] usb 4-1.1: USB disconnect, device number 7

Has usb 4-1.1 been the drive?

> [  291.152801] sd 8:0:0:0: [sdb] Unhandled error code
> [  291.152803] sd 8:0:0:0: [sdb]  Result: hostbyte=DID_NO_CONNECT
> driverbyte=DRIVER_OK
> [  291.152806] sd 8:0:0:0: [sdb] CDB: Read(10): 28 00 03 20 f0 7f 00 00 f0
> 00
> [  291.152811] end_request: I/O error, dev sdb, sector 52490367
> [  291.152830] sd 8:0:0:0: [sdb] Unhandled error code
> [  291.152831] sd 8:0:0:0: [sdb]  Result: hostbyte=DID_NO_CONNECT
> driverbyte=DRIVER_OK
> [  291.152833] sd 8:0:0:0: [sdb] CDB: Read(10): 28 00 03 20 f1 6f 00 00 10
> 00
> [  291.152837] end_request: I/O error, dev sdb, sector 52490607
> [  291.275859] usb 4-1.1: new full-speed USB device number 8 using ehci_hcd
> [  291.347612] usb 4-1.1: device descriptor read/64, error -32
> [  291.523504] usb 4-1.1: device descriptor read/64, error -32
> [  291.699237] usb 4-1.1: new full-speed USB device number 9 using ehci_hcd
> [  291.771127] usb 4-1.1: device descriptor read/64, error -32
> [  291.946866] usb 4-1.1: device descriptor read/64, error -32

Seems so. Then above scsi block layer messages make sense,

> [  292.122578] usb 4-1.1: new full-speed USB device number 10 using ehci_hcd
> [  292.529829] usb 4-1.1: device not accepting address 10, error -32
> [  292.601888] usb 4-1.1: new full-speed USB device number 11 using ehci_hcd
> [  293.009116] usb 4-1.1: device not accepting address 11, error -32
> [  293.009290] hub 4-1:1.0: unable to enumerate USB device on port 1

So lost connect and was unable to get the drive connected again. Did you
try to plug / unplug it here? Or if this just happening while copying?

> [  299.624267] FAT-fs (sdb1): Directory bread(block 138556096) failed
> [  299.624271] FAT-fs (sdb1): Directory bread(block 138556097) failed
> [  299.624274] FAT-fs (sdb1): Directory bread(block 138556098) failed
> [  299.624276] FAT-fs (sdb1): Directory bread(block 138556099) failed
> [  299.624278] FAT-fs (sdb1): Directory bread(block 138556100) failed

Obviously, when the disk has gone.

> [  299.624403] FAT-fs (sdb1): Directory bread(block 138556158) failed
> [  299.624405] FAT-fs (sdb1): Directory bread(block 138556159) failed
> [  347.480149] usb 4-1.1: new full-speed USB device number 12 using ehci_hcd
> [  347.552040] usb 4-1.1: device descriptor read/64, error -32
> [  347.727777] usb 4-1.1: device descriptor read/64, error -32
> [  347.903515] usb 4-1.1: new full-speed USB device number 13 using ehci_hcd
> [  347.975405] usb 4-1.1: device descriptor read/64, error -32
> [  348.151145] usb 4-1.1: device descriptor read/64, error -32

I´d check:

1) cabling.

2) power supply, especially when it is a 2.5 inch disk the USB port in use
may not supply enough power. Use second connector or powered USB
hub.

3) try different USB ports anyway. I have a Sony Playstation 2 controller
to USB adapter that just works in USB port of ThinkPad T520 Minidock
and not in USB port from ThinkPad itself - whyever.

4) some kind of power saving mode on Freecom disk?

5) check with different drive (to exclude that host has problems)

6) if ok, then place harddisk from Freecom case into different case and
try again.

Ciao,
-- 
Martin 'Helios' Steigerwald - http://www.Lichtvoll.de
GPG: 03B0 0D6C 0040 0710 4AFA  B82F 991B EAAC A599 84C7


--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201209291236.54514.mar...@lichtvoll.de

Reply via email to