Lerking/rpi-clone
1
0
Fork 0
Code Issues 129 Pull Requests 10 Packages Projects Releases Wiki Activity

RPI CM4 clone from eMMC to NVMe drive fails due to partition naming #144

New Issue
Closed
opened 2022-08-29 09:26:37 +02:00 by tkuehne71 · 2 comments
tkuehne71 commented 2022-08-29 09:26:37 +02:00 (Migrated from github.com)
Copy Link

I have a Raspberry Compute module 4 running Ubuntu server 22.04 LTS from the internal eMMC flash of the CM4. I am trying to clone from the eMMC flash memory of the compute module to an NVMe drive that is attached to the PCIe slot and subsequently boot and run the system from the NVMe drive.

The device is enumerated as "/dev/nvme0n1", and the two partitions would appear as "/dev/nvme0n1p1" and "/dev/nvme0n1p2".

Rpi-clone does not appear to be able to support this naming, since it only wants to add a single digit number for the partitions, i.e. it is trying to name the partition as "/dev/nvme0n11" or "/dev/nvme0n12".

Is it possible to explicitly name the output partitions to support this naming scheme?

Here's what lsblk shows:
mmcblk0 179:0 0 29.1G 0 disk ├─mmcblk0p1 179:1 0 256M 0 part /boot/firmware └─mmcblk0p2 179:2 0 28.9G 0 part / mmcblk0boot0 179:32 0 4M 1 disk mmcblk0boot1 179:64 0 4M 1 disk nvme0n1 259:0 0 119.2G 0 disk ├─nvme0n1p1 259:1 0 256M 0 part └─nvme0n1p2 259:2 0 119G 0 part

Here's the output of the failed run:

rpi-clone /dev/nvme0n1 -v

Target disk nvme0n1 ends with a digit so may be a partition.
rpi-clone requires disk names like 'sda' and not partition names like 'sda1'.

Continue anyway? (yes/no): yes

Booted disk: mmcblk0 31.3GB Destination disk: nvme0n1 128.0GB

Part Size FS Label Part Size FS Label
1 /boot/firmware 256.0M fat32 -- 1 256.0M fat32 --
2 root 28.9G ext4 writable 2 119.0G -- --

== Initialize: IMAGE partition table - FS types conflict ==
1 /boot/firmware (73.0M used) : MKFS SYNC to nvme0n11
2 root (3.7G used) : RESIZE MKFS SYNC to nvme0n12

Run setup script : no.

Verbose mode : yes.
** WARNING ** : All destination disk nvme0n1 data will be overwritten!
-----------------------:

Initialize and clone to the destination disk nvme0n1? (yes/no): yes
Optional destination ext type file system label (16 chars max):

Initializing
Imaging past partition 1 start.
=> dd if=/dev/mmcblk0 of=/dev/nvme0n1 bs=1M count=5 ...
Resizing destination disk last partition ...
Resize success.
Changing destination Disk ID ...
=> mkfs -t vfat -F 32 /dev/nvme0n11 ...
=> mkfs -t ext4 /dev/nvme0n12 ...

Syncing file systems (can take a long time)
Syncing mounted partitions:
Mounting /dev/nvme0n12 on /mnt/clone
mount: /mnt/clone: special device /dev/nvme0n12 does not exist.
Mount failure of /dev/nvme0n12 on /mnt/clone.
Aborting!

I have a Raspberry Compute module 4 running Ubuntu server 22.04 LTS from the internal eMMC flash of the CM4. I am trying to clone from the eMMC flash memory of the compute module to an NVMe drive that is attached to the PCIe slot and subsequently boot and run the system from the NVMe drive. The device is enumerated as "/dev/nvme0n1", and the two partitions would appear as "/dev/nvme0n1p1" and "/dev/nvme0n1p2". Rpi-clone does not appear to be able to support this naming, since it only wants to add a single digit number for the partitions, i.e. it is trying to name the partition as "/dev/nvme0n11" or "/dev/nvme0n12". Is it possible to explicitly name the output partitions to support this naming scheme? Here's what lsblk shows: `mmcblk0 179:0 0 29.1G 0 disk ├─mmcblk0p1 179:1 0 256M 0 part /boot/firmware └─mmcblk0p2 179:2 0 28.9G 0 part / mmcblk0boot0 179:32 0 4M 1 disk mmcblk0boot1 179:64 0 4M 1 disk nvme0n1 259:0 0 119.2G 0 disk ├─nvme0n1p1 259:1 0 256M 0 part └─nvme0n1p2 259:2 0 119G 0 part ` Here's the output of the failed run: > rpi-clone /dev/nvme0n1 -v > > Target disk nvme0n1 ends with a digit so may be a partition. > rpi-clone requires disk names like 'sda' and not partition names like 'sda1'. > > Continue anyway? (yes/no): yes > > Booted disk: mmcblk0 31.3GB Destination disk: nvme0n1 128.0GB > --------------------------------------------------------------------------- > Part Size FS Label Part Size FS Label > 1 /boot/firmware 256.0M fat32 -- 1 256.0M fat32 -- > 2 root 28.9G ext4 writable 2 119.0G -- -- > --------------------------------------------------------------------------- > == Initialize: IMAGE partition table - FS types conflict == > 1 /boot/firmware (73.0M used) : MKFS SYNC to nvme0n11 > 2 root (3.7G used) : RESIZE MKFS SYNC to nvme0n12 > --------------------------------------------------------------------------- > Run setup script : no. > Verbose mode : yes. > -----------------------: > ** WARNING ** : All destination disk nvme0n1 data will be overwritten! > -----------------------: > > Initialize and clone to the destination disk nvme0n1? (yes/no): yes > Optional destination ext type file system label (16 chars max): > > Initializing > Imaging past partition 1 start. > => dd if=/dev/mmcblk0 of=/dev/nvme0n1 bs=1M count=5 ... > Resizing destination disk last partition ... > Resize success. > Changing destination Disk ID ... > => mkfs -t vfat -F 32 /dev/nvme0n11 ... > => mkfs -t ext4 /dev/nvme0n12 ... > > Syncing file systems (can take a long time) > Syncing mounted partitions: > Mounting /dev/nvme0n12 on /mnt/clone > mount: /mnt/clone: special device /dev/nvme0n12 does not exist. > Mount failure of /dev/nvme0n12 on /mnt/clone. > Aborting! >
tkuehne71 commented 2022-08-29 10:28:23 +02:00 (Migrated from github.com)
Copy Link

Duplicate of #123, apologies

Duplicate of #123, apologies
framps commented 2022-08-29 10:58:00 +02:00 (Migrated from github.com)
Copy Link

FYI

raspiBackup recently got support for NVMe on CM4 ;-)

FYI [raspiBackup](https://www.linux-tips-and-tricks.de/en/all-raspibackup-articles/612-support-for-raspberry-compute-module-4-and-nvme/) recently got support for NVMe on CM4 ;-)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
duplicate
enhancement
invalid
question
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Lerking
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Lerking/rpi-clone#144
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?