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'm getting that same 'not a valid block device' message.
Bought a Sandisk Cruzer Mini 128 today.
Stuck it in my W2Kmachine - poof - it was available and I threw a file on it.
Decided to try it on my Red Hat 8 machine, but first... check LQ for threads.
Found this thread. Stepped through the steps.
Tried /dev/sda1, sda, sdb1, sdc1, etc etc...
This was from that tail command:
Jan 12 21:12:26 localhost su(pam_unix)[2268]: session opened for user root by (uid=500)
Jan 12 21:13:13 localhost kernel: Initializing USB Mass Storage driver...
Jan 12 21:13:13 localhost kernel: usb.c: registered new driver usb-storage
Jan 12 21:13:13 localhost kernel: USB Mass Storage support registered.
This happened when I did the 'insmod usb-storage', and got the same thing earlier when I used 'modprobe usb-storage'.
When I stick the drive in the usb slot, nothing happens.
[root@localhost /]# fdisk -l
Disk /dev/hda: 255 heads, 63 sectors, 4866 cylinders
Units = cylinders of 16065 * 512 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 4092 4866 6225187+ 83 Linux
/dev/hda3 14 3837 30716280 83 Linux
/dev/hda4 3838 4091 2040255 f Win95 Ext'd (LBA)
/dev/hda5 3838 4091 2040223+ 82 Linux swap
Partition table entries are not in disk order
[root@localhost /]# mount /dev/sda1 /mnt/flash
mount: /dev/sda1 is not a valid block device
And, like I said, I also went through the whole process for sdb, sdc, sdd...
The little light on the end of the little 'drive' never comes on in the linux machine.
How can I determine which device is associated with the thing??
Well, I'm having a similar problem. I have the Sandisk Cruzer Mini 256 and I'm having problems connecting it to my Redhat Linux 9 system. The usb-storage module loads fine, but the system locks solid each time I connect the cruzer. When I first tried to connect the stick (pre reading this howto), it did the same thing. I checked /var/log/messages and nothing is in there that might give a clue. The last entry before my last reboot was that the USB Storage module was successfully loaded. Any thoughts?
Interesting enough, I have 2 memory sticks. One is a PNY Attache 128 Meg, the other is a SanDisk Cruzer mini, 256 Meg.
The PNY works just fine, with this tutorial. However, I can't seem to get the Cruzer working. I wonder if it has to do with it being a Cruzer, or the capacity.
Thank you for contacting SanDisk Technical Support.
We apologize for any inconvenience this may have caused.
The Cruzer Mini is not supported on Windows Red Hat 8 Systems. However, it is supported on Windows98SE and higher.
If you have any further questions, please feel free to reply to this e-mail or contact our technical support department toll free at 866-SANDISK (866-726-3475). Our technical support team is open Monday through Friday, 7 am to 4 pm PST. Have a Great Day and thank you for choosing SanDisk!
Nice info on USB drives as i just purchased one a few days ago. All the info i needed is right here.
'nbd' did raise a question that didnt seem to get answered, and i was wondering about the same thing.
refering to the fact that is is possible for auto mounting when you plug in the device and un-mounting when you unplug the device.
"No USB attached -> no /dev/sda1 (or similar) icon on the desktop
Attach USB -> /dev/sda1 icon appears on the desktop
Remove USB -> /dev/sda1 icon disappears from the desktop" --nbd
I am sure you can put a small script somewhere that does this for you since my system already loads 'usb-storage' module automaically once the device is plugged in.
Right now all i have to do is 'mount -t vfat /dev/sda1 /mnt/usbkey'
As stated above, i was wondering if the process could be furthur automated by having the key auto mount / unmount as you plugin the usb-key.
I plug in the flash drive and messages returns the following:
Feb 7 21:59:52 JimNote kernel: hub.c: new USB device 00:07.2-1, assigned address 8
Feb 7 21:59:55 JimNote /etc/hotplug/usb.agent: Setup usb-storage for USB product 781/7101/102
Feb 7 21:59:58 JimNote devlabel: devlabel service started/restarted
Here is the tail output and the lsusb -v output. The error I get when trying to mount the thumbdrive is:
root@slacker:/home/chuck# mount /mnt/thumb
mount: /dev/sda1 is not a valid block device
Feb 8 09:00:57 slacker kernel: usb 1-1: USB disconnect, address 2
Feb 8 09:01:05 slacker kernel: hub 1-0:1.0: new USB device on port 1, assigned address 3
Feb 8 09:01:05 slacker kernel: usb 1-1: Product: JUMPDRIVE
Feb 8 09:01:05 slacker kernel: usb 1-1: Manufacturer: LEXAR MEDIA
Feb 8 09:01:05 slacker kernel: usb 1-1: SerialNumber: L137142325060
Feb 8 09:01:06 slacker modprobe: FATAL: Module usb_storage already in kernel.
Feb 8 09:01:06 slacker kernel: scsi1 : SCSI emulation for USB Mass Storage devi ces
Feb 8 09:01:06 slacker scsi.agent[1501]: bogus sysfs DEVPATH=/devices/pci0000:0 0/0000:00:1f.2/usb1/1-1/1-1:1.0/host1/1:0:0:0
Feb 8 09:01:06 slacker kernel: Vendor: LEXAR Model: JUMPDRIVE Rev : 1.11
Feb 8 09:01:06 slacker kernel: Type: Direct-Access ANS I SCSI revision: 02
Unknown line at line 1809
Duplicate HUT Usage Spec at line 2650
Hi there,
I followed the instructions and here's what happened at the point where i plug in the usb key(i am using fedora core 1)...
root$ tail -s 3 -f /var/log/messages
Feb 8 22:48:23 localhost kernel: emu10k1: Audigy rev 4 model 0x1007 found, IO at 0xdf00-0xdf3f, IRQ 5
Feb 8 22:48:23 localhost kernel: ac97_codec: AC97 Audio codec, id: 0x8384:0x7609 (SigmaTel STAC9721/23)
Feb 8 22:48:23 localhost modprobe: modprobe: Can't locate module sound-service-0-0
Feb 8 22:49:44 localhost kernel: Initializing USB Mass Storage driver...
Feb 8 22:49:44 localhost kernel: usb.c: registered new driver usb-storage
Feb 8 22:49:44 localhost kernel: USB Mass Storage support registered.
Feb 8 22:51:37 localhost kernel: hub.c: new USB device 00:1d.7-6, assigned address 2
Feb 8 22:51:37 localhost kernel: usb.c: USB device not accepting new address=2 (error=-71)
Feb 8 22:51:37 localhost kernel: hub.c: new USB device 00:1d.7-6, assigned address 3
Feb 8 22:51:37 localhost kernel: usb.c: USB device not accepting new address=3 (error=-71)
Hey guys.
I just recently updated to RH9, previously running RH8. I've got two USB Flash Drives, a PNY Attache 64MB and a ghetto cheap one I picked up for free (16MB). Before the upgrade, I had read the how-to in this thread and had managed to get both drives to work beautifully.
But post-update, I can only get the ghetto cheap drive to work (and it works fine), but I'm a bit constricted by the relative small size. Is there any reason that one should work and the other wouldn't?
Feb 9 19:34:13 SplicedBox su(pam_unix)[23245]: session opened for user root by csplice(uid=500)
Feb 9 19:36:16 SplicedBox kernel: hub.c: new USB device 00:07.2-2, assigned address 16
Feb 9 19:36:19 SplicedBox /etc/hotplug/usb.agent: Setup usb-storage for USB product 9a6/8001/100
Feb 9 19:36:21 SplicedBox kernel: SCSI device sda: 31520 512-byte hdwr sectors (16 MB)
Feb 9 19:36:21 SplicedBox kernel: sda: Write Protect is off
Feb 9 19:36:21 SplicedBox kernel: sda: sda1
Feb 9 19:36:21 SplicedBox kernel: Device not ready. Make sure there is a disc in the drive.
Feb 9 19:36:21 SplicedBox kernel: sdb : READ CAPACITY failed.
Feb 9 19:36:21 SplicedBox kernel: sdb : status = 1, message = 00, host = 0, driver = 08
Feb 9 19:36:21 SplicedBox kernel: Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready
Feb 9 19:36:21 SplicedBox kernel: sdb : block size assumed to be 512 bytes, disk size 1GB.
Feb 9 19:36:21 SplicedBox kernel: sdb: I/O error: dev 08:10, sector 0
Feb 9 19:36:21 SplicedBox kernel: I/O error: dev 08:10, sector 0
Feb 9 19:36:21 SplicedBox kernel: unable to read partition table
Feb 9 19:36:22 SplicedBox devlabel: devlabel service started/restarted
Despite the few error-ish messages, the drive mounts/unmounts beautifully just by double-clicking the icon on my Desktop. Another thing... I've got the drive set up to be /dev/sda1... so what's with this stuff about sdb in the tail output?
Moving on, here's the output for the non-working Attache:
Code:
Feb 9 19:39:55 SplicedBox kernel: hub.c: new USB device 00:07.2-2, assigned address 17
Feb 9 19:39:58 SplicedBox /etc/hotplug/usb.agent: Setup usb-storage for USB product ea0/6828/110
Feb 9 19:39:59 SplicedBox kernel: Device not ready. Make sure there is a disc in the drive.
Feb 9 19:39:59 SplicedBox kernel: sda : READ CAPACITY failed.
Feb 9 19:39:59 SplicedBox kernel: sda : status = 1, message = 00, host = 0, driver = 08
Feb 9 19:39:59 SplicedBox kernel: Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready
Feb 9 19:39:59 SplicedBox kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
Feb 9 19:39:59 SplicedBox kernel: sda: I/O error: dev 08:00, sector 0
Feb 9 19:39:59 SplicedBox kernel: I/O error: dev 08:00, sector 0
Feb 9 19:39:59 SplicedBox kernel: unable to read partition table
Feb 9 19:40:00 SplicedBox kernel: SCSI device sdb: 128000 512-byte hdwr sectors (66 MB)
Feb 9 19:40:00 SplicedBox kernel: sdb: Write Protect is off
Feb 9 19:40:00 SplicedBox kernel: sdb: sdb1
Feb 9 19:40:03 SplicedBox devlabel: devlabel service started/restarted
Feb 9 19:40:17 SplicedBox kernel: Device not ready. Make sure there is a disc in the drive.
Feb 9 19:40:17 SplicedBox kernel: sda : READ CAPACITY failed.
Feb 9 19:40:17 SplicedBox kernel: sda : status = 1, message = 00, host = 0, driver = 08
Feb 9 19:40:17 SplicedBox kernel: Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready
Feb 9 19:40:17 SplicedBox kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
Feb 9 19:40:17 SplicedBox kernel: sda: I/O error: dev 08:00, sector 0
Feb 9 19:40:17 SplicedBox kernel: I/O error: dev 08:00, sector 0
Feb 9 19:40:17 SplicedBox kernel: unable to read partition table
Feb 9 19:40:17 SplicedBox kernel: Device not ready. Make sure there is a disc in the drive.
Feb 9 19:40:17 SplicedBox kernel: sda : READ CAPACITY failed.
Feb 9 19:40:17 SplicedBox kernel: sda : status = 1, message = 00, host = 0, driver = 08
Feb 9 19:40:17 SplicedBox kernel: Info fld=0xa00 (nonstd), Current sd00:00: sense key Not Ready
Feb 9 19:40:17 SplicedBox kernel: sda : block size assumed to be 512 bytes, disk size 1GB.
Feb 9 19:40:17 SplicedBox kernel: sda: I/O error: dev 08:00, sector 0
Feb 9 19:40:17 SplicedBox kernel: I/O error: dev 08:00, sector 0
Feb 9 19:40:17 SplicedBox kernel: unable to read partition table
Also...
Code:
[root@SplicedBox root]# mount /mnt/usbstick
mount: No medium found
Now I'm sure that I've probably screwed something up along the way (I don't feel bad, that's how ya learn!), so please point it out to me.
Any help is greatly appreciated.
*edit* After viewing a post here, I typed the following at the command line:
Code:
[root@SplicedBox root]# fdisk -l /dev/sd[a-z]
Disk /dev/sdb: 65 MB, 65536000 bytes
16 heads, 32 sectors/track, 250 cylinders
Units = cylinders of 512 * 512 = 262144 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 249 63728 6 FAT16
[root@SplicedBox root]# mount /dev/sdb1
[root@SplicedBox root]#
It mounted fine.. I edited fstab, and now that device (at least) works okay... by why would one work on /dev/sda1 and one on /dev/sdb1? Personally, I think that's wierd...
Guidance, please?
Last edited by CodeSplice; 02-09-2004 at 07:59 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.