Problem switching to a new HD

DST73

Member
Apr 22, 2023
40
0
6
Hi,

I have cloned my internal SSD (sdb) to an new external device (sdc).
(The new SSD is a Samsung 970 EVO Plus NVMe M.2 SSD, inside a Dsonix M.2 NVMe SATA SSD USB Adapter)
Than I have changed the boot order in bios to boot from the new device

If I now look at the devices I see
1698922354317.png

but in the console it looks like

Code:
root@pve:~# lsblk
NAME                 MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0                  7:0    0     4G  0 loop
loop1                  7:1    0     2G  0 loop
loop2                  7:2    0     4G  0 loop
loop3                  7:3    0     4G  0 loop
loop4                  7:4    0    48G  0 loop
sda                    8:0    0 931.5G  0 disk
sdb                    8:16   0 238.5G  0 disk
├─sdb1                 8:17   0  1007K  0 part
├─sdb2                 8:18   0     1G  0 part /boot/efi
└─sdb3                 8:19   0 237.5G  0 part
  ├─pve-swap         253:0    0     8G  0 lvm  [SWAP]
  ├─pve-root         253:1    0  69.4G  0 lvm  /
  ├─pve-data_tmeta   253:2    0   1.4G  0 lvm
  │ └─pve-data-tpool 253:4    0 141.2G  0 lvm
  │   └─pve-data     253:5    0 141.2G  1 lvm
  └─pve-data_tdata   253:3    0 141.2G  0 lvm
    └─pve-data-tpool 253:4    0 141.2G  0 lvm
      └─pve-data     253:5    0 141.2G  1 lvm
sdc                    8:32   0 931.5G  0 disk
├─sdc1                 8:33   0  1007K  0 part
├─sdc2                 8:34   0     1G  0 part
├─sdc3                 8:35   0 237.5G  0 part
└─sdc4                 8:36   0   693G  0 part /mnt/pve/ext_pve

Does this mean that proxmox still uses the old device? How can I change this?

Initially I wanted to exchange the drive inside my mini pc but that is not possible because the screws to open the PC and to get access to the old SSD don't work anymore.
So I have to leave the old SSD inside :(

Thank you!
 
How exactly have you cloned your drive ?
 
clonezilla does not really copy byte to byte, but instead copies the content of the partition. And it seems to me, that it was not able to copy your logical volumes.
If you want to copy byte to byte use dd instead. Afterwards use parted or gparted to resize your partition [1] to use the full 1TB and also adjust the fs.

[1]https://pve.proxmox.com/wiki/Resize_disks
 
Last edited:
As others said it does not look like the copy was successful. Keep in mind even if you do copy the context, you will likely have to deal with duplicate LVM groups which may require manual intervention.

Additionally, since your old disk moved to sdB, and it was likely sdA before, and your OS booted - that means /etc/fstab is pointing at UUID of the disk (as it should). The OS will continue to mount old disk as root until you change things. But first, make sure you have a good copy. I would put more effort into eventually trying to either get rid of old disk, or at least disable it until you get a good boot going. Perhaps in the bios.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
sda is an old disk that I used for backups (witch became to slow and was the reason I have bought a new one).
My old boot disk was sdb and after I have installed some time ago the disk for backups (witch was sda) it still was sdb
I think I will setup Proxmox fresh and install it directly on my new drive.

I have looked at some tutorials. If I understand it right I have to do the following steps.
1) Backup VMs and CTs to another drive
2) Install Proxmox on my new drive
3) Restore each backup of my VMs and CTs
 
sda is an old disk that I used for backups (witch became to slow and was the reason I have bought a new one).
My old boot disk was sdb and after I have installed some time ago the disk for backups (witch was sda) it still was sdb
Ok, its the Samsung 870 vs 970 that confused me at least.
So if the new disk is sdC - seems like copy has worked. At a high level you still need:
a) deal with duplicate volume groups, possibly by booting into live CD and de-activating sdB, activating sdC
b) deal with /etc/fstab
c) deal with boot loader : https://pve.proxmox.com/wiki/Host_Bootloader

good luck


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
I have looked at some tutorials. If I understand it right I have to do the following steps.
1) Backup VMs and CTs to another drive
2) Install Proxmox on my new drive
3) Restore each backup of my VMs and CTs
Don't forget to backup your hosts "/etc" folder, especially "/etc/pve".
 
  • Like
Reactions: DST73
So I have installed Proxmox fresh on my new SSD.
I still have the same problem that if I backup a bigger container like the one of my docker looks like the whole system freezes.
1699001620132.png
1699001589862.png

But the backup is in progress
1699001650500.png
I have tried it with all three more or less new SSDs. Same problem. Backup freezes the system

And after some while the system is not reachable anymore
1699001950995.png

1699001976291.png

Looks like the new SSD in that USB device gets very hot
1699003290012.png


Any ideas what the problem could be?
Any way to give them backup-process less power?

If I connect a monitor to my mini pc I can see these errors
1699004310279.png


Thank you!
 

Attachments

  • 1699003221733.png
    1699003221733.png
    25.6 KB · Views: 7
Last edited:
I have bought another SSD and and an ICY Box with an active cooling system.
No problems since than besides one that S.M.A.R.T does not work with that ICY Box

1699531243653.png


Code:
root@pve:/# smartctl --health /dev/sdc
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.2.16-19-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

Read Device Identity failed: scsi error unsupported scsi opcode

If this is a USB connected device, look at the various --device=TYPE variants
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
root@pve:/#
 
Yes the backup problem seems to be fixed...

It is an IB-1816M-C31 but i can't find it in the list of supported devices
 
If you want to trust this article you can try using smartctl -d sntjmicron as your icy box is apparently using a jmicron bridge
 
Unfortunately that didn't work :(

Code:
root@pve:~# smartctl -d sntjmicron --health /dev/sdc
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.2.16-19-pve] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

Read NVMe Identify Controller failed: scsi error unsupported scsi opcode
root@pve:~#
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!