Boost.python error in job bootloader

First of all sorry for disturbance.
But I really want to dual boot my HP laptop ( win 8.1 and Garuda)
I know there is also a same topic, I found but I don't understand well cause I am not from IT field or have any experience in computer
So please tell me in layman langauge
I make a bootable pendrive with Garuda and boot with USB hard disk (UEFI)
and then boot with open driver
select install Garuda linux
After basic information
Select replace a partition
After 7-10 min the following error show

Please check in your BIOS if you are booting in UEFI mode and that secure boot is disabled (if such option is available in your BIOS).
Post also the restults of

sudo fdisk -l
lsblk -f
1 Like

First of all Thank you very much for reply
in boot option device i select usb (UEFI) to boot and i disable secure boot and fastboot
and below is the output of the both command

Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: WDC WD10JPVX-60J
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0xfc515ad7

Device     Boot     Start        End    Sectors   Size Id Type
/dev/sda1  *         2048     718847     716800   350M  7 HPFS/NTFS/exFAT
/dev/sda2          720896  204804095  204083200  97.3G  7 HPFS/NTFS/exFAT
/dev/sda3       204806142 1867505663 1662699522 792.8G  f W95 Ext'd (LBA)
/dev/sda5       204806144  817940479  613134336 292.4G  7 HPFS/NTFS/exFAT
/dev/sda6       817942528 1867502887 1049560360 500.5G  7 HPFS/NTFS/exFAT

Partition 3 does not start on physical sector boundary.


Disk /dev/sdb: 14.45 GiB, 15514730496 bytes, 30302208 sectors
Disk model: Storage Media   
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: 0x00000000

Device     Boot   Start     End Sectors  Size Id Type
/dev/sdb1  *         64 4796259 4796196  2.3G  0 Empty
/dev/sdb2       4796260 4804451    8192    4M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 17.67 MiB, 18530304 bytes, 36192 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: 364.28 MiB, 381972480 bytes, 746040 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: 1.11 GiB, 1193598976 bytes, 2331248 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: 709.05 MiB, 743497728 bytes, 1452144 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/zram0: 1.92 GiB, 2062544896 bytes, 503551 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram1: 1.92 GiB, 2062544896 bytes, 503551 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram2: 1.92 GiB, 2062544896 bytes, 503551 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Disk /dev/zram3: 1.92 GiB, 2062544896 bytes, 503551 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
NAME   FSTYPE FSVER  LABEL                      UUID                                 FSAVAIL FSUSE% MOUNTPOINT
loop0  squash 4.0                                                                          0   100% /run/miso/
loop1  squash 4.0                                                                          0   100% /run/miso/
loop2  squash 4.0                                                                          0   100% /run/miso/
loop3  squash 4.0                                                                          0   100% /run/miso/
sda
├─sda1 ntfs          System Reserved            01D8118C548FE640
├─sda2 ntfs                                     01D8118CE06DB750
├─sda3
├─sda5 ntfs          Game                       01D8118CE69863F0
└─sda6 ntfs          Storage                    01D8106667B62AD0
sdb    iso966 Joliet GARUDA_DR460NIZED_SOARING_ 2021-05-07-11-01-06-00                     0   100% /run/miso/
├─sdb1 iso966 Joliet GARUDA_DR460NIZED_SOARING_ 2021-05-07-11-01-06-00
└─sdb2 vfat   FAT12  MISO_EFI                   BF22-740A
sr0
zram0                                                                                               [SWAP]
zram1                                                                                               [SWAP]
zram2                                                                                               [SWAP]
zram3                                                                                               [SWAP]

Please read

Your disk is MBR based, so you shouldn't boot in UEFI mode. Select something like Legacy mode (depending on the naming)

5 Likes

WOW its Work
Thank you very much
i check both the OS work pretty well
:joy: when i boot the windows the damage/corrupt image show i think windows get corrupted but later after a minute it start and work well
before ending the discussion
can i turn on Fastboot ? cause i feel windows take more time to start

1 Like

I strongly suggest to avoid the use of windows fast boot, because it kind of keeps on-hold some HW resources, like Wifi and blootooth cards, etc, that might then not work in Garuda the next time.
Furthermore, with fastboot on I think you should never change (add, update, delete) from Garuda any file in the Windows partiton, becuase that could get kind of corrupted. At least this might occur from Windows 10, where fast boot is actually an hibernation. I don't remember about win8.1...
You can try if you want, but then just remove it before opening a new topic for relevant problems :slight_smile:

3 Likes

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