This is the first time I’ve seen a ‘blue-screen’ from a Linux operating system!
I have attached a screenshot of the message. I normally try to resolve these sorts of things myself, but in this instance I wouldn’t know where to start.
I can simply setup the VM again, but that goes against my nature of trying to fix things first.
If anyone can point me in a direction for a potential fix, that’d be great.
This is using virt-manager, with QEMU/KVM, in case that helps.
Line 7 and 8 of that message appear to point to the problem.
module binfmt-0000 → is that the real name of that module?
/bin/sh exists but could not be executed
some sort of file system error?
I’d first run fsck manually if it is not run automatically - or perhaps it encounters errors that won’t be fixed automatically
Boot from ISO, open the encrypted container and run a check …
Ok, thank you for the additional info. I ran the attached command along with the output, which looks reasonably error-free. I was also able to chroot into the volume without issues.
I have attempted reinstalling the shell etc. which all reinstalled fine, but boot continued to fail. I ran out of time to fix this, so setup the whole virtual machine again.
Thank you for your help in any case!
