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.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
i've got the same problem but with /dev/hda. it was working fine before except for this one time when it didn't. i had compiled a kernel. i just restarted and it worked. so i doubt it's a kernel issue. it's happening again now again, with another kernel. i doubt it's even a driver/module issue, but just to let ull know, the fs modules were included (vfat). why does this happen anyway? (works most of the time)
Distribution: K/Ubuntu 18.04-14.04, Scientific Linux 6.3-6.4, Android-x86, Pretty much all distros at one point...
Posts: 1,802
Rep:
I have a similar problem with a SanDisk Cruzer Mini 128 running on SuSE 8.2 with a 2.4.20 kernel.
On my desktop machine, I can get the thing to mount, but on the laptop machine I have, it hangs trying to mount. When I do a dmesg, I see that the thing is being assigned to /dev/sda1,... but it won't mount no matter what I do.
Frustrating. I can only assume it's a chipset related bug thing with USB services...
6) turn on usb_storage device
7) ran cdrecord -scanbus ( only way I know to see scsi devices address)
scsibus1:
1,0,0 100) 'IC35L090' 'AVV207-0 ' 'V23O' Disk
At this point I still could not mount /dev/sda1 /mnt/usbhd ? HOWEVER !
I tried this next :
8) fdisk /dev/sda1
There was a message about block 0 that would be corrected with a "write" before
leaving fdisk. ( sorry for not coping the message) Well this always freaks me out so I just quit fdisk instead. When I quit fdisk the light flashed on my usb_storage disk so I tried mount /dev/sda1 /mnt/usbhd again. AND IT WORKED !!
I can only guess something weird was written to block zero at some point and prevented me from mounting the disk. I won't know if it was a complete success until I try to re-boot with the mount /dev/sda1 parameters in fstab
Any how for now my system is running 100% on kernel 2.6.3 Just need to figure out how to load the modules on boot instead of running modprobe manually. I think there is a module.conf file that takes cae of this.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.