Upgraded to 2.6.9, now I can't mount usb flash drive
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Upgraded to 2.6.9, now I can't mount usb flash drive
Hi all,
I am new to the forum and have come over from the dark side in the recent months. I have been using Linux at my school labs for quite sometime, so I decided it was just time to go Linux full-time.
Anyhow, I custom-built my 2.6.9 kernel and got it running with some minor problems on my system (Redhat 8.0 distribution, 2.4.18 former kernel, P4 system). I seemed to have fixed them all with the exception of being able to mount my usb drive (creative muvo 64). Now, lsusb has it showing up, as well as my other usb devices (hub, joystick and printer) just fine. The problem is when I go to mount the drive. I type the standard mount /dev/sda1 /mnt/usb and I get "/dev/sda1 is not a valid block device." That command would work just fine with my former kernel. Also, when I check the system logs after plugging it in, it shows up just fine (no errors in the log). When building my kernel I built all of the relevant usb modules into the kernel (which seem to be working, given the other usb devices are running fine). Finally, I did run all sorts of different mounts using /dev/sda, /dev/sda2, etc. to no avail.
hi,
i've got a nomad muvo2 which worked fine (both mount and eject-recharge features fully functional) with the 2.6.8 kernel.
now, after upgrading to 2.6.9 (precisely 2.6.9-gentoo-dev-r13), it seems that something has been changed in the management of usb mass storage devices (!)
My muvo is no longer handled as a SCSI disc (sd* stopped working), but appears with the name "uba" in /dev/ub/a/disc (with the same M/m numbers of /dev/discs/disc2/disc).
The problem is that I'm no longer able to mount this device, it returns the error "mount: /dev/ub/a/disc: can't read superblock", the kernel outputs:
Code:
uba: device 8 capacity nsec 50 bsize 512
/dev/ub/a:end_request: I/O error, dev uba, sector 2
Buffer I/O error on device uba, logical block 1
end_request: I/O error, dev uba, sector 4
Buffer I/O error on device uba, logical block 2
end_request: I/O error, dev uba, sector 6
Buffer I/O error on device uba, logical block 3
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 2
Buffer I/O error on device uba, logical block 1
end_request: I/O error, dev uba, sector 4
Buffer I/O error on device uba, logical block 2
end_request: I/O error, dev uba, sector 6
Buffer I/O error on device uba, logical block 3
end_request: I/O error, dev uba, sector 0
Buffer I/O error on device uba, logical block 0
unable to read partition table
also, this device refuses the eject-recharge command ("eject: unable to eject, last error: Inappropriate ioctl for device").
Try something like this if you are working with Low Performance USB in your kernel.
mount -t vfat /dev/ub/a/part1 /mnt
Worked for me with a vfat pendrive, although I still have bother with CF readers.
Then I discovered that this may not be such a good thing. Seems better to switch off LowPerformanceUSB in DeviceDrivers->BLockDevices->LowPerformanceUSB
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.