tivasyk, 6 months ago

@hamoid you might need to...

1. boot from a liveusb;
2. mount the partition containing the root dir (/) on your m.2 drive;
3. chroot to it;
4. check the contents of the /etc/mkinitcpio.conf, fix if required;
5. regenerate the initcpio;
6. exit chroot and try to boot from the m.2 again.

this is just a general procedure outline, check your distro's doc-tion / forums for details.

example of a similar issue resolved:

https://forum.manjaro.org/t/error-device-uuid-device-uuid-not-found-skipping-fsck/70809

hamoid, 6 months ago

@tivasyk I tried for 2 days until I gave up. I just installed Manjaro from scratch and it works fine. The only reason I was restoring an .img with dd was to save time, but that didn't really work as expected this time. Thank you for the tips though! :-)

sardaukar, 6 months ago

@hamoid do you have the old disk still plugged in? If two identical UUIDs are present, it causes problems

hamoid, 6 months ago

@sardaukar Thank you, no the old disk was copied months ago with dd and I no longer have that disk, only its .img

slyecho, 6 months ago

@hamoid What is the UUID in the emergency shell? It could be different. I've seen this when the type of the drive is different (SATA vs Virtio). It's also possible the drive is not detected and some module needs to be added to the initrd.

hamoid, 6 months ago

@slyecho The old disk was an 2.5 SSD and the new one is an M.2 disk. But I also tried with a 2.5 SSD and got the same error.

Ah interesting about the initrd.

In the emergency shell, I just do blkid to find out the UUID?

hamoid, 6 months ago

@slyecho I believe the drives are not detected. In the same computer I can boot from drives A and B. A works fine (my every day drive), B fails to boot. In A, ls /dev/nvme* shows the drives, in B it doesn't.

Adding a screenshot just to cheer myself up :-)