On 03/12/2018 06.00, George from the tribe wrote:
On 12/2/18 8:21 AM, Felix Miata wrote:
Carlos E. R. composed on 2018-12-02 14:56 (UTC+0100):
So, again, look *inside* your initrd file and find that UUID. Then find out who/what writes it.
The initrd file is just a (compressed?) cpio archive. You can open it with mc by changing the extension temporarily to cpio.
Or use the lsinitrd command (since 10 years ago[1]) with less or grep.
I don't seem to be able to find that uuid, or in fact any uuid in the initrd file: tribetrekDellbig:/boot # lsinitrd | grep disk tribetrekDellbig:/boot # lsinitrd | grep d3224 tribetrekDellbig:/boot # lsinitrd | grep fd2 tribetrekDellbig:/boot # lsinitrd | grep uuid -rwxr-xr-x 1 root root 30840 Nov 14 07:48 usr/lib64/libuuid.so.1.3.0 lrwxrwxrwx 1 root root 16 Dec 1 03:30 usr/lib64/libuuid.so.1 -> libuuid.so.1.3.0
Is there another way to read the initrd file?
It is not a file, it is an archive. And I told you: 'mc'. With "lsinitrd" it would be something like: lsinitrd -f * | grep 3224276-2d28fa but it does not work for me, I get xzcat: 20021107.1530.ethereal: File format not recognized Instead, you can do: md test cd test /usr/lib/dracut/skipcpio /boot/initrd-VERSION | xz -cd | cpio -idv which will create a tree of files. Then, I insist that you use 'mc' to find what file contains the string 3224276-2d28fa. Or grep: Telcontar:~/testing # grep -ril ac173013 etc/cmdline.d/95root-dev.conf Telcontar:~/testing # Telcontar:~/testing # cat ./etc/cmdline.d/95root-dev.conf root=UUID=ac173013-18ad-4c4e-921e-fd2ecfb56495 rootfstype=ext4 rootflags=rw,relatime,lazytime,data=ordered You can try "grep", but be warned that I failed: Note: it took me about an hour to find out all this, and I tested the procedure on my computer. So please, do it! -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)