INTL 3:770/1 3:770/3   
   REPLYADDR tnp@invalid.invalid   
   REPLYTO 3:770/3.0 UUCP   
   MSGID:  39006c18   
   REPLY:  0e6250f0   
   PID: SoupGate-Win32 v1.05   
   On 01/08/2024 12:31, Jesper wrote:   
   > Then the system to copy is on the 2 last lines. Correct?   
   >   
   No.   
      
   In order to preserve the partition information *you must dd the raw disk*   
      
   dd id=/dev/sda od = /dev/nvme0n1 (or whatever)   
      
   That will create a two partition disk with the UUIDS of the partitions   
   the same as is mentioned in the boot data: If they don't match it wont boot.   
      
   Viz:   
      
      
   df -h | grep ^/dev/   
   /dev/root        15G  1.5G   13G  11% /   
   /dev/mmcblk0p1  255M   51M  205M  20% /boot   
      
   These are the TWO partitions on a bootable PI device   
   In /boot which is DOS style formatted will be instructions on how to   
   boot the main system   
      
   In the main bootable system there will be the fstab file which needs to   
   tally with the partition ids.   
      
   more /etc/fstab:   
      
   proc            /proc           proc    defaults          0       0   
   PARTUUID=b8c9fbb7-01  /boot           vfat    defaults          0       2   
   PARTUUID=b8c9fbb7-02  /               ext4    defaults,noatime  0       1   
      
   In the BOOT partition is this file   
     more *.txt   
   ::::::::::::::   
   cmdline.txt   
   ::::::::::::::   
   console=serial0,115200 console=tty1 root=PARTUUID=b8c9fbb7-02   
   rootfstype=ext4 fs   
   ck.repair=yes rootwait modules-load=dwc2,g_ether   
      
   Unless the bootloader finds that partition ID, it will *not load Linux*   
      
   AIUI the boot sequence is this:   
      
   Look for a DOS style VFAT partition on SD card, then USB, then NVME.   
      
   Look for a file named 'cmdline.txt' parse the root partition ID  and   
   attempt to load a linux image from the boot  partition and have the   
   kernel image mount the aforementioned PARTUUID as root partition.   
      
   If the PARTUUIDs don't match, the boot sequence hangs   
      
   So it is important to have the same PARTUUID in /boot/cmdline.txt, and   
   in /etc/fstab, and in the partition label on the boot partition   
      
   The easy way to do this is not to clone the partitions, but the RAW DISK   
      
      
   > And following drucks first suggestion I should run these 2 commands:   
   > 1: dd if=/dev/sda2 of=/dev/nvme0n1 bs=1M status=progress   
   > and   
   > 2: dd if=/dev/sda1 of=/dev/nvme0n1 bs=1M status=progress   
   >   
   > replacing the name of the NVME to what I see when it is installed on the   
   > raspi.   
   >   
   > Best regards, and thank you for the help.   
      
   That wont work, but you wont destroy anything by trying.   
      
      
   --   
   Outside of a dog, a book is a man's best friend. Inside of a dog it's   
   too dark to read.   
      
   Groucho Marx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: Agency HUB, Dunedin - New Zealand | Fido<>Usenet Gateway (3:770/3)   
   SEEN-BY: 90/1 105/81 106/201 129/305 153/757 7715 218/700 840 220/70   
   SEEN-BY: 221/1 6 242 360 226/17 30 100 227/114 229/110 111 114 200   
   SEEN-BY: 229/206 300 317 400 426 428 470 550 616 664 700 230/0 266/512   
   SEEN-BY: 267/800 280/5003 282/1038 291/111 292/854 2226 8125 301/1   
   SEEN-BY: 310/31 320/219 322/757 335/364 341/66 342/200 396/45 410/9   
   SEEN-BY: 423/81 460/58 633/280 712/848 770/1 3 100 330 340 772/210   
   SEEN-BY: 772/220 230 5020/400 5058/104 5075/35   
   PATH: 770/3 1 218/840 221/6 1 292/854 229/426