Linux Mint 21.02 - Clone & Replace 1TB NVMe with a 2TB NVMe - Page 1
Forum section: electronics / general

author: bingo600
author_rank: Super Contributor
timestamp: August 06, 2023, 11:58:33 am
content: Intro:-----------How2 Clone a 1TB NVMe ssd to a 2TB NVMe ssd with CloneZilla Live - USB Boot.I used : clonezilla-live-3.1.0-22-amd64OSLinux Mint 21.02BootSecure BootHDD Partition tableGPTHardware used:Lenovo Thinkpad w. a 1TB 980 NVMe disk installedOriginal 1TB NVMeSamsung 980 1TB PCIe 3.0 (up to 3,500 MB/s) NVMe M.2 Internal Solid State Drive (SSD) (MZ-V8V1T0BW)https://www.amazon.de/dp/B08TJ2649W/New 2TB NVMeSamsung 980 PRO 2 TB PCIe 4.0 (up to 7,000 MB/s) NVMe M.2 (2280) Internal Solid State Drive (SSD) (MZ-V8P2T0BW)https://www.amazon.de/dp/B08QJHLC8J/Orico NVMe (10GB) - USB Adapterhttps://www.amazon.de/dp/B0B4S5QZBN/16GB USB Stick for Clonezilla.How to Clone fast and easy with Clonezilla.--------------------------------------------As usual i ran out of space on my Lenovo laptop ....So i bougt a new 2TB NVMe disk, this time a "2TB 980 PRO" ...I'm not sure if my laptop can utilize the faster PCIe-4 xfer , but it can utilize the better TBW.But howto Clone a NVMe on a laptop w. only one NVMe slot ??I had a look around, and found some USB NVMe adapters on eBay & Ali, but i had no idea about the performance, and didn't want to wait 3..4 weeks.Then i found the Orico's on Amazon (de)Fair price, and apparently nice performance.So i bougt a Dual NVMe/Sata - Note the only "dual" is the chassis, each adapter has it's own USB Cable.Orico Dual NVMe (10GB) & Sata - USB Adapterhttps://www.amazon.de/dp/B0B4RZ4Y5V/And i also bought the "single" NVMe USB Adapter. I could use that as a "Fast" NVMe External SSD.For cloning i used the "single slot" 10GB USB Adapter.1: Determine if my setup uses MBR(msdos) or gpt partitioning--------------------------------------------------------------$ sudo fdisk -l /dev/nvme0n1Disk /dev/nvme0n1: 931,51 GiB, 1000204886016 bytes, 1953525168 sectorsDisk model: Samsung SSD 980 1TBUnits: sectors of 1 * 512 = 512 bytesSector size (logical/physical): 512 bytes / 512 bytesI/O size (minimum/optimal): 16384 bytes / 131072 bytesDisklabel type: gptDisk identifier: xxxxxxx2: Download Conezilla--------------------------I downloaded Clonezilla (clonezilla-live-3.1.0-22-amd64) , in both zip and ISO formats.https://clonezilla.org/downloads.phpNote: Only the 64-bit verion supports Secureboot3:Create Clonezilla USB Boot stick (Non working)-----------------------------------------------Format USB Stick - Fat32.I tried their recipe for creating a bootable USB Stick from the zip file (just copy files from zip to USB Stick) , but ended up with it getting stuck at boot (twice).https://clonezilla.org/liveusb.php#linux-setupHmmm ... Try the ISO ...4:Create Clonezilla USB Boot stick (working)-----------------------------------------------I used etcher to "burn" the ISO to the USB Stick.5: Mount new 2TB NVMe in Orico "single" NVMe USB Adapter.-----------------------------------------------------------Mounting MVMe was not that bad to do .... Even though i had some challenges fitting the "rubber screw/thingy" at the end of the NVMe disk for "fixture".I decided NOT to remove the plastic on the "Cooling pad side" that connected towards the NVMe, as i had to remove the 2TB NVMe disk after copying.But i was glad that i did mount the Cooling pad. After copying 900GB of data it got "quite hot".Connect the NVME (syslog) - Orico seems to use a Realtek RTL9210 USB --> NVMe chip.I used the TP's USBC plug - It's USB3.? - Actually don't know if it's USB 3.1 or 3.2 ... Prob. 3.1Aug 6 12:40:26 TP1 kernel: [ 4198.067445] usb 2-1: new SuperSpeed Plus Gen 2x1 USB device number 6 using xhci_hcdAug 6 12:40:26 TP1 kernel: [ 4198.094581] usb 2-1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01Aug 6 12:40:26 TP1 kernel: [ 4198.094587] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3Aug 6 12:40:26 TP1 kernel: [ 4198.094589] usb 2-1: Product: RTL9210Aug 6 12:40:26 TP1 kernel: [ 4198.094591] usb 2-1: Manufacturer: RealtekAug 6 12:40:26 TP1 kernel: [ 4198.094592] usb 2-1: SerialNumber: xxxxxxxxxxxxxxxxxxAug 6 12:40:26 TP1 kernel: [ 4198.097281] usb 2-1: Enable of device-initiated U1 failed.Aug 6 12:40:26 TP1 kernel: [ 4198.098340] usb 2-1: Enable of device-initiated U2 failed.Aug 6 12:40:26 TP1 kernel: [ 4198.115803] usb 2-1: Enable of device-initiated U1 failed.Aug 6 12:40:26 TP1 kernel: [ 4198.116903] usb 2-1: Enable of device-initiated U2 failed.Aug 6 12:40:26 TP1 kernel: [ 4198.119442] scsi host0: uasAug 6 12:40:26 TP1 mtp-probe: checking bus 2, device 6: "/sys/devices/pci0000:00/0000:00:14.0/usb2/2-1"Aug 6 12:40:26 TP1 kernel: [ 4198.123171] scsi 0:0:0:0: Direct-Access Realtek RTL9210 NVME 1.00 PQ: 0 ANSI: 66: Boot (from) Clonezilla USB Stick-------------------------------------Shutdown TP, Insert USB Stick, Turn on TP.Press F12 to select Boot menu - In Boot menu boot from USB HDDNote: I never saw the GUI, As CZ seemed to decide to boot in text "Blue screen" mode.. (Not an issue)7: Load Clonezilla---------------------I chose : Clonezilla live (VGA 800x600 & To RAMD) (cz1.png) , where it copies the USB Boot disk to Ramdisk , allwing you to remove the USB Stick after the copy ... (I didn't remove the stick)Not it takes a bit of time, where CZ shows it's copying it self to the RamDiskSet Clonezilla Codepage (cz2.png) + Kbd (cz3.png)Start Clonezilla (cz4.png)

author: bingo600
author_rank: Super Contributor
timestamp: August 06, 2023, 11:59:39 am
content: 8: Setup Clonezilla Disk Clone (Beginner mode)-------------------------------------------------I wanted to Clone my internal 1TB NVMe directly to the USB attached 2TB NVMeI Selected :Code:Operating mode : device - device (cz5.png)Run mode : Beginner (cz6.png)Clone mode : Disk to Local disk Clone (cz7.png)Partition : Clone the originalSource disk : Select Internal NVMe (cz8.png)Dest disk : Select USB NVMe (Realtek Realtek RTL9210 attached) (cz9.png)Check Source : Trusk Source disk .. Skip FSCK (cz10.png)Dest partition : -k0 - Use partition table from source disk (cz11.png) - I'll extend my /home partition later on with gparted.Now CZ will ask if you are sure about the Source & Desk disks (twice)Answer the appropriate ....CZ will start to work , gather info and clone the individual partitions.That Orico is FAST on my USB Gen 3.?? USBC plug (cz-speed.png)On my machine it took about 15..18min to clone approx. 900TB to the new 2TB disk.When done (cz-done.png) - REMEMBER to select powerdown.CZ mentions the OS could be confused if/when you boot with two disks with the same ID.Now i opened the TP, and mounted the new 2TB NVMe in there.My Linux mint booted up right away, no secureboot issues or anything at allA BIG THANK YOU to the Clonezilla Team from me.Now all i had to do was fire up gparted:Select my /home partition (that i had placed as the last partition), select Resize, and pull the "slider" all the way to the end.Apply the change (took a few seconds), and i now have a 1.78TB /home partition.Hopefully it would last a while,before i run out of diskspace .... :-)Edit:The observant reader will notice , that the last clonezilla images w source + dest selection was made w. a 512G NVMe in the USB adapter ...I forgot to take picts of the 2TB cloning, and just used the 512G i had installed in the USB NVMe adapter, after cloning the 2TB./Bingo

author: Marco
author_rank: Super Contributor
timestamp: August 06, 2023, 02:46:06 pm
content: Worked great for me, once I reformated the old drive. The OS doesn't like two drives with the same UUID.

author: bingo600
author_rank: Super Contributor
timestamp: August 06, 2023, 03:32:01 pm
content: YeppCZ even informs about that, in the final messages.Where they recommend you to power down, and remove one of the two cloned disks , before boot./Bingo

author: bingo600
author_rank: Super Contributor
timestamp: August 07, 2023, 06:28:10 am
content: Hmm ....Seems like Amazon (de) , just increased the Orico prices a bit.I paid 21€ for the single , and €38 for the dualWell you can apply for a 10% rebate (Voucher)/Bingo

author: bingo600
author_rank: Super Contributor
timestamp: August 20, 2023, 06:06:31 pm
content: Had an issue with my new NVME , where my linux just "stopped/crashed" and only power off was working.It became more and more frequentNoticed a lot of these in the kernel logCode:Aug 20 16:02:38 Laptop kernel: [56912.524953] nvme 0000:07:00.0: device [144d:a80a] error status/mask=00000001/0000e000Aug 20 16:02:38 Laptop kernel: [56912.524957] nvme 0000:07:00.0: [ 0] RxErrAug 20 16:02:38 Laptop kernel: [56912.524960] nvme 0000:07:00.0: AER: Error of this Agent is reported firstAug 20 16:02:18 Laptop kernel: [56893.050368] nvme 0000:07:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)Aug 20 16:02:18 Laptop kernel: [56893.050369] nvme 0000:07:00.0: device [144d:a80a] error status/mask=00000001/0000e000Aug 20 16:02:18 Laptop kernel: [56893.050371] nvme 0000:07:00.0: [ 0] RxErrAug 20 16:02:18 Laptop kernel: [56893.050372] nvme 0000:07:00.0: AER: Error of this Agent is reported firstAug 20 16:02:38 Laptop kernel: [56912.524922] pcieport 0000:00:1d.4: AER: Multiple Corrected error received: 0000:07:00.0Aug 20 16:02:38 Laptop kernel: [56912.524936] pcieport 0000:00:1d.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)Aug 20 16:02:38 Laptop kernel: [56912.524939] pcieport 0000:00:1d.4: device [8086:02b4] error status/mask=00001000/00002000Aug 20 16:02:38 Laptop kernel: [56912.524944] pcieport 0000:00:1d.4:  TimeoutAug 20 16:02:38 Laptop kernel: [56912.524951] nvme 0000:07:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)Aug 20 16:02:38 Laptop kernel: [56912.524953] nvme 0000:07:00.0: device [144d:a80a] error status/mask=00000001/0000e000Aug 20 16:02:38 Laptop kernel: [56912.524957] nvme 0000:07:00.0: [ 0] RxErrAug 20 16:02:38 Laptop kernel: [56912.524960] nvme 0000:07:00.0: AER: Error of this Agent is reported firstAug 20 16:11:20 Laptop kernel: [57435.188243] pcieport 0000:00:1d.4: AER: Multiple Corrected error received: 0000:07:00.0Aug 20 16:11:20 Laptop kernel: [57435.188265] pcieport 0000:00:1d.4: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)Aug 20 16:11:20 Laptop kernel: [57435.188272] pcieport 0000:00:1d.4: device [8086:02b4] error status/mask=00001000/00002000Aug 20 16:11:20 Laptop kernel: [57435.188280] pcieport 0000:00:1d.4:  TimeoutAug 20 16:11:20 Laptop kernel: [57435.188339] nvme 0000:07:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)Aug 20 16:11:20 Laptop kernel: [57435.188344] nvme 0000:07:00.0: device [144d:a80a] error status/mask=00000001/0000e000Aug 20 16:11:20 Laptop kernel: [57435.188350] nvme 0000:07:00.0: [ 0] RxErrAug 20 16:11:20 Laptop kernel: [57435.188355] nvme 0000:07:00.0: AER: Error of this Agent is reported firstAccording to "google" they should be "just informational" , but my PC kept locking up.Saw a lot of suggestions.https://askubuntu.com/questions/1401726/pcieport-0000001d-0-aer-corrected-error-received-00000400-0But decided to upgrade BIOS & NVME FW to latest.Upgraded Bios first , and then NVME FW (Samsung NVME updater said it was already on latest)But the Bios upgrade seems to have fixed it, I haven't seen a single pci/nvme error (logentry) since the upgrade./Bingo

author: PlainName
author_rank: Super Contributor
timestamp: August 20, 2023, 06:22:51 pm
content: Shouldn't one take this opportunity to restore from backup to the new drive? That way you get the job doneandbe reassured that your backups do indeed restore. And in the end, if it all goes titsup, you still have the untouched original drive to shove back in.

