Ubuntu Booting up in emergency mode

[thegoodstuff24]

Grub is definitely installed and working fine, as far as I know. I can still boot to windows fine and at least select Ubuntu to boot from.

There indeed is a line for /boot/efi and is displayed as follows:

/swapfile                                                         none             swap   sw        0            0
           UUID=C7C9-45DF    /boot/efi            vfat       defaults        0          1

That appears to match line 183. There is only one other UUID shown in the blkid:

UUID = 042B-FE10    /media/SHARED-WIN-LIN-600G    vfat       auto,user,uid=1000,gid=100,dmask=027,fmask=137    0       0

Not sure where that one fits in as it is not in the boot info logs.

[thegoodstuff24]

Yes I believe it was a windows recovery partition. I updated the BIOS then reset my settings, but I can check again. I will also look at updating my SSD firmware as I have not done that yet.

[Dennis N]

Grub is definitely installed and working fine, as far as I know. I can still boot to windows fine and at least select Ubuntu to boot from.
There indeed is a line for /boot/efi and is displayed as follows:

/swapfile                                                         none             swap   sw        0            0
           UUID=C7C9-45DF    /boot/efi            vfat       defaults        0          1

That appears to match line 183...

The UUID is correct here for the ESP. But I think fstab is not getting read at all. I suspect your initramfs (needed to startup) may be looking for that missing partition UUID=042B-FE10 and it's not there so you end up in the emergency mode. If this analysis is correct, initramfs would need to be regenerated. The command (run as root) is:

update-initramfs -u

BUT, this only works if you run it from root partition of Ubuntu OS filesystem. If you can't boot Ubuntu, you have to chroot into the Ubuntu root partition from live media, execute the command above, followed by update-grub.

Hopefully, that will fix things.

[thegoodstuff24]

Ok, do you have a recommended procedure for setting up chroot?

[oldfred]

With chroot you have to mount the necessary folders in root from identical live installer.
It varies a bit if UEFI (as you have to also mount the ESP) or LVM with encryption.

To chroot, you need the same 32bit or 64 bit kernel. Best to use same version.
https://help.ubuntu.com/community/BasicChroot
drs305 chroot to purge & reinstall grub2
http://ubuntuforums.org/showthread.php?t=1581099
kansasnoob- full chroot one line version with &&---- change sda3 to your install


UEFI chroot - shows mount of ESP also
http://askubuntu.com/questions/53578/can-i-install-in-uefi-mode-with-the-alternate-installer/57380#57380

chroot with UEFI, LVM, encryption on NVMe drive
https://ubuntuforums.org/showthread....8#post13602088

[Dennis N]

Get device name for Ubuntu root partition from boot info summary --> /dev/nvme0n1p4
and use this as device in first mount command below (I already put it in). Words in [...] are comments. don't type in.

Work Notes:
STEPS TO ENTER AND EXIT CHROOT ENVIRONMENT
sudo mount /dev/nvme0n1p4 /mnt
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo chroot /mnt
[enters chroot environment with root prompt]
update-initramfs -u
update-grub
exit
[leaves chroot environment]
sudo umount /mnt/sys
sudo umount /mnt/proc
sudo umount /mnt/dev
sudo umount /mnt

[thegoodstuff24]

So I chrooted in and followed your steps but still have the same issue.
I looked at the boot info logs again and I am wondering lines 165-171 are the actual issue.

Failed to mount '/dev/nvme0n1p1': Invalid argumentThe device '/dev/nvme0n1p1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
mount /dev/nvme0n1p1 : Error code 12
mount -r /dev/nvme0n1p1 /mnt/boot-sav/nvme0n1p1 NTFS signature is missing.

From my liveUSB i opened Gparted and it does not recognize ncme0n1p1.
I honestly don't even know what that partition is. Maybe I could try formatting it to ntfs?

[oldfred]

Typical default installs of Windows have the first partition as some sort of recovery.
I believe it usually is NTFS.

It could be hibernated as Windows sets hibernation flag on all NTFS partitions when fast start up is on.
Or if as message says NTFS signature is missing, may be a NTFS partition boot sector is damaged.
If that is issue then you may be able to restore the signature from a backup.

http://www.ntfs.com/fat-partition-sector.htm
PBR - partition boot sector NTFS must be Windows
[HowTo] Repair the bootsector of a Windows partition - YannBuntu
https://help.ubuntu.com/community/BootSectorFix
http://ubuntuforums.org/showthread.php?t=1926510
http://askubuntu.com/questions/65529.../655486#655486
As described, testdisk has an option to "Recover NTFS boot sector from its backup"
If Backup BS isn't available, choose RebuildBS, otherwise Windows repairs will not work
Instructions - see section on NTFS partition boot sector recovery
http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step
You want to get to this screen:
http://www.cgsecurity.org/wiki/TestD...ector_recovery
select [Advanced] instead of [Analyse] and select [BackupBS]

[thegoodstuff24]

If it truly is a Windows recovery partition why would that prevent me from booting into Ubuntu?
And why would Windows be booting properly?

[oldfred]

While maybe not the issue, did you fix it so we know for sure it is not the issue?

Did you update UEFI on new motherboard? As installed it may not have newest UEFI which is required.