Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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.
I have two sata drives and one usb drive. After booting, /dev/sdb is sometimes the second sata drive and other times the usb drive. I understand that there are work-arounds for a number of problems this causes; some of these are the use of udev rules or LABELs or UUIDs to identify partitions, but I still would rather have a consistent name for my second sata drive. (My drives all have multiple partitions, and it's hard for me to keep them straight without consistent nomenclature.) Is there any way to prevent the kernel from recognizing any usb drive at boot time, with a way to recognize it later after boot?
I've noticed that the order seems to be dependent on the time between the first display of the grub.cfg menu and the time when an entry is selected. Is there any way to build a delay into the boot process, either through grub commands or through kernel boot parameters?
You can use labels in fstab, or UUID's. Use blkid, it will show you PARTUUID's and UUID's. Labeling is probably the nicest way, you can label your filesystems 'storage', 'data', 'system', whatnot.
Are the two internal disks really SATA, or do you have an old (E)IDE drive in there that gets represented as /dev/sd# ?. Various distros handle this mix poorly.
The ordering is determined by how long it takes drives to respond to a controller query...
The only relatively guaranteed disk is /dev/sda, which is used by the BIOS/UFI to load the boot program; and that is only because it must be spun up and ready when the boot program takes over. After that all bets are off.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.