author: bingo600
author_rank: Super Contributor
timestamp: August 20, 2023, 07:21:48 pm
content: The above isn't a NVME issue , but a PCIebus oddness.And Btw: It isn't resolved yet ... Just had another lockupConsidering thisCode:the solution pcie_aspm=off (/etc/default/grub)Active-State Power Management (ASPM) saves power in the Peripheral Component Interconnect Express (PCI Express or PCIe) subsystem by setting a lower power state for PCIe links when the devices to which they connect are not in use. ASPM controls the power state at both ends of the link, and saves power in the link even when the device at the end of the link is in a fully powered-on state.thisCode:The solution was adding pci=nommconf to the kernel boot parameters, which disables Memory-Mapped PCI Configuration Space & reverts to the traditional handling of configuration spaceOr thisUpgrading Kernel to a newer release train.It does seem like it began , when i switched from the 1TB 980 nvme , to the 2TB 980Pro nvme.Or installed the new kernel, from updateThere's nothing in the log .... and screen seems normal , i just "loose" my keybd + mouse/touchpad ... AKA PC seems dead.I might try to ssh into the pc , next time it happens/Bingo

author: bingo600
author_rank: Super Contributor
timestamp: September 16, 2023, 05:10:28 am
content: Short followup on my PCIe issue.I was still experiencing unmotivated system lockups, apparently caused by a combination of my Laptop NVME PCIe chipset , and the Samsung Pro2.The Laptop is made for PCIe 3 disks, and the 980 Pro2 is a PCIe 4.And even though a PCIe 4 should be backwards compatible with a PCIe 3 disk, it seems to cause random system lockup.And i kept getting those pcie/nvme errors described above.First trying this in grub : #GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer"Not making any real difference.Then after updating to the latest Mint (Ubuntu) Kernel : 6.2.0-32-generic #32~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Fri Aug 18 10:40:13 UTC 2 x86_64 x86_64 x86_64 GNU/LinuxIt was reduced to a few times a week, but still not acceptable.**** Why doesn't Samsung make a 980 in 2TB , i had no issued with that one (1TB)I have now bought a WD SN 570 2TB disk , that is PCIe 3 , and have cloned the 980 Pro2 disk onto that one.Cloning was as easy as the first time, taking around 18min.Let's see if i have a stable system now ...../BingoEdit:My future "performance" NVME's would probably be WD SN850X, if/when i get a PCIe 4 compatible Laptop.SN850X - PCIE4 2TB €126https://www.amazon.de/dp/B0B7CMZ3QH/Edit2:WD seems a tad less professional wrt. NVME firmware updates ...I really liked the Samsung NVME Firmware upgrade - Boot ISO.Makes upgrading the firmware a Breeze no matter what OS you have.WD only offers "official" FW update, using a M$ program

author: bingo600
author_rank: Super Contributor
timestamp: September 16, 2023, 06:24:15 am
content: So far not a single pcie/nvme error in the logLooking promising.Turned out to be a PC HW issue ...Same disk in another PC works flawlessly/Bingo

author: bjorn_helgaas
author_rank: Newbie
timestamp: April 26, 2024, 05:28:40 pm
content: IIUC, you had this issue with the new Samsung 980 PRO 2 TB PCIe 4.0 NVMe SSD:Code:Aug 20 16:02:18 Laptop kernel: [56893.050368] nvme 0000:07:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)Aug 20 16:02:18 Laptop kernel: [56893.050369] nvme 0000:07:00.0: device [144d:a80a] error status/mask=00000001/0000e000Aug 20 16:02:18 Laptop kernel: [56893.050371] nvme 0000:07:00.0: [ 0] RxErrand "pci=noaer" made no real difference.And you resolved the issue by switching from the Samsung NVMe to a WD NVMe, and no kernel parameters like "pci=noaer", "pcie_aspm=off", etc are needed.We have a report of a similar issue with that Samsung device (https://bugzilla.kernel.org/show_bug.cgi?id=215027), but I suspect it may be related to ASPM configuration.I would really like to debug this PCIe Correctable Error issue. If you're interested in helping, you could reinstall the Samsung 980 Pro2, reproduce the issue, and open a bug report athttps://bugzilla.kernel.org/, product Drivers/PCI. Mention the hardware platform, and attach:complete dmesg log (I assume this will include some Correctable Errors)output of "sudo lspci -vv"Try booting with the "pcie_aspm=off" kernel parameter to see if it makes any difference. If it does, please also attach similar dmesg and lspci output for this boot.This seems similar tohttps://bugzilla.kernel.org/show_bug.cgi?id=215027, which we originally thought was related to Intel VMD and/or the Samsung NVMe device you have, but I now suspect we might have an ASPM configuration problem.