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-01-2013, 09:15 PM
|
#1
|
Senior Member
Registered: May 2009
Location: center of singularity
Distribution: Xubuntu, Ubuntu, Slackware, Amazon Linux, OpenBSD, LFS (on Sparc_32 and i386)
Posts: 2,895
Rep: 
|
USB device probing is inconsistent
I think this problem is caused by udev, but maybe also the kernel.
I just bought 3 new USB backup drives, WD My Passport brand, 2TB each. I have Slackware64-current installed from the packages as of 2013-08-21. When I boot up the system installed on the /dev/sda hard drive on SATA (there is also /dev/sdb on SATA), with one new USB drive plugged in, the USB drive does not come up in /proc/partitions, not even the whole drive line. If I unplug the drive, then plug it back in, then it does show up as /dev/sdc.
But this is MOST of the time. ONE time it did show up in the initial boot, as /dev/sdh. But even then replugging it changed it to /dev/sdc.
When I boot the install DVD, it always shows up in that system as dev/sdh.
But in the cases where it does not show up in /proc/partitions, it does show up in the output of "lsusb -t" as a storage device.
And udev is always reporting errors on devices up through /dev/sdg. Is it just a bad udev configuration? udev seems to always be a big trouble maker, and it has one of the most difficult configuration schemes I have ever seen (requires knowledge about existing devices when the goal should be to operate correctly regardless of the devices).
I'm actually wanting to install Slackware on the USB drive as a backup system. I probably could install it. But apparently when I boot it, it won't see its root filesystem device and won't be able to run.
|
|
|
09-02-2013, 10:51 AM
|
#2
|
LQ Addict
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-15.0
Posts: 11,361
Rep: 
|
Quote:
Originally Posted by Skaperen
I'm actually wanting to install Slackware on the USB drive as a backup system. I probably could install it. But apparently when I boot it, it won't see its root filesystem device and won't be able to run.
|
I'd append a "rootdelay=20" or so in /etc/lilo.conf and identify the device by its UUID (plug it in then run blkid as root to know which it is), in /etc/fstab as in /etc/lilo.conf.
|
|
|
09-02-2013, 09:51 PM
|
#3
|
Senior Member
Registered: May 2009
Location: center of singularity
Distribution: Xubuntu, Ubuntu, Slackware, Amazon Linux, OpenBSD, LFS (on Sparc_32 and i386)
Posts: 2,895
Original Poster
Rep: 
|
Quote:
Originally Posted by Didier Spaier
I'd append a "rootdelay=20" or so in /etc/lilo.conf and identify the device by its UUID (plug it in then run blkid as root to know which it is), in /etc/fstab as in /etc/lilo.conf.
|
I'm not using lilo. I'm guessing you mean to have the kernel wait before trying to mount root. But keep in mind that the kernel never sees the USB device. It's not a matter of time.
|
|
|
09-03-2013, 08:33 PM
|
#4
|
LQ Guru
Registered: Jul 2011
Location: California
Distribution: Slackware64-15.0 Multilib
Posts: 6,564
|
You could always try to remove udev and replace it with mdev and hotplug. Few guys had a similar setup working with Gentoo a while back.
It will eliminate auto-mounting drives, meaning you'll have to setup optical drives manually and mount stuff by hand, but it works fairly well if udev is being a total pain and needs to be sacrificed and put to death.
Hotplug's last Slackware source and binary package should work with modern systems, though you may want to pour over the legacy scripts to make sure they're up-to-date. Hotplug should be able to work where mdev doesn't with auto-detecting devices and loading the driver modules for them.
Binary package:
http://mirrors.slackware.com/slackwa...-noarch-11.tgz
Source (and SlackBuild):
http://mirrors.slackware.com/slackwa...rce/a/hotplug/
Information on mdev can be found here:
https://wiki.gentoo.org/wiki/Mdev
Be warned, this is a rather advanced method to solving udev issues, and shouldn't be attempted unless udev absolutely has to be gotten rid of.
There is also Hotplug2 you can look into as well:
http://code.google.com/p/hotplug2/
Last edited by ReaperX7; 09-03-2013 at 08:51 PM.
|
|
|
All times are GMT -5. The time now is 10:27 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.
|
Latest Threads
LQ News
|
|