Yeah no go.
that first command sudo mount /dev/sda1 mnt gives the error
Mount: /mnt: unknown filesystem type ‘ext4’. Dmesg(1) May have more information after failed mount system call.I’m sorry. Thanks for your help tho.
I give up, I’ll re-install. But I don’t know which option to choose: erase, replace, or manual.
And you won’t. Bios can’t be read in UEFI. Why are you not installing in UEFI instead of Bios? If it were me and the system has UEFI then make sure CSM is disabled along with secure boot and reinstall Windows in UEFI mode and then install EOS.
Good luck!
This was the original problem: I couldn’t get bios to read USB UEFI, I tried like four different methods to make live isos: balenca, grub2win, and two others I can’t recall.
Bios never gave me an option to boot off a USB.
If the system is running in UEFI there should be no reason that it can’t boot off of usb.
Edit: If secure boot is not disabled i could see it. I also always clear the keys.
Edit2: Plus i disable CSM.
I dunno, I’m at my max computer knowledge.
I can’t install anything from a USB in legacy, BIOS just won’t give me the option. Even with a blank hard drive when I started, BIOS in UEFI wouldn’t load an iso.
I’ll wipe everything again and start from scratch again, I just don’t understand what I’m doing wrong. It’s like the fifth time.
I’m not sure I’m following you here. If the computer is UEFI and you have it set to run in UEFi mode only. No legacy, not Bios and secure boot is disabled and CSM is turned off. Then it will not boot in Bios. So it should boot the live EOS ISO in UEFI mode.
Edit: Also as I said I always clear secure boot keys first before disabling secure boot.
I swear to god I’m going to figure this out.
Can boot into Win10 via Grub.
Following this guide on getting grub to read EN.
Here’s where I am stuck, I updated everything
:: Searching databases for updates…
:: Searching AUR for updates…
there is nothing to do
[root@EndeavourOS liveuser]# sudo mount /dev/sda1 /mnt
mount: /mnt: /dev/sda1 already mounted on /mnt.
dmesg(1) may have more information after failed mount system call.
[root@EndeavourOS liveuser]# sudo su
[root@EndeavourOS liveuser]# sudo mount --bind /dev /mnt/dev
[root@EndeavourOS liveuser]# sudo chroot /mnt
[root@EndeavourOS /]# grub-install /dev/sda
Installing for i386-pc platform.
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
Installation finished. No error reported.
[root@EndeavourOS /]#
This is my grub file: (which I understand like zero)
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
insmod part_gpt
insmod part_msdos
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 bd583318-445a-4c80-9452-60139baa46eb
else
search --no-floppy --fs-uuid --set=root bd583318-445a-4c80-9452-60139baa46eb
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=en_US
insmod gettext
fi
terminal_input console
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 bd583318-445a-4c80-9452-60139baa46eb
else
search --no-floppy --fs-uuid --set=root bd583318-445a-4c80-9452-60139baa46eb
fi
insmod gfxmenu
loadfont ($root)/boot/grub/themes/EndeavourOS/unifont-regular-16.pf2
insmod png
set theme=($root)/boot/grub/themes/EndeavourOS/theme.txt
export theme
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'EndeavourOS Linux, with Linux linux' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-advanced-bd583318-445a-4c80-9452-60139baa46eb' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 bd583318-445a-4c80-9452-60139baa46eb
else
search --no-floppy --fs-uuid --set=root bd583318-445a-4c80-9452-60139baa46eb
fi
echo 'Loading Linux linux ...'
linux /boot/vmlinuz-linux root=UUID=bd583318-445a-4c80-9452-60139baa46eb rw loglevel=3 nowatchdog nvme_load=YES
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux.img
}
menuentry 'EndeavourOS Linux, with Linux linux (fallback initramfs)' --class endeavouros --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-linux-fallback-bd583318-445a-4c80-9452-60139baa46eb' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 bd583318-445a-4c80-9452-60139baa46eb
else
search --no-floppy --fs-uuid --set=root bd583318-445a-4c80-9452-60139baa46eb
fi
echo 'Loading Linux linux ...'
linux /boot/vmlinuz-linux root=UUID=bd583318-445a-4c80-9452-60139baa46eb rw loglevel=3 nowatchdog nvme_load=YES
echo 'Loading initial ramdisk ...'
initrd /boot/initramfs-linux-fallback.img
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
menuentry 'UEFI Firmware Settings' $menuentry_id_option 'uefi-firmware' {
fwsetup
}
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg
fi
### END /etc/grub.d/41_custom ###
[root@EndeavourOS /]#
Further up in the thread, you have been given links to guides on EndeavourOS Wiki on how to restore Grub bootloader. I would follow instructions in those articles.
you have been given links to guides on EndeavourOS Wiki
I followed repair a non-booting Grub Wiki, making sure to chroot from Arch-Root wiki.
I got the output below.
[root@EndeavourOS /]# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
Found theme: /boot/grub/themes/EndeavourOS/theme.txt
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/initramfs-linux.img
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
Found fallback initrd image(s) in /boot: initramfs-linux-fallback.img
/proc/devices: fopen failed: No such file or directory
/proc/devices: fopen failed: No such file or directory
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.
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: Unable to open /proc/mounts or /etc/mtab
ERROR: finding sysfs mount point
ERROR: mkdir /var/lock/dmraid
grep: /proc/mounts: No such file or directory
Cannot find list of partitions! (Try mounting /sys.)
done
[root@EndeavourOS /]# exit
exit
[root@EndeavourOS liveuser]# grub-mkconfig -o /boot/grub/grub.cfg
/usr/bin/grub-probe: error: failed to get canonical path of `airootfs'.
[root@EndeavourOS liveuser]# sudo grub-mkconfig -o /boot/grub/grub.cfg
/usr/bin/grub-probe: error: failed to get canonical path of `airootfs'.
[root@EndeavourOS liveuser]# sudo su
[root@EndeavourOS liveuser]# cd ..
[root@EndeavourOS home]# cd ..
[root@EndeavourOS /]# sudo grub-mkconfig -o /boot/grub/grub.cfg
/usr/bin/grub-probe: error: failed to get canonical path of `airootfs'.
[root@EndeavourOS /]#
Now, when I open terminal I get the error message: failed to execute child, failed to open PTY: no such device.
Not really wanting to bother people here and feeling dumb, I made a post in r/endeavourOS and got another path to try.
Going to re-boot to the liveiso.
I feel like such a dumbass.
I would reinstall EnOS at this stage:
Good luck!
But that would mean that you have booted up your Live USB in UEFI mode.
During the course of this thread, several times suggestions have been made to disable Legacy/CSM mode in your firmware settings.
You said before that doing so you couldn’t boot up your live USB in UEFI mode.
I am a bit confused by the contradictory info.
I’m sorry about that. That’s why I wanted to start another thread.
While trying to get Win10 installed, I was using a trial and error with three different isos: one direct from Microsoft where you have to enter your email and get a link, one from TPB, and one from a website I can’t remember.
I was using ventoy, grub2win, etcher, yumi, and rufus. I’d try one loader on my mac, and load each live iso in turn and try to install using UEFI. When the USBs wouldn’t be recognized in UEFI, I’d switch to the next bootloader, try each iso. Nothing worked. I then flashed the BIOS starting from the versions A01 to A06, then start again with the first loader, first iso. Then first loader, second iso. On and on.
After three days, some combination worked. I can’t remember which, my desk was a mess with so many USBs and I was so frustrated.
I didn’t want to be a pia to the community, my thread was getting so much attention and felt embarrassed to ask for any more help. I thought I could just follow the wikis and google my way into the dual boot. After all, I finally got a boot into UEFI. But after making a few Reddit threads, re-doing the wikis, and still a no go, I thought making a separate thread was a good idea.
I’m really sorry for the trouble. I’m honestly thankful for all the help you guys have given me.
If you keep doing the same things that failed before, you will always fail.
This is a Universal Law.
Start from zero.
Don’t read ANY tutorials, only follow advice from forum support.
If you don’t understand some terminology, ask for explanation here.
efibootmgr
If it gives error, continue with installation.
Post back, when you finished the above.
Your current drives are all MBR partitioned, so your easy way is to not install on UEFI.
If you want UEFI installation it’s a longer road and I wouldn’t suggest it, unless you are experienced.
Your Windows is already installed in Legacy mode on a disk with msdos partition table.
If you want to follow the Path of Least Resistance, boot up your Live USB in Legacy mode and:
Just reiterating what was said above by @petsam 
EFI variables are not supported on this system