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

  • Hellmo_luciferrari@lemm.eeOPEnglish
    2·
    9 months ago

    I sorted out Arch not booting. By taking out the Windows drive, Arch boots just fine.

    If I am not mistaken, having them on separate drives may have caused some issues. Someone else somewhere had suggested that is known to cause issues.

    Not sure if it’s windows and GRUB fighting even though they are on two separate hard drives.

    I did not end up trying os-prober at all. I went the more drastic method of removing the drive because the end goal is to ditch windows anyways.

    Though my issues with Arch are a completely different thing entirely. Mostly fighting with my GPU to cooperate.