Have you tried/installed nvme-cli and/or xnvme
I wonder if your issues come from buggy nvme modules
this post was submitted on 24 Jan 2024
11 points (73.9% liked)
Linux
48314 readers
143 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
No that wasn't the problem. I should edit it as solved. What I did was delete the partitions and regenerate mkinicpio, delete all arguments and some grub configs. The efi partition still gets mounted but at least I need root privileges to modify and that's good enough
idk mybe your drive is fucked up so you should try a new one. also did you use fdisk or the graphical one ? and did you generate a new gpt/mbr tab ?
I solved it somewhat. There's only two entries in fstab now but for some reason the efi partition still gets automatically mounted and the grub theme dosen't work
- I think so, it ships with arch, right?
- I had it mounted in more places. First on /boot then in /grub and now it's in /efi.
- The grub.cfg config has always been in the same folder but I'll check it to make sure.
When I had an /efi mount just as arch said on wiki I didn't have problems. /boot stayed with root system, so it can be booted with efi or mbr.
If you have 2+ disks and one has mbr the other is gpt you can boot from either bootloader.
You should also try limine, less headaches than grub.
I have windows with broken efi partition on another disk but that's not important, or is it?
To turn os-prober on see /etc/default/grub -> false and install os-prober, then run grub-mkconfig -o ..
Dosen't work. At first the partition was dirty no I managed to run chxdisk(or whatever its called) and can mount it without hassle but it still dosen't appear in boot menu. I think there's something wrong with grub.cfg since the theme is not displaying but I don't know how to solve it
The theme itself is defined in grub.cfg, but it may be the case that it is stored in your root partition not in efi, so during bootloading the drive can't be read from.
So if you manually change the location of the theme directory and copy it inside efi it may work, and change the position of in grub.cfg
I was looking through commands history and I noticed something. If I'm mounting efi in /efi but I save grub-mkconfig -o to /boot/grub/grub.cfg during boot grub won't even notice the config file since root is not mounted. Should I save changes to /efi/grub/grub.cfg instead? Or /boot/grub/grub.cfg is the place it should be?
root must always be mounted if you have a system, either by booting or chroot. If you mount just efi from another system .
On my setup /efi/EFI/grub only has the grub efi binary no config, /boot and therefore /boot/grub is on /root partition
Now if you have the entire /boot in the /efi partition then it would be /efi/boot/grub/grub.cfg?
What I meant is that during boot efi partition gets mounted before root so it wouldn't be able to get config files from root partition. But that's not the problem, I tried regenerating grub. Most likely it's something wrong with the theme I applied. It keeps saying that it dosent found grub and that it should be mounted either in /efi or /boot but it is mounted. I'll try with grub-customizer.
Managed to get grub theme work so the grub is set up right. I guess I should stop being a help vampire. Anyway thanks for the help
@Hiro8811 not a problem, I learn while helping too, regrouping and refining what I know, through pain :)
If you have installed grub into that other efi then you may have the two, and you are customizing one and it boots another. You can use refind or hit F12 (or whatever it is in your mb) to select device and boot with other disk, see what it does. Usually linux os-prober is good at making an entry for windows booting too, but it would have been best to leave it alone.
Your windows system may be fine, it just needs the efi fixed or carried by grub.
reinstall arch without using archinstall maybe
I tried using archinstall but I got errors so I did it manually
expected
Expected me using it or getting errors?
both
Aha. If I modify them manually, what configs do I need to change?