[SOLVED] Boot Managers don't detect my partition

bspk · 2021-07-25 21:26:13

Edit: Solved, see V1del's post below

I'm trying to install Arch on my new HP laptop. I have replaced the NVMe SSD with a empty 500GB one. I created 2 partitions, one for the EFI and the other one for Arch itself.
The installation goes well but when I reboot my device, it doesn't find my partition.

GRUB:

Starting version 249.2-1-arch
ERROR: device 'UUID=c6821fb7-c7ba-4b06-a7c4-498987319221' not found. Skipping fsck.
mount: /new_root: can't find UUID=c6821fb7-c7ba-4b06-a7c4-498987319221.
You are now being dropped into an emergency shell.

It does pretty much the same thing with systemd; it times out trying to find the device.

I don't know if it can be useful but here is how I manually installed Arch:

mkfs.vfat /dev/nvme0n1p1
mkfs.ext4 /dev/nvme0n1p2
mount /dev/nvme0n1p2 /mnt
mkdir -p /mnt/boot/efi
mount /dev/nvme0n1p1 /mnt/boot/efi
pacstrap /mnt base linux linux-firmware vim git intel-ucode
genfstab -U /mnt >> /mnt/etc/fstab
arch-chroot /mnt
dd if=/dev/zero of=/swapfile bs=1M count=8192
chmod 600 /swapfile
mkswap /swapfile
swapon /swapfile
echo "/swapfile	none	swap	defaults	0	0" >> /etc/fstab

// define hostname, gen locale...

pacman -S grub efibootmgr networkmanager network-manager-applet linux-headers
grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=GRUB
grub-mkconfig -o /boot/grub/grub.cfg
exit
umount -a
reboot

I previously tried with some installer scripts, same result. The only thing that worked was trying to install PopOS which is completely different but it might be useful to know?.

I have absolutely no idea what I can provide to help. Hence the Newbie Corner
I've been browsing the forum and found pretty much the same issue but I don't really understand the thread...

Last edited by bspk (2021-07-25 23:09:46)

ewaller · 2021-07-25 21:33:50

Boot from the install media and post the output of lsblk -fs

bspk · 2021-07-25 21:42:10

Here it is:

NAME      FSTYPE   FSVER            LABEL       UUID                                 FSAVAIL FSUSE% MOUNTPOINTS
loop0     squashfs 4.0                                                                     0   100% /run/archiso/airootfs
sda1      iso9660  Joliet Extension ARCH_202107 2021-07-01-13-49-18-00                     0   100% /run/archiso/bootmnt
└─sda     iso9660  Joliet Extension ARCH_202107 2021-07-01-13-49-18-00                              
sda2      vfat     FAT16            ARCHISO_EFI 8319-ECE0                                           
└─sda     iso9660  Joliet Extension ARCH_202107 2021-07-01-13-49-18-00                              
nvme0n1p1 vfat     FAT32                        BF58-BCF3                                           
└─nvme0n1                                                                                           
nvme0n1p2 ext4     1.0                          c6821fb7-c7ba-4b06-a7c4-498987319221                
└─nvme0n1

ewaller · 2021-07-25 21:58:02

That looks correct. What if you (as a test) use the volume path instead of the UUID?

bspk · 2021-07-25 22:17:15

I am not sure I did that the correct way. I changed this in the /boot/grub/grub.cfg file:

root=UUID=c6821fb7-c7ba-4b06-a7c4-498987319221

to

root=/dev/nvme0n1p2

but it gives me that:

Starting version 249.2-1-arch
ERROR: device '/dev/nvme0n1p2' not found. Skipping fsck.
mount: /new_root: no filesystem type specified
You are now being dropped into an emergency shell.

V1del · 2021-07-25 22:53:27

Make sure the drive is set to AHCI mode and not RAID in the BIOS, or if you don't find a relevant setting mount all relevant partitions and chroot add/change

MODULES=( vmd )

in your /etc/mkinitcpio.conf and regenerate your initramfs with

mkinitcpio -P

PythonLinux · 2021-07-25 22:57:14

Not a Grub expert and still trying to get a fully working and stable Arch install on my laptop myself (so take with a grain of salt) but it looks like one of 3 things: 1)Some SATA mode issue (which is what I had and since I have a terrible UEFI and can't change it I had to attempt to use Systemd and enable the vmd module in mkinitcpio 2)a corrupt file system of some sort 3) Some sort of weird fstab error.
Edit: See v1del's better comment

Last edited by PythonLinux (2021-07-25 22:59:48)

bspk · 2021-07-25 23:07:17

V1del wrote:

Make sure the drive is set to AHCI mode and not RAID in the BIOS, or if you don't find a relevant setting mount all relevant partitions and chroot add/change
MODULES=( vmd )
in your /etc/mkinitcpio.conf and regenerate your initramfs with
mkinitcpio -P

Oh it's working, and that's the only thing I didn't try in the other thread. Unfortunately I don't see anything related to that in the BIOS. Is there a way to switch from RAID to AHCI from somewhere else?

Edit: I googled that and it seems that HP laptops can't switch from RAID to AHCI...

Last edited by bspk (2021-07-25 23:10:42)

PythonLinux · 2021-07-25 23:24:10

No wonder I couldn't switch modes.

PythonLinux · 2021-07-26 00:03:31

I'm gonna try the commands in this thread and see if I can get Grub working
Edit: Nope this is not the magical fix that makes Grub work. I still get the error.

Last edited by PythonLinux (2021-07-26 00:24:04)

Arch Linux

#1 2021-07-25 21:26:13

[SOLVED] Boot Managers don't detect my partition

#2 2021-07-25 21:33:50

Re: [SOLVED] Boot Managers don't detect my partition

#3 2021-07-25 21:42:10

Re: [SOLVED] Boot Managers don't detect my partition

#4 2021-07-25 21:58:02

Re: [SOLVED] Boot Managers don't detect my partition

#5 2021-07-25 22:17:15

Re: [SOLVED] Boot Managers don't detect my partition

#6 2021-07-25 22:53:27

Re: [SOLVED] Boot Managers don't detect my partition

#7 2021-07-25 22:57:14

Re: [SOLVED] Boot Managers don't detect my partition

#8 2021-07-25 23:07:17

Re: [SOLVED] Boot Managers don't detect my partition

#9 2021-07-25 23:24:10

Re: [SOLVED] Boot Managers don't detect my partition

#10 2021-07-26 00:03:31

Re: [SOLVED] Boot Managers don't detect my partition

Board footer