USB Thumb Drive Will Not Mount Unless Present During Boot.
SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
so I would mount it with "mount /dev/sda1 /mnt/camera" (if I had a directory "camera" under /mnt)
Okay, judging from the output of tailing /var/log/messages, my system is acknowledging the presence of the drive, but not really creating any device for it. This is what I get when I plug the thing in and out hot:
Sep 10 21:17:39 darkstar kernel: usb.c: USB disconnect on device 00:10.2-1 address 6
Sep 10 21:17:39 darkstar kernel: usb.c: USB disconnect on device 00:10.2-1.1 address 7
Sep 10 21:19:05 darkstar kernel: hub.c: new USB device 00:10.2-1, assigned address 8
Sep 10 21:19:05 darkstar kernel: hub.c: USB hub found
Sep 10 21:19:05 darkstar kernel: hub.c: 1 port detected
Sep 10 21:19:06 darkstar kernel: hub.c: new USB device 00:10.2-1.1, assigned address 9
Sep 10 21:19:35 darkstar kernel: usb.c: USB disconnect on device 00:10.2-1 address 8
Sep 10 21:19:35 darkstar kernel: usb.c: USB disconnect on device 00:10.2-1.1 address 9
Sep 10 21:19:47 darkstar kernel: hub.c: new USB device 00:10.2-1, assigned address 10
Sep 10 21:19:47 darkstar kernel: hub.c: USB hub found
Sep 10 21:19:47 darkstar kernel: hub.c: 1 port detected
Sep 10 21:38:31 darkstar -- MARK --
And that's all she wrote. I have no idea what to do about it, though. What is not happening now that evidently happens during boot?
Originally posted by mdg Well, I don't know what the problem is, maybe the fstab entry, maybe modules not loading?
Anyway, here's the page I used to set up my usb stick, have a look through and compare.
Line for line, that's preciesly what I did, except that it showed up as /dev/sda. And it worked twice: the first time immediately after I set everything up, and then once after a reboot cycle. Now, it does not work at all no matter what I try, and I haven't changed anything permanent. I've modprobed usb-storage out the wazoo, and that does not appear to be the problem.
I dunno. Something must be different, but I can't for the life of me pin down what it is. It's not the stick itself; it still performs happily in XP.
Oh, so *now* it's /dev/sdb. I wonder how long that will last.
Okay, that was my problem. Slack decided to pull a fast one on me.
I know this is an old thread, but I've been fighting this issue for about a week, and this is the FIRST post that gave me any idea of what to look for - specifically, I noticed that my system was pointing to the thumb drive as "/dev/sdd1" instead of "/dev/sda1" like my other usb devices (I didn't know that was even a possibility???.) I WAS able to mount the thumb drive when I pointed to /dev/sdd1. Possible stupid question - would it be worthwhile to add an additional line to my /etc/fstab file to account for this situation? I just tried my Olympus camera as well while typing this - THAT device went to /dev/sdb1??? Can somebody possibly explain what's happening here? I haven't read anything anywhere about Linux/Slackware rotating/changing which scsi device path different devices get assigned - if there IS a page somewhere describing this I'd appreciate it if somebody posted a link to it.
GNU/Linux assigns devices by the order they are originally detected.
For example: first USB device it finds maybe /dev/sda, but if you unplug it hot, then plug back into another port, it may decide that it's /dev/sdb.
So, any ideas on how one sets up /etc/fstab for this? I played with it a few more times last night, and it "appeared" that the devices maintained their assignments, meaning no matter how many times I disconnected the thumb drive it was assigned the same device path, and the same behavior for my camera. As long as this behavior's consistent, it's not a problem, though I'd hate to have to create an entirely new mount point for each and every new device I'd attach.
Note that this is all on the same USB port - I haven't connected 1 device to 1 port, the next to another (I've only got 2 ports on the machine anyway...)