SlackwareThis 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.
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.
Distribution: Xubuntu, Mythbuntu, Lubuntu, Picuntu, Mint 18.1, Debian Jessie
Posts: 1,207
Rep:
USB drive won't automount
I am running Slackware 12 with kernel 2.6.23.8 and using an external hard drive as an extra ext3 partition. I setup /etc/fstab to automount this drive automatically at boot with the following command:
/dev/sda1 /mnt/mp3 ext3 defaults 0 0
This computer moves too fast to read the boot messages, but I examined dmesg and /var/log/messages and found nothing that indicates an error. The problem is that sda1 is not getting mounted on boot. I can manually mount this drive with:
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Just want to make sure on some things. With the newer kernels many IDE controlers are using pata to sata mode drivers which in older kernels IDE were seen as /dev/hdXX and new kernels use /dev/sdXX. So I am curious as to what the system sees with the USB drive plugged in. Post ouptu of this command as root.
/sbin/fdisk -l
Distribution: Xubuntu, Mythbuntu, Lubuntu, Picuntu, Mint 18.1, Debian Jessie
Posts: 1,207
Original Poster
Rep:
root@LinuxHippy:~# fdisk -l
Disk /dev/hda: 20.0 GB, 20020396032 bytes
16 heads, 63 sectors/track, 38792 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 19146 9649552+ 83 Linux
/dev/hda2 19147 38292 9649584 83 Linux
/dev/hda3 38293 38792 252000 82 Linux swap
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 9729 78148161 83 Linux
/dev/sda2 9730 19457 78140160 83 Linux
I have 2 partitions on each drive and 1 swap on the hard drive.
Last edited by linuxhippy; 11-22-2007 at 07:20 AM.
I only want my user to have read and execute access to this drive. Do I have to add to plugdev for this?
I'm fairly certain that for automount to happen your user needs to be a member of plugdev.
Not sure if you need plugdev for just read and execute.
I'll let someone else answer that one:-)
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
Maybe placing the auto option on the fstab line for the mount might do it.
Other than that leave the fstab alone and add the mont command you use to mount in /etc/rc.local.
Distribution: Xubuntu, Mythbuntu, Lubuntu, Picuntu, Mint 18.1, Debian Jessie
Posts: 1,207
Original Poster
Rep:
Quote:
Originally Posted by Brian1
Maybe placing the auto option on the fstab line for the mount might do it.
Other than that leave the fstab alone and add the mont command you use to mount in /etc/rc.local.
Brian
I was thinking I could just add the mount command to /etc/rc.local...but will it be file checked?
I bet this is a problem with the "mount" command happening before "udev" is launched and the corresponding USB mass storage modules loaded. The error would appear in the virtual terminal but not in /var/log/messages or "dmesg". Try to put the "noauto" keyword in the fstab line and add the mount command to rc.local and report results.
Distribution: Xubuntu, Mythbuntu, Lubuntu, Picuntu, Mint 18.1, Debian Jessie
Posts: 1,207
Original Poster
Rep:
Quote:
Originally Posted by rg3
I bet this is a problem with the "mount" command happening before "udev" is launched and the corresponding USB mass storage modules loaded. The error would appear in the virtual terminal but not in /var/log/messages or "dmesg". Try to put the "noauto" keyword in the fstab line and add the mount command to rc.local and report results.
Distribution: Distribution: RHEL 5 with Pieces of this and that.
Kernel 2.6.23.1, KDE 3.5.8 and KDE 4.0 beta, Plu
Posts: 5,700
Rep:
glad to see you have it working. I forgot you were using Slackware and just thought Redhat type when I seen your sig to the left. At any point you have it working. There seems to be some odd stuff with the 2.6.23 kernels and the way some items are started up in the runlevels be seeing weird stuff like this everywhere and on many distros.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.