Re: A Grub Boot Question about initrd
Martin McCormick composed on 2021-06-06 16:59 (UTC-0500):
...
> Swap is the last partition.
> Disk /dev/sde:
This is a big lurking booby trap that could have been the problem both last time
and this time. It's one of the reasons why installation systems and Grub switched
from using device names to using UUIDs: inconsistent and/or unpredicable device
enumeration.
Is this a PC with both PATA and SATA controllers? These old PCs can compound the
issue.
Different kernel, disk controller, USB controller and BIOS combinations can cause
e.g. an SATA or PATA disk sda to become sde, or sdb become sda, IOW, device names
that don't persist. UUIDs are supposed to prevent inconsistent device names from
being a problem, but in a rescue environment, it can muddy the waters, or backfire.
> 29.8 GiB, 32017047552 bytes, 62533296 sectors
> Disk model: 600
> Units: sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disklabel type: dos
> Disk identifier: 0x00000080
> Device Boot Start End Sectors Size Id Type
> /dev/sde1 2048 59314876 59312829 28.3G 83 Linux
> /dev/sde2 59314877 62533295 3218419 1.5G 5 Extended
> /dev/sde5 59316925 62533295 3216371 1.5G 82 Linux swap / Solaris
Is this 32GB (29.8GiB) sde disk in fact the disk in the problem PC, and not a USB
device?
I still think yours is fixable most easily by using volume labels. They're easier
on human brains, yet can be functionally as unique as needs be. Post /etc/fstab
from this disk, and blkid output, the first complete grub.cfg stanza, and
/etc/default/grub to get started. If that 28G partition that is shows above as
sde1 doesn't have a label, give it one with e2label or tune2fs.
--
Evolution as taught in public schools is, like religion,
based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
Reply to: