Re: major booting issues after installing debian 12.6 with speech on a dual boot system with windows 10 pro 64 bits on another drive that is mountable after the debian installation
Hello,
Again, this is a question for debian-boot@lists.debian.org where all the
people with all booting experience are.
Samuel
nick@nickgawronski.com, le lun. 21 oct. 2024 19:45:11 -0500, a ecrit:
> Hi, I have installed debian 12.6 successfully on my System76 Serval WS 11
> laptop on the first nvme drive that is two terabytes. On the second drive I
> have windows 10 pro 64 bits which is also two terabytes and have two more
> drives that are four terabytes in size. All drives including the windows
> drive and the other storage drives are mountable and I can access their
> data. During the installation grub told me that it can modify the nvram to
> have grub boot into debian by default but I told it no as I am totally blind
> and had someone set the uefi boot order so that the windows drive was booted
> first. Now when I reboot I hear the grub beep and no windows option and
> os-prober is running as it told me that it could not detect any other
> operating systems during installation. I did some reading and it appears
> there is an esp partition that contains the efi boot files which only exists
> on the first nvme drive with debian and no windows efi files exist. I did
> look in the windows partition and found lots of .efi files and tried copying
> bootmgr into another directory /boot/efi/efi/windows that I created but no
> luck. What method can I use to repair this system so I can use the system
> where debian does not even touch windows and where I can easily choose the
> windows boot option or make it the default as update-grub says nothing about
> this issue and no os-prober output is given if I run it as root I just get
> put back to the shell? Does debian or another service besides Aira which is
> paid and does not really know much about linux exist where I can do a video
> call or some type of remote access where they can remote into this linux
> system to try to fix windows? Nick Gawronski
Reply to: