ERROR: device ‘UUID=<device_uuid>’ not found

Support
1

I have cloned my disk to a bigger one using clonezille from Manjaro USB Live which worked great. Now after swapping the disks I get this error:

ERROR: device ‘UUID=<device_uuid>’ not found. Skipping fsck 
mount: /new_root: can't find <device_uuid>.
You are now being dropped into an emergency shell.
sh: can't access tty: job control turned off

I have seen this thread Mount: /new_root: can't find <device_uuid> with similar problems, but when I run manjaro-chroot -a after booting again in Manjaro USB Live I get

>>> sudo su
>>> [manjaro manjaro]# manjaro-chroot -a
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sda1.  Check your device.map.
==> ERROR: No Linux partitions detected!
>>>[manjaro manjaro]#

What is also strange, that I do not find the disk on KDE Partition Manager. But in BIOS it seems to find the disk.

Any help?

2

manjaro-chroot should find the manjaro partition if it is there.

What is the output of sudo lsblk -f and sudo fdisk -l when run from the liveUSB?

3 
>>> lsblk -l 
NAME  MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0   7:0    0  21.2M  1 loop /run/miso/sfs/livefs
loop1   7:1    0 717.4M  1 loop /run/miso/sfs/mhwdfs
loop2   7:2    0   1.9G  1 loop /run/miso/sfs/desktopfs
loop3   7:3    0 645.3M  1 loop /run/miso/sfs/rootfs
sda     8:0    1  14.9G  0 disk /run/miso/bootmnt
sda1    8:1    1   3.3G  0 part 
sda2    8:2    1     4M  0 part 
>>> fdisk -l
fdisk: cannot open /dev/loop0: Permission denied
fdisk: cannot open /dev/loop1: Permission denied
fdisk: cannot open /dev/loop2: Permission denied
fdisk: cannot open /dev/loop3: Permission denied
fdisk: cannot open /dev/sda: Permission denied
4

For the sake of completness:

I did connect the new M2 SSD via case and USB. Then cloned the old disk to the new one via clonezilla. After the cloning both disks were shown in KDE Partition Manager as expected. Then finally switched the disks.

5

Since you created a new partition the UUID changed. you have to find the new ID and pass that along.

1 Like
6

I guess I did something wrong on cloning and have to do more homework. I put the disk back in the case and now I can boot it analog as my USB without any problem.

7

Even as I made an error and gave you not so good instructions (I have edited my comment now), it seems by the output of the lsblk command, that your NVMe drive is not being detected, at least when you boot from the liveUSB. Can you check that the drive is firmly in place? Is there any other thing that can affect the visibility of the drive?

You have be able to see the drive to chroot into it and change fstab file to replace the old UUID with the new UUID

No, you did good. This is the normal behavior. You have to update the UUID after the cloning. It’s just that.

8

A full clone will result in same UUID and thus should boot directly.

9

I am still on liveUSB. sda is the old disk on the internal slot. sdb is the clone connected via USB. It seems like, the IDs are fine and matching.

 >>> blkid | grep sda
/dev/sda4: LABEL="Diverses" UUID="69598026-5ac6-412b-be21-c3619990cd93" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="cb70996b-7d17-ed46-9ed2-f66e59d97064"
/dev/sda2: UUID="48191653-d99d-4f52-af33-82c9cf9cb732" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="root" PARTUUID="02bfb37d-5c26-2443-801d-535add43d64b"
/dev/sda3: LABEL="Dokumente" UUID="bd3acb08-d395-491b-be4c-9fd72c331d64" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f9365be6-a0e0-c041-a440-89014919f182"
/dev/sda1: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="0150-1B5C" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f083eea8-7a2f-8c40-a03e-d3e1e4dfa0fb"
 blkid | grep sdb                                                                                                                                        ✔ 
/dev/sdb4: LABEL="Diverses" UUID="69598026-5ac6-412b-be21-c3619990cd93" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="cb70996b-7d17-ed46-9ed2-f66e59d97064"
/dev/sdb2: UUID="48191653-d99d-4f52-af33-82c9cf9cb732" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="root" PARTUUID="02bfb37d-5c26-2443-801d-535add43d64b"
/dev/sdb3: LABEL="Dokumente" UUID="bd3acb08-d395-491b-be4c-9fd72c331d64" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="f9365be6-a0e0-c041-a440-89014919f182"
/dev/sdb1: LABEL_FATBOOT="NO_LABEL" LABEL="NO_LABEL" UUID="0150-1B5C" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="f083eea8-7a2f-8c40-a03e-d3e1e4dfa0fb"

The disk itself is bought at Cruicial and they asure compatibility. Anyway, I guess I reach out to their support as well.

10

Or maybe so a system rollback to fix it.

11

have you tried to boot with just one of them connected? maybe your bios/eufi gets confused when two have same UUID.

12

Yes. I now put only the clone into the internal slot and I am back to the original problem. I won’t even find it with blkid booting on liveUSB.

13

Crucial support told me to switch SATA-settings to AHCI in BIOS. It worked, the system recognizes the cloned disk in internal slot.

I am no expert in this so I am not able to answer this post properly. If somebody can, please feel free to do so.

Thanks everybody for the help.