USB Flash drive unable to detect on Mandriva 2010.2
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
USB Flash drive unable to detect on Mandriva 2010.2
USB Flash Drive unable to mount on Mandriva 2010.2. Some USB Device are detected example of these are printers, usb bluetooth, etc. Only Mass Storage are not detected. Thanks in advance.
Last edited by tailinlinux; 01-12-2013 at 01:20 AM.
as root tail /var/log/messages as you plug in the usb device. you should see it as /dev/sdX_something_or_other, or once you have it plugged into the computer run fdisk -l. both work for identifying the device. the tail will give you more details about what the system sees and if it is able to access the device or not. you will get errors if it is unable to access the device.
once you get that info report back with fdisk -l, or the /dev/sdX# from /var/log/messages and ill help you mount and access the device.
as root tail /var/log/messages as you plug in the usb device. you should see it as /dev/sdX_something_or_other, or once you have it plugged into the computer run fdisk -l. both work for identifying the device. the tail will give you more details about what the system sees and if it is able to access the device or not. you will get errors if it is unable to access the device.
once you get that info report back with fdisk -l, or the /dev/sdX# from /var/log/messages and ill help you mount and access the device.
result of tail /var/log/messages
Quote:
[root@linux58 aries_baluyot]# tail /var/log/messages
Jan 11 10:21:10 linux58 smbd[17232]: [2013/01/11 10:21:10.553766, 0] lib/util_sock.c:675(write_data)
Jan 11 10:21:10 linux58 smbd[17232]: [2013/01/11 10:21:10.553986, 0] lib/util_sock.c:1432(get_peer_addr_internal)
Jan 11 10:21:10 linux58 smbd[17232]: getpeername failed. Error was Transport endpoint is not connected
Jan 11 10:21:10 linux58 smbd[17232]: write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
Jan 11 10:21:10 linux58 smbd[17232]: [2013/01/11 10:21:10.554129, 0] smbd/process.c:79(srv_send_smb)
Jan 11 10:21:10 linux58 smbd[17232]: Error writing 4 bytes to client. -1. (Transport endpoint is not connected)
Jan 11 10:28:26 linux58 kernel: usb 1-8: new high speed USB device using ehci_hcd and address 2
Jan 11 10:28:27 linux58 kernel: usb 1-8: New USB device found, idVendor=090c, idProduct=1000
Jan 11 10:28:27 linux58 kernel: usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 11 10:28:27 linux58 kernel: usb 1-8: SerialNumber: 12051580005333
At first glance, I would suspect that your USB device isn't formatted. Also, for "fdisk -l" to be useful, you need to specify the device for the correct drive--the USB drive. /dev/sda is almost always reserved for your operating system's system disk.
Please do this and post the output:
ls /dev/sd*
and:
lsusb
and (as root):
blkid
and (as root):
for i in `ls /dev/sd*` ; do fdisk -l "$i" ; done
Please note that the "`" marks in the above are "backticks," which are found to the left of the "1" key on your keyboard (QWERTY). When in doubt, copy and paste.
Thanks for using "quote" tags, above; please use "code" tags for these, as they'll be pretty long and might contain characters that would get turned into smileys.
If your drive isn't formatted, it won't show up in most places until you format it. We can help you with that. If it IS formatted and isn't showing up, the above commands should reveal as much, and we can go from there.
-bash-4.1$ ls /dev/sd*
/dev/sda /dev/sda1 /dev/sda2 /dev/sda5 /dev/sda6
Quote:
[root@linux58 aries_baluyot]# lsusb
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 090c:1000 Feiya Technology Corp. Flash Drive
Disk /dev/sda6 doesn't contain a valid partition table
[root@linux58 aries_baluyot]# for i in `ls /dev/sd6` ; do fdisk -l "$i" ; done
ls: cannot access /dev/sd6: No such file or directory
[root@linux58 aries_baluyot]# for i in `ls /dev/sd*` ; do fdisk -l "$i" ; done
interesting. the lsubs shows the flash drive, but none of the others show that the system did anything with it.
try this. while running tail -f /var/log/messages (this will catch the end of the file thus any changes you will see on the screen) and remove the flash drive. wait no less then 30sec. then plug the flash drive back in.
Odds are that it will be detected as /dev/sdb as sda is your internal HDD.
If the system still does not see the flash drive as a /dev/sdX, then we have problems that might be out of my skill set to help.
do we know for 100% that this flash drive works? if so what OS have you tested it in? is it formatted FAT32 or NTFS or other?
USB Flash Drive unable to detect on Mandriva 2010.2. Some USB Device are detected example of these are printers, usb bluetooth, etc. Only Mass Storage are not detected. Thanks in advance.
Based on what you posted, it looks like the flash drive isn't working. The reason is you're only seeing /dev/sdaxx, which is your hard drive. You should also see /dev/sdbxx, which would (at the very least), be the un-formatted stick. You don't.
Does this same device work in another machine? Has it EVER worked? As root, with the drive unplugged, run "dmesg -c", then plug the drive in and run "dmesg", and post the results.
I've seen this kind of thing before with problematic flash drives, so I concur with the others here that it looks to be non-functional due to a hardware problem in the drive. If you're certain that it (still) works with other machines and/or other operating systems, we can go from there, but it looks "dead" to me.
Yes it is working in other device or operating system.
My BIOS configure correctly. Any Mass Storage is not
working on my mandriva. I Think it is block or something.
I suspect that someone configure my system to do not detect
mass storage.
interesting. the lsubs shows the flash drive, but none of the others show that the system did anything with it.
try this. while running tail -f /var/log/messages (this will catch the end of the file thus any changes you will see on the screen) and remove the flash drive. wait no less then 30sec. then plug the flash drive back in.
Odds are that it will be detected as /dev/sdb as sda is your internal HDD.
If the system still does not see the flash drive as a /dev/sdX, then we have problems that might be out of my skill set to help.
do we know for 100% that this flash drive works? if so what OS have you tested it in? is it formatted FAT32 or NTFS or other?
It is still unmounted.
See result after running commands.
Quote:
[root@linux58 aries_baluyot]# tail -f /var/log/messages
Jan 12 08:19:47 linux58 kernel: usb 1-8: new high speed USB device using ehci_hcd and address 2
Jan 12 08:19:47 linux58 kernel: usb 1-8: New USB device found, idVendor=090c, idProduct=1000
Jan 12 08:19:47 linux58 kernel: usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 12 08:19:47 linux58 kernel: usb 1-8: SerialNumber: 12051580005333
Jan 12 08:20:01 linux58 nmbd[2149]: [2013/01/12 08:20:01.981356, 0] nmbd/nmbd_become_lmb.c:395(become_local_master_stage2)
Jan 12 08:20:01 linux58 nmbd[2149]: *****
Jan 12 08:20:01 linux58 nmbd[2149]:
Jan 12 08:20:01 linux58 nmbd[2149]: Samba name server LINUX58 is now a local master browser for workgroup WORKGROUP on subnet 192.168.50.158
Jan 12 08:20:01 linux58 nmbd[2149]:
Jan 12 08:20:01 linux58 nmbd[2149]: *****
Jan 12 08:20:56 linux58 kernel: usb 1-8: USB disconnect, address 2
Jan 12 08:21:12 linux58 kernel: usb 1-8: new high speed USB device using ehci_hcd and address 3
Jan 12 08:21:12 linux58 kernel: usb 1-8: New USB device found, idVendor=090c, idProduct=1000
Jan 12 08:21:12 linux58 kernel: usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan 12 08:21:12 linux58 kernel: usb 1-8: SerialNumber: 12051580005333
...but where is its /dev/ device?? If it doesn't have one (as previous posts indicate), then it can't be mounted, at all!
Please remove the drive, reboot your computer, wait for it to finish loading everything, insert the drive, and wait 1 minute. Then, re-run the commands I gave you previously and post their output. It's possible that it was in a "safely-removed" state when you last tried those commands.
@ TBone and DaneM
Yes it is working in other device or operating system.
Which other system? What OS? And how is it formatted? Have you tried other USB sticks/external drives? Have you rebooted, or restarted the haldaemon? Does it show up under your USB device applet in your GUI?
Quote:
My BIOS configure correctly. Any Mass Storage is not working on my mandriva. I Think it is block or something. I suspect that someone configure my system to do not detect mass storage.
"Someone"??? Isn't this YOUR system? If it's yours...how could 'someone' modify things to make it not work? If it's not yours, are you sure your user has rights to see/mount external devices?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.