You are not logged in.
Before yesterday I wouldn't consider myself a noob but I guess Arch will find a way.
fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# /dev/nvme0n1p5
/dev/nvme0n1p5 / ext4 rw,relatime 0 1
/etc/resolv.conf /etc/resolv.conf none rw,bind 0 0
/dev/nvme0n1p1 /boot vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro 0 2arch.conf
title Arch Linux
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options root=PARTUUID=0d44ccfc-4af8-ba47-afc6-9dcd50ccb3f7 rootfstype=ext4loader.conf
default arch.conf
timeout 4
console-mode max
editor noalso when I chroot in it loses the /boot mount and I have to mount it a second time
Last edited by Ghx5t (2024-09-17 07:04:49)
Offline
In what way is your boot "broken"? Please describe the actual problem in full.
I would ask why you've bind mounted /etc/resolv.conf to itself but I think I'll just live with the mystery, it doesn't seem relevant here.
I think these outputs would be useful, they can be run from any live ISO image:
efibootmgr -u
parted --list
blkidSharing method: https://wiki.archlinux.org/title/List_o … ted_client
Thanks!
Jin, Jîyan, Azadî
Offline
Okay that has something to do with it. I just successfully booted arch but it wouldn't connect to the Internet. so thinking the resolv.conf had something to do with that I erased the bind part. Now it says on boot
Failed to mount /etc/resolv.confOffline
fstab errors are fatal and you cannot not bind-mount a file.
Delete that line and focus on whatever you're actually trying to achieve with this nonsense - preferably in a new thread ![]()
Then please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.
Ftr.
also when I chroot in it loses the /boot mount and I have to mount it a second time
No, it's more that the target fstab is completely irrelevant when chrooting and the source /boot gets replaced by the target /boot (ie. eg. /mnt/boot) through the chroot.
Online
yeah, I got it figured out. I was just panicing somehow /etc/resolv.conf got put on fstab by genfstab
Thanks for your help. ![]()
Offline
you cannot not bind-mount a file
I thought that but:
$ findmnt -n /etc/resolv.conf
/etc/resolv.conf /dev/nvme0n1p2[/@rootfs/etc/resolv.conf] btrfs rw,relatime,ssd,space_cache=v2,subvolid=256,subvol=/@rootfs
$I think it would actually "work" if the filesystem was correctly listed in fstab (it says "none", which I should have noticed, sorry OP).
also when I chroot in it loses the /boot mount and I have to mount it a second time
Use this command after chrooting:
mount -a^ That will mount everything listed in /etc/fstab.
Jin, Jîyan, Azadî
Offline