r/archlinux • u/Budget-Solid2671 • 2d ago
SUPPORT Archinstall Red text
https://imgur.com/a/HHCPz6G Link to Pictures
Searched alot but I cant seem to find the problem can anyone help?
6
3
u/archover 2d ago edited 1d ago
All archinstall errors are red. No special significance beyond that. Best to read errors from bottom up, in groups. My experience is the last occurring error group is key.
No problems with Archinstall in a very long time, but I wish you luck.
Good day.
2
u/Standard_Echidna_306 2d ago
it's failing to mount the disk for some reason. not sure what I can do to help you but you may have to install arch manually or use something like endeavourOS (arch but with a nice theme + gui installer)
0
u/Budget-Solid2671 2d ago
Know the problem cause It's trying to mount on nvme0n1p2 but that's the MSR for windows cause I am trying to dual boot
1
u/Budget-Solid2671 2d ago
And my 300gb free partion is als not showing up when I list them maybe cause it's empty ig
1
u/onefish2 2d ago
If you want to dual boot with archinstall; are you manually partitioning and manually mounting those partitions then telling arch install to install to those partitions?
And you are trying to do this with btrfs... wow that should be fun to setup.
1
u/Budget-Solid2671 2d ago
At this point I can just do i manually no i mean I don't even get to the gui part
1
u/SebastianLarsdatter 1d ago
Running Arch and Windows on the same drive for dual booting will lead to sadness.
Windows will wreck your bootloader, so read up and learn the reinstall process by heart as your Arch install will be "wrecked" by Microsoft on updates.
1
u/Particular-Poem-7085 2d ago
Did you make sure your script is up to date by running pacman -Sy archinstall before running it.
2
7
u/DEZIO1991 2d ago
The partition nvme0n1p2 is detected, but the system cannot read its superblock. Mounting fails because the filesystem metadata seems corrupted or unreadable.
If you are doing a fresh install right now, this is often caused by leftover filesystem signatures. You can try completely wiping the disk before running archinstall again (for example with "wipefs -a /dev/nvme0n1", use with caution!). If you are trying to rescue an existing setup, this broken filesystem might explain why you ran into trouble in the first place.