Re: [usb-storage + sd] Driver fails to read e-reader av (autovision) 606

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

 



On Sat, Feb 16, 2013 at 10:07:55AM +0100, Ronald wrote:
> > 3) The device should appear as /dev/sdb according to the logs
> 
> It did, once. There were no partitions. Manual does not mention an
> initial format and I don't want to brick it. It did come up with
> another device /dev/sdc. The size really roughly corresponds to what
> the manual mentions. However, it contains four (bogus?) partitions,
> one of them mentioning Novell Netware or something like that. Please
> note, this is with a v3.4 kernel. Looks like behaviour varies across
> kernel versions. Don't think this counts as a regression though...
> 
> Disk /dev/sdc: 3426 MB, 3426746368 bytes
> 106 heads, 62 sectors/track, 1018 cylinders, total 6692864 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x6f20736b
> 
> This doesn't look like a partition table
> Probably you selected the wrong device.
> 
>    Device Boot      Start         End      Blocks   Id  System
> /dev/sdc1   ?   778135908  1919645538   570754815+  72  Unknown
> /dev/sdc2   ?   168689522  2104717761   968014120   65  Novell Netware 386
> /dev/sdc3   ?  1869881465  3805909656   968014096   79  Unknown
> /dev/sdc4   ?           0  3637226495  1818613248    d  Unknown
> 
> Mounting them does not work, the /dev/sdc* nodes are never created:
> 
> mount: special device /dev/sdc1 does not exist
> mount: special device /dev/sdc2 does not exist
> mount: special device /dev/sdc3 does not exist
> mount: special device /dev/sdc4 does not exist

Did you also try to mount the /dev/sdc device directly?  It might be
an unpartitioned device with a FAT filesystem (Android phones which
support USB storage mode look like this from the USB host side).  The
first sector of such filesystems in most cases contains the bootloader
code at the place where the MS-DOS partition table would be located in
an MBR, therefore fdisk shows bogus partitions when used with such
devices.  However, the Linux kernel is usually smart enough to notice
that the data does not look like a proper partition table and avoid
registering the partitions.

> Furthermore:
> 
> mount: /dev/sg0 is not a block device
> mount: /dev/sg1 is not a block device
> mount: /dev/sg2 is not a block device
> mount: /dev/sg3 is not a block device

Mounting /dev/sg* will never work - these are character devices used
by programs which send SCSI commands directly.

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux