When you get the grub prompt, hit "e" for edit mode, or maybe better "c"
for command line. By typing "root (" and hitting tab, it should let you
know what disks it sees. If you're not sure which disk is which which,
accept one (such as hd0) and then hit tab to see the partitions it sees.
Possible reasons (mainly pulled out of thin air) does the partition need
the boot flag set? do you need to specify rootfs type?
On 7/25/19 11:25 AM, Grant Edwards wrote:
On 2019-07-25, Grant Edwards <[email protected]> wrote:
All the examples I can find of people using root=PARTUUID=<> show the
longer PARTUUID values you get with a GPT parition table. Does the
root=PARTUUID=<> mechanism only work with GPT and not with DOS
parition tables?
The comments in the kernel source certinaly indicate that DOS PARTUUID
values should work. From init/do_mounts.c:
/*
* Convert a name into device number. We accept the following variants:
[...]
* 6) PARTUUID=00112233-4455-6677-8899-AABBCCDDEEFF representing the
* unique id of a partition if the partition table provides it.
* The UUID may be either an EFI/GPT UUID, or refer to an MSDOS
* partition using the format SSSSSSSS-PP, where SSSSSSSS is a zero-
* filled hex representation of the 32-bit "NT disk signature", and PP
* is a zero-filled hex representation of the 1-based partition number.
[...]
I've also tried just passing root=/dev/sdb1 (which in the current
setup is consistently the device the root partition shows up on).
That doesn't work either and I'm begining to suspect that the kernel
simply isn't recognizing the USB storage device at all.
I wish I could figure out how to get scrollback to work so I could see
all of the kernel messages before the panic...
