(The installed system is not Manjaro but I’m using Manjaro live USB to fix the problem … that’s why I decided to post here.)
The problem
I have dualboot between Windows 8.1. and OpenSUSE TumbleWeed with encrypted harddisk.
And now, when I try to boot the laptop - I get this error:
Welcome to GRUB!
error: no such cryptodisk found.
error: disk 'cryptouuid/...' not found.
Entering rescue mode...
grub rescue> _
How I got here:
I wanted to increase the Windows partition size, so I shrinked the Linux one. Thus some unallocated space appeared at the end of the harddisk. And I wanted to add it to the Windows partition, while the Linux one is between them. Which caused the corruption … (Didn’t know it will … so stupid …)
The state at the moment:
These are the partitions at the moment:
/dev/sda1 A6FA-7092 vfat SYSTEM
/dev/sda2 1A08019608017255 ntfs Windows
/dev/sda3 C090CFA090CF9AF4 ntfs
/dev/sda4 6e0637a3-2cd0-4411-8923-1bbea143a68a crypto_LUKS
/dev/sda5 60F8C9E0F8C9B496 ntfs Extended
sda4 is my Suse partition. I can see all my files there when I open it with file manager and enter the password for it. So my hope is that I’ll be able to restore the things as they were before and not have to re-install everything again.
What I tried so far:
I followed a tutorial I found and so - I booted Manjaro from USB (cause I got only that at that moment), mounted the Linux partition on /mnt and also /dev, /sys and /proc to /mnt/(dev|sys|proc) … then I did chroot to /mnt and tried update-grub. Manjaro doesn’t have update-grub command so I found that I have to do grub-mkconfig -o {path-to-grub.cfg}.
I tried, it gave me a lot of errors and no result.
===
Anything I can do here? … Any help will be appreciated.
Sorry, i can only give you a hint, since i never used to encrypt my partitions. At least the UUID needs to be fixed. Maybe someone with more experience could help you.
No worries, @megavolt, any info I can get is welcome.
I backed up everything important, so I got a bit more brave and deleted the windows partitions - so that now the things are much simpler.
When I run sudo lsblk -f from live USB - I get this:
The UUID that starts with 6e0637 is what can not be found upon booting.
And at the same time - when I check the etc/fstab file on the old SUSE partition - I see only this:
UUID=082f44... / ext4 acl,user_xattr 0 1
=====
Does that mean that if I fix the fstab file - it’ll be able to boot correctly into Suse? And if so - can I use a command that will automatically fill the fstab with the correct info?
However - the lsblk -frno uuid /dev/sda4 command returns two lines:
6e0637...
082f44...
And then the sed command gives me error unterminated 's' command. (Probably because of the new line in the result of lsblk?)
=====
I tried also one more things - backed up fstab and created a new one where I just replaced the UUID with the wanted one. (Not sure if this was the goal actually.) Upon booting however I got the old error - no such cryptodisk / disk ‘cryptouuid/6e0637…’ found
Aaah, @megavolt … that must have been the solution …
However, the thing is that I have a deadline and had to act quickly, so today I wiped out the entire SSD and installed the stuff a-new. I’ve backed up the most vital info so was able to work again in very short time.
=====
But still, thank you so much for all the help and the info you provided. As a matter of fact - when I see what the guys from the arch linux stated in the article you’ve provided - most probably I would have been able to boot into my old Linux. … So I’ll mark this as solved as it may help other guys who encounter the same issue and/or situation.
