so I am new to how to do these, so I apologize if something I say is not how things are done here.
So I have been using Ubuntu 18.04 for a while now. Recently I wanted to try and dual boot LineageOS to just play around with it, and I think I may have damaged my Grub files (or whatever it is called). I have tried to force boot the partition with Ubuntu on it, but I keep getting the same error.
Grub rescue> ls
(hd0) (hd0,msdos1) (hd1) (hd1,msdos1)
grub rescue>set boot=(hd0,msdos1)
grub rescue>set prefix=(hd0,msdos1)/boot/grub
insmod normal
error:unknown filesystem.
I tried the same thing with set root=(hd0,msdos1)
but that got me the same issue. I tried both of these variants with (hd0)
, (hd1)
, (hd1,msdos1)
, and got again the same errors. I am unsure of what to do at this point because I have gone through a lot of different things to try and fix this issue and none of them have done anything. Any advice or suggestions are welcome, and I appreciate all of it!
Note: I did try to boot off of a live USB, which gives me a blank screen, and if I try to boot it through Grub rescue ((hd1,msdos1) is its file system) and I get the same error through Grub. If there are any questions at all feel free to ask, and thank you in advance.
ls (hd0,0)/
ls (hd0,1)/
ls (hd1,0)/home/
etc..etc... until you've located the correct one (you can just use the number).... Also take a look at what returns from just typing 'set' – WU-TANG Jul 22 '20 at 00:03cmdpath=(hd0)
prefix=(lvmid/h1gqcw-ntj0-gciK-2Doa-XdKn-YMQa-4DG2FV/OBg9xz-gk30-aMsG-SNOc-SLFS-HBTQ-LTsxzj)/boot/grub
root=lvmid/h1gqcw-ntj0-gciK-2Doa-XdKn-YMQa-4DG2FV/OBg9xz-gk30-aMsG-SNOc-SLFS-HBTQ-LTsxzj
I am not sure what any of this means, but when entering grub rescue, I get error: disk 'the same strand as prefix and root here' not found. Entering rescue mode...
– TheBlinded Jul 22 '20 at 05:35cat /etc/fstab
says cat is still unknown, but ls /etc/fstab says the disk 'string ID here' not found. – TheBlinded Jul 24 '20 at 21:53ls (hd0,1)/etc/fstab
... but it does not seem to be recognizing the drive that way. You may have to use the long string above or something like (lvm,XYZ....). It's hard to describe this here.. I don't know what your "play around with" entailed... First thing is getting the filesystem to respond, if it still will... the other thing i would do is try to get the live USB to boot. – WU-TANG Jul 24 '20 at 22:27