Boot failure. PC does not start

Newbie Corner
, ,
#1

Afterlast update, nothing works for me, i.e .:
Manjaro does not start. Errors appear as below:

I do not use hibernation, but the above error applies to the SWAP partition (sda3).
The second error refers to the system partition (sda2).

lsblk -f
NAME   FSTYPE LABEL    UUID                                 MOUNTPOINT
sda                                                         
├─sda1 vfat            DFDC-27CF                            
├─sda2 ext4   M        79492466-7c01-4f91-93b6-d7bc1a79f22d /media/M
├─sda3 swap            4a557fab-5124-49d5-b531-2d023b88efef [SWAP]

I can not run Manjaro with a second kernel too (there are other errors).

I managed to run my liveUSB Manjaro 16.10.3 to restore GRUB.
But I can not restore GRUB, as I used to do it, as described in the wiki Manjaro:

  • unlike always, after entering the sudo command - there is no prompt for the password, and after entering the sudo mhwd-chroot command, there is no asking for the selection of the system partition, as it was before.

So alternatively, I made a manual chroot, as below. Seemingly without errors (except for one unclear entry: EFI variables are not supported on this system.)
GRUB is generated, but the system still does not start (there is still an error as in the first picture).

[manjaro manjaro]# mount /dev/sda2 /mnt
[manjaro manjaro]# cd /mnt
[manjaro mnt]# mount -t proc proc /mnt/proc
[manjaro mnt]# mount -t sysfs sys /mnt/sys
[manjaro mnt]# mount -o bind /dev /mnt/dev
[manjaro mnt]# mount -t devpts pts /mnt/dev/pts/
[manjaro mnt]# chroot /mnt
[manjaro /]# sudo pacman -S mtools os-prober
[manjaro /]# sudo mount /dev/sda1 /boot/efi 
[manjaro /]# sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck 
Installing for x86_64-efi platform.
EFI variables are not supported on this system.
Installation finished. No error reported.
[manjaro /]# sudo update-grub 
Generating grub configuration file ...
Found background: /usr/share/grub/background.png
Found linux image: /boot/vmlinuz-4.14-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.14-x86_64.img
Found initrd fallback image: /boot/initramfs-4.14-x86_64-fallback.img
Found linux image: /boot/vmlinuz-4.9-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.9-x86_64.img
Found initrd fallback image: /boot/initramfs-4.9-x86_64-fallback.img
Found Manjaro Linux (16.10.3) on /dev/sda5
Found unknown Linux distribution on /dev/sda7
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

I also created liveUSB Manjaro 17.1.10 (using dd), but I can not start a Live system (there are other errors).

What should I do to fix my installation of Manjaro?

1 Like
[Stable Update] 2018-06-07 - Kernels, Systemd, Pamac, Octopi, Rebuilds
[Stable Update] 2018-06-07 - Kernels, Systemd, Pamac, Octopi, Rebuilds
#2

You have attempted grub rescue in bios-legacy when your system is uefi.
Your data is not complete, you have a sda7 linux OS unknown (and if uefi?) and we don't know if you have more disks other than sda and if there are more $esp outside sda.

By chrooting and attempting grub rescue, your manjaro grub conf is probably now not reliable ( so my method here may not work anymore).

Can you still boot into sda7 OS? If uefi, you should be able to by selecting boot setup key (F8~F12).
You have another Manjaro in sda5. Can you boot into it? Boot to it then and..
No? If you can, boot to sda7 OS (tell us what it is) and from there, let us know
You do not provide enough information for us to help you.
As a start,

confirm your wanted manjaro is sda2
contents of Manjaro's /etc/fstab
sudo parted -l (all disks)
efibootmgr -v
sudo blkid

1 Like
#3

If you installede Manjaro in EUFI, you must boot in UEFI in order to fix boot properly...

You may also be interested in using RESCATUX or boot-repair-disk (even I could not boot in UEFI last time I burnt boot-repair-disk in a USB but it worked for me before!)...

Also, you may want to check GRUB kernel boot parameters and see if there isn't a bad flag there....

