You are not logged in.
Pages: 1
Hello!
This is my first post here, into which I was forced after my laptop stopped booting recently.
First, a little bit of working background before I get to the issue.
I have an old laptop that I used at school, and had 3 different OS' installed
1) Windows 10 (For playing games)
2) Debian (Primary work OS)
3) Arch (Newly installed)
Everything worked, and so I decided that I liked Arch enough to get rid of the Debian. No need for 2 different Linux distros to take up HDD space.
I did so by removing all the appropriate partitions that belonged to Debian (using fdisk), then ran grub-mkconfig to get those changes noticed by grub. A first tell-tale sign that something might be off was when it didn't even see the Windows partitions... Odd, but I still tried to reboot.
Only... To get presented with the recovery console and an error "No such partition"
Some time has passed, during which I was trying to figure out which partition it couldn't find. And only today, I found out that, for some reason, the key variables that are used even before the "normal" module gets loaded are completely wrong.
The "prefix" is still set to the old Debian partition (Which no longer exists), and the root is as well.
I corrected those manually in the recovery console, but alas, there is one more problem.
Seeing that the hard-drive was pre-partitioned when I got it, and I only ever kept resizing and moving the partitions that were already there, the EFI boot partition is, in fact, formatted as Fat32. And without the fat module file, GRUB cannot work with it in any way (Stating "Unknown filesystem" error when I try). Which means it cannot access the /boot at all. And thus gets stuck.
I tried to mitigate it by copying all the /boot files to a new directory placed in the Arch root (While running from a live USB).
THEN I was able to load the fat module, but loading the normal module afterwards failed with "Symbol grub_real_boot_time not found"
So the next thing I did was reinstalling the whole GRUB using grub-install, and re-creating the configuration file with grub-mkconfig.
But it is still stuck at the same error "No such partition", even when running it from chrooted Arch from here a live medium.
There are still things I Haven't tried, like running a rescue USB to fix GRUB for me, but I chose not to as I would like to learn something about the way that GRUB itself works. And manually fixing things like this could be handy in the future.
Does anyone have any ideas what more I should try to get it up and working again?
Offline
Pages: 1