New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
So the command to try would be the:
mdadm --manage /dev/md126 --add nvme1n1p2
Note, that im currently not in any chroot and I dont have anything mounted. Its just plain rescue.
Yup seems that way to me. Good luck.
root@rescue:~# mdadm --manage /dev/md126 --add nvme1n1p2
mdadm: nvme1n1p2 only meaningful with -r or -f, not -a
I wonder if this guide can help @jackb to figure out some command for my situation xD
https://www.thomas-krenn.com/en/wiki/Mdadm_recovery_and_resync
Need to specify the full path of the partition not just the name.
I consider this site a fairly good source.
Please explain me like im an idiot. And im fairly sure I am at this point. xD
It's probably in /dev
Looking better. Try to reinstall grub again from chroot and see if it works without error this time.
Mind giving me full mount commands for this situation from page 1 so I dont fuck up at this point? xD
mount /dev/md127 /mnt
mount /dev/md126 /mnt/boot
mount -t proc /proc /mnt/proc/
mount --rbind /sys /mnt/sys/
mount --rbind /dev /mnt/dev/
chroot /mnt
update-grub
I assume.
You'll need to mount as below:
Root
/mnt
Boot
/mnt/boot
Boot/efi (at least, I mount it if it is present. Not sure if it's strictly required for a grub reinstall or not)
/mnt/boot/efi
Then chroot as below.
https://superuser.com/a/417004
root@rescue:~# mount /dev/md127 /mnt
root@rescue:~# mount /dev/md126 /mnt/boot
root@rescue:~# mount -t proc /proc /mnt/proc/
root@rescue:~# mount --rbind /sys /mnt/sys/
root@rescue:~# mount --rbind /dev /mnt/dev/
root@rescue:~# chroot /mnt
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
root@rescue:/# update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.15.108-1-pve
Found initrd image: /boot/initrd.img-5.15.108-1-pve
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
root@rescue:/# ls /boot
System.map-5.15.108-1-pve efi initrd.img-5.15.108-1-pve pve
config-5.15.108-1-pve grub lost+found vmlinuz-5.15.108-1-pve
root@rescue:/# ls /boot/efi
I think I missed the EFI. Where do I get it again?
I'd be tempted to try a reboot at that point. Efi is probably your smallest partition, but I have a suspicion not mounting it during grub reinstall probably won't break anything.
root@rescue:~# mount /dev/nvme1n1p1 /mnt/boot/efi
root@rescue:~# chroot /mnt
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF-8)
root@rescue:/# ls /boot/efi/
EFI
Solved.
I did
Once more.
Will reboot now.
No luck yet.
Strange. Do you get the grub menu on reboot? Have you tried booting into an older kernel if so?
Here is the bootup process.. with everything above done.
Doesn't look like there's any old kernels available to me, though I'm not too familiar with proxmox.
Next thing I'd try is entering setup during the boot process and using a boot override to hit the second drive instead of the first.
If that doesn't work, it might be worth trying entering setup and change from UEFI boot mode to bios/legacy in case it's an issue with your EFI partition. Though, that's not something I've needed to do personally even though we've used UEFI boot for a number of years.
Second entry does the exact same thing.
I'm pretty sure that, at this point its probly best to re-install lol.
I do have these files elsewhere, so it should probly be enough to restore the VM?
That's you gone through my standard "Linux system doesn't boot" steps so my bet is this is proxmox related.
There's a variety of boot parameters that might be related e.g. noapic.
I'll try enabling noapic once more xD
If that fails, I'll just re-install. Would love to know if the .qcow2 file is enough to boot and restore Windows VM.
It gets stuck here with noapic grub option.
Do I need to use grub install into EFI? How would I target my EFI then?
I think its those 2x 500 MB partitions in lsblk output.
There was no saving it. I backed up the data, and Im now re-installing it.
Yes, it is.
Probably too late and just a hunch: The UUIDs might have changed plus iirc you mounted the non boot array first.
Short version: compare and be sure that /etc/fstab is OK and matching the actual UUIDs.
Anyway, I wish you good luck. May the patient survive and fully recover