#4

Removed, because not related.

#5

@Dan2
Your issue is not the same as the OP here nor the same as the link you mentioned.
I know you're new here, but can you start a new topic on your own?
Not sure if you can boot to Manjaro but provide
/etc/fstab of manjaro partition
sudo blkid
sudo parted -l
either from booted OS or from livecd.

#6

@gohlip
Answering your questions:
Until yesterday my main Manjaro UEFI 64-bit (on sda2) was working fine.
After problems occurred I tried to rescue GRUB in UEFI mode, as I was doing it in the past but this time I had some problem (as previously described ).

I have 2 disks, both in gpt and both have EFI partitions and $esp flags (I just have confirmed it in gparted).

My main disk is sda, with:

  • sda2 - current Manjaro UEFI 64-bit ( / + home )
  • sda3 - SWAP
  • sda5 - second and older installation of Manjaro UEFI 64-bit - version 16.10.3 . It was working fine until few months ago, but now it is not working (working only partially in tty),
  • sda7 - a small Slitaz Linux 64-bit, installed over year ago. It is working (I just use it). I do not know if it is in UEFI (can not find EFI directory inside).
uname -a
Linux slitaz 3.2.71-slitaz64 #2 SMP Fri Feb 24 08:05:23 CET 2017 x86_64 GNU/Linux
  • the others partitions are for data.

The second disk (sdb) has no system installed at the moment and is used for data only.

Now I place all the commands I can place from Slitaz (more when I will switch to LiveUSB Manjaro).

sudo blkid
Password: 
/dev/sda1: UUID="DFDC-27CF" TYPE="vfat" PARTUUID="33e218e3-f7ab-4b1e-8a65-15e52ee43baa"
/dev/sda2: LABEL="M" UUID="79492466-7c01-4f91-93b6-d7bc1a79f22d" TYPE="ext4" PARTLABEL="M" PARTUUID="30c70731-28aa-4c2e-8e9b-951f0dc0e81d"
/dev/sda3: UUID="4a557fab-5124-49d5-b531-2d023b88efef" TYPE="swap" PARTUUID="c6e308e6-60df-47f8-b803-ba0bc1f0d90f"
/dev/sda4: LABEL="testy24g" UUID="ccb66e9c-28a3-407a-9e98-33cdfc33a105" TYPE="ext4" PARTLABEL="tst24g" PARTUUID="4b970c56-4688-424b-97de-f3d9dd7ae00d"
/dev/sda5: LABEL="M2r16g" UUID="c0fe9982-bfcf-43b7-a26e-d480011ed2a0" TYPE="ext4" PARTUUID="e233939e-42a6-4eb8-b751-70477d0b4908"
/dev/sda6: LABEL="bd" UUID="84e26864-1cb9-4bd7-9cfd-915a847f1859" TYPE="ext4" PARTLABEL="bd" PARTUUID="26639df1-1172-45f7-9a84-b0144ba68889"
/dev/sda7: LABEL="slit" UUID="f9e1a6e3-9ab1-4e97-ae1f-1d0f953d5ed4" TYPE="ext4" PARTLABEL="slitaz" PARTUUID="aca6d5df-b090-4fe3-817b-ebb712772488"
/dev/sdb1: LABEL="EFI-B" UUID="5576-CD7B" TYPE="vfat" PARTLABEL="EFI System" PARTUUID="4f068499-e42c-40b2-b4b3-987edd834908"
/dev/sdb2: LABEL="hdW7" UUID="0C7F14897F0DDEED" TYPE="ntfs" PARTLABEL="W7" PARTUUID="376d94f8-a572-44f3-af71-ed6c89d3cffa"
/dev/sdb5: LABEL="hdKop" UUID="264e382b-4b5d-4a3f-87c0-69e9c36b43c5" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="f7e2466d-091e-4be1-8528-fe7f5c3ec800"

