Clonezilla Live is unable to see second nvme Drive
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
Hello Folks,
I am unable to see the drive that I'm trying to clone to--which is a 4TB
WD_BLACK SN850X NVMe SSD card. It was originally being mounted on startup,
I have since unmounted it. I am trying to clone my 1TB Samsung SSD to the
aforementioned drive. When I boot up Clonezilla Live and start the process
for a disk-to-disk cloning, I only see the 1TB Samsung SSD drive and not
the 4TB drive.
If there's anything you need me to see like the output of commands,
feel free to let me know.
Thank you,
Gregory
Please give the latest Clonezilla live a try, e.g., 3.1.2-22 or 20240408-noble:
https://clonezilla.org//downloads.php
It comes with Linux kernel 6.7 or 6.8, and might support your hardware better.
Steven
Will do. I'm using 20240408-noble, I'm currently on Pop!OS (Ubuntu 22.04 LTS). I'll follow-up on if this newer version works compared to what I've used previously.
I tried running through he steps as listed in "Disk to disk clone : Clone small disk to larger disk (e.g. 20 GB to 60 GB) (Step by step)" and I wasn't able to see the drive that I have mounted as
nvme1n1when I boot into Pop!OS I can only see the drive that is mounted asnvme0n1. Whe I load Clonezilla to RAM I see my 1TB drive and the 16GB USB, still not able to see the 4TB drive that I'm looking to clone to.I did find it a bit odd that the output of name of the drive in Clonezilla was different from the output of
lsblk. The 1TB drive (my current bootable drive) is namednvme0n1and it is being read by clonezilla asnvme1n1.Here's the output of when I boot into Pop!OS:
Last edit: Gregory Power 2024-04-20
Please boot Clonezilla live 20240408-noble, enter command line prompt, then run:
1. sudo -i
2. cat /proc/partitions
3. mount
4. df -h
Please post the results of 2-4. Thanks.
Steven
2 . cat /proc/partitions
3 . mount
Apologies for how messy this one is.
4 . df -h
Last edit: Gregory Power 2024-04-21
This is interesting. Since your source or destination disk is not mounted, it should be shown in the TUI.
Anyhow, I suggest you backup important data first, then use command to do that. Forget about TUI.
The command is like the green command here:
https://clonezilla.org//clonezilla-live/doc/03_Disk_to_disk_clone/images/ocs-08-3-command-to-run.png
i.e., something like:
sudo ocs-onthefly -g auto -e1 auto -e2 -r -j2 -sfsck -k0 -p choose -f YOUR_SOURCE_DISK -d YOUR_DEST_DISK
You have to be very careful about assigning the correct source disk and destination disk. If you give the wrong devices, then there is almost no chance to recover the data.
Good luck.
Steven
So I suppose the recommended command for my usecase would be the following? I want to make sure I get these targets right because it seems like when I boot clonezilla, my 1TB drive is nvme1n1 in the TUI, even though the output of
cat /proc/partitionslists my drives correctly.If your source disk have 4 partitions, and its size is around 1 TB, yes, from the photo you booted into Clonezilla live (noble), I can tell it it nvme0n1.
The destination without any partition, and its size is 3.6 TB, is nvme1n1.
Steven
Thanks for the clarification, I'll be sure to let you know how it goes. Your help is very much appreciated! Any way I can donate to the repo/org Clonezilla is affiliated with?
No dice, unfortunately it wasn't able to complete the process.
Interesting.
Please run the commands in Clonezilla live (noble):
1. sudo -i
2. blkid /dev/nvme0n1
3. blkid /dev/nvme1n1
Please show the results of 2 & 3.
Steven
Here you go:
Could have the error been to me using
nvme0n1instead of/dev/nvme0n1as my file source andnvme1n1instead of/dev/nvme1n1as my file destination?Last edit: Gregory Power 2024-04-21
So your /dev/nvme1n1 has a file system without any partition? If so, it will be treated as a partition in Clonezilla. That's why.
If you are sure the data on it can be wiped, please run:
sudo wipefs -f /dev/nvme1n1
Then back to Clonezilla TUI by running "sudo clonezilla", and everything should be normal.
In the future, I think we should wipe all the partition layout and file system of destination disk in Clonezilla.
BTW, either /dev/nvme0n1 or nvme0n1 can be accepted by ocs-onthefly.
Steven
I do have a filesystem and I thought it was a single partition. I'm fine with everything on the 4TB drive being wiped, I'll be sure to follow up.
Last edit: Gregory Power 2024-04-22
From here:
https://sourceforge.net/p/clonezilla/discussion/Help/thread/86224024c7/?limit=25#0fa4
There is one disk /dev/nvme1n1, but no /dev/nvme1n1p1. It means your disk /dev/nvme1n1 has no partition. Your ext4 file system is directly on the block disk /dev/nvme1n1.
Otherwise, I am confused...
Steven
Okay, I'm tracking. I'm the one who is confused here. I didn't realize you could have a file system without it being within a partition.
Okay, I'm tracking. I'm the one who is confused here. I didn't realize you could have a file system without it being within a partition.
Even though the files were wiped, I ended up having to use
gpartedand formatting the drive as 'cleared' so it would be visible to Clonezilla. I was able to use the TUI when I did that.OK, so your issue is solved?
Steven
Yes, my issue is resolved.
TLDR:
All we had to do was wipe the disk, use gparted to format the disk to "cleared", and I was able to successfully clone all of my files and partitions.
I understand your issue is resolved. I've had been having an issue that presented the same but was a different solution. One poster replied about changing the mode to AHCI. That solution was close..but it did not solve my problem. It was however close.Apparently the system is defaults the SATA mode to "RST with Optane"(despite no optane present). Also not leaving a menu option to change this. BUT apparently a thread somewhere said by tabing to the "Main" section and pressing ctrl+s the option appears and can be changed to AHCI. This solved my issue. Figured I would post this here to consolodate some Behavior-->Solutions into one thread.