On 10/22/26 3:22 PM, [email protected] wrote:
When booted /boot isnt needed anymore right?
Whats the difference between /boot partition and grub partition?
I am not aware of grub partitions.
But you will need your /boot partition to be present when using
grub-install and grub-mkconfig.
I suspect you have now a directory /boot with grub information on your
nvme0n1p2.
What is on your /boot partition (nvme0n1p1) is a question now !
The Arch Wiki mentions that the installation of GRUB on an UEFI system is:
grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB
Since you cannot boot your Arch Linux system normally I think you should
try to boot from the Arch ISO.
If possible then mount /dev/nvme0n1p2 to /mnt and /dev/nvme0n1p1 to
/mnt/boot (after cleaning the present /mnt/boot)
Then go into arch-chroot -S /mnt and retry the installation of grub and
check /boot.
Make sure there is a kernel by running mkinitcpio -P.
After that exit the arch-chroot and umount /dev/nvme0n1p1 and
umount /dev/nvme0n1p2 and restart the computer.
I reinstalled grub with grub-install /dev/nvme0n1 nvme0n1p1 is the
boot partition nvme0n1p2 is the root.
And then grub-mkconfig -o /boot/grub/grub.cfg, this finished without
reporting any errors.
Zitat von Zerro <[email protected]>:
On 10/22/26 2:57 PM, [email protected] wrote:
I did something really stupid:
I booted the sytem, unmounted the boot partition and reinstalled grub.
Oh virtual media I think is just a supermicro term(?), I mean just
mount a ISO File in the supermicro interface.
Its not a multi boot system.
Best,
Lucienne
You write you unmounted the boot partition, how did you do that ?
Do you remember how you reinstalled grub, with what command ?
~Zerro
Zitat von Zerro <[email protected]>:
On 10/22/26 2:25 PM, [email protected] wrote:
GPT.
But the partitions itself were formatted as MBR.
I dont know how this works - maybe protective mbr?
Internet mentions for protective mbr:
A GPT disk always has a "protective MBR" placed in LBA 0 purely for
legacy tools so they don’t mistake the unreadable GPT disk for an
unformatted drive, though it does not contain actual MBR
Sounds as you have a GPT disk.
In the Bios I tried both, to boot from legacy and dual.
Then I would choose dual.
Right now I also have the problem, that the bios does not
recognize my main partition anymore: I reset the BIOS Boot Order,
and now all other drives show up (which wasnt the case before),
but not the one, that should boot.
Maybe the drive is also corrupted?
I can't get physical access though right now - only IPMI, but it
also does not let me mount virtual media because I need some kind
of supermicro licence.
... :(
The server has more than one physical drive ?
Also is it a multi-boot system ?
virtual media ?
And moreover how could you install GRUB on a not booting system ?
Regards, ~Z
Zitat von Zerro <[email protected]>:
On 10/22/26 9:16 AM, [email protected] wrote:
Hello,
I switched my boot partition, changed its label from
"legacy_boot" to "bios_grub" (grub-install wouldnt work otherwise).
I have a btrfs root, and my boot partition is ext4 (I don't know
why someone did that, I just inherited it. But it worked in the
past.)
I did a grub-install /dev/nvme0n1 and a grub-mkconfig -o
/boot/grub/grub.cfg and added the parition to my fstab to mount
as /boot.
Now when I boot, it only shows "GRUB _" (with a blinking cursor
after it), and I cannot input anything.
I have a supermicro server and I am accessing the server on its
remote console.
Can anyone help me debug this? (Supermicro remote console is
also kinda shitty, tbh)
Best,
Lucienne
May I ask is that disk a MBR or GPT partitioned disk ?
The Arch GRUB Wiki page mentions different installation
instructions for GRUB GPT UEFI and GRUB MBR.
Also the BIOS should be instructed to use the right UEFI or
legacy MBR ?
Regards, ~Z
