[Solved] USB stick: can't read superblock

jskier · 2004-11-24 19:11:51

I have vfat in the kernel and have reformatted my usb stick in windows (formatiting in linux won't work). All modules needed for a usb stick are built in the kernel. Any ideas on how to fix this? I am using udev and 2.6.9 custom kernel. Below is some output:
Thanks

[root@wookie jjohnson]# mount /dev/stick
mount: /dev/stick: can't read superblock

dmesg when plugged in and after mount command is run:

ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001803 POWER sig=j  CSC CONNECT
hub 1-0:1.0: port 1, status 0501, change 0001, 480 Mb/s
ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001803 POWER sig=j  CSC CONNECT
hub 1-0:1.0: debounce: port 1: total 125ms stable 100ms status 0x501
ehci_hcd 0000:00:1d.7: CTRL: TypeReq=0x2301 val=0x2 idx=0x0 len=0 ==> -32
hub 1-0:1.0: port 1 not reset yet, waiting 50ms
ehci_hcd 0000:00:1d.7: port 1 high speed
ehci_hcd 0000:00:1d.7: GetStatus port 1 status 001005 POWER sig=se0  PE CONNECT
usb 1-1: new high speed USB device using address 3
usb 1-1: new device strings: Mfr=2, Product=3, SerialNumber=4
usb 1-1: default language 0x0409
usb 1-1: Product: Cruzer Mini
usb 1-1: Manufacturer: SanDisk Corporation
usb 1-1: SerialNumber: 000036280
usb 1-1: hotplug
usb 1-1: adding 1-1:1.0 (config #1, interface 0)
usb 1-1:1.0: hotplug
ub 1-1:1.0: usb_probe_interface
ub 1-1:1.0: usb_probe_interface - got id
uba: device 3 capacity nsec 512000 bsize 512
uba: was not changed
 uba: uba1
ub: signature 0x53550000
uba: tag orig 0x5 reply 0x55342
uba: made changed
uba: device 3 capacity nsec 512000 bsize 512
uba: device 3 capacity nsec 512000 bsize 512
 uba:end_request: I/O error, dev uba, sector 0
Buffer I/O error on device uba, logical block 0
end_request: I/O error, dev uba, sector 0
Buffer I/O error on device uba, logical block 0
 unable to read partition table
end_request: I/O error, dev uba, sector 0
FAT: unable to read boot sector

FSTAB:

/dev/stick /mnt/usb vfat noauto,user 0 0

mike182 · 2004-11-24 19:26:26

Maybe, yah. You need to change your fstab. You've got the right approach, but its a little off. Put the following in your fstab.

/mnt/usb    /dev/stick vfat noauto,user 0 0

Then you should mount with the following

mount /mnt/usb

Look at the man pages for mount and you'll see that you just had the syntax switched around a bit.

jskier · 2004-11-24 19:49:30

Actaully your way is backwards... All my other devices are set up the way I had it.... Anyway I just tried it for sake of showing it doesn't work that way (modified fstab to your way too):

[root@wookie jjohnson]# mount /mnt/usb/
mount: /mnt/usb is not a block device

dmesg didn't put anything new in it either.

JSkier

jskier · 2004-11-26 06:54:46

I was able to test a Lexmar stick and it worked fine... My guess is something changed in the latest kernel and my Sandisk is giving it a hard time. After I try to mount it the device LED shuts down also, and it disappears from the /dev/ listing. No idea why this is,and why it works just fine in Windoze. Oh well, I'll go get a Lexmar stick

JSkier

vacant · 2004-11-26 09:06:30

Strange. I've got a 2.6.9 kernel (stick also OK with 2.6.9-nitro), a "no name" usb stick and SDDR-09 compiled into the kernel. My dmesg gives:

usb 1-2: new full speed USB device using address 2
scsi0 : SCSI emulation for USB Mass Storage devices
  Vendor: STF       Model: Flash Drive       Rev: 1.89
  Type:   Direct-Access                      ANSI SCSI revision: 02
USB Mass Storage device found at 2
sda: Unit Not Ready, sense:
Current : sense = 70  6
ASC=28 ASCQ= 0
Raw sense data:0x70 0x00 0x06 0x00 0x00 0x00 0x00 0x0a 0x00 0x00 0x00 0x00 0x28 0x00 0x00 0x00 0x00 0x00
SCSI device sda: 512000 512-byte hdwr sectors (262 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
 sda: sda1
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0

then a "mount /dev/sda1 /mnt/tmp" give me access to by stick (ext2, used for backups). I don't bother with an entry in fstab as I only use it once each week.

cat /proc/bus/usb/devices gives

T:  Bus=01 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  2 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs=  1
P:  Vendor=0ea0 ProdID=6828 Rev= 1.10
S:  Manufacturer=USB
S:  Product=Flash Disk
S:  SerialNumber=4CAA929F3F71A908
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=255ms

You say you can't format it in Linux. To me "format" means creating a blank file system. Can you partition it in Linux (fdisk)?

jskier · 2004-11-26 14:22:32

By format I mean mkfs.vfat /dev/uba -or- mkfs.vfat /dev/uba1.
Fdisk returns (dev/uba) superblock error or not a (dev/uba1) block device response and gives dmesg a bunch of these and then the LED on the stick goes out:

end_request: I/O error, dev uba, sector 120
Buffer I/O error on device uba, logical block 15
end_request: I/O error, dev uba, sector 0
Buffer I/O error on device uba, logical block 0

fdisk and mkfs.* for my CF media just fine.

I don't know what it is about the Sandisk usb stick
I searched google and found a minority of people with similar problems but no solutions.

I also tried with and without Sanidisk support built in with the kernel. And the problem is reproducable on my laptop as well.

JSkier

jskier · 2005-03-11 00:39:49

Having low level USB block device compiled in cripples some usb stick support... Go figure, problem solved.

Arch Linux

#1 2004-11-24 19:11:51

[Solved] USB stick: can't read superblock

#2 2004-11-24 19:26:26

Re: [Solved] USB stick: can't read superblock

#3 2004-11-24 19:49:30

Re: [Solved] USB stick: can't read superblock

#4 2004-11-26 06:54:46

Re: [Solved] USB stick: can't read superblock

#5 2004-11-26 09:06:30

Re: [Solved] USB stick: can't read superblock

#6 2004-11-26 14:22:32

Re: [Solved] USB stick: can't read superblock

#7 2005-03-11 00:39:49

Re: [Solved] USB stick: can't read superblock

Board footer