Slackware This Forum is for the discussion of Slackware 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
|
09-09-2005, 04:21 PM
|
#1
|
Member
Registered: Mar 2004
Location: Dreary, Pennsylvania USA
Distribution: Slackware 10.2
Posts: 77
Rep:
|
USB Thumb Drive Will Not Mount Unless Present During Boot.
Actually, the title sort of says it all. I've set my thumb drive up in my fstab, but it will only mount if it was plugged in during boot. Otherwise, I get the following error:
mount: wrong fs type, bad option, bad superblock on /dev/sda,
or too many mounted file systems
I'm guessing this has something to do with hotplug, though it was my understanding that hotplug operates all the time, not just at boot.
Anyway, I can't figure out what I'm not doing, and would appreciate assistance.
|
|
|
09-09-2005, 04:43 PM
|
#2
|
Senior Member
Registered: Jun 2003
Location: California
Distribution: Slackware
Posts: 1,181
Rep:
|
have you tried mounting /dev/sda1 instead of just /dev/sda ? That was my problem at first as well.
|
|
|
09-09-2005, 04:49 PM
|
#3
|
Member
Registered: Mar 2004
Location: Dreary, Pennsylvania USA
Distribution: Slackware 10.2
Posts: 77
Original Poster
Rep:
|
Yup, I just tried it again, and sda1 is still not a valid block device.
|
|
|
09-10-2005, 12:35 AM
|
#4
|
Member
Registered: Sep 2003
Distribution: Slackware
Posts: 626
Rep:
|
After plugging the drive in, use the following command to check how the drive is identified:
Code:
tail -s 3 -f /var/log/messages
then mount it as the identified device.
The output on my system after plugging in my camera is
Code:
tail -s 3 -f /var/log/messages
Sep 10 08:28:54 kernel: SCSI device sda: 494753 512-byte hdwr sectors (253 MB)
Sep 10 08:28:54 kernel: sda: assuming Write Enabled
Sep 10 08:28:54 kernel: SCSI device sda: 494753 512-byte hdwr sectors (253 MB)
Sep 10 08:28:54 kernel: sda: assuming Write Enabled
Sep 10 08:28:54 udev[18731]: creating device node '/dev/sda'
Sep 10 08:28:54 kernel: sda: sda1
Sep 10 08:28:54 kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Sep 10 08:28:54 kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Sep 10 08:28:55 udev[18739]: creating device node '/dev/sda1'
Sep 10 08:28:55 udev[18755]: creating device node '/dev/sg0'
so I would mount it with "mount /dev/sda1 /mnt/camera" (if I had a directory "camera" under /mnt)
|
|
|
09-10-2005, 06:22 AM
|
#5
|
Member
Registered: Mar 2005
Location: chennai(madras), India
Distribution: slackware ofcourse
Posts: 654
Rep:
|
r u enabled hotplug start, do u enabled it in kernel
do a dmesg after plugging the usb, if u have enabled hotplug
c what the device is labeled as most probably it will b in /dev/sda1
if so u could mout it as u desire if u want u count mount it in /mnt/cdrom hi
|
|
|
09-10-2005, 08:42 PM
|
#6
|
Member
Registered: Mar 2004
Location: Dreary, Pennsylvania USA
Distribution: Slackware 10.2
Posts: 77
Original Poster
Rep:
|
Quote:
Originally posted by mdg
After plugging the drive in, use the following command to check how the drive is identified:
Code:
tail -s 3 -f /var/log/messages
then mount it as the identified device.
The output on my system after plugging in my camera is
Code:
tail -s 3 -f /var/log/messages
Sep 10 08:28:54 kernel: SCSI device sda: 494753 512-byte hdwr sectors (253 MB)
Sep 10 08:28:54 kernel: sda: assuming Write Enabled
Sep 10 08:28:54 kernel: SCSI device sda: 494753 512-byte hdwr sectors (253 MB)
Sep 10 08:28:54 kernel: sda: assuming Write Enabled
Sep 10 08:28:54 udev[18731]: creating device node '/dev/sda'
Sep 10 08:28:54 kernel: sda: sda1
Sep 10 08:28:54 kernel: Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
Sep 10 08:28:54 kernel: Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type 0
Sep 10 08:28:55 udev[18739]: creating device node '/dev/sda1'
Sep 10 08:28:55 udev[18755]: creating device node '/dev/sg0'
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:
Code:
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?
Last edited by IamI; 09-10-2005 at 08:54 PM.
|
|
|
09-11-2005, 11:08 AM
|
#7
|
Member
Registered: Mar 2004
Location: Dreary, Pennsylvania USA
Distribution: Slackware 10.2
Posts: 77
Original Poster
Rep:
|
Now the damn thing doesn't work at all. It worked once, but I haven't changed anything. What the hell?
|
|
|
09-11-2005, 11:26 AM
|
#8
|
Member
Registered: Sep 2003
Distribution: Slackware
Posts: 626
Rep:
|
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.
|
|
|
09-11-2005, 01:15 PM
|
#9
|
Member
Registered: Mar 2004
Location: Dreary, Pennsylvania USA
Distribution: Slackware 10.2
Posts: 77
Original Poster
Rep:
|
Quote:
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.
|
|
|
09-11-2005, 02:33 PM
|
#10
|
Member
Registered: Mar 2004
Location: Dreary, Pennsylvania USA
Distribution: Slackware 10.2
Posts: 77
Original Poster
Rep:
|
Oh, so *now* it's /dev/sdb. I wonder how long that will last.
~Edit~
Okay, that was my problem. Slack decided to pull a fast one on me.
Last edited by IamI; 09-11-2005 at 02:45 PM.
|
|
|
02-19-2006, 09:17 PM
|
#11
|
Member
Registered: Oct 2004
Location: Missouri, USA
Distribution: Slackware 12.2, Xubuntu 9.10
Posts: 371
Rep:
|
Quote:
Originally Posted by IamI
Oh, so *now* it's /dev/sdb. I wonder how long that will last.
~Edit~
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/sd b1??? 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.
Thanks.
|
|
|
02-20-2006, 04:47 AM
|
#12
|
Member
Registered: Mar 2004
Location: Dreary, Pennsylvania USA
Distribution: Slackware 10.2
Posts: 77
Original Poster
Rep:
|
Thanks for the thread necromancy. I'd forgotten about it, and I still have this irritating problem with Slack.
|
|
|
02-20-2006, 04:58 AM
|
#13
|
Senior Member
Registered: Dec 2004
Location: In my house.
Distribution: Ubuntu 10.10 64bit, Slackware 13.1 64-bit
Posts: 2,649
Rep:
|
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.
If you do it enough with enough devices/ports, you can easily get to /dev/sdz. After that, I have no idea....... /dev/sd@ or sd+.....
Any ideas? Hmm.....Sounds like an interesting research project....
Last edited by cwwilson721; 02-20-2006 at 05:00 AM.
|
|
|
02-20-2006, 07:57 AM
|
#14
|
Member
Registered: Oct 2004
Location: Missouri, USA
Distribution: Slackware 12.2, Xubuntu 9.10
Posts: 371
Rep:
|
Quote:
Originally Posted by cwwilson721
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...)
Thanks,
|
|
|
02-20-2006, 05:02 PM
|
#15
|
Member
Registered: Mar 2004
Location: Dreary, Pennsylvania USA
Distribution: Slackware 10.2
Posts: 77
Original Poster
Rep:
|
Quote:
Originally Posted by pnellesen
So, any ideas on how one sets up /etc/fstab for this?
|
Or perhaps more to the point: is there any way to reserve /dev devices that will remain stable and be assigned only to a specific device that may or may not be present at any given time?
|
|
|
All times are GMT -5. The time now is 06:15 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|