On 7/30/24 2:45 PM, Patrick O'Callaghan wrote:
On Tue, 2024-07-30 at 14:13 -0700, Samuel Sieb wrote:
A logical place to look is in /etc/dracut.d. The manpage for
dracut.cmdline says you can specify a "root=UUID=..." parameter,
but
not where you put it ('dracut root=...' and 'dracut --root=...'
both
fail). The manpage for dracut.conf has no mention of a root
parameter,
and the contents of /etc/default/cmdline come in part from the
files in
/etc/dracut.d (that's where my 'resume' parameter comes from).
It's certainly not going to come from dracut. I don't even have an
/etc/default/cmdline.
I think I have that because there's a resume.conf in /etc/dracut.d.
It might be getting it from the kernel command line. Try editing the
loader entry, boot it, then run mkconfig again.
Tried that and this time it did get the correct UUID in the boot
command line (verified from the grub menu). However the boot failed
with some 'not found' errors. I can't completely discount the
possibility of some errors in copying the original root to the new
drive, unlikely though that is. Or maybe there's some other config file
that needs editing.
Remember that any config files you're editing (other than things in
/boot) are on the wrong root file system. If you haven't modified the
fstab on the new drive, it's going to have some trouble booting.
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
