You are not logged in.
I have windows 10 installed on disk 1 (installed this first -- has its own EFI partition on disk 1).
I have archlinux installed on disk 0 (has its own EFI partition on disk 0 -- 1gig, 4k cluster size.).
using UEFI.
secure boot and all that jazz is disabled. TPM disabled. Everything security related in bios is disabled.
fast boot disabled (100% positive there's no hibernation file). Sleep disabled.... windows defender disabled. All exploit protection disabled. Everything that can be disabled is disabled -- performance is close to enough to win7 (not quite, but close enough).
Everything is fine... EXCEPT:
When I boot into windows (doesn't matter if it's through grub or bios ), it wants to run chkdsk. Doesn't say what partition. 8 sec countdown.
If I let it do what it wants (the chkdsk scan), it doesn't scan the windows C drive (it completes way too quickly). It seems to scan the new EFI partition on disk 0. Completes almost immediately, and boot continues. Windows runs fine.
After that, the efi partition for arch linux is gone from the bios uefi boot menu.
Boot from arch installer usb, mount the efi partition... mount reports a filesystem error -- mounted in read only mode.
Blow the whole thing away, and start over.
Same problem.
Windows' chkdsk on arch's efi partition on disk 0 trashes the fat32 filesystem.
It'll keep wanting to do the chkdsk every single time --- until I remove the efi partition on disk 0. That's the only thing that makes it happy.
There is no scheduled chkdsk. It's doing this as some kind of security measure, but I have secure boot disabled so I dunno what it's thinking.
If I DO schedule a chkdsk on C on reboot, it'll scan C (takes a minute or 2)... says it's successful... and then it hangs -- gotta pull the plug. Then it goes back to wanting to scan the efi partition on disk 0 all over again.
Changing the boot order in bios doesn't change this weird win10 chkdsk behavior.
My google-fu has failed me, so trying these forums.
I don't want win10 and linux to use the same EFI partition. I may as well just boot ubuntu live from usb.
I really wanted to be able to use grub on disk 0 to choose whatever linux flavors I have installed on disk 0, +win10 on disk 1.
Any ideas?
Is it borked SPECIFICALLY because win10 is on drive 1 and I'm putting arch on drive 0 (instead of vice versa? Why should that even matter?
UPDATE:
Solved by formatting the linux efi partition from within win10 using diskpart. With the same exact parameters (fat32, 4k cluster size, labeled LINUX_BOOT).
It shouldn't have worked because it's the SAME EXACT THING... but it did... so it's not the same exact thing, apparently.
So... there's SOMETHING different about mkfs.fat -F 32 -S 4096 -n LINUX_BOOT that win10 didn't like.
Gonna schedule a chkdsk on C to see if it still hangs afterwards... if you don't hear from me, everything is fine.
Last edited by Daemonjax (2023-08-21 02:06:55)
Offline