On Tue, Jan 26, 2021 at 03:41:23PM +0000, tetrahe...@danwin1210.me wrote:
Any ideas why the kernel isn't seeing sr0a as a root device?
As suggested in the "Managed to mess up the system encrypted disk. I can
no longer boot" thread, I tried running installboot from the working
(booted from the internal disk bootloader) system against all the
relevant disks:
- the USB drive
- sd0 (the physical disk, with the bootloader)
- sd1 (aka sr0 or softraid0, the now-decrypted encrypted volume)
Unfortunately this did not fix the problem, I am still geting kernel
panics.
Looking more closely at the error message:
panic: root device (e8xxxx) not found
the code given (e8xxxx) is the disklabel disk ID of the root volume (sd1
/ softraid0) as given in /etc/fstab (when the system is booted from the
internal bootloader). It's the ID of the (decrypted) softraid volume.
Therefore:
- when booting from the bootloader on the internal HD, and after
decrypting the encrypted volume, the system is able to find the disk
e8xxxx without trouble, but
- when booting from the bootloader on the USB stick, and after
decrypting the same encrypted volume (with the same password, etc),
the system is NOT able to find the disk e8xxxx.
What the heck is going on? Why can't the system find softraid volume
that it just decrypted?
