Boot problem on USB HDD: can't find /mnt in /etc/fstab error
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.
If it matters:
Of the machines that i can boot:
My two home PCs (one is HP, the other is homebuilt AMD machine with K8N Neo motherboard), and a Sony Vaio netbook.
Of the machines that i can't boot:
A nobrand microtower with Biostar P4M900-M4 MB
Dell OptiPlex 5060
Are you actually using the UUID of your harddrive in the mkinitrd command? I'm not sure if yours is edited to not show the UUID (which it doesn't really matter if those are made public or not) or if that is the actual command you ran.
And you'll definitely want to switch your /etc/fstab to UUIDs as if there is another harddrive or USB drive (or sometimes even cardreaders), it can affect your device names (/dev/sda, /dev/sdb, etc). Using UUIDs in your fstab will make sure that you don't run into issues with those changing. My guess is your problem is caused by the lack of UUIDs in your fstab and once you fix that, it will likely fix your problem.
Of the machines that i can't boot:
A nobrand microtower with Biostar P4M900-M4 MB
Dell OptiPlex 5060
Any suggestion how to fix this?
Could it be that the machines you cannot boot have UEFI enabled, which means they will need a FAT formatted UEFI partition with kernel and initrd ON your external hard disk?
Are you actually using the UUID of your harddrive in the mkinitrd command? I'm not sure if yours is edited to not show the UUID (which it doesn't really matter if those are made public or not) or if that is the actual command you ran.
And you'll definitely want to switch your /etc/fstab to UUIDs as if there is another harddrive or USB drive (or sometimes even cardreaders), it can affect your device names (/dev/sda, /dev/sdb, etc). Using UUIDs in your fstab will make sure that you don't run into issues with those changing. My guess is your problem is caused by the lack of UUIDs in your fstab and once you fix that, it will likely fix your problem.
Could it be that the machines you cannot boot have UEFI enabled, which means they will need a FAT formatted UEFI partition with kernel and initrd ON your external hard disk?
UEFI boot is disabled on this Dell machine I had issue with, it uses Legacy boot.
Based on the error screen the issue is most likely a missing module in the initrd. I wonder if an initrd similar to the one offered with a Slackware installation USB is the way to go for your use case. Maybe the "usbboot.img" found in the usb-and-pxe-installers directory of a 14.1 mirror can point the way to creating a universally bootable USB HDD for your mix of PCs?
You could try running /usr/share/mkinitrd/mkinitrd_command_generator.sh on the problematic machine and add any missing modules it suggests to your initrd.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.