[SOLVED] Slackware 15 - NVME clone to external NVME

Klaus150 · 10-13-2022, 01:22 AM

Hi,
I run Slackware 15 on an internal NVMe without any problem. To have a second "Backup", I have cloned with Clonezilla the internal NVMe to an external NVMe, connected to the laptop on the GEN2-Usb. Cloning runs without problems.
I also changed the FSTAB of the external NVMe to the right UUIDs.
By boot over EFI, i can choose the external NVMe, but always boot into the internal NVMe.
Any idea what I can do?
Thanks a lot.
Regards,
Klaus

mrmazda · 10-13-2022, 01:50 AM

Show us output from efibootmgr -v and lsblk -f run while the external is attached.

Klaus150 · 10-13-2022, 02:10 AM

Code:

NAME        FSTYPE FSVER LABEL    UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
sda                                                                                   
├─sda1      vfat   FAT32          4824-3095                                           
├─sda2                                                                                
├─sda3      ntfs                  38F825A6F825637C                                    
└─sda4      ntfs                  6EB0989EB0986DF9                                    
sdb                                                                                   
├─sdb2      vfat   FAT32          FE6E-941A                                           
├─sdb3      ext4   1.0            8836a4a7-105b-4b77-b934-9696a8f4bc73                
└─sdb4      swap   1              839a05d6-b6f6-4a65-a201-b8096155665c                
mmcblk0                                                                               
└─mmcblk0p1 ntfs         SD256GB  7FE61F9436AFF054                                    
nvme0n1                                                                               
├─nvme0n1p1 vfat   FAT32 NO_LABEL 9F80-F609                                           
└─nvme0n1p2 ext4   1.0            780537c0-44c1-4fd5-a095-9142ee9dd714                
nvme1n1                                                                               
├─nvme1n1p2 vfat   FAT32          FE6E-941A                             478,6M     4% /boot/efi
├─nvme1n1p3 ext4   1.0            8836a4a7-105b-4b77-b934-9696a8f4bc73    484G    42% /
└─nvme1n1p4 swap   1              839a05d6-b6f6-4a65-a201-b8096155665c                [SWAP]

Code:

BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0000,0001,0003,2001,2002,2003
Boot0000* EFI Hard Drive (Samsung SSD 970 EVO Plus 1TB)	PciRoot(0x0)/Pci(0x1b,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-56-11-51-8C-20)/HD(1,GPT,bc2b0b5f-28b7-7c48-bca3-6c23595dfda3,0x1000,0x96000)RC
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 1b / 01 01 06 00 00 00 / 03 17 10 00 01 00 00 00 00 25 38 56 11 51 8c 20 / 04 01 2a 00 01 00 00 00 00 10 00 00 00 00 00 00 00 60 09 00 00 00 00 00 5f 0b 2b bc b7 28 48 7c bc a3 6c 23 59 5d fd a3 02 02 / 7f ff 04 00
    data: 52 43
Boot0001  EFI Hard Drive 1 (Samsung SSD 970 EVO Plus 1TB)	PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-25-38-5B-11-50-35-5A)/HD(2,GPT,fb4091c7-a0e2-4f16-9391-38bb4e4d62d9,0xfa800,0xfa000)RC
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 1d / 01 01 06 00 00 00 / 03 17 10 00 01 00 00 00 00 25 38 5b 11 50 35 5a / 04 01 2a 00 02 00 00 00 00 a8 0f 00 00 00 00 00 00 a0 0f 00 00 00 00 00 c7 91 40 fb e2 a0 16 4f 93 91 38 bb 4e 4d 62 d9 02 02 / 7f ff 04 00
    data: 52 43
Boot0002* EFI USB Device (SSK)	PciRoot(0x0)/Pci(0x14,0x0)/USB(18,0)/HD(2,GPT,fb4091c7-a0e2-4f16-9391-38bb4e4d62d9,0xfa800,0xfa000)RC
      dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 03 05 06 00 12 00 / 04 01 2a 00 02 00 00 00 00 a8 0f 00 00 00 00 00 00 a0 0f 00 00 00 00 00 c7 91 40 fb e2 a0 16 4f 93 91 38 bb 4e 4d 62 d9 02 02 / 7f ff 04 00
    data: 52 43
