Page 1 of 2 12 LastLast
Results 1 to 10 of 16

Thread: not booting after sudden power loss

  1. #1
    Join Date
    Jan 2012
    Beans
    8

    not booting after sudden power loss

    Hi there,

    my laptop's battery ran out and laptop suddenly shut down. When plugged the laptop to the power and restarted it, grub appeared with "Minimal BASH-like line editing is supported.." screen. Following the instructions on this page, I have restarted the laptop with live usb, installed boot repair, and saved the boot-Info summary (accessible at https://paste.ubuntu.com/p/26bJgdHrmT/ also pasted below). Can anyone tell what the problem is? Is the recommended repair appropriate?

    Thanks
    -----
    Code:
    boot-repair-4ppa2081                                              [20241008_1515]
    
    ============================== Boot Info Summary ===============================
    
     => No boot loader is installed in the MBR of /dev/nvme0n1.
    
    nvme0n1p1: _____________________________________________________________________
    
        File system:       vfat
        Boot sector type:  FAT32
        Boot sector info:  No errors found in the Boot Parameter Block.
        Operating System:  
        Boot files:        /efi/BOOT/fbx64.efi /efi/BOOT/mmx64.efi 
                           /efi/ubuntu/fwupdx64.efi /efi/ubuntu/grubx64.efi 
                           /efi/ubuntu/mmx64.efi /efi/ubuntu/shimx64.efi 
                           /efi/ubuntu/grub.cfg
    
    nvme0n1p2: _____________________________________________________________________
    
        File system:       ext4
        Boot sector type:  -
        Boot sector info: 
        Operating System:  Ubuntu 20.04.6 LTS
        Boot files:        /boot/grub/grub.cfg /etc/fstab /etc/default/grub
    
    sda: ___________________________________________________________________________
    
        File system:       iso9660
        Boot sector type:  Unknown
        Boot sector info: 
        Mounting failed:   mount: /mnt/BootInfo/FD/sda: /dev/sda already mounted or mount point busy.
    
    
    ================================ 1 OS detected =================================
    
    OS#1 (linux):   Ubuntu 20.04.6 LTS on nvme0n1p2
    
    ================================ Host/Hardware =================================
    
    CPU architecture: 64-bit
    Video: NVIDIA Corporation UHD Graphics from NVIDIA Corporation Intel Corporation
    Live-session OS is Ubuntu 64-bit (Ubuntu 20.04.6 LTS, focal, x86_64)
    
    ===================================== UEFI =====================================
    
    BIOS/UEFI firmware: 1.29.0(1.29) from Dell Inc.
    The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
    SecureBoot disabled (confirmed by mokutil).
    BootCurrent: 0004
    Timeout: 0 seconds
    BootOrder: 0004,0005,0001,0002,0000,0003,0006
    Boot0000* UEFI BC501 NVMe SK hynix 512GB CD9AN8683113YBI1B 1    PciRoot(0x0)/Pci(0x1d,0x0)/Pci(0x0,0x0)/NVMe(0x1,00-00-00-00-00-00-00-00)/HD(1,GPT,7d00b35a-8068-4cf7-a855-b714713388a5,0x800,0x100000)/File(\EFI\Boot\BootX64.efi)N.....YM....R,Y.
    Boot0001* ONBOARD NIC (IPV4)    PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(70b5e8a9c5df,0)/IPv4(0.0.0.00.0.0.0,0,0)N.....YM....R,Y.
    Boot0002* ONBOARD NIC (IPV6)    PciRoot(0x0)/Pci(0x1d,0x5)/Pci(0x0,0x0)/MAC(70b5e8a9c5df,0)/IPv6([::]:<->[::]:,0,0)N.....YM....R,Y.
    Boot0003* Linux Firmware Updater    HD(1,GPT,7d00b35a-8068-4cf7-a855-b714713388a5,0x800,0x100000)/File(\EFI\ubuntu\fwupdx64.efi)
    Boot0004* UEFI Generic Mass Storage 5470D802    PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/HD(2,MBR,0x405a23c7,0x573ca4,0x1fc0)/File(\EFI\Boot\BootX64.efi)N.....YM....R,Y.
    Boot0005* ubuntu    HD(1,GPT,7d00b35a-8068-4cf7-a855-b714713388a5,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
    Boot0006* UEFI Generic Mass Storage 5470D802 2    PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/CDROM(1,0x573ca4,0x7f00)/File(\EFI\Boot\BootX64.efi)N.....YM....R,Y.
    
    64e4182ead3316166f817dcc6131cd7a   nvme0n1p1/BOOT/fbx64.efi
    522f1fff3eaefbaeb449d98436d24041   nvme0n1p1/BOOT/mmx64.efi
    3dae829e41062a758307e7c3ca9e8b2f   nvme0n1p1/ubuntu/fwupdx64.efi
    d4646b0af24b169d62bc44cff8967793   nvme0n1p1/ubuntu/grubx64.efi
    522f1fff3eaefbaeb449d98436d24041   nvme0n1p1/ubuntu/mmx64.efi
    07e25dcaf57c776875f78fa36827c58e   nvme0n1p1/ubuntu/shimx64.efi
    07e25dcaf57c776875f78fa36827c58e   nvme0n1p1/BOOT/BOOTX64.efi
    
    ============================= Drive/Partition Info =============================
    
    Disks info: ____________________________________________________________________
    
    nvme0n1    : is-GPT,    no-BIOSboot,    has---ESP,     not-usb,    not-mmc, has-os,    no-wind,    2048 sectors * 512 bytes
    
    Partitions info (1/3): _________________________________________________________
    
    nvme0n1p1    : no-os,    64, nopakmgr,    no-docgrub,    nogrub,    nogrubinstall,    no-grubenv,    noupdategrub,    not-far
    nvme0n1p2    : is-os,    64, apt-get,    signed grub-pc grub-efi ,    grub2,    grub-install,    grubenv-ok,    update-grub,    end-after-100GB
    
    Partitions info (2/3): _________________________________________________________
    
    nvme0n1p1    : is---ESP,    part-has-no-fstab,    no-nt,    no-winload,    no-recov-nor-hid,    no-bmgr,    notwinboot, vfat
    nvme0n1p2    : isnotESP,    fstab-has-goodEFI,    no-nt,    no-winload,    no-recov-nor-hid,    no-bmgr,    notwinboot, ext4
    
    Partitions info (3/3): _________________________________________________________
    
    nvme0n1p1    : not--sepboot,    no---boot,    part-has-no-fstab,    not-sep-usr,    no---usr,    part-has-no-fstab,    no--grub.d,    nvme0n1
    nvme0n1p2    : not--sepboot,    with-boot,    fstab-without-boot,    not-sep-usr,    with--usr,    fstab-without-usr,    std-grub.d,    nvme0n1
    
    fdisk -l (filtered): ___________________________________________________________
    
    Disk nvme0n1: 476.96 GiB, 512110190592 bytes, 1000215216 sectors
    Disk identifier: 46B55DE5-F739-41D8-9CF7-503EE0C3C10C
               Start        End   Sectors   Size Type
    nvme0n1p1    2048    1050623   1048576   512M EFI System
    nvme0n1p2 1050624 1000214527 999163904 476.4G Linux filesystem
    Disk sda: 15.24 GiB, 16357785600 bytes, 31948800 sectors
    Disk identifier: 0x405a23c7
         Boot   Start      End  Sectors  Size Id Type
    sda1  *          0  8498951  8498952  4.1G  0 Empty
    sda2       5717156  5725283     8128    4M ef EFI (FAT-12/16/32)
    sda3       8499200 31948799 23449600 11.2G 83 Linux
    
    parted -lm (filtered): _________________________________________________________
    
    sda:16.4GB:scsi:512:512:unknown:Generic Flash Disk:;
    nvme0n1:512GB:nvme:512:512:gpt:BC501 NVMe SK hynix 512GB:;
    1:1049kB:538MB:537MB:fat32:EFI System Partition:boot, esp;
    2:538MB:512GB:512GB:ext4::;
    
    blkid (filtered): ______________________________________________________________
    
    NAME        FSTYPE   UUID                                 PARTUUID                             LABEL                    PARTLABEL
    sda         iso9660  2023-03-16-15-57-27-00                                                    Ubuntu 20.04.6 LTS amd64 
    ├─sda1      iso9660  2023-03-16-15-57-27-00               405a23c7-01                          Ubuntu 20.04.6 LTS amd64 
    ├─sda2      vfat     1544-BBA2                            405a23c7-02                                                   
    └─sda3      ext4     057e7441-fd4f-4e35-bbc6-23cae93c5a6f 405a23c7-03                          writable                 
    nvme0n1                                                                                                                 
    ├─nvme0n1p1 vfat     7477-E22F                            7d00b35a-8068-4cf7-a855-b714713388a5                          EFI System Partition
    └─nvme0n1p2 ext4     57b8e19f-45d0-4737-8b97-45c67f5b95cd ac22aee6-9824-4b24-b748-246385401b17                          
    
    Mount points (filtered): _______________________________________________________
    
                                                                   Avail Use% Mounted on
    /dev/nvme0n1p1                                                456.4M  11% /mnt/boot-sav/nvme0n1p1
    /dev/nvme0n1p2                                                107.2G  72% /mnt/boot-sav/nvme0n1p2
    /dev/sda1                                                          0 100% /cdrom
    
    Mount options (filtered): ______________________________________________________
    
    /dev/nvme0n1p1                                                vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
    /dev/nvme0n1p2                                                ext4            rw,relatime
    /dev/sda1                                                     iso9660         ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8
    
    =================== nvme0n1p1/efi/ubuntu/grub.cfg (filtered) ===================
    
    search.fs_uuid 57b8e19f-45d0-4737-8b97-45c67f5b95cd root 
    set prefix=($root)'/boot/grub'
    
    =================== nvme0n1p2/boot/grub/grub.cfg (filtered) ====================
    
    Ubuntu   57b8e19f-45d0-4737-8b97-45c67f5b95cd
    ### END /etc/grub.d/30_os-prober ###
    UEFI Firmware Settings   uefi-firmware
    ### END /etc/grub.d/30_uefi-firmware ###
    
    ======================== nvme0n1p2/etc/fstab (filtered) ========================
    
    # <file system> <mount point>   <type>  <options>       <dump>  <pass>
    # / was on /dev/nvme0n1p2 during installation
    UUID=57b8e19f-45d0-4737-8b97-45c67f5b95cd /               ext4    errors=remount-ro 0       1
    # /boot/efi was on /dev/nvme0n1p1 during installation
    UUID=7477-E22F  /boot/efi       vfat    umask=0077      0       1
    /swapfile                                 none            swap    sw              0       0
    
    ==================== nvme0n1p2/etc/default/grub (filtered) =====================
    
    GRUB_DEFAULT=0
    GRUB_TIMEOUT_STYLE=hidden
    GRUB_TIMEOUT=0
    GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
    GRUB_CMDLINE_LINUX=""
    
    ================= nvme0n1p2: Location of files loaded by Grub ==================
    
               GiB - GB             File                                 Fragment(s)
     262,500125885 = 281,857363968  boot/grub/grub.cfg                             3
     286,832054138 = 307,983572992  boot/vmlinuz                                   2
     157,144542694 = 168,732667904  boot/vmlinuz-5.15.0-107-generic                1
     286,832054138 = 307,983572992  boot/vmlinuz-5.15.0-117-generic                2
     247,457061768 = 265,704996864  boot/vmlinuz-5.15.0-122-generic                2
     157,144542694 = 168,732667904  boot/vmlinuz.old                               1
     157,477535248 = 169,090215936  boot/initrd.img                               10
     183,383785248 = 196,906840064  boot/initrd.img-5.15.0-107-generic            10
     157,477535248 = 169,090215936  boot/initrd.img-5.15.0-117-generic            10
     183,383785248 = 196,906840064  boot/initrd.img.old                           10
    
    =================== nvme0n1p2: ls -l /etc/grub.d/ (filtered) ===================
    
    -rwxr-xr-x 1 root root 18224 Jan 11  2022 10_linux
    -rwxr-xr-x 1 root root 42359 Aug 17  2020 10_linux_zfs
    -rwxr-xr-x 1 root root 13101 Dec 18  2022 20_linux_xen
    -rwxr-xr-x 1 root root 12059 Jul 31  2020 30_os-prober
    -rwxr-xr-x 1 root root  1424 Jul 31  2020 30_uefi-firmware
    -rwxr-xr-x 1 root root   700 Feb 21  2022 35_fwupd
    -rwxr-xr-x 1 root root   214 Jul 31  2020 40_custom
    -rwxr-xr-x 1 root root   216 Jul 31  2020 41_custom
    
    
    
    Suggested repair: ______________________________________________________________
    
    The default repair of the Boot-Repair utility would reinstall the grub-efi of
    nvme0n1p2,
    using the following options:  nvme0n1p1/boot/efi
    Additional repair would be performed: unhide-bootmenu-10s use-standard-efi-file
    
    Final advice in case of suggested repair: ______________________________________
    
    Please do not forget to make your UEFI firmware boot on the Ubuntu 20.04.6 LTS entry (nvme0n1p1/efi/****/grub****.efi (**** will be updated in the final message) file) !
    Last edited by deadflowr; 3 Weeks Ago at 06:47 PM. Reason: code tags

  2. #2
    Join Date
    May 2008
    Beans
    4,452
    Distro
    Ubuntu 24.04 Noble Numbat

    Re: not booting after sudden power loss

    After a power interruption, your file systems may have suffered some damage.
    Boot into a "Try Ubuntu" live session
    Open a terminal and enter:-
    Code:
    sudo fsck /dev/nvme0n1p1
    Follow terminal output to repair
    Then
    Code:
    sudo fsck /dev/nvme0n1p1
    Close terminal and power off.

    Does your PC boot normally now?

  3. #3
    Join Date
    Jan 2012
    Beans
    8

    Re: not booting after sudden power loss

    Thanks. I booted into "Try Ubuntu" and ran the first command. Found that dirty bit set. Is it safe to go ahead with action 1)? Below is the screen shot.


  4. #4
    Join Date
    May 2008
    Beans
    4,452
    Distro
    Ubuntu 24.04 Noble Numbat

    Re: not booting after sudden power loss

    Your screenshot is invisible.
    "Dirty bit set" is probably the culprit after an ungraceful shutdown due to power loss.
    Follow the repair instructions (I can't reproduce the problem without damaging my own ESP, although I have repaired this partition previously with fsck)

  5. #5
    Join Date
    Jan 2012
    Beans
    8

    Re: not booting after sudden power loss

    Apologies for failing to add the screenshot. I went ahead and applied fsck repair. Now it is not reporting any errors. Unfortunately, the laptop is still not booting. Stuck with the same grub screen.

  6. #6
    Join Date
    May 2008
    Beans
    4,452
    Distro
    Ubuntu 24.04 Noble Numbat

    Re: not booting after sudden power loss

    Quote Originally Posted by sdayanik View Post
    Apologies for failing to add the screenshot. I went ahead and applied fsck repair. Now it is not reporting any errors. Unfortunately, the laptop is still not booting. Stuck with the same grub screen.
    When you reach the grub screen "Minimal BASH-like line editing is supported.."
    Type exit and hit enter.
    What happens?

  7. #7
    Join Date
    Jan 2012
    Beans
    8

    Re: not booting after sudden power loss

    The same grub screen comes back.

  8. #8
    Join Date
    Jan 2012
    Beans
    8

    Re: not booting after sudden power loss

    Quote Originally Posted by sdayanik View Post
    The same grub screen comes back.
    Hmm. I tried a second time. Now it says "StartImage failed: Load Error"

  9. #9
    Join Date
    Jan 2012
    Beans
    8

    Re: not booting after sudden power loss

    Quote Originally Posted by sdayanik View Post
    Hmm. I tried a second time. Now it says "StartImage failed: Load Error"
    OK. Rebooted again. Grub screen appeared. Typed exit and hit the key. The same grub screen came back again. If I try type exit and hit enter again, then "StartImage failed: Load Error" appears. Then it reboots by itself. Back to the same grub screen.

  10. #10
    Join Date
    May 2008
    Beans
    4,452
    Distro
    Ubuntu 24.04 Noble Numbat

    Re: not booting after sudden power loss

    I've just noticed that I had an incorrect instruction in post 2.
    I typed nvme0n1p1 twice by mistake - schoolboy error........
    Can you boot into a live session again and run fsck on both partitions.
    Code:
    sudo fsck /dev/nvme0n1p1
    Code:
    sudo fsck /dev/nvme0n1p2

Page 1 of 2 12 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
  •