I strongly suspect that your parted output is not from your installed system but from the loopback image on the USB drive.
Now I’m using the USB drive, but the main HDD which has got Manjaro installed can’t boot. No kernel seem to be installed.
I’ve used parted with chmod, I don’t know if it can still cause problems.
I found these, see what can be utilized from these in your case.
1 Like
This is why I didn’t want to make grub-install (if not necessary) 
With update-grub it should have worked fine. We didn’t have any indication that grub install was broken, just that the grub menu config file needed an update.
1 Like
But it didn’t, and right now I don’t even know what we’re dealing with anymore. 
Let’s start from the beginning. What error are you getting when you try to boot Manjaro?
Please boot from the installation USB, chroot to your Manjaro system and run the following:
parted -l
lsblk -f
And post the output of the commands
1 Like
Here`s parted output:
Model: ATA ST1000DM003-1ER1 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 556MB 555MB ntfs Basic data partition hidden, diag
2 556MB 661MB 105MB fat32 EFI system partition boot, esp
3 661MB 677MB 16.8MB Microsoft reserved partition msftres
4 677MB 788GB 787GB ntfs Basic data partition msftdata
5 788GB 1000GB 212GB ntfs Basic data partition msftdata
Model: USB DISK 3.0 (scsi)
Disk /dev/sdb: 15.5GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
2 3120MB 3124MB 4194kB primary esp
Model: ST500LT0 12-1DG142 (scsi)
Disk /dev/sdc: 500GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 491GB 491GB primary ext4 boot
2 491GB 500GB 8791MB primary linux-swap(v1)
Here you are lsblk output:
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0
loop1
loop2
loop3
sda
|-sda1
|-sda2
|-sda3
|-sda4
`-sda5
sdb
|-sdb1
`-sdb2
sdc
|-sdc1 329.1G 22% /
`-sdc2
sr0There are problems with kernel, so I don’t know if bash could work.
So you’ve got three drives…
-
/dev/sdahas a GPT partition table and has an EFI system partition, but apart from that, it holds only Windows partitions. -
/dev/sdbhas an MSDOS partition table and holds only an EFI system partition. -
/dev/sdchas an MSDOS partition table, and it holds your Manjaro root filesystem and a swap partition.
Using an MSDOS partition table in combination with UEFI boot is possible, but it’s not recommended, and it’s officially not supported in Manjaro because not all UEFI implementations can handle that.
Also, the fact that you’ve got two separate EFI system partitions ─ while not a problem ─ makes things confusing, because if you install GRUB, which of the two EFI system partitions does it use? Or is Manjaro actually booting in legacy mode and is your GRUB really installed in the MBR of /dev/sdc?
I forgot to mention the errors I get at boot:
error: can't find command 'fwsetup'
Press any key to continue...
Failed to boot both default and fallback entries.
Press any key to continue...
Yes, but /dev/sdb is the USB medium. /dev/sda and /dev/sdc are two completely different drives. Honestly I don’t know why why the partition table is MSDOS, when I’ve installed Manjaro on /dev/sdc/ I’ve used mostly the default settings.
It seems you didn’t run lsblk with -f parameter. But anyway, If I understand this correctly, you have Windows installed in UEFI mode, but Manjaro was installed in BIOS mode. How do you select what OS to boot?
The fwsetup error comes from grub that I think is trying to open UEFI setup from the BIOS mode. You are booting your USB in UEFI mode and that tries to prepare grub menu config in for UEFI mode (even if you actually boot your Manjaro in BIOS mode).
What I actually recommend you is to boot Manjaro also in UEFI mode. For that:
- Boot once again your USB in UEFI mode and chroot to your Manjaro
- Create a mount point for the EFI partition:
mkdir /boot/efi - Mount EFI partition there:
mount /dev/sda2 /boot/efi - Install grub to the EFI partition:
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck - Update grub menu config:
update-grub - Reboot
This has one small problem. It makes your Manjaro install to depend on your Windows disk (because there is where the EFI partition resides). You can also try to do a EFI partition in your Manjaro disk, but I don’t want to mess up things still more.
Option B is just continue the way things were, so:
- Boot once again your USB but this time in BIOS mode and chroot to your Manjaro
- Check that your Manjaro drive is still
/dev/sdcwithparted -l - Reinstall grub:
grub-install --recheck /dev/sdc - Update grub menu config:
update-grub - Reboot
You decide which way to go…
2 Likes
I select what OS to boot by accessing UEFI boot override settings. To make it clear, it’s not like dual booting, in fact Windows can’t recognize Manjaro as the alternative OS.
It never happened to me before.
It gives me this output:
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
grub-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
Now Manjaro is in UEFI mode, an I can confirm that by looking at the boot ovverride UEFI settings section. It still can`t boot, no errors are shown, I can see just a black screen for about 20 seconds and then my machine reboots.
Did you do an install-grub now? (Don’t need to do it now, just want to know)
Can you check have you a Manjaro folder somewhere in /dev/sda2 (mount it first):
mount /dev/sda2 /mnt
ls -al /mnt/EFI
# or
ls -al /mnt/efi
Please, show the output of sudo efibootmgr -v (To check is there a Manjaro entry there and where it points)
chroot to your Manjaro and run ls -al /boot (show us the output)
1 Like
I issued just the grub-install command you mentioned in the last reply.
ls -al /mnt/EFI output:
total 5
drwxr-xr-x 5 root root 1024 Sep 3 12:04 .
drwxr-xr-x 4 root root 1024 Jan 1 1970 ..
drwxr-xr-x 2 root root 1024 Nov 23 2019 Boot
drwxr-xr-x 2 root root 1024 Sep 3 12:04 manjaro
drwxr-xr-x 4 root root 1024 Nov 23 2019 Microsoft
efibootmgr output:
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0000,0003,0004,0002,0001
Boot0000* Windows Boot Manager HD(2,GPT,95adc510-bfad-4de5-9a1f-cb5d8fdb3e7f,0x109000,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}...6................
Boot0001* CD/DVD Drive BBS(CDROM,,0x0)..GO..NO........O.H.L.-.D.T.-.S.T. .D.V.D.R.A.M. .G.H.2.4.N.S.C.0.................>..Gd-.;.A..MQ..L.1.K.E.7.F.9.3.I.5.4. .0. . . . . . . . ........BO
Boot0002* Hard Drive BBS(HD,,0x0)..GO..NO........O.S.T.1.0.0.0.D.M.0.0.3.-.1.E.R.1.6.2.................>..Gd-.;.A..MQ..L. . . . . . . . . . . . .4.Z.1.Y.5.M.H.M........BO..NOu.......G. .U.S.B. .D.I.S.K. .3...0.................6..Gd-.;.A..MQ..L.7.F.0.0.9.C.E.0.E.2.D.0.8.2.0.0........BO..NO........c.S.T.5.0.0.L.T.0.1.2.-.1.D.G.1.4.2.................R..Gd-.;.A..MQ..L.F.F.5.0.0.F.F.0.1.2.0.0.0.0.0.0.0.0.0.0.0.0.F.3.F.F.F.F.6.F........BO
Boot0003* UEFI: USB DISK 3.0 PciRoot(0x0)/Pci(0x14,0x0)/USB(16,0)/HD(1,MBR,0x0,0x5cf8f0,0x2000)..BO
Boot0004* manjaro HD(2,GPT,95adc510-bfad-4de5-9a1f-cb5d8fdb3e7f,0x109000,0x32000)/File(\EFI\manjaro\grubx64.efi)
ls -al /boot output:
total 3116
drwxr-xr-x 5 root root 4096 Sep 3 14:03 .
drwxr-xr-x 18 root root 4096 Jul 21 11:00 ..
drwxr-xr-x 2 root root 4096 Sep 3 14:03 efi
drwxr-xr-x 6 root root 4096 Sep 3 14:04 grub
-rw-r--r-- 1 root root 3161088 Jun 16 19:50 intel-ucode.img
-rw-r--r-- 1 root root 23 Aug 7 11:22 linux414-x86_64.kver
-rw-r--r-- 1 root root 0 Aug 7 12:11 linux57-x86_64.kver
drwxr-xr-x 2 root root 4096 Jun 6 10:03 memtest86+Everything is there, except for the kernels and initramfs. 
What are linux414-x86_64.kver and linux57-x86_64.kver? They don’t have executive permissions.
[nx-74205:/dev/pts/3][/home/aragorn]
[14:13:12][aragorn] > file /boot/linux54-x86_64.kver
/boot/linux54-x86_64.kver: ASCII text
[nx-74205:/dev/pts/3][/home/aragorn]
[14:13:32][aragorn] > cat /boot/linux54-x86_64.kver
5.4.60-2-MANJARO x64
[nx-74205:/dev/pts/3][/home/aragorn]
[14:14:02][aragorn] >
Please post also output of (from chroot):
cat /etc/fstab
lsblk -f
You are going to need to install/reinstall some kernel. Chroot to your Manjaro (and make sure that EFI partition is also mounted in /boot/efi)
pacman -Sy linux57
mount
update-grub
Please, post the output of all commands. “Work” or “don’t work” it’s not enough.
1 Like
cat /etc/fstab output:
# /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=010a5748-c34c-42d4-8546-400ea5be93f0 / ext4 defaults,noatime 0 1
UUID=22c150a3-8ecd-4ffc-a168-341770672ed4 swap swap defaults,noatime 0 2
lsblk -f output:
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0
loop1
loop2
loop3
sda
|-sda1
|-sda2 69.3M 28% /mnt
|-sda3
|-sda4
`-sda5
sdb
|-sdb1 329.1G 22% /
`-sdb2
sdc
|-sdc1
`-sdc2
sr0
pacman -Sy linux57 output:
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
resolving dependencies...
looking for conflicting packages...
Packages (1) linux57-5.7.17-2
Total Download Size: 84.44 MiB
Total Installed Size: 145.46 MiB
:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
linux57-5.7.17-2... 84.4 MiB 9.27 MiB/s 00:09 [###################] 100%
(1/1) checking keys in keyring [###################] 100%
(1/1) checking package integrity [###################] 100%
(1/1) loading package files [###################] 100%
(1/1) checking for file conflicts [###################] 100%
error: failed to commit transaction (conflicting files)
linux57: /boot/linux57-x86_64.kver exists in filesystem
Errors occurred, no packages were upgraded.
mount output:
/dev/sdb1 on / type ext4 (rw,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (ro,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=1925800k,nr_inodes=481450,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
shm on /dev/shm type tmpfs (rw,nosuid,nodev,relatime)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
tmp on /tmp type tmpfs (rw,nosuid,nodev)
overlay on /etc/resolv.conf type overlay (rw,relatime,lowerdir=/run/miso/sfs/livefs:/run/miso/sfs/mhwdfs:/run/miso/sfs/desktopfs:/run/miso/sfs/rootfs,upperdir=/run/miso/overlay_root/upper,workdir=/run/miso/overlay_root/work,index=off)
/dev/sda2 on /mnt type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
/dev/sda2 on /boot/efi type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
update-grub output:
bash: $'u\303\303pdate-grub': command not found