After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

Utini · 2022-02-08 20:31:23

Hello again ,

today my laptop got a new motherboard. After the change I couldn't boot GRUB anymore.

So I booted the Arch_USB in order to try re-installing GRUB.

lsblk shows me my two nvme SSDs.

/dev/nvme0n1:
/dev/nvme0n1/p1 Windows Recocery environment
/dev/nvme0n1/p2 EFI Systems
/dev/nvme0n1/p3 Microsoft Reserved
/dev/nvme0n1/p4 Microsoft Basic Data

/dev/nvme1n1:
/dev/nvme1n1/p1 EFI Systems
/dev/nvme1n1/p2 Linux Filesystem
/dev/nvme1n1/p3 Linux LVM

However, when trying to xmount /dev/nvme1n1 /mnt" I get:
mount: /mnt: wrong fs type, bad option, bad superblock on /dev/nvme1n1, missing codepage or helper program, or other error.

I have done this several times already but never encountered this error

Thanks!

V1del · 2022-02-08 20:35:30

n1 is the namespace not a partition. You need to mount the partitions. i.e.

mount /dev/nvme1n1p3 /mnt
mount /dev/nvme1n1p2 /mnt/efi

or whatever

Utini · 2022-02-08 20:47:41

V1del wrote:

n1 is the namespace not a partition. You need to mount the partitions. i.e.
mount /dev/nvme1n1p3 /mnt
mount /dev/nvme1n1p2 /mnt/efi
or whatever

Ah stupid me. And ofcourse I also have to decrypt the volume.

I now did:

cryptsetup open /dev/nvme1pn3 cryptlvm

Now I have:
/dev/mapper/cryptlvm 953.47 GB, 1999579791 sectors
/dev/mapper/MyLVM-root 953.47 GB, 1999577088 sectors

I guess I need to mount MyLVM-root to /mnt and then proceed as normal in chroot?

@edit:
I sucessfully decrypted and opened my LVM container but wouldn't this be the correct command rather than the one I used?
cryptsetup luksOpen /dev/nvme1n1p3 cryptdisk

Last edited by Utini (2022-02-08 20:49:41)

loqs · 2022-02-08 21:07:44

Utini wrote:

I now did:
cryptsetup open /dev/nvme1pn3 cryptlvm

Utini wrote:

wouldn't this be the correct command rather than the one I used?
cryptsetup luksOpen /dev/nvme1n1p3 cryptdisk

cryptsetup.8#BASIC_ACTIONS

Utini · 2022-02-08 21:10:39

Yep you were faster than I was checking the wiki.

So I mounted everything and re-installed GRUB.
How ever, I still cannot boot from my "Linux SSD" (as in GRUB is not loading, BIOS tells me some hardware is missing).
I read that I probably have to somehow restore missing NVRAM keys/entries that were lost or changed due to the motherboard change?

As a reference, this is what I did so far:

- cryptsetup luksOpen /dev/nvme1n1p3 lvm
- fdisk -l                                #to verify the correct /dev/mapper/path for mounting the correct LVM container
- mount /dev/mapper/MyVolGroup-whatever /mnt 
- mount /dev/nvme1n1p2 /mnt/boot                #mounting the boot partition according to "fdisk -l"
- mkdir /mnt/esp                             #creating random mnt folder
- mount /dev/nvme1np1 /mnt/esp                    #mounting EFI to random mnt folder
- arch-chroot /mnt
- ls -al /boot/                           #to verify I mounted correctly
- grub-install --target=x86_64-efi --boot-directory=/boot --efi-directory=/esp --removable
- grub-mkconfig -o /boot/grub/grub.cfg      
- exit
umount -R /mnt
reboot

Last edited by Utini (2022-02-08 21:27:26)

Utini · 2022-02-09 05:14:15

Does that mean I have to re-generate fstab entries?

So after mountain all partitions but before chroot, I would need to run:

genfstab -U /mnt >> /mnt/etc/fstab

Or is creating NVRAM keys/entries smth else?

V1del · 2022-02-09 07:54:46

NVRAM keys is running the grub-install command without the removable flag so that the EFI firmware boot menu has more entries. With the removable flag GRUB will allocate an appropriate entry, with the removable flag it will be placed at then default location that has to be able to be booted by selecting the drive rather than an entry. If you intend to move this drive around the NVRAM entries are cleared anyway so with the removable flag you can still boot that (the problem of that is that there's only one fallback path, potentially contested by multiple operating systems)

Utini · 2022-02-09 18:05:39

V1del wrote:

NVRAM keys is running the grub-install command without the removable flag so that the EFI firmware boot menu has more entries. With the removable flag GRUB will allocate an appropriate entry, with the removable flag it will be placed at then default location that has to be able to be booted by selecting the drive rather than an entry. If you intend to move this drive around the NVRAM entries are cleared anyway so with the removable flag you can still boot that (the problem of that is that there's only one fallback path, potentially contested by multiple operating systems)

Well I tried to run grub-install without removable flag but that didn't help.

- cryptsetup luksOpen /dev/nvme1n1p3 lvm
- fdisk -l                                #to verify the correct /dev/mapper/path for mounting the correct LVM container
- mount /dev/mapper/MyVolGroup-whatever /mnt 
- mount /dev/nvme1n1p2 /mnt/boot                #mounting the boot partition according to "fdisk -l"
- mkdir /mnt/esp                             #creating random mnt folder
- mount /dev/nvme1n1p1 /mnt/esp                    #mounting EFI to random mnt folder
- arch-chroot /mnt
- ls -al /boot/                           #to verify I mounted correctly
- grub-install --target=x86_64-efi --boot-directory=/boot --efi-directory=/esp
- grub-mkconfig -o /boot/grub/grub.cfg      
- exit
umount -R /mnt
reboot

No errors in the output but I am still not getting to GRUB when booting :S

V1del · 2022-02-09 18:41:09

efibootmgr installed/what's the output of

efibootmgr -uv

what's the new MB exactly? MSI boards are notoriously buggy and will only boot the fallback path, the fallback path will only be booted if you explicitly set the "drive" as the first priority in the UEFI boot order

Utini · 2022-02-09 19:35:18

V1del wrote:

efibootmgr installed/what's the output of
efibootmgr -uv
what's the new MB exactly? MSI boards are notoriously buggy and will only boot the fallback path, the fallback path will only be booted if you explicitly set the "drive" as the first priority in the UEFI boot order

Output as screenshot:
http://imgur.com/a/TGifaDH

I tried booting "arch" and from "nvme1n1" via BIOS. Both wont work. Booting "nvme1n0" boots Windows (as it is installed on that nvme drive).

It is a laptop (Lenovo Thinkpad X1 Extreme Gen 1) which just a warranty replacement motherboard.

@edit: Oh now "arch" suddenly boots grub!

Last edited by Utini (2022-02-09 19:38:24)

Arch Linux

#1 2022-02-08 20:31:23

After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

#2 2022-02-08 20:35:30

Re: After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

#3 2022-02-08 20:47:41

Re: After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

#4 2022-02-08 21:07:44

Re: After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

#5 2022-02-08 21:10:39

Re: After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

#6 2022-02-09 05:14:15

Re: After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

#7 2022-02-09 07:54:46

Re: After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

#8 2022-02-09 18:05:39

Re: After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

#9 2022-02-09 18:41:09

Re: After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

#10 2022-02-09 19:35:18

Re: After motherboard change: Can't mount /dev/nvme1n1 to re-install grub

Board footer