SEO

I recently got a USB ProDrive memory key. Everything was fine
initially and I was able to access it fine from Linux (Slack9.1) using
mount /dev/sda1 /mnt/usb. Unfortunately it became necessary to format
it (which I did with XP) and I can now can't access it from Linux at
all.

Have I chosen the wrong disk format? - I've tried FAT and FAT32 from
Windows, with similar results.

How do I know which device to mount?

Can anybody help me??

Below are the sad details:

# mount /dev/sda1 /mnt/usb
/dev/sda1: Input/output error
mount: you must specify the filesystem type

# mount /dev/sda1 /mnt/usb -t msdos (or vfat)
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
or too many mounted file systems
(same result with /dev/sda2)

# mkdosfs -F 32 /dev/sda2
mkdosfs 2.8 (28 Feb 2001)
mkdosfs: unable to allocate space for FAT image in memory

# mkfs.vfat /dev/sda2
mkfs.vfat 2.9 (15 May 2003)
mkfs.vfat: Attempting to create a too large file system

# lsmod (relevant parts):
usb-storage 69952 0
uhci 26832 0 (unused)
usbcore 65664 1 [usb-storage uhci]

# cat /proc/bus/usb/drivers
usbdevfs
hub
usb-storage

# cat /proc/scsi/usb-storage-0/1
Host scsi1: usb-storage
Vendor:
Product: 3in1 MobileDrive
Serial Number: 14371D00026A
Protocol: Transparent SCSI
Transport: Bulk
GUID: 0d7d0280000014371d00026a
Attached: Yes

