You are not logged in.
- Topics: Active | Unanswered
#1 2024-08-14 17:24:34
- deepforest
- Member
- Registered: 2020-03-24
- Posts: 354
after cloning Devuan Daedulus to SSD grub still use old root UUID(hdd)
1. copy hdd ext4 partiotion to ssd ext4
2. install grub to ssd partition
3. update ssd fstab with new UUID
4. update-gub
try to boot in grub boot menu ssd entry still use old uuid from hdd partition
old hdd uuid
linux /boot/vmlinuz-6.1.0-23-amd64 root=039cfdd1-19a0-436a-868e-93ad302371ad
new sdd uuis
if i am manually change via "e"
linux /boot/vmlinuz-6.1.0-23-amd64 root=bab95b18-9201-499e-b96b-6ab89bfd41e0
all booting ok in to sdd
root@home:/boot/grub# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
fd0 2:0 1 4K 0 disk
sda 8:0 0 186.3G 0 disk
├─sda1 8:1 0 10.5G 0 part
├─sda2 8:2 0 1K 0 part
├─sda5 8:5 0 29.3G 0 part
├─sda6 8:6 0 48.8G 0 part
├─sda7 8:7 0 48.8G 0 part
└─sda8 8:8 0 48.8G 0 part
sdb 8:16 0 223.6G 0 disk
├─sdb1 8:17 0 72.3G 0 part /
├─sdb2 8:18 0 72.3G 0 part
├─sdb3 8:19 0 75G 0 part
├─sdb4 8:20 0 1K 0 part
└─sdb5 8:21 0 4G 0 part [SWAP]
sdc 8:32 0 149.1G 0 disk
├─sdc1 8:33 0 70.3G 0 part
├─sdc2 8:34 0 4.5G 0 part
├─sdc3 8:35 0 50M 0 part
└─sdc4 8:36 0 74.2G 0 part
sdd 8:48 0 931.5G 0 disk
├─sdd1 8:49 0 75.7G 0 part
├─sdd2 8:50 0 4G 0 part
├─sdd3 8:51 0 345.7G 0 part /home
├─sdd4 8:52 0 1K 0 part
└─sdd5 8:53 0 506.1G 0 part
sde 8:64 0 149G 0 disk
├─sde1 8:65 0 70.3G 0 part
├─sde2 8:66 0 4G 0 part
└─sde3 8:67 0 74.7G 0 part
root@home:/boot/grub# root@home:/# blkid
/dev/sdd2: UUID="34d1ae4c-5d37-4bb7-bdd4-ae5a95060504" TYPE="swap" PARTUUID="907085ae-02"
/dev/sdd5: LABEL="NEW5" BLOCK_SIZE="512" UUID="3232708532704FB9" TYPE="ntfs" PARTUUID="907085ae-05"
/dev/sdd3: UUID="24c316e7-38e1-4db4-a0aa-ade09eea7782" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="907085ae-03"
/dev/sdd1: UUID="5720e815-c048-427f-b2f8-c5bd6d68665b" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="907085ae-01"
/dev/sdb2: UUID="e4470a2b-7a42-4eee-9051-2f0ce31da08c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="1f909dee-02"
/dev/sdb5: UUID="d531b1fd-dfd5-4734-9ab2-e4f304348902" TYPE="swap" PARTUUID="1f909dee-05"
/dev/sdb3: LABEL="New 10" BLOCK_SIZE="512" UUID="B842FF8142FF42A4" TYPE="ntfs" PARTUUID="1f909dee-03"
/dev/sdb1: UUID="bab95b18-9201-499e-b96b-6ab89bfd41e0" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="1f909dee-01"
/dev/sde2: UUID="a5633ead-0ebc-4f5b-b0fd-cd036aeb94f6" TYPE="swap" PARTUUID="0002426d-02"
/dev/sde3: UUID="c266328b-3853-45d6-b1e5-5e795370f40e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0002426d-03"
/dev/sde1: UUID="039cfdd1-19a0-436a-868e-93ad302371ad" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="0002426d-01"
/dev/sdc2: UUID="b6b16d67-2aab-43c1-bfc4-d948e4a270b5" TYPE="swap" PARTUUID="6296eae2-02"
/dev/sdc3: LABEL="System Reserved" BLOCK_SIZE="512" UUID="A0D6B4C7D6B49ECA" TYPE="ntfs" PARTUUID="6296eae2-03"
/dev/sdc1: LABEL="NEW4" BLOCK_SIZE="512" UUID="4E9E2ABD9E2A9E09" TYPE="ntfs" PARTUUID="6296eae2-01"
/dev/sdc4: LABEL="NEW_10" BLOCK_SIZE="512" UUID="A414D1AC14D1822A" TYPE="ntfs" PARTUUID="6296eae2-04"
/dev/sda7: LABEL="NEW_7" BLOCK_SIZE="512" UUID="0EAC29DEAC29C157" TYPE="ntfs" PARTUUID="3dd23dd1-07"
/dev/sda5: LABEL="NEW1" BLOCK_SIZE="512" UUID="E498D01C98CFEADE" TYPE="ntfs" PARTUUID="3dd23dd1-05"
/dev/sda1: LABEL="M-PM-^]M-PM->M-PM-2M-QM-^KM-PM-9 M-QM-^BM-PM->M-PM-<" BLOCK_SIZE="512" UUID="064C49404C492BAD" TYPE="ntfs" PARTUUID="3dd23dd1-01"
/dev/sda8: LABEL="NEW3" BLOCK_SIZE="512" UUID="B8E45713E456D2EC" TYPE="ntfs" PARTUUID="3dd23dd1-08"
/dev/sda6: LABEL="NEW2" BLOCK_SIZE="512" UUID="E8802A87802A5C76" TYPE="ntfs" PARTUUID="3dd23dd1-06"
root@home:/# already did, not help
root@home:/# tune2fs -U bab95b18-9201-499e-b96b-6ab89bfd41e0 /dev/sdb1
/etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sdb1 during installation
UUID=bab95b18-9201-499e-b96b-6ab89bfd41e0 / ext4 errors=remount-ro 0 1
# /home was on /dev/sdd3 during installation
UUID=24c316e7-38e1-4db4-a0aa-ade09eea7782 /home ext4 defaults 0 2
# swap was on /dev/sdb2 during installation
UUID=d531b1fd-dfd5-4734-9ab2-e4f304348902 none swap sw 0 0/etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
#GRUB_CMDLINE_LINUX_DEFAULT="quiet rd.driver.blacklist=nouveau mitigations=off"
GRUB_CMDLINE_LINUX_DEFAULT=""
GRUB_CMDLINE_LINUX=""
#GRUB_DEVICE_UUID="bab95b18-9201-499e-b96b-6ab89bfd41e0"
# If your computer has multiple operating systems installed, then you
# probably want to run os-prober. However, if your computer is a host
# for guest OSes installed via LVM or raw disk devices, running
# os-prober can cause damage to those guest OSes as it mounts
# filesystems to look for things.
GRUB_DISABLE_OS_PROBER=false
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"/boot/grub/grub.cfg
https://pastebin.com/raw/XGDbb5mL
root@home:/home/freeartist-devuan# update-grub2
Generating grub configuration file ...
Found background image: splash.png
Found linux image: /boot/vmlinuz-6.1.0-23-amd64
Found initrd image: /boot/initrd.img-6.1.0-23-amd64
Found linux image: /boot/vmlinuz-6.1.0-21-amd64
Found initrd image: /boot/initrd.img-6.1.0-21-amd64
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows 7 on /dev/sda1
Found MS-DOS 5.x/6.x/Win3.1 on /dev/sda6
Found Windows 7 on /dev/sda7
Found Windows 10 on /dev/sdc1
Found Windows 10 on /dev/sdc3
Found Fedora Linux 40 (Xfce) on /dev/sdd1
Found Devuan GNU/Linux 5 (daedalus) on /dev/sde1
Found Artix Linux (rolling) on /dev/sde3
doneroot@home:/home/freeartist-devuan# grub-install -v
grub-install: info: executing modprobe efivars 2>/dev/null.
grub-install: info: Looking for /sys/firmware/efi ...
grub-install: info: ... not found.
grub-install: info: Looking for /proc/device-tree ...
grub-install: info: ... not found.
Installing for i386-pc platform.
grub-install: error: install device isn't specified.
root@home:/home/freeartist-devuan# -=linux its buggy crap that have no antifool protection (c)=- 
*linux is free software, and comes with ABSOLUTELY NO WARRANTY*
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+
Offline
#2 2024-08-14 22:24:51
- GlennW
- Member
- From: Brisbane, Australia
- Registered: 2019-07-18
- Posts: 646
Re: after cloning Devuan Daedulus to SSD grub still use old root UUID(hdd)
Just one glaring observation...
Your grub uuid for / is commented.
/etc/default/grub
#GRUB_DEVICE_UUID="bab95b18-9201-499e-b96b-6ab89bfd41e0"Un-comment (#) that line and run update-grub again.
reboot to check...
maybe the boot system is picking up the old UUID from a vmlinuz file from the old system (hdd)
pic from 1993, new guitar day.
Offline
#3 2024-08-16 01:34:14
- deepforest
- Member
- Registered: 2020-03-24
- Posts: 354
Re: after cloning Devuan Daedulus to SSD grub still use old root UUID(hdd)
thanks for reply.
#GRUB_DEVICE_UUID="bab95b18-9201-499e-b96b-6ab89bfd41e0"
its line i did when try to get it work
hmm i do not know how but its working now. grub now use correct uuid.
may be this cmd help?
tune2fs -U bab95b18-9201-499e-b96b-6ab89bfd41e0 /dev/sdb1
maybe the boot system is picking up the old UUID from a vmlinuz file from the old system (hdd)
maybe, how check it, or update vmlinuz?
Last edited by deepforest (2024-08-16 01:36:12)
-=linux its buggy crap that have no antifool protection (c)=-
*linux is free software, and comes with ABSOLUTELY NO WARRANTY*
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+
Offline
#4 2024-08-16 02:27:45
- GlennW
- Member
- From: Brisbane, Australia
- Registered: 2019-07-18
- Posts: 646
Re: after cloning Devuan Daedulus to SSD grub still use old root UUID(hdd)
To be honest, I don't really know, but looking it up I found a few related articles, like for checking initrd... amongst others.
One hack is to rename the file so it's not found and is re-generated based on the latest successful boot process (live).
The boot process will just take a little bit longer, the virtual machine ram disks were meant to speed up the boot process before todays speed of devices.
The / files maybe links to /boot/ files... be warned!
Burying into the kernel is no longer on my wish list, but you may research some of it here... Duck Duck Go search...
gnu/linux create vmlinuz initrd update-initramfsin particular...
https://dev.to/er_dward/understanding-the-initrd-and-vmlinuz-in-linux-boot-process-534f
https://www.kernel.org/doc/html/latest/admin-guide/initrd.html
https://www.baeldung.com/linux/initrd-vs-initramfsThe only process I have used lately is to rebuild initramfs to include bluetooth device(s) (bt headphones, etcetera) for more complete functions during the boot process, although my system does not rely on bt to boot to a working system.
Deleting the old vmlinuz, initrd.img may be risky... have a good search yourself, and backup by renaming instead of deleting files so you can back-track if you need to. It's outside my scope of knowledge now, although I have dabbled in kernel config modifications and making/installing in the long past.
I hope this gives you something to work with.
pic from 1993, new guitar day.
Offline
#5 2024-08-16 02:29:46
- GlennW
- Member
- From: Brisbane, Australia
- Registered: 2019-07-18
- Posts: 646
Re: after cloning Devuan Daedulus to SSD grub still use old root UUID(hdd)
this is what I have saved in my post-install help file...
# # Load modules at boot
# rsync -avh /home/glenn/local/other/backup/backup-etc-sys/etc/modules /etc/
# chown root:root /etc/modules
# chmod a+rx /etc/modules
# run after changing this file
update-initramfs -u -k all
#Usage: update-initramfs {-c|-d|-u} [-k version] [-v] [-b directory]
#Options:
# -k version Specify kernel version or 'all'
# -c Create a new initramfs
# -u Update an existing initramfs
# -d Remove an existing initramfs
# -b directory Set alternate boot directory
# -v Be verbosepic from 1993, new guitar day.
Offline
#6 2024-08-20 02:01:58
- deepforest
- Member
- Registered: 2020-03-24
- Posts: 354
Re: after cloning Devuan Daedulus to SSD grub still use old root UUID(hdd)
this is what I have saved in my post-install help file...
thanks its very useful
-=linux its buggy crap that have no antifool protection (c)=-
*linux is free software, and comes with ABSOLUTELY NO WARRANTY*
+ALL YOURS ACTIONS at Linux YOU DO at YOUR OWN RISK!+
Offline
