Page 1 of 3 123 LastLast
Results 1 to 10 of 21

Thread: Ubuntu Booting up in emergency mode

  1. #1
    Join Date
    Sep 2019
    Beans
    11

    Ubuntu Booting up in emergency mode

    My Specs:
    Dell XPS 8930
    Ubuntu 18.04 Dual Boot
    Samsung 960 Evo (M2)

    So my Motherboard failed recently and I had to replace it. Upon installing it and booting my grub menu no longer worked, it went right to windows 10.
    I used boot-repair to resolve that and I tried to boot Ubuntu but I get the following errors:

    [ 0.056310] ACPI Exception: AE_BAD_PERAMETER, Could not install Pciconfig handler for root Bridge PCIO (20170831/evrgnini-245)
    [ 1.938421] Couldn't get size: 0x800000000000000e
    /dev/nvme0n1p4: Clean, 573615/2564096 files, 8285104/10239744 blocks
    Timed out Waiting for device dev-disk-by\x2uuid-042B\x2dFE10.device.

    I looked at the blkid and compared the UUID to the one in etc/fstab and I am pretty sure they match correctly.
    I also tried editing the grub menu config to:

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=strict"

    and updated it but still no difference. I can also boot from a live USB (With the Ubuntu installer/ISO) with no issue.


    Been struggling with this for a while, any thoughts or help would be appreciated.


    EDIT:
    Here is the requested boot-info Link:
    http://paste.ubuntu.com/p/5nJ8xYn7zb/
    Last edited by thegoodstuff24; 1 Week Ago at 11:02 PM.

  2. #2
    Join Date
    Mar 2010
    Beans
    8,756
    Distro
    Ubuntu Mate

    Re: Ubuntu Booting up in emergency mode

    Hi and welcome to the forums

    Best to see details from the boot info summary (first link in my signature).

    Thanks.

  3. #3
    Join Date
    Sep 2019
    Beans
    11

    Re: Ubuntu Booting up in emergency mode

    Ok, I added it to my post.

  4. #4
    Join Date
    Sep 2019
    Beans
    11

    Ubuntu Boot up Issue

    My Specs:
    Dell XPS 8930
    Ubuntu 18.04 Dual Boot with Windows 10
    Samsung 960 Evo (M2)

    Just replaced my Motherboard that failed and now Ubuntu will not boot. I can still get to my grub menu and boot from Windows though, as well as a USB device.
    Ubuntu however goes into emergency mode and gives the following errors:

    [ 0.056310] ACPI Exception: AE_BAD_PERAMETER, Could not install Pciconfig handler for root Bridge PCIO (20170831/evrgnini-245)
    [ 1.938421] Couldn't get size: 0x800000000000000e
    /dev/nvme0n1p4: Clean, 573615/2564096 files, 8285104/10239744 blocks
    Timed out Waiting for device dev-disk-by\x2uuid-042B\x2dFE10.device.

    I tried Boot-Repair and a couple of other solutions but have had no luck.
    Here is my boot info:
    http://paste.ubuntu.com/p/5nJ8xYn7zb/

    Any assistance would be appreciated.

  5. #5
    Join Date
    Jun 2007
    Location
    Arizona U.S.A.
    Beans
    4,270

    Re: Ubuntu Boot up Issue

    Because of the "Timed out Waiting for device..." message, check if the UUIDs in your /etc/fstab are actual system UUIDs given in lines 182-198 of boot repair output. Change the UUID in /etc/fstab to match so it can mount. Possibly the EFI system partition has wrong UUID.

  6. #6
    Join Date
    Sep 2019
    Beans
    11

    Re: Ubuntu Boot up Issue

    Here is what I have in fstab:

    [IMG]C:\Users\dfaulkner\Desktop[/IMG]


    If the picture does not upload here is essentially what it shows:

    ext4 (or /dev/nvmeonp4) UUID = 51792f78-d42b-4900-8b50-de7178762b7b

    Compare that to line 185 and I believe that it is correct, so is there anything else I can check?
    Last edited by thegoodstuff24; 1 Week Ago at 08:25 PM.

  7. #7
    Join Date
    Sep 2019
    Beans
    11

    Re: Ubuntu Boot up Issue

    Just noticed this:
    /dev/sda1: LABEL="UBUNTU 18_0" UUID="15E2-0D5B" TYPE="vfat" PARTLABEL="Microsoft Basic Data" PARTUUID="824d2a16-b1f3-4c69-9853-aac49fb1e20b"

    That does not seem right to me. Is that the system partition?

  8. #8
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Ubuntu Booting up in emergency mode

    Even if new motherboard, you may still need UEFI update.
    Did you also update SSD firmware, make sure that is most current version.

    And updating UEFI or new motherboard will reset many UEFI settings. So anything you changed before, you need to redo. I have 5 to 7 settings I change (some optional), so I keep a list.

    Report shows issue with nvme0pn1p1 or first partition. Was that a Dell or Windows recovery partition, since ESP is p2?

    Another Dell 8930.
    Installing Ubuntu 18.04.2 on Dell 8930 with dual boot win10
    https://ubuntuforums.org/showthread.php?t=2413145
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  9. #9
    Join Date
    Jun 2009
    Location
    SW Forida
    Beans
    Hidden!
    Distro
    Ubuntu

    Re: Ubuntu Booting up in emergency mode

    Duplicate threads merged.
    For more info on UEFI boot install & repair - Regularly Updated :
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to change to [Solved] when/if answered completely.

  10. #10
    Join Date
    Jun 2007
    Location
    Arizona U.S.A.
    Beans
    4,270

    Re: Ubuntu Booting up in emergency mode

    If the picture does not upload here is essentially what it shows:

    ext4 (or /dev/nvmeonp4) UUID = 51792f78-d42b-4900-8b50-de7178762b7b

    Compare that to line 185 and I believe that it is correct, so is there anything else I can check?
    That UUID is for the root partition, and that is correct. There should also be an entry in /etc/fstab to mount the EFI system partition. Use your live media to look again for an entry line mounting some partition at /boot/efi. Since the UUID in the error message doesn't exist, It may have the wrong UUID. (You can use code tags to format more clearly what you post.)

    "Timed out Waiting for device dev-disk-by\x2uuid-042B\x2dFE10..." is looking for UUID=042B-FE10, causing failure. No sign of that UUID in boot repair summary.

    I see no /boot/grub/grub.cfg menu entries from the NVMe drive - only sda. Grub seems not to be installed?
    Last edited by Dennis N; 1 Week Ago at 03:22 PM. Reason: removed double preposition

Page 1 of 3 123 LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •