1 |
On Sat, Feb 16, 2019 at 8:48 PM Bill Kenworthy <billk@×××××××××.au> wrote: |
2 |
> |
3 |
> I have cloned a gentoo image for a raspberry pi to another sdcard. |
4 |
> It fails to boot because the storage uuid's have changed and dracut has |
5 |
> the previous uuid's stored internally. Is there a way around this |
6 |
> without changing the new storage's uuids back to match the original (its |
7 |
> bad practise to duplicate uuids) or using an original rpi kerneal and |
8 |
> rebuild the custom one? |
9 |
|
10 |
Are you passing root=UUID=xyz on the command line? Also, do you have |
11 |
the correct UUID in /etc/fstab? |
12 |
|
13 |
Dracut does save a snapshot of fstab internally, but I think it should |
14 |
work if passed the UUID on the command line. You do want the real |
15 |
/etc/fstab to have the correct UUID, because after dracut mounts root |
16 |
it checks fstab and remounts root with any options in case its |
17 |
internal copy is stale. If the fstab on the hard drive is incorrect |
18 |
that could lead it astray. |
19 |
|
20 |
If it isn't breaking to a shell you can force it to with a command |
21 |
line option, and then from there just mount root yourself on /sysroot, |
22 |
and exit the shell, and then it should boot. Another option is to |
23 |
just use it as a rescue image and just mount root on /sysroot and then |
24 |
just chroot into it, and now you're basically at a semi-working |
25 |
system. You could easily rebuild dracut from there. Or you can just |
26 |
boot from a rescue disk and regenerate dracut. |
27 |
|
28 |
But, I suspect just editing your command line in grub will do the |
29 |
trick if /etc/fstab on the hard drive is good. |
30 |
|
31 |
-- |
32 |
Rich |