Unusual looking /boot directory

gingerheef · 2022-01-07 01:56:15

I recently installed Arch and during the installation process there were a few mistakes wherein I installed grub in /boot/efi instead of /boot. I had completed the installation after that (after installing grub in /boot) however my EFI system partition looks really messed up from what I know it should

$ ls /boot
dev   etc    initramfs-linux-fallback.img   proc   sys				 tmp   vmlinuz-linux
 EFI   grub   initramfs-linux.img	     run   'System Volume Information'	 var

I'm not sure what to do about this. It doesn't cause up any problems in during boot. But I can't seem to keep these files here knowing they're not supposed to be here

V1del · 2022-01-07 02:38:41

Looks like you did some broken chroot or so. actually look at the directories, all the ones that "are not supposed" to be there are normally system directories that should be empty now (... dev,etc,proc,sys,tmp,var,run). However this reads like you accidentally double mounted your rootfs.

Post your fstab and

mount

PS: GRUB is perfectly capable to boot kernels from a linux file system and installing GRUB into /boot/efi instead of /boot should not really be an issue (... and especially if you intend to have multiple kernels, you'll oft an have more space on your root rather than the ESP) assuming you did it at least correctly in so far to have /boot be a normal dir and /boot/efi the mountpoint of your ESP

gingerheef · 2022-01-07 03:50:50

V1del wrote:

PS: GRUB is perfectly capable to boot kernels from a linux file system and installing GRUB into /boot/efi instead of /boot should not really be an issue (... and especially if you intend to have multiple kernels, you'll oft an have more space on your root rather than the ESP) assuming you did it at least correctly in so far to have /boot be a normal dir and /boot/efi the mountpoint of your ESP

Oh. Ok. Didn't know that. thank you

my fstab

# Static information about the filesystems.
# See fstab(5) for details.

# <file system> <dir> <type> <options> <dump> <pass>
# /dev/nvme0n1p9
UUID=18cfe318-9136-4c6f-9e80-1bae9b6cc852	/         	ext4      	rw,relatime,stripe=32	0 1

# /dev/nvme0n1p10
UUID=f76c8e44-6e89-466d-919b-cad8c5cb83cb	/home     	ext4      	rw,relatime,stripe=32	0 2

# /dev/nvme0n1p1 LABEL=SYSTEM
UUID=C4DF-1710      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/nvme0n1p8
UUID=add90e6a-c073-4dbf-8111-9d069445aee2	none      	swap      	defaults  	0 0

$ mount
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sys on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
dev on /dev type devtmpfs (rw,nosuid,relatime,size=8020648k,nr_inodes=2005162,mode=755,inode64)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755,inode64)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
/dev/nvme0n1p9 on / type ext4 (rw,relatime,stripe=32)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,inode64)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
cgroup2 on /sys/fs/cgroup type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=13682)
mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime)
/dev/nvme0n1p10 on /home type ext4 (rw,relatime,stripe=32)
/dev/nvme0n1p1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,size=8028812k,nr_inodes=1048576,inode64)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=1605760k,nr_inodes=401440,mode=700,uid=1000,gid=1000,inode64)

V1del · 2022-01-07 07:37:04

Looks alright, then this should be as stated, check the mentioned directories, they should be empty and safe to remove.

gingerheef · 2022-01-07 08:46:02

Yes. 5 of them are empty.
/boot/etc has pacman.d/
/boot/var has cache/ lib/ log

Is it safe to assume removing these will not affect my system?

Thanks for you help again.

gingerheef · 2022-01-08 11:14:42

Okay. i have one more problem related to this and I'm need some help
https://ibb.co/0h3Wh6F
I seem to have two grubx64.efi files. I know only one is used and the other must've been created due to my faulty installation process. can you help me figure out which one. I don't want to delete the wrong one and brick my system

V1del · 2022-01-08 11:45:54

It should be safe to remove them check that you have the relevant equivalents in your / however, even having those there means you must have at some point ran an incorrect pacstrap with your /boot as the logical root (/)

The "canonical" one by a proper GRUB install is esp/EFI/GRUB/grubx64.efi to know which one is currently actually used check

efibootmgr -uv

it will show you which path your EFI knows about.

gingerheef · 2022-01-08 12:03:57

Thank you. It worked. I guess u can close this topic now. Is there something I should do to make it [SOLVED]

Slithery · 2022-01-08 12:06:19

CoC - How to post

AndroGR · 2022-01-09 00:09:54

Either the kernel confuses the boot partition with the root partition, or you messed up something during the installation. I doubt the first one unless it is a result of the second.

AndroGR · 2022-01-09 00:11:38

gingerheef wrote:

Okay. i have one more problem related to this and I'm need some help
https://ibb.co/0h3Wh6F
I seem to have two grubx64.efi files. I know only one is used and the other must've been created due to my faulty installation process. can you help me figure out which one. I don't want to delete the wrong one and brick my system

It's fine. Don't remove any, GRUB sometimes places more than one file. Especially if you distrohop or dual boot.

V1del · 2022-01-09 10:45:43

@AndroGR you are rather late here and GRUB will certainly not place itself twice with the same logical substructure just shifted a dir down. This was explicit misconfiguration induced by incorrectly mounting and reinstalling GRUB twice, which has now been solved.

Arch Linux

#1 2022-01-07 01:56:15

Unusual looking /boot directory

#2 2022-01-07 02:38:41

Re: Unusual looking /boot directory

#3 2022-01-07 03:50:50

Re: Unusual looking /boot directory

#4 2022-01-07 07:37:04

Re: Unusual looking /boot directory

#5 2022-01-07 08:46:02

Re: Unusual looking /boot directory

#6 2022-01-08 11:14:42

Re: Unusual looking /boot directory

#7 2022-01-08 11:45:54

Re: Unusual looking /boot directory

#8 2022-01-08 12:03:57

Re: Unusual looking /boot directory

#9 2022-01-08 12:06:19

Re: Unusual looking /boot directory

#10 2022-01-09 00:09:54

Re: Unusual looking /boot directory

#11 2022-01-09 00:11:38

Re: Unusual looking /boot directory

#12 2022-01-09 10:45:43

Re: Unusual looking /boot directory

Board footer