Hello, world!
I recently noticed that the GRUB boot menu is not detecting Windows 10. I uncommented /added GRUB_DISABLE_OS_PROBER=false and when I try to use sudo update-grub It doesn’t complete and freezes after “Its output will be used to detect bootable binaries on them and create new boot entries.”
Any solution?
How long do you wait until you stop it? If I recall it right, in some situations, it can take up to 2 minutes to run the update-grub command.
Also you can try to clarify what’s happening with the system logs. Update-grub logs there what it is doing:
journalctl -b -xe
sda error 
if this command does not freeze, can you paste here sudo fdisk -l text ouput ( not screenshot 
)
I added a HDD few month back but It was working fine at that moment. Here’s the output of sudo fdisk -l
Disk model: ST3200826AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xacaa964a
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 206847 204800 100M c W95 FAT32 (LBA)
/dev/sda2 206848 81919999 81713152 39G 7 HPFS/NTFS/exFAT
/dev/sda3 81920000 235519999 153600000 73.2G 7 HPFS/NTFS/exFAT
/dev/sda4 235520000 390719487 155199488 74G 7 HPFS/NTFS/exFAT
Disk /dev/sdb: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: ST3500418AS
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x085ca783
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 2048 1187839 1185792 579M 7 HPFS/NTFS/exFAT
/dev/sdb2 1187840 213250047 212062208 101.1G 7 HPFS/NTFS/exFAT
/dev/sdb3 213250048 585140223 371890176 177.3G 7 HPFS/NTFS/exFAT
/dev/sdb4 585142270 976771071 391628802 186.7G 5 Extended
/dev/sdb5 937404416 976771071 39366656 18.8G 82 Linux swap / Solaris
/dev/sdb6 585144318 711096319 125952002 60.1G 83 Linux
/dev/sdb7 711098368 937402367 226304000 107.9G 83 Linux
Partition table entries are not in disk order.
Disk /dev/loop0: 9.52 MiB, 9977856 bytes, 19488 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop1: 99.38 MiB, 104202240 bytes, 203520 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop2: 55.42 MiB, 58114048 bytes, 113504 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop3: 99.38 MiB, 104210432 bytes, 203536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop4: 55.44 MiB, 58134528 bytes, 113544 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop5: 61.77 MiB, 64770048 bytes, 126504 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop6: 162.87 MiB, 170778624 bytes, 333552 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop7: 61.73 MiB, 64729088 bytes, 126424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop8: 164.76 MiB, 172761088 bytes, 337424 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop9: 243.91 MiB, 255762432 bytes, 499536 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop10: 65.1 MiB, 68259840 bytes, 133320 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop11: 62.2 MiB, 65224704 bytes, 127392 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop12: 225.27 MiB, 236208128 bytes, 461344 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop13: 32.29 MiB, 33853440 bytes, 66120 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop14: 32.3 MiB, 33865728 bytes, 66144 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop15: 122.01 MiB, 127934464 bytes, 249872 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop16: 128.29 MiB, 134524928 bytes, 262744 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop17: 74.63 MiB, 78254080 bytes, 152840 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop18: 62.93 MiB, 65986560 bytes, 128880 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop19: 75.38 MiB, 79044608 bytes, 154384 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop20: 62.89 MiB, 65949696 bytes, 128808 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop21: 242.25 MiB, 254021632 bytes, 496136 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk /dev/loop22: 242.24 MiB, 254005248 bytes, 496104 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes```A guy on some forum had the same issue, changing kernal to real time fixed his issue. I also tried that OS installs that kernal but doesn’t switch to it.
The following packages will be installed:
linux510-rt
linux510-rt-virtualbox-host-modules
linux510-rt-r8168
linux510-rt-headers
Starting
resolving dependencies...
looking for conflicting packages...
Packages (4) linux510-rt-5.10.52_rt47-3 linux510-rt-headers-5.10.52_rt47-3 linux510-rt-r8168-8.049.02-3 linux510-rt-virtualbox-host-modules-6.1.24-3
Total Installed Size: 205.49 MiB
:: Proceed with installation? [Y/n]
checking keyring...
checking package integrity...
loading package files...
checking for file conflicts...
checking available disk space...
:: Processing package changes...
installing linux510-rt...
Optional dependencies for linux510-rt
crda: to set the correct wireless channels of your country [installed]
installing linux510-rt-virtualbox-host-modules...
===> You must load vboxdrv module before starting VirtualBox:
===> # modprobe vboxdrv
installing linux510-rt-r8168...
>>> The module r8168 conflicts with r8169. You can blacklist it with:
>>> `echo "blacklist r8169" > /etc/modprobe.d/r8169_blacklist.conf`
installing linux510-rt-headers...
:: Running post-transaction hooks...
(1/5) Arming ConditionNeedsUpdate...
(2/5) Updating module dependencies...
(3/5) Install DKMS modules
(4/5) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux510-rt.preset: 'default'
-> -k /boot/vmlinuz-5.10-rt-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-rt-x86_64.img
==> Starting build: 5.10.52-3-rt47-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [autodetect]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [plymouth]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-rt-x86_64.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux510-rt.preset: 'fallback'
-> -k /boot/vmlinuz-5.10-rt-x86_64 -c /etc/mkinitcpio.conf -g /boot/initramfs-5.10-rt-x86_64-fallback.img -S autodetect
==> Starting build: 5.10.52-3-rt47-MANJARO
-> Running build hook: [base]
-> Running build hook: [udev]
-> Running build hook: [modconf]
-> Running build hook: [block]
-> Running build hook: [keyboard]
-> Running build hook: [keymap]
-> Running build hook: [plymouth]
-> Running build hook: [resume]
-> Running build hook: [filesystems]
-> Running build hook: [fsck]
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-5.10-rt-x86_64-fallback.img
==> Image generation successful
(5/5) Updating Grub-Bootmenu
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-5.10-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-x86_64-fallback.img
Found linux image: /boot/vmlinuz-5.10-rt-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-5.10-rt-x86_64.img
Found initrd fallback image: /boot/initramfs-5.10-rt-x86_64-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
mkdir: cannot create directory '/var/lib/os-prober/mount': File exists
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
Done ...
This is the output I had when I tried to switch to real time kernal.
It says “mkdir: cannot create directory ‘/var/lib/os-prober/mount’: File exists” after warning: os-prober" line.
I don’t have anything else in that folder but a labels file. You can try to delete everything else there. I think even the labels file can be deleted.
It can also be just the result of interrupting the previous run of update-grub (which runs os-prober in the background)
Boot a live ISO and perform an fsck on all partitions of sda. There are obvious read errros on some sectors.
What also looks strange is that sda is msdos parted (with MBR) but seems to carry with sda1 an ESP, why? Are you booting in UEFI ro BIOS mode? To verify run
test -d /sys/firmware/efi && echo efi || echo bios
To see the Windoze system as entry in grub’s boot menu, Windoze and your Manjaro must be installed in the same mode.
Uhh, I think I know the reason why so many things are wrong with my OS. I was using an HDD (500GB) with Dual Book on it. Then I went ahead and attached a second HDD in the first header data header. So my original sda1, sda2 and sda3s become sdb1, sdb2 and sdb3. I don’t know exactly but I am assuming this. And when I used pamac. What do you think about this? would switching harddrive had an impact on my pc? does this make any sense? 