Fixed Arch install error

Fixed by using grub.

Error when trying to boot into new install. ERROR: device ’ ’ not found. Skipping fsck. :: mounting ’ ’ on real root mount : /new_root: no valid filesystem type specified. ERROR: Failed to mount ’ ’ on real rootAnd I’m getting dropped in emergency shell. I used official wiki, used refind as bootloader. Second time I tried installing and got same error.
Edit1: fstab
`#/dev/nvme0n1p2
UUID=4dae009f-c08f-4636-b1b5-85a4713a6f40 / ext4 rw,relatime 0 1

#/dev/nvme0n1p1
UUID=0019-78B6 /boot vfat rw,relatime, fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2 `
p2 is root partition
p1 is efi partition.

Edit2: running timedatectl in chroot returns System has not been booted with systemd as init system (PID 1). Can’t operate. Failed to connect to bus: Host is down

yianiris,
@yianiris@kafeneio.social avatar

@Hiro8811

1 Did you boot the live medium with bios or efi?

2 Do you have libnvme and nvme-cli installed? If no, try them, if yes look up things on the manuals. It may be that your bootloader can't read/mount from the nvme

3 Ever since systemd-boot appeared things have been not working so well, now, have they?

luthis,

Both lines are commented out, # means that it is ignored

Hiro8811,

TheUUID is not comented out. Only nvme0n1p is

luthis,

Should there be a space between ‘relatime, flask=’ ? Is that in fstab? It should all be one string, like in mine mine rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro

Hiro8811,

It’s one line with no spaces but I’m writing on a phone and Jarboa autocorrect is ass.

Hiro8811,

Still same error

Nibodhika,

Refind does not generate the proper Configs when ran from the live image. From the wiki

Warning: When refind-install is run in chroot (e.g. in live system when installing Arch Linux) /boot/refind_linux.conf is populated with kernel options from the live system not the one on which it is installed. Edit /boot/refind_linux.conf and make sure the kernel parameters in it are correct for your system, otherwise you could get a kernel panic on your next boot. See .conf for an example file.

This is how my /boot/refind_linux.conf looks like:


<span style="color:#323232;">"Boot with standard options"  "rw root=/dev/nvme1n1p2"
</span><span style="color:#323232;">"Boot to single-user mode"    "rw root=/dev/nvme1n1p2 single"
</span><span style="color:#323232;">"Boot with minimal options"   "ro root=/dev/nvme1n1p2"
</span>
Hiro8811,

Using nano it just created new file

Nibodhika, (edited )

Have you mounted /boot? Usually it’s in a different partition so you’ll need to mount it.

Edit: yup, your boot is in a different partition according to your fstab

Hiro8811,

From where should I mount it? Emergency shell? Chroot?

Nibodhika, (edited )

Every time I made this mistake I booted again the live iso, mounted the boot drive and edit it.

Edit: you can also just edit the entry on refind directly to boot once on a correct config, and then fix it inside your actual system. The error is that the root filesystem will have an uuid that relates to the live iso image, not to your actual system.

Hiro8811,

I think I managed to mount it but what should I edit?

Nibodhika, (edited )

Ok, if I understood correctly your fstab what you should do is:

  1. Boot the live iso
  2. Run mount /dev/nvme0n1p1 /mnt
  3. run nano /mnt/refind_linux.conf
  4. Alter the file so it says this:

<span style="color:#323232;">"Boot with standard options"  "rw root=/dev/nvme0n1p2"
</span><span style="color:#323232;">"Boot to single-user mode"    "rw root=/dev/nvme0n1p2 single"
</span><span style="color:#323232;">"Boot with minimal options"   "ro root=/dev/nvme0n1p2"
</span>
  1. Save and close
  2. Unmount the drive umount /mnt
  3. Reboot

That should work

Edit: noticed my disk was 1 while yours is 0, didn’t remembered I had two ssds on that machine hahahah

Edit2: check that the file exists in /mnt, it should if you ran refind-install the first time.

Hiro8811,

I get the same error. Should I install grub?

Nibodhika,

Did you confirm that the file existed before editing? And that you were mounting the correct boot and not root partition?

I don’t know what else it can be if that doesn’t solve it.

yianiris,
@yianiris@kafeneio.social avatar

systemd doesn't like booting with ro, too dumb to check then mount filesystems.

@Nibodhika @Hiro8811

hperrin,

Check your /etc/fstab file to make sure your root partition is correctly specified, then rerun your bootloader install.

luthis,

Also come on guys, let’s prove that the Arch community isn’t all full of assholes, let’s help this dickhead sort their stupid ass issue.

(/s)

  • All
  • Subscribed
  • Moderated
  • Favorites
  • linux@lemmy.ml
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #