Follow-up to installing Arch
Follow-up to installing Arch
So, I am making the switch to using Arch full time instead of Windows.
Here is the rundown:
I have windows installed on one NVME and installed Arch on another NVME. After installing Arch on the one drive, and rebooting Arch hung at loading initial ramdisk. It never completed, I force shutdown my PC.
I went back into bios, and there wasn't an entry for my Arch drive whatsoever.
In fact, before this happened I had all bootable drives go missing from within my bios.
So, after the reboot, I left the boot options default, and it did in fact boot to windows.
Other potentially important details:
I used archinstall rather than walking through manually.
UEFI
Secureboot off
GRUB bootloader
Unified Kernel Images on
Luks encrypted BTRFS partitions
Audio Pipewire
Kernels: Linux and Linux-Zen
Network Manager
Hardware:
CPU: i7-12700KF
Motherboard: TUF GAMING Z690-PLUS WIFI D4
GPU: EVGA GeForce RTX 3090 FTW3
RAM: Corsair VENGEANCE® RGB PRO 16GB (x4)
PSU: EVGA SuperNOVA 1000 GT 1000W
Drives: 1tb WD Black SN750 (Drive intended for Arch to be installed on)
1tb Samsung 980 Pro (Drive windows is installed on)
2tb Samsung 980 Pro (separate data drive)
Should I remove my windows drive while installing Arch on another drive?
Rather, what would be the best approach to this?
Could anyone provide any help regarding this?
Edit: More details
What boot loader are you using? That is what allows you to pick between what OS (in your case, drive) to boot at power-on.
Are you using UEFI for this?
I am using UEFI, and GRUB for my bootloader. I did update my post with a bit more information now.
I was not able to select boot order in BIOS because it wasn't reporting properly, or my drives were "messed up" along the way.
I did not have the option for my Windows drive listed as a bootable option. It did however show a generic entry for my WD Black drive (which is what I installed Arch on) as a bootable entry, but it ended up booting to windows after forcing the machine down because Arch hung at initializing Ramdisk.
I had the afterthought to choose to install os-prober for grub within additional packages.
Hmm.
Not being able to select boot order in BIOS suggests something very strange is going on, because it suggests that the BIOS can't see all the drives. That has to happen before the bootloader can be evoked.
It sounds like GRUB is installed on the WD Black. BIOS -> drives it can see -> boot loader
What was the specific error that the Arch boot attempt threw? How did os-prober work for you?
Installing arch on OneDrive is an entertaining concept
But Microsoft would cuck your Arch install if it were somehow installed onto onedrive D':
It would still somehow manage to overwrite whatever would pass for a boot loader
This is the guide I followed when I was installing Arch manually. I hope the method has not changed. Make sure to choose the correct partition if you're planning on dual booting.
Here is an alternative Piped link(s):
https://www.piped.video/watch?v=68z11VAYMS8
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I'm open-source; check me out at GitHub.
So did you actually turn off secure boot in your UEFI setup? Or did you just state that it's off to archinstall?
I turned it off in bios. Sorry for confusion due to order of information or wording.
From past forums reading I remember that a boot loader in Linux can have trouble booting properly when you use two different physical drives (Rather than one drive and different partitions), I think it needs to specifically get to know about both drives. Does this help ?
That very well may help, I read a bit of what you sent. I will have to try when not at work. Thank you!
I had a similar issue with my laptop, where Arch wouldn't be recognized as a bootable system on my NVMe drive unless I disabled RST with Optane on the BIOS, setting it to AHCI mode.
I do remember seeing a similar issue a while ago as well, but I don't remember if the user managed to fix it.
I could suggest removing the Windows drive, installing Arch and checking if everything works, then plugging the Windows drive back in. Windows loves to delete non-Windoes bootloaders from every drive it can.
Ultimately, I removed the windows drive, it booted. But yay Novideo, I mean Nvidia drivers on arch is a pain.
have you turned off avx512
I have not, but I can look into how to do that. What would that do, if I may ask?
it's an instruction set only available in early 12th gen intel chips, so you can usually go into the bios and find settings to turn it off.