lsblk -f 
NAME   FSTYPE LABEL    UUID                                 MOUNTPOINT
sda                                                         
├─sda1 vfat            DFDC-27CF                            
├─sda2 ext4   M        79492466-7c01-4f91-93b6-d7bc1a79f22d /media/M
├─sda3 swap            4a557fab-5124-49d5-b531-2d023b88efef [SWAP]
├─sda4 ext4   testy24g ccb66e9c-28a3-407a-9e98-33cdfc33a105 
├─sda5 ext4   M2r16g   c0fe9982-bfcf-43b7-a26e-d480011ed2a0 /media/M2r16g
├─sda6 ext4   bd       84e26864-1cb9-4bd7-9cfd-915a847f1859 /media/bd
└─sda7 ext4   slit     f9e1a6e3-9ab1-4e97-ae1f-1d0f953d5ed4 /
sr0                                                         
sdb                                                         
├─sdb1 vfat   EFI-B    5576-CD7B                            
├─sdb2 ntfs   hdW7     0C7F14897F0DDEED                     
└─sdb5 ext4   hdKop    264e382b-4b5d-4a3f-87c0-69e9c36b43c5

Contents of Manjaro’s /etc/fstab :

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>                           <mount point>  <type>  <options>  <dump>  <pass>
UUID=DFDC-27CF                            /boot/efi      vfat    defaults,noatime 0       2
UUID=79492466-7c01-4f91-93b6-d7bc1a79f22d /              ext4    defaults,noatime 0       1
UUID=84e26864-1cb9-4bd7-9cfd-915a847f1859 /run/media/ja/bd ext4  defaults,noatime 0       2
UUID=4a557fab-5124-49d5-b531-2d023b88efef swap           swap    defaults,noatime 0       0
How to restore the normal GRUB Menu and to restore the correct GRUB version
#7

Now I am on liveUSB Manjaro 16.10.3 UEFI .

uname -a
Linux manjaro 4.4.33-1-MANJARO #1 SMP PREEMPT Fri Nov 18 18:06:44 UTC 2016 x86_64 GNU/Linux

Rest of commands:

