On 23/10/2019 11:44, Chris Elvidge wrote:
> On 22/10/2019 16:12, Mike Scott wrote:
>> Hi all, I'm stumped with this one.
>>
....
> Try redoing your rsync from /dev/mmcblk0p2 (root partition) to /dev/sda3
> (new root partition) with -avx (x = don't cross filesystem boundaries;
> this will ignore things like /boot, /proc, /dev)
> I.e mount /dev/sda3 on (e.g.) /mnt
> Then "rsync -avx / /mnt/" (as root)
>
> My cmdline.txt now looks like (note this is all one line and I use btrfs
> on the new root partition):
> # cat /boot/cmdline.txt
> dwc_otg.lpm_enable=0 console=serial0,115200 console=tty1
> root=PARTUUID=5cf6b9c2-9894-cd47-933e-ad3840ae4e5c rootfstype=btrfs
> elevator=deadline fsck.repair=yes rootwait quiet splash
> plymouth.ignore-serial-consoles net.ifnames=0 biosdevname=0
> usbhid.mousepoll=0
>
> Don't change the original /etc/fstab file (the one on /dev/mmcblk0p2).
>
> This is on a RPi3+, boot on /dev/mmcblk0p1, root on /dev/sda2
>

Hi; thanks for your patience.

I've redone the rsync (nothing interesting changed), changed cmdline.txt
on the card (with rootwait and rootdelay=15), and edited fstab (on the
new HD partition). Still the same kernel panic. It looks increasingly as
though although the HD is detected correctly, there's a problem reading
it at that point.

Looks like I'll have to sacrifice another system's backup disk to get a
spare usb drive to try in place of this one. Tedious :-{



--
Mike Scott
Harlow, England

--- SoupGate-Win32 v1.05