Linux - Laptop and NetbookHaving a problem installing or configuring Linux on your laptop? Need help running Linux on your netbook? This forum is for you. This forum is for any topics relating to Linux and either traditional laptops or netbooks (such as the Asus EEE PC, Everex CloudBook or MSI Wind).
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 tried to install arch Linux on my laptop, and I have messed up somehow. This is what I get...
error: no such device: a0b8124e-507a-4c5a-bfc9-79e306898aa2.
Entering rescue mode...
Grub rescue> ls
(hd0)
Grub rescue>ls (hd0)
(hd0): Filesystem is unknown.
Grub rescue>
Since you only got as far as first reboot, you might try starting over (carefully) from scratch. Make sure that you do not skip any steps. I also always label disks, and use the label in grub, fstab, etc. but that would be overkill for your issue.
BTW: what it APPEARS is going on is that the UUID for the disk as used in grub (perhaps in stage-1) does not match the UUID on the disk. This can happen if the disk was re-established with a new UUID, but grub was not fully and correctly written after. There are other things that can cause this, and other ways it can happen, but I am NOT an expert on that, I just read about them happening to others. (Been very lucky that way since pre Fedora days, knock wood.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.