BIOS can't detect NVME SSD

smsuil · 11-11-2022, 08:35 PM

Hi all

OS - Ubuntu 22.04 desktop

My old 1TB Samsung NVME Gen 3 SSD runs out of space. I bought a new 2TB Samsung NVME Gen 3 SSD. Just cloned the old 1TB drive on the new 2TB drive running pvmove. Installation went through without problem.

But after finish, on reboot the motherboard BIOS can't detect it. on Terminal lsblk can find the new 2TB drive.

$ lsblk

Code:

NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0     7:0    0     4K  1 loop /snap/bare/5
loop1     7:1    0  55.6M  1 loop /snap/core18/2566
loop2     7:2    0  55.6M  1 loop /snap/core18/2620
loop3     7:3    0  63.2M  1 loop /snap/core20/1623
loop4     7:4    0  63.2M  1 loop /snap/core20/1695
loop5     7:5    0 400.8M  1 loop /snap/gnome-3-38-2004/112
loop6     7:6    0 346.3M  1 loop /snap/gnome-3-38-2004/119
loop7     7:7    0  91.7M  1 loop /snap/gtk-common-themes/1535
loop8     7:8    0  81.3M  1 loop /snap/gtk-common-themes/1534
loop9     7:9    0    83M  1 loop /snap/scrcpy/386
loop10    7:10   0  45.9M  1 loop /snap/snap-store/582
loop11    7:11   0  45.9M  1 loop /snap/snap-store/599
loop12    7:12   0    48M  1 loop /snap/snapd/17029
loop13    7:13   0    48M  1 loop /snap/snapd/17336
loop14    7:14   0   284K  1 loop /snap/snapd-desktop-integration/14
sda       8:0    0 465.8G  0 disk 
├─sda1    8:1    0   512M  0 part /boot/efi
└─sda2    8:2    0 465.3G  0 part /
nvme0n1 259:0    0   1.8T  0 disk

Please help. Thanks in advance.

Regards

mrmazda · 11-11-2022, 08:54 PM

Just a few days ago I upgraded from 120G NVME to 500G NVME, but my trouble was somewhat different, depending on your exact meaning of "can't find", and how exactly you "cloned". Can't find was my initial problem. Here's the mailing list thread you may wish to read through.

smsuil · 11-11-2022, 09:19 PM

Quote:

Originally Posted by mrmazda

Just a few days ago I upgraded from 120G NVME to 500G NVME, but my trouble was somewhat different, depending on your exact meaning of "can't find", and how exactly you "cloned". Can't find was my initial problem. Here's the mailing list thread you may wish to read through.

Hi,

Thanks for your reply.

Cloning went through without complaint

sudo pvmove /dev/nvme1n1p2 /dev/nvme0n0

Code:

...
  /dev/nvme1n1p2: Moved: 60.53%
  /dev/nvme1n1p2: Moved: 62.11%
  /dev/nvme1n1p2: Moved: 63.68%
  /dev/nvme1n1p2: Moved: 91.33%
  /dev/nvme1n1p2: Moved: 95.97%
  /dev/nvme1n1p2: Moved: 99.90%
  /dev/nvme1n1p2: Moved: 100.00%

$ lsblk -f | grep nvme1

Code:

nvme1n1             LVM2_member LVM2 001       yxVkpN-FbNF-HsAM-APTr-R2J6-YxR2-wmdoMj

$ blkid | grep nvme1
no output

2 years ago I cloned a 500G SATA3 SSD onto a 1TB SATA3 SSD running "dd". It went through without problem. I succeeded upgrading the SSD.

This time I tried something new in order to learn. "pvmove" is completely new to me.

Pls inform what method you ran to upgrade your SSD?

Regards

mrmazda · 11-11-2022, 09:31 PM

Pvmove I have no experience with, but I would expect it to apply to copying or moving LVM volumes only. Your pvmove /dev/nvme1n1p2 /dev/nvme0n0 would have copied from a partition on an NVME to an unpartitioned NVME directly, not something my intuition says is likely to be supported. Without knowing the partitioning of either source or target it's pretty hard to guess what else could be errant.

lvm_ · 11-12-2022, 04:00 AM

The fact that linux cannot see partitions on a new disk (nvme0n1 259:0 0 1.8T 0 disk) is a clear indication that cloning went horribly wrong. But there is more: pvmove is not only the wrong tool for the job used in the wrong way, as was already noted, it is a tool that *moves* LVM extents, so now your source data on the old disk could be gone. Before you proceed with the cloning proper, stop and check the health of your 'old' system. Caveats: assuming the source was an LVM volume, also I was never interested in how thoroughly pvmove cleans up the source, data there is probably recoverable and maybe even accessible, but better to be safe than sorry. After that - https://www.google.co.uk/search?hl=e...one+disk+linux

smsuil · 11-12-2022, 06:38 AM

Quote:

Originally Posted by lvm_

The fact that linux cannot see partitions on a new disk (nvme0n1 259:0 0 1.8T 0 disk) is a clear indication that cloning went horribly wrong. But there is more: pvmove is not only the wrong tool for the job used in the wrong way, as was already noted, it is a tool that *moves* LVM extents, so now your source data on the old disk could be gone. Before you proceed with the cloning proper, stop and check the health of your 'old' system. Caveats: assuming the source was an LVM volume, also I was never interested in how thoroughly pvmove cleans up the source, data there is probably recoverable and maybe even accessible, but better to be safe than sorry. After that - https://www.google.co.uk/search?hl=e...one+disk+linux

Hi,

Thanks for your advice.

The source 1TB NVMe SSD is still able to work.

Then I ran;
$ sudo dd if=/dev/nvme1n1 of=/dev/nvme0n1 bs=64K conv=noerror,sync

Installation went through without complaint. Unfortunately after finish both the source and target SSDs are unable to boot. They only show a dark screen;
grub>

Please advise how to fix the problem? I have Ubuntu 22.04 boot USB

Thanks in advance

Regards

teckk · 11-12-2022, 07:37 AM

Looks like the same as this one.
https://www.linuxquestions.org/quest...em-4175718708/

Guess I answered the wrong one.

jefro · 11-14-2022, 08:26 AM

Might boot to efishell for more clues?
Yes, the clone part is suspect.

colorpurple21859 · 11-14-2022, 09:15 AM

Quote:

Looks like the same as this one.

I think it is also, which is marked solved

smsuil · 11-14-2022, 09:38 AM

Quote:

Originally Posted by jefro

Might boot to efishell for more clues?
Yes, the clone part is suspect.

Hi

Thanks for your advice.

Problem solved as follow;

Restore the backup image of the old 1TB NVME SSD on the new 2TB NVME SSD. The backup image was created before running pvmove. Now Ubuntu 22.04 on the new 2TB NVME SSD can be started.

But there is any problem generated. The storage size of Ubuntu 22.04 is only 1TB on the new 2TB NVME SSD. Please see my another posting on;

How to increase the disc space
https://www.linuxquestions.org/quest...52#post6392252

Thanks

Regards