You are not logged in.
Hello:
I dd'd devuan_daedalus_5.0.1_amd64_netinstall.iso to an 4.0Gb SD card.
Then installed it on an 8.0Gb USB stick.
The usual precautions taken:
- checked SHA256 of the downloaded *.iso
- installer check of the installation media before anything else
This is how the USB is partitioned:
# fdisk -l /dev/sdg
Disk /dev/sdg: 7.22 GiB, 7757398016 bytes, 15151168 sectors
Disk model: DataTraveler 2.0
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: 0xdb4d27ce
Device Boot Start End Sectors Size Id Type
/dev/sdg1 * 2048 4190207 4188160 2G 83 Linux
/dev/sdg2 4192254 15151103 10958850 5.2G 5 Extended
/dev/sdg5 4192256 14741503 10549248 5G 83 Linux
/dev/sdg6 14743552 15151103 407552 199M 82 Linux swap / Solaris
#
On booting the USB, I get this:
GRUB loading.
Welcome to GRUB!
error: file ` /boot/grub/i386-pc/normal.mod not found.
grub rescue>
The installation was run on my Sun Ultra 24 which is not hampered by att the UEFI whatever crap.
Just plain BIOS boot, thank you.
It is as bare as could be (still needs a good clean-up) as I want to use it to run Clonezilla-Live.
Just the defaults, no desktop enviroment.cd.
When I mount the drive, CD to /boot, I get this:
$ /boot/grub$ ls
grub.cfg splash.png unicode.pf2
$
Seems that grub is pointing to my system drive UUID ...
search --no-floppy --fs-uuid --set=root d6841f29-e39b-4c87-9c52-3a9c3bafe2d3
... instead of pointing to the USB UUID:
# blkid
--- snip ---
/dev/sdb1: LABEL="devuan" UUID="d6841f29-e39b-4c87-9c52-3a9c3bafe2d3" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0004a8f4-01"
--- snip ---
/dev/sdg1: UUID="68f8d933-a2a1-40eb-916f-eba5582c8968" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="db4d27ce-01"
--- snip ---
#
No idea how that happened, but it did.
Question:
Manually changing all instances of the system UUID for the correct one will do?
If not, which is the easiest/fastest way to fix this?
Thanks.
Best,
A.
Offline
Usually it would amount to chroot onto the target and then run update-grub though possibly the installation of grub got confused by something (e.g. a presence of an EFI partition on the host during the installation; the installer has one) and then installed the wrong package variant.
I guess you should have the grub-pc package installed, So make sure the chroot filesystem has the right package and then run grub-install for it (which probably does require mounting of /proc, /sys and /dev) before update-grub.
Offline