sudo parted -l
Model: ATA ST3500413AS (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End    Size    File system     Name    Flags
 1      2098kB  317MB  315MB   fat32                   boot, esp
 2      317MB   105GB  105GB   ext4            M
 6      105GB   448GB  343GB   ext4            bd
 4      448GB   474GB  25.8GB  ext4            tst24g
 5      474GB   490GB  15.8GB  ext4
 7      490GB   491GB  1341MB  ext4            slitaz
 3      491GB   500GB  8869MB  linux-swap(v1)


Model: ATA FUJITSU MHY2200B (scsi)
Disk /dev/sdb: 200GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: 

Number  Start   End     Size    File system  Name              Flags
 1      1049kB  316MB   315MB   fat32        EFI System        boot, esp
 2      316MB   44.5GB  44.2GB  ntfs         W7                msftdata
 5      44.5GB  200GB   156GB   ext4         Linux filesystem

efibootmgr -v
BootCurrent: 000F
Timeout: 0 seconds
No BootOrder is set; firmware will attempt recovery

sudo blkid
/dev/sdb1: LABEL="EFI-B" UUID="5576-CD7B" TYPE="vfat" PARTLABEL="EFI System" PARTUUID="4f068499-e42c-40b2-b4b3-987edd834908"
/dev/sdb2: LABEL="hdW7" UUID="0C7F14897F0DDEED" TYPE="ntfs" PARTLABEL="W7" PARTUUID="376d94f8-a572-44f3-af71-ed6c89d3cffa"
/dev/sdb5: LABEL="hdKop" UUID="264e382b-4b5d-4a3f-87c0-69e9c36b43c5" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="f7e2466d-091e-4be1-8528-fe7f5c3ec800"
/dev/sda1: UUID="DFDC-27CF" TYPE="vfat" PARTUUID="33e218e3-f7ab-4b1e-8a65-15e52ee43baa"
/dev/sda2: LABEL="M" UUID="79492466-7c01-4f91-93b6-d7bc1a79f22d" TYPE="ext4" PARTLABEL="M" PARTUUID="30c70731-28aa-4c2e-8e9b-951f0dc0e81d"
/dev/sda3: UUID="4a557fab-5124-49d5-b531-2d023b88efef" TYPE="swap" PARTUUID="c6e308e6-60df-47f8-b803-ba0bc1f0d90f"
/dev/sda4: LABEL="testy24g" UUID="ccb66e9c-28a3-407a-9e98-33cdfc33a105" TYPE="ext4" PARTLABEL="tst24g" PARTUUID="4b970c56-4688-424b-97de-f3d9dd7ae00d"
/dev/sda5: LABEL="M2r16g" UUID="c0fe9982-bfcf-43b7-a26e-d480011ed2a0" TYPE="ext4" PARTUUID="e233939e-42a6-4eb8-b751-70477d0b4908"
/dev/sda6: LABEL="bd" UUID="84e26864-1cb9-4bd7-9cfd-915a847f1859" TYPE="ext4" PARTLABEL="bd" PARTUUID="26639df1-1172-45f7-9a84-b0144ba68889"
/dev/sda7: LABEL="slit" UUID="f9e1a6e3-9ab1-4e97-ae1f-1d0f953d5ed4" TYPE="ext4" PARTLABEL="slitaz" PARTUUID="aca6d5df-b090-4fe3-817b-ebb712772488"
/dev/sdc1: LABEL="P8G" UUID="14FE-45D0" TYPE="vfat" PARTUUID="24092408-01"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
[manjaro@manjaro ~]$

where /dev/sdc1 is a pendrive with liveUSB Manjaro 16.10.3

#8

There is a problem with the PC boot mode, I guess. Please check this when booting with Manjaro (installation or LiveISO)

At your GRUB menu, do not boot up to live OS, but press ‘c’ and you’ll get to the grub prompt

(grub>).

To be sure you’ve started up livecd in the right mode, at grub prompt, check output of

grub> echo $grub_platform

If output is pc, you’ve booted up in bios-legacy.
If output is efi, you’ve booted up in uefi.

Check your UEFI/BIOS settings to see if they were reset in any way and check what is recognized as boot options.
More troubleshooting tips here as already pointed.

Edit: I changed the title, as it was not informative of the issue, also tagged.

#9

Okay, got your information.
Understand. Your Manjaro you want is sda2
The other linuxes (sda5 and sda7) not important, don't care.

Just preliminary info for you.. I think your problem is..

efibootmgr -v
BootCurrent: 000F
Timeout: 0 seconds
No BootOrder is set; firmware will attempt recovery

I need some time, doing something else. Hang on for a while but looks to be rescueable.
Oh, since I need some time, windows.. sdb2 and $esp on sdb1, correct?
Windows booting okay ? (I don't think so) but confirm how you used to boot it.
Through Manjaro grub or F key?

Catch up with you later. (about 3 hours later)

@AgentS, there seems to have a lot of non-bootable OS's after recent updates in other topics elsewhere. Please help out if you can. I have no problem myself (after updates). What gives? (uh... what do you think is the problem?) Thanks.
Please help out.

1 Like
#10

@gohlip
A the moment sdb2 is empty .
(It is not a case now, but few weeks ago there was Windows XP installed there. In this time the whole sdb disk was under MBR and to login to Windows I was forced to switch in my EFI/Bios from "AHCI mode" to "Legacy Bios mode". But after removing Windows XP I converted the whole sdb disk from MBR to GPT with UEFI and computer runs now in "AHCI mode" only).

One more thing that I just noticed:
Something is broken in GRUB, where kernels 4.14 and 4.9 should be visible, but kernels 4.9 and 4.4 are visible.
In the case of booting with GRUB menu option - kernel 4.9, an error appears as in the first image of this thread.
In the case of booting with GRUB menu option - kernel 4.4 , there is an error : lack of kernel 4.4.

How to restore the normal GRUB Menu and to restore the correct GRUB version
#11

Sorry. Didn't take 3 hours and assemble the reply earlier than thought.
Here goes.

@majo, A few things first to clarify.
If your Manjaro disk (sda) or Windows disk (unlikely) is removable (like external), tell us and meantime do not ever pull out (if removable) before we get back to you.

Now try to boot to Manjaro (sda2), If you can, do it yourself.
If not, follow this way.. The link can guide, but I'll write again here what's relevant.

  1. Take the manjaro livecd and start it up in uefi.
  2. Do not boot up to live OS, but press ‘c’ at the menu and we’ll get to the grub prompt (grub>).
  3. To be sure you’ve started up livecd in theuefi mode, at grub prompt, check output of
    grub> echo $grub_platform
    If output is pc, you’ve booted up in bios-legacy.
    If output is efi, you’ve booted up in uefi.
    If you’re in the wrong mode, reboot livecd in uefi.
  4. Confirm Manjaro partition
    grub> ls (hd0,2)
    Does that state label='M' ?
    If not try
    grub> ls (hd1,2)
  5. Then
    grub> set root=(hd0,2) . . . . . {or set root=(hd1,2)} like this...
    grub> set root=(hd0,2)
    grub> ls ($root)/boot
    Copy down and confirm the listed vmlinuz and initrd files like "vmlinuz-4.14-x86_64" and "initramfs-4.14-x86_64.img"
  6. Continue.
    grub> linux /boot/vmlinuz-4.14-x86_64 rw
    grub> initrd /boot/initramfs-4.14-x86_64.img
    grub> boot

When booted to Manjaro sda2 OS, open terminal and do this
First confirm /boot/efi partition with

findmnt /boot/efi

Does that give sda1 ?
If it gives sdb1, change the "sudo efibootmgr -c -d" below line to sdb instead of sda.

sudo grub-install
sudo update-grub
sudo cp /boot/grub/x86_64-efi/core.efi /boot/efi/EFI/boot/bootx64.efi
sudo efibootmgr -c -d /dev/sda -p 1 -L "manjaro" -l "\EFI\Manjaro\grubx64.efi"

Done. Good luck.

Oh important reminder, and confirm please if disk is removable or not.
If your Manjaro disk (sda) or Windows disk (unlikely) is removable (like external), tell us and meantime do not ever pull out (if removable) before we get back to you.

[edit] - saw your last post, the above remains unchanged since but to add ...

If above at step 5, if
grub> ls ($root)/boot

does not give a good corresponding vmlinuz and initramfs, your system will be unbootable and you must reinstall.
But if there is either
vmlinuz-4.14-x86_64 and initramfs-4.14-x86_64.img
or
vmlinuz-4.9-x86_64 and initramfs-4.9-x86_64.img
Then use the right one for the commands.
But i can't see why any should be missing.

If any is missing, tell us what you think causes it.
It may be your guess, but it is better than nothing.
And what you think causes this problem in the first place.
( I thought you pulled out one of the disks)

#12

IMPORTANT

If you have kernel 4.9, look at this link.
It may be the solution

1 Like
A content of the entire system partition has been deleted
#13

As described by @benob, it worked for me too:

  1. Create manjaro usb and boot on it
  2. Open terminal
  3. Find your manjaro partition sudo fdisk -l
  4. If the live usb mounted your manjaro partion, umount /dev/sdaX
  5. Mount it: sudo mount /dev/sdaX /mnt
  6. Chroot to manjaro hard drive: manjaro-chroot /mnt /bin/bash
  7. Reinstall old package from pacman cache: 9. pacman -U /var/cache/pacman/pkg/linux49-4.9.105-1-x86_64.pkg.tar.xz
  8. Exit exit chroot
  9. Unmount unmount /mnt
  10. Reboot reboot

You should have something like this afterwards:

image

Do not re-update until the Kernel 4.9.106-1 gets fixed.

3 Likes
#14

The solution works :slight_smile:
Thanks you all for your help and especially for @gohlip and @marcottedan :slight_smile:

How to restore the normal GRUB Menu and to restore the correct GRUB version
#15

Thanks. WORKS!

And should mount patitions as your Reality.:grin:

#16

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Forum kindly sponsored by