You are not logged in.
I read on this post that I need to mount /boot before updating the kernel.
I'm sure I'm being super dense, but I don't know if I'm understanding what it means to mount /boot.
This is what I'm getting.
$ mount /boot
mount: can't find /boot in /etc/fstab
And when I try to get the uuid with
$ ls -l /dev/disk/by-uuid
I don't see a reference to /boot. How am I supposed to add it to my fstab?
I've also tried
$ lsblk -f
NAME FSTYPE LABEL UUID MOUNTPOINT
sda
├─sda1 vfat EFI 67E3-17ED
├─sda2 hfsplus Macintosh HD 26ff8b30-732b-329d-99fe-aa00493c9b1f
├─sda3 hfsplus Recovery HD 22be4c40-6473-3fa6-9748-d006672c6101
├─sda4 swap 228548e8-d797-460a-b141-692f7011bc0c [SWAP]
└─sda5 ext4 c0b1eb2b-ed87-4d0e-bf08-b7bfd81be877 /
Offline
It looks like you do not have a separate boot partition. You should know if you do. Did you create one when you installed archlinux? How did you install arch?
Please post the output of the following:
pacman -Q linux
uname -a
I suspect your actual problem has nothing to do with the presence/absence or mouting of a boot partition.
Mod note: not a sys admin issue, moving to N.C.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
No, I do not remember creating a boot partition. I was confused because I do have the /boot directory.
Pacman command:
$ pacman -Q linux
linux 4.5.1-1
Uname command:
$ uname -a
Linux turing 4.5.1-1-ARCH #1 SMP PREEMPT Thu Apr 14 19:19:32 CEST 2016 x86_64 GNU/Linux
Last edited by austincrft (2016-07-04 18:38:53)
Offline
So no issues there. Your problem is not at all related to the thread you linked to. You just have one similar symptom. So tell us about the symptoms: when did this start? What are the diagnostics? (eg, the output of the following)
ip a
lspci -vnn | grep -i net
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
It looks like you do not have a separate boot partition.
Eh? What about the EFI partition? That is the partition that should have an fstab entry for /boot
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
*headdesk*
Oops. Yes. Nevermind me. My previous posts are almost completely wrong. Sorry.
"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" - Richard Stallman
Offline
@OP: Which bootloader are you using?
systemd-boot will mount /boot automatically when needed.
You can mount /boot yourself with:
# mount /dev/sda1 /boot
EDIT: this presumes you have mounted /boot to the EFI system partition during installation.
Is this the case?
To generate an fstab entry you could then use:
grep sda1 /proc/self/mounts >> /etc/fstab
But it would probably be better to write the entry yourself with reference to `man fstab` & `man mount`
Last edited by Head_on_a_Stick (2016-07-04 21:29:02)
Offline
@OP: Which bootloader are you using?
I'm using rEFInd.
systemd-boot will mount /boot automatically when needed.
After reading the wiki page on this, I'm still a little unsure of what systemd-boot is. My understanding is that it's a boot manager like rEFInd. Does the info in the wiki page relate to me?
You can mount /boot yourself with:
# mount /dev/sda1 /boot
I tried updating the linux kernel after mounting like this. After a reboot, I noticed there was now another linux entry in rEFInd in addition to Arch. It just hung when I tried to load that one, not even progressing past the rEFInd screen. When I tried to load the Arch one, got this message on startup:
[FAILED] Failed to start Load Kernel Modules.
See `systemctl status systemd-modules-load.service` for details.
When I was dropped to the login prompt, I realized my laptop keyboard wasn't working, so I couldn't get in to view the logs.
I've since used the live disk to revert to 4.5.1-1.
EDIT: this presumes you have mounted /boot to the EFI system partition during installation.
Is this the case?
I can't remember exactly. What's the best way to tell?
Sorry for the inexperience, this is my first Arch install. Apparently I've got a lot more to learn.
Offline
Head_on_a_Stick wrote:EDIT: this presumes you have mounted /boot to the EFI system partition during installation.
Is this the case?
I can't remember exactly.
If you cannot remember such a fundamental detail then I cannot help you.
Offline
Head_on_a_Stick wrote:EDIT: this presumes you have mounted /boot to the EFI system partition during installation.
Is this the case?
I can't remember exactly. What's the best way to tell?
Sorry for the inexperience, this is my first Arch install. Apparently I've got a lot more to learn.
Look at the output of the mount command to see if it is mounted now.
Look at the contents of /etc/fstab (Which you may have created using a script [per the beginner's guide], but you were supposed to audit it [per the beginner's guide]) to see if is to be mounted at boot.
rEFInd is almost foolproof. Although, I did mess it up the first time I tried
systemd-boot is an alternative to rEFInd (as is GRUB)
Post your output of mount and the contents of your /etc/fstab if you've questions.
Last edited by ewaller (2016-07-05 21:38:06)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I don't see the /boot directory anywhere in the output of mount. I'm not completely sure what I should be looking for.
Output of 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=4040552k,nr_inodes=1010138,mode=755)
run on /run type tmpfs (rw,nosuid,nodev,relatime,mode=755)
/dev/sda5 on / type ext4 (rw,relatime,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/net_cls type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=808624k,mode=700,uid=1000,gid=10)
Contents of fstab:
# /dev/sda5
UUID=c0b1eb2b-ed87-4d0e-bf08-b7bfd81be877 / ext4 rw,relatime,data=ordered 0 1
# /dev/sda4
UUID=228548e8-d797-460a-b141-692f7011bc0c none swap defaults 0 0
Offline
% mount | grep /md | sort
/dev/md1 on /boot type ext2 (rw,relatime,block_validity,barrier,user_xattr,acl,stripe=4)
/dev/md3 on / type ext4 (rw,relatime,data=ordered)
/dev/md4 on /home type ext4 (rw,relatime,data=ordered)
All that means is that boot is a subdir of /. Nothing wrong with that.
Offline