Boot0003  Windows Boot Manager	HD(1,GPT,b0fb1e0a-05d1-4d1f-b001-c7f2754d7ee1,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...d................
      dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 0a 1e fb b0 d1 05 1f 4d b0 01 c7 f2 75 4d 7e e1 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
    data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 64 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot2001* EFI USB Device	RC
      dp: 7f ff 04 00
    data: 52 43
Boot2002* EFI DVD/CDROM	RC
      dp: 7f ff 04 00
    data: 52 43
Boot2003* EFI Network	RC
      dp: 7f ff 04 00
    data: 52 43

The external NVMe is EFI USB Device (SSK)

.

Klaus150 · 10-13-2022, 02:32 AM

I just noticed, that the internal NVMe have the same UUIDs as the external USB-NVMe (for ESP / SWAP and Root).
Should I change the UUIDs with tune2fs ?

Didier Spaier · 10-13-2022, 03:17 AM

Quote:

Originally Posted by Klaus150

I just noticed, that the internal NVMe have the same UUIDs as the external USB-NVMe (for ESP / SWAP and Root).
Should I change the UUIDs with tune2fs ?

Yes, or name the partitions by label.

Klaus150 · 10-13-2022, 06:17 AM

I have changed in the clone of the FSTAB-file the original INTERNAL NVMe against the /DEV/SDBx (as per LSBLK).
I can boot from the external NVMe (shown also by EFIBOOTMGR), but it load everything directly from the internal NVMe. IT means, there are some links to the Internal NVMe.
Any Idea?

elcore · 10-13-2022, 06:58 AM

Quote:

Originally Posted by Klaus150

I have changed in the clone of the FSTAB-file the original INTERNAL NVMe against the /DEV/SDBx (as per LSBLK).
I can boot from the external NVMe (shown also by EFIBOOTMGR), but it load everything directly from the internal NVMe. IT means, there are some links to the Internal NVMe.
Any Idea?

Use labels in fstab, or if you insist on using names like 'sd*' make sure the kernel doesn't change the names dynamically.
It does that when usb_storage is compiled in, so where sda was initially SATA it may sometimes become USB ..
I'm assuming when nvme is compiled in, the kernel also dynamically names it nvme0/nvme1 depending on how it's wired and what is set in bios.
So yeah, I guess use labels or uuid in fstab.

mrmazda · 10-13-2022, 07:19 AM

Quote:

Originally Posted by Klaus150

I just noticed, that the internal NVMe have the same UUIDs as the external USB-NVMe (for ESP / SWAP and Root).
Should I change the UUIDs with tune2fs ?

All UUIDs on a clone need to be changed, lest you risk corruption you may not notice until something inexplicably crashes sometime in the future.

Please edit your post #3 to contain what you posted within code tags. Always paste command input/output within code tags to preserve the readability of the original output.

Klaus150 · 10-13-2022, 09:04 AM

Should be OK now.

keefaz · 10-13-2022, 09:15 AM

Quote:

Originally Posted by Klaus150

Edit over NC.

CODE markup is not closed at the end, add a slash: [/CODE]

colorpurple21859 · 10-13-2022, 09:17 AM

post the output of

Code:

lsblk -o NAME,FSTYPE,UUID,PARTUUID,FSAVAIL,FSUSE%,MOUNTPOINT

Klaus150 · 10-13-2022, 09:23 AM

lsblk -o NAME,FSTYPE,UUID,PARTUUID,FSAVAIL,FSUSE%,MOUNTPOINT

Code:

NAME FSTYPE UUID                                 PARTUUID                             FSAVAIL FSUSE% MOUNTPOINT
sda                                                                                                  
├─sda1
│    vfat   4824-3095                            b0fb1e0a-05d1-4d1f-b001-c7f2754d7ee1                
├─sda2
│                                                a31227e1-0fe7-4ba1-8b07-e87267ce0e6e                
├─sda3
│    ntfs   38F825A6F825637C                     98b2d9e4-d10d-48a1-99d7-e0223d2bfbf8                
└─sda4
     ntfs   6EB0989EB0986DF9                     ae612cb8-e0a3-45a8-806d-23175e3ea05e                
sdb                                                                                                  
├─sdb2
│    vfat   FE6E-941A                            fb4091c7-a0e2-4f16-9391-38bb4e4d62d9                
├─sdb3
│    ext4   8836a4a7-105b-4b77-b934-9696a8f4bc73 59bb120b-9a4c-466b-a1e9-7eb75ae8b23f                
└─sdb4
     swap   839a05d6-b6f6-4a65-a201-b8096155665c 9279f267-eff3-4101-b821-cdb94f6c953b                
mmcblk0
│                                                                                                    
└─mmcblk0p1
     ntfs   7FE61F9436AFF054                     f9bdb882-01                                         
nvme0n1
│                                                                                                    
├─nvme0n1p1
│    vfat   9F80-F609                            bc2b0b5f-28b7-7c48-bca3-6c23595dfda3                
└─nvme0n1p2
     ext4   780537c0-44c1-4fd5-a095-9142ee9dd714 8460e172-99b6-5e46-8427-1b32d3fa8188                
nvme1n1
│                                                                                                    
├─nvme1n1p2
│    vfat   FE6E-941A                            fb4091c7-a0e2-4f16-9391-38bb4e4d62d9  478,6M     4% /boot/efi
├─nvme1n1p3
│    ext4   8836a4a7-105b-4b77-b934-9696a8f4bc73 59bb120b-9a4c-466b-a1e9-7eb75ae8b23f    484G    42% /
└─nvme1n1p4
     swap   839a05d6-b6f6-4a65-a201-b8096155665c 9279f267-eff3-4101-b821-cdb94f6c953b                [SWAP]

Didier Spaier · 10-13-2022, 09:55 AM

As others have pointed out each fileystem should have its own UUID (file system UUID) and each partition its own PARTUUID (Partition UUID). The second U in UUID stands for unique.

Klaus150 · 10-13-2022, 10:14 AM

I have changed the UUID of the ROOT-partition.
I can also delete the SWAP-partition to get a new UUID for it. No Poblem.
My problem is how to change the UUID of the EFI (which is VFAT)-Partition.
Maybe some hints. Thanks.

elcore · 10-13-2022, 10:26 AM

Quote:

Originally Posted by Klaus150

I have changed the UUID of the ROOT-partition.

The real mess is that a certain boot loader sometimes decides where the root is by reading uuid.
If you have such a boot loader, which you neglected to mention, it may boot from nvme1 and set sdb3 as root because sdb3 has the same uuid.
And I don't understand the benefit of multiple vfat partitions for EFI, don't you need just one per machine?