My laptop has two drives. One SSD and one m.2. Both are enumerated as NVM devices: /dev/nvme0n1 and the m.2 connector was /dev/nvme1n1 (partitions where pX on each). I am attempting to replace the drive in the SSD position and the new device enumerates as /dev/sda, which causes the original /dev/nvme0n1 device to become /dev/nvme1n1 device. When I attempt to boot, I get to an "Welcome to emergency mode" and am placed into the the /root directory on the device. However, it appears the drive and partitions are correctly mounted and I can access all files on the system and user directories.
I've looked at journalctl -xb output and dont recognize any failures so I'm not sure what I can do to get the system to fully startup.
I'm assuming the fact that the boot device's name has changed is the root of the problem. Any advice on overecoming this obstacle?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I was able to resolve the issue by booting off usb and checking all files and fsck all partitions. Found dirty bit on EFI partition. Fixed and rebooted as normal.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My laptop has two drives. One SSD and one m.2. Both are enumerated as NVM devices: /dev/nvme0n1 and the m.2 connector was /dev/nvme1n1 (partitions where pX on each). I am attempting to replace the drive in the SSD position and the new device enumerates as /dev/sda, which causes the original /dev/nvme0n1 device to become /dev/nvme1n1 device. When I attempt to boot, I get to an "Welcome to emergency mode" and am placed into the the /root directory on the device. However, it appears the drive and partitions are correctly mounted and I can access all files on the system and user directories.
I've looked at journalctl -xb output and dont recognize any failures so I'm not sure what I can do to get the system to fully startup.
I'm assuming the fact that the boot device's name has changed is the root of the problem. Any advice on overecoming this obstacle?
I was able to resolve the issue by booting off usb and checking all files and fsck all partitions. Found dirty bit on EFI partition. Fixed and rebooted as normal.
Thanks for sharing that.
Steven