# cat /proc/bus/usb/devices
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI-alt Root Hub
S: SerialNumber=d400
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 11/900 us ( 1%), #Int= 1, #Iso= 0
D: Ver= 1.00 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 0.00
S: Product=USB UHCI-alt Root Hub
S: SerialNumber=d000
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=255ms
T: Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 4
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0451 ProdID=1446 Rev= 1.10
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 1 Ivl=255ms
T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0d7d ProdID=0280 Rev= 1.00
S: Manufacturer=
S: Product=3in1 MobileDrive
S: SerialNumber=14371D00026A
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=08(stor.) Sub=06 Prot=50
Driver=usb-storage
E: Ad=81(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=02(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=83(I) Atr=03(Int.) MxPS= 2 Ivl=1ms

Robert wrote:

> I recently got a USB ProDrive memory key. Everything was fine
> initially and I was able to access it fine from Linux (Slack9.1) using
> mount /dev/sda1 /mnt/usb. Unfortunately it became necessary to format
> it (which I did with XP) and I can now can't access it from Linux at
> all.
>
> Have I chosen the wrong disk format? - I've tried FAT and FAT32 from
> Windows, with similar results.

Is the vfat driver loaded or compiled in?
And you've got all the relevant modules?
Show us the lsmod output, all of it, not just the parts *you think* are
relevant

> How do I know which device to mount?

The sd_mod module tells you about the partitions of the SCSI drive.
Print the relevant cut of the dmesg output here.

--
Jabber: molchun@jabber.org
PGP ID: 0x304563A8

> How do I know which device to mount?

Plug the device in, then wait some seconds, and
look at the output (last few lines) of /var/log/messages.

It tells you that it noticed a new device on the usb slot,
and normally also which device it is attached to.

Robert <send_to_me@areujoking.com> wrote:
> I recently got a USB ProDrive memory key. Everything was fine
> initially and I was able to access it fine from Linux (Slack9.1) using
> mount /dev/sda1 /mnt/usb. Unfortunately it became necessary to format

Are you sure?
The Genie Pro 2.0 I've got was formatted like a floppy, that is:
NO partitions (you have to mount it as /dev/sd?, no number):
/dev/sdb /Mst vfat user,noauto 0 0

So it is a "fat" type (probably fat16) filesystem, with the BOOT
blok at the beginning, no MBR, cq partition table.

In fact, this is the first blok (dd piped into od):
0000000 eb 3e 90 50 72 6f 6c 69 66 69 63 00 02 20 01 00
k > dle P r o l i f i c nul stx sp soh nul
0000020 02 50 02 00 00 f8 7d 00 3f 00 ff 00 00 00 00 00
stx P stx nul nul x } nul ? nul del nul nul nul nul nul
0000040 00 a0 0f 00 80 00 29 00 00 00 00 00 00 00 00 00
nul sp si nul nul nul ) nul nul nul nul nul nul nul nul nul
0000060 00 00 00 00 00 00 46 41 54 31 36 00 00 00 f1 7d
nul nul nul nul nul nul F A T 1 6 nul nul nul q }
0000100 fa 33 c9 8e d1 bc fc 7b 16 07 bd 78 00 c5 76 00
z 3 I so Q < | { syn bel = x nul E v nul
0000120 1e 56 16 55 bf 22 05 89 7e 00 89 4e 02 b1 0b fc
rs V syn U ? " enq ht ~ nul ht N stx 1 vt |
0000140 f3 a4 06 1f bd 00 7c c6 45 fe 0f 8b 46 18 88 45
s $ ack us = nul | F E ~ si vt F can bs E
0000160 f9 fb 38 66 24 7c 04 cd 13 72 3c 8a 46 10 98 f7
y { 8 f $ | eot M dc3 r < nl F dle can w
0000200 66 16 03 46 1c 13 56 1e 03 46 0e 13 d1 50 52 89
f syn etx F fs dc3 V rs etx F so dc3 Q P R ht
0000220 46 fc 89 56 fe b8 20 00 8b 76 11 f7 e6 8b 5e 0b
F | ht V ~ 8 sp nul vt v dc1 w f vt ^ vt
0000240 03 c3 48 f7 f3 01 46 fc 11 4e fe 5a 58 bb 00 07
etx C H w s soh F | dc1 N ~ Z X ; nul bel
0000260 8b fb b1 01 e8 94 00 72 47 38 2d 74 19 b1 0b 56
vt { 1 soh h dc4 nul r G 8 - t em 1 vt V
0000300 8b 76 3e f3 a6 5e 74 4a 4e 74 0b 03 f9 83 c7 15
vt v > s & ^ t J N t vt etx y etx G nak
0000320 3b fb 72 e5 eb d7 2b c9 b8 d8 7d 87 46 3e 3c d8
; { r e k W + I 8 X } bel F > < X
0000340 75 99 be 80 7d ac 98 03 f0 ac 84 c0 74 17 3c ff
u em > nul } , can etx p , eot @ t etb < del
0000360 74 09 b4 0e bb 07 00 cd 10 eb ee be 83 7d eb e5
t ht 4 so ; bel nul M dle k n > etx } k e
0000400 be 81 7d eb e0 33 c0 cd 16 5e 1f 8f 04 8f 44 02
> soh } k ` 3 @ M syn ^ us si eot si D stx
0000420 cd 19 be 82 7d 8b 7d 0f 83 ff 02 72 c8 8b c7 48
M em > stx } vt } si etx del stx r H vt G H
0000440 48 8a 4e 0d f7 e1 03 46 fc 13 56 fe bb 00 07 53
H nl N cr w a etx F | dc3 V ~ ; nul bel S
0000460 b1 04 e8 16 00 5b 72 c8 81 3f 4d 5a 75 a7 81 bf
1 eot h syn nul [ r H soh ? M Z u ' soh ?
0000500 00 02 42 4a 75 9f ea 00 02 70 00 50 52 51 91 92
nul stx B J u us j nul stx p nul P R Q dc1 dc2
0000520 33 d2 f7 76 18 91 f7 76 18 42 87 ca f7 76 1a 8a
3 R w v can dc1 w v can B bel J w v sub nl
0000540 f2 8a 56 24 8a e8 d0 cc d0 cc 0a cc b8 01 02 cd
r nl V $ nl h P L P L nl L 8 soh stx M
0000560 13 59 5a 58 72 09 40 75 01 42 03 5e 0b e2 cc c3
dc3 Y Z X r ht @ u soh B etx ^ vt b L C
0000600 03 18 01 27 0d 0a 49 6e 76 61 6c 69 64 20 73 79
etx can soh ' cr nl I n v a l i d sp s y
0000620 73 74 65 6d 20 64 69 73 6b ff 0d 0a 44 69 73 6b
s t e m sp d i s k del cr nl D i s k
0000640 20 49 2f 4f 20 65 72 72 6f 72 ff 0d 0a 52 65 70
sp I / O sp e r r o r del cr nl R e p
0000660 6c 61 63 65 20 74 68 65 20 64 69 73 6b 2c 20 61
l a c e sp t h e sp d i s k , sp a
0000700 6e 64 20 74 68 65 6e 20 70 72 65 73 73 20 61 6e
n d sp t h e n sp p r e s s sp a n
0000720 79 20 6b 65 79 0d 0a 00 49 4f 20 20 20 20 20 20
y sp k e y cr nl nul I O sp sp sp sp sp sp
0000740 53 59 53 4d 53 44 4f 53 20 20 20 53 59 53 80 01
S Y S M S D O S sp sp sp S Y S nul soh
0000760 00 57 49 4e 42 4f 4f 54 20 53 59 53 00 00 55 aa
nul W I N B O O T sp S Y S nul nul U *

You'll even see the DOS filenames there (IO.SYS, MSDOS.SYS).
And it IS a fat16 (see line 000060) file system.
--
************************************************** ******************
** Eef Hartman, Delft University of Technology, dept. EWI/TWA **
** e-mail: E.J.M.Hartman@math.tudelft.nl, fax: +31-15-278 7295 **
** snail-mail: P.O. Box 5031, 2600 GA Delft, The Netherlands **
************************************************** ******************

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Oct 24, 2003 at 06:48:39AM PDT, Robert wrote
in article <fac9158b.0310240548.6aec900b@posting.google.com >:

> How do I know which device to mount?

> # mount /dev/sda1 /mnt/usb
> /dev/sda1: Input/output error

try this:
# fdisk -l /dev/sda

then see what you get.


Jurgen.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/mZQG1ucXIiwNwbURAp73AJ0TBLIoAXSPntz1YJRuw0O1AN8q4Q CdE45n
4WSHgbTdX1eKVh3PwpIMlAA=
=EwVU
-----END PGP SIGNATURE-----

> The sd_mod module tells you about the partitions of the SCSI drive.
> Print the relevant cut of the dmesg output here.
>
Thanks for the answers. After a bit of trial and error I managed to access
the drive intermittently using mount /dev/sda /mnt/usb.

Now when I do # tail
/var/log/messages, I sometimes get:
Oct 25 07:49:09 athlon kernel: hub.c: new USB device 00:11.2-2.1, assigned
address 8
Oct 25 07:49:09 athlon kernel: scsi2 : SCSI emulation for USB Mass Storage
devices
Oct 25 07:49:09 athlon kernel:**sda:*sda1*sda2*sda3*sda4
Oct 25 07:49:11 athlon usb.agent[964]: missing kernel or user mode driver
usbcore
Oct 25 07:49:11 athlon usb.agent[964]: missing kernel or user mode driver
usbcore
Oct 25 07:49:11 athlon usb.agent[977]: missing kernel or user mode driver
usb-storage
Oct 25 07:49:12 athlon usb.agent[993]: missing kernel or user mode driver
usb-storage

This seems to happen on one of my other pcs

If I do # lsmod, usb-storage and usbcore are still there.

Is there any explanation for this?

On Sat, 25 Oct 2003 11:23:23 +0000, Robert S wrote:

>
> Now when I do # tail
> /var/log/messages, I sometimes get:
> Oct 25 07:49:09 athlon kernel: hub.c: new USB device 00:11.2-2.1, assigned
> address 8
> Oct 25 07:49:09 athlon kernel: scsi2 : SCSI emulation for USB Mass Storage
> devices
> Oct 25 07:49:09 athlon kernel:**sda:*sda1*sda2*sda3*sda4
<snip>
>
> If I do # lsmod, usb-storage and usbcore are still there.
>
> Is there any explanation for this?

I believe you also need the scsi_mod and sr_mod/sd_mod loaded. At least I
need them to access the memory card on my digital camera. It mounts it as
a scsi device, hence the /dev/sd?...