can't mount usb key

[rodogh]

Hi,

I've upgraded to Mandrake 10.1 and now I can't mount any usb device. I have no message when i try to do it... ¿ any idea ?

Thanks,
rodogh

[AlexK]

See this tutorial and follow its steps thoroughly. http://www.linuxforums.org/tutorials...ial-26510.html

Make sure that the usb drive is plugged in when you boot and you should be fine.

[rodogh]

Thanks for your reply.

I've tried it, and the problem is that I have no /dev/sd? device on my machine. If I boot it up with a linux live cd, it works with no problem (the same with my 'old' Mandrake 9.2)

I'll continue searching the problem...

[AlexK]

The /dev/sdX# is only created when the drive is detected during boot. So, before turning on the PC, plug in the drive and then boot into linux. And only then the /dev/sda1 will be created.

[rodogh]

Hi AlexK,

I've done the way you said and the result is the same: I have no /dev/sd* device. It's very strange because before installing Mandrake 10.1 it always were the /dev/sda and /dev/sda1 devices created (with or without pluggin the usb key before booting)

So in essence, the problem is not be able to have any /dev/sd*. Any idea ?

[AlexK]

type lsmod and see if the scsi and usb modules are loaded. also what does your fstab file say for the line corresponding to the /dev/sda1 device?

[rodogh]

Hi AlexK,

thank you for spending your time with me:

# lsmod | grep usb -i
usbhid 41088 0
usb-storage 65504 2
scsi_mod 104044 3 sg,sd_mod,usb-storage
usbcore 103172 6 usbhid,usb-storage,ehci-hcd,uhci-hcd

# cat /etc/fstab | grep sda
/dev/sda1 /mnt/removable vfat noauto,users,rw,umask=0 0 0

# lspci | grep usb -i
00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 0
00:0b.0 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
00:0b.1 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 61)
00:0b.2 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 62)

# 'a small part of /etc/lilo.conf'
default="linux"
boot=/dev/hda9
map=/boot/map
keytable=/boot/es-latin1.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label="linux"
root=/dev/hda9
initrd=/boot/initrd.img
append="devfs=nomount acpi=ht splash=silent"
vga=788
read-only

One day I tried to change the append line in order to put it the way i had it
append="quiet devfs=mount hdb=ide-scsi hdc=ide-scsi"
but it crashed my computer.

Regards,
rodogh.

[genesus]

how about your fstab, have you tried automounting with the line

/dev/sda1 /mnt/usbflash vfat noauto,users,rw,umask=0 0 0

in reference to the tutorial you posted?

[AlexK]

Here is the line in my fstab corresponding to the usb storage device:
/dev/sda1 /mnt/removable auto umask=0,user,iocharset=iso8859-1,sync,kudzu,codepage=850,noauto,exec,users 0 0

Another thing you could try is to supermount the drive. Simply replace the 1st auto (the one in bold) with supermount. This will force the system to create the sda files as required.

[rodogh]

Hello again,

upssss. It doesn't work. I think is not the way it must be put in the fstab file. Here you have the log of /var/log/messages

Mar 30 23:02:45 localhost kernel: SCSI error : <0 0 0 0> return code = 0x70000
Mar 30 23:02:45 localhost kernel: end_request: I/O error, dev sda, sector 256000
Mar 30 23:02:45 localhost kernel: Buffer I/O error on device sda, logical block 256000
Mar 30 23:02:45 localhost kernel: p1
Mar 30 23:02:45 localhost kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Mar 30 23:02:45 localhost kernel: usb 1-1: USB disconnect, address 3
Mar 30 23:02:49 localhost kernel: usb 1-1: new full speed USB device using address 4
Mar 30 23:02:50 localhost kernel: usb 1-1: device not accepting address 4, error -71
Mar 30 23:02:50 localhost kernel: usb 1-1: new full speed USB device using address 5
Mar 30 23:02:50 localhost kernel: usb 1-1: device not accepting address 5, error -71
Mar 30 23:03:08 localhost perl: drakupdate_fstab called with --auto --del /dev/sda1

I've tried again with Knoppix and SysRescueCd and it works with no problem.