On 22/10/2019 20:10, druck wrote:
> On 22/10/2019 16:12, Mike Scott wrote:
>> Hi all, I'm stumped with this one.
>>
>> I've got a running raspbian system: the root partition is on the SD
>> card, while everything else is on various partitions on a connected
>> hard drive.
>>
>> The hard drive has a spare partition, sda3, and I've rsync'ed root
>> from the SD card onto that.
>>
>> I've changed cmdline.txt to reflect the moved root partition:
>>
>> original:
>> console=...... root=PARTUUID=6c586e13-02 .....
>> new:
>> console=s.... root=PARTUUID=b9a242b4-1890-4c02-808b-36961834b2f6 ...
>
> Have you also added this to cmdline.txt
>
>      rootwait rootdelay=15
>
> If you haven't it can fault loading the kernel as you've described.
>
> ---druck
>

Thanks for that. No, only rootwait was there. However, I've now tried
your suggestion; same kernel panic though.

cmdline.txt contains
console=serial0,115200 console=tty1
root=PARTUUID=b9a242b4-1890-4c02-808b-36961834b2f6 rootfstype=ext4
rootwait rootdelay=15 elevator=deadline fsck.repair=yes rootwait

same problem if I try root=/dev/sda3.

However, if I use root=UUID=..... (getting the UUID from blkid), the
behaviour changes... it just hangs, the last console messages being
along the lines of
7.5 sda: sda1 sda2 ......
7.5 sda 0:0:0:0 [sda]
21.5 waiting for root device UUID=......
24.8 random: crng init done

Characters typed on the keyboard echo, but nothing else happens.

Rider: should I use the UUID or the PARTUUID in cmdline.txt, or doesn't
it matter?


--
Mike Scott
Harlow, England

--- SoupGate-Win32 v1.05