[SOLVED] Problems booting system: "Failed to mount /boot"

maartenvanschagen · 2020-04-13 20:48:31

My system started to have problems booting and I can't figure out why exactly.
I get the error messages "Failed to mount /boot" and "Failed to start Load Kernel Modules".
The systemd-modules-load service does indeed result in a failure (in journalctl logs).

I think I have found the error message in the journalctl logs:

Apr 14 12:03:48 maarten-arch systemd-fsck[506]: There are differences between boot sector and its backup.
Apr 14 12:03:48 maarten-arch systemd-fsck[506]: This is mostly harmless. Differences: (offset:original/backup)
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   90:33/0e, 91:c9/1f, 92:8e/be, 93:d1/77, 94:bc/7c, 95:f4/ac, 96:7b/22
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 97:8e/c0, 98:c1/74, 99:8e/0b, 100:d9/56, 101:bd/b4, 102:00/0e, 103:7c/bb
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 104:88/07, 105:56/00, 106:40/cd, 107:88/10, 108:4e/5e, 109:02/eb
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 110:8a/f0, 111:56/32, 112:40/e4, 113:b4/cd, 114:41/16, 115:bb/cd
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 116:aa/19, 117:55/eb, 118:cd/fe, 119:13/54, 120:72/68, 121:10/69
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 122:81/73, 123:fb/20, 124:55/69, 125:aa/73, 126:75/20, 127:0a/6e
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 128:f6/6f, 129:c1/74, 130:01/20, 131:74/61, 132:05/20, 133:fe/62
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 134:46/6f, 135:02/6f, 136:eb/74, 137:2d/61, 138:8a/62, 139:56/6c
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 140:40/65, 141:b4/20, 142:08/64, 143:cd/69, 144:13/73, 145:73/6b
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 146:05/2e, 147:b9/20, 148:ff/20, 149:ff/50, 150:8a/6c, 151:f1/65
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 152:66/61, 153:0f/73, 154:b6/65, 155:c6/20, 156:40/69, 157:66/6e
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 158:0f/73, 159:b6/65, 160:d1/72, 161:80/74, 162:e2/20, 163:3f/61
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 164:f7/20, 165:e2/62, 166:86/6f, 167:cd/6f, 168:c0/74, 169:ed/61
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 170:06/62, 171:41/6c, 172:66/65, 173:0f/20, 174:b7/66, 175:c9/6c
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 176:66/6f, 177:f7/70, 178:e1/70, 179:66/79, 180:89/20, 181:46/61
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 182:f8/6e, 183:83/64, 184:7e/0d, 185:16/0a, 186:00/70, 187:75/72
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 188:39/65, 189:83/73, 190:7e/73, 191:2a/20, 192:00/61, 193:77/6e
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 194:33/79, 195:66/20, 196:8b/6b, 197:46/65, 198:1c/79, 199:66/20
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 200:83/74, 201:c0/6f, 202:0c/20, 203:bb/74, 204:00/72, 205:80/79
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 206:b9/20, 207:01/61, 208:00/67, 209:e8/61, 210:2c/69, 211:00/6e
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 212:e9/20, 213:a8/2e, 214:03/2e, 215:a1/2e, 216:f8/20, 217:7d/0d
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 218:80/0a, 219:c4/00, 220:7c/00, 221:8b/00, 222:f0/00, 223:ac/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 224:84/00, 225:c0/00, 226:74/00, 227:17/00, 228:3c/00, 229:ff/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 230:74/00, 231:09/00, 232:b4/00, 233:0e/00, 234:bb/00, 235:07/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 237:cd/00, 238:10/00, 239:eb/00, 240:ee/00, 241:a1/00, 242:fa/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 243:7d/00, 244:eb/00, 245:e4/00, 246:a1/00, 247:7d/00, 248:80/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 249:eb/00, 250:df/00, 251:98/00, 252:cd/00, 253:16/00, 254:cd/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 255:19/00, 256:66/00, 257:60/00, 258:80/00, 259:7e/00, 260:02/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 262:0f/00, 263:84/00, 264:20/00, 266:66/00, 267:6a/00, 269:66/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 270:50/00, 271:06/00, 272:53/00, 273:66/00, 274:68/00, 275:10/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 277:01/00, 279:b4/00, 280:42/00, 281:8a/00, 282:56/00, 283:40/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 284:8b/00, 285:f4/00, 286:cd/00, 287:13/00, 288:66/00, 289:58/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 290:66/00, 291:58/00, 292:66/00, 293:58/00, 294:66/00, 295:58/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 296:eb/00, 297:33/00, 298:66/00, 299:3b/00, 300:46/00, 301:f8/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 302:72/00, 303:03/00, 304:f9/00, 305:eb/00, 306:2a/00, 307:66/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 308:33/00, 309:d2/00, 310:66/00, 311:0f/00, 312:b7/00, 313:4e/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 314:18/00, 315:66/00, 316:f7/00, 317:f1/00, 318:fe/00, 319:c2/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 320:8a/00, 321:ca/00, 322:66/00, 323:8b/00, 324:d0/00, 325:66/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 326:c1/00, 327:ea/00, 328:10/00, 329:f7/00, 330:76/00, 331:1a/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 332:86/00, 333:d6/00, 334:8a/00, 335:56/00, 336:40/00, 337:8a/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 338:e8/00, 339:c0/00, 340:e4/00, 341:06/00, 342:0a/00, 343:cc/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 344:b8/00, 345:01/00, 346:02/00, 347:cd/00, 348:13/00, 349:66/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 350:61/00, 351:0f/00, 352:82/00, 353:74/00, 354:ff/00, 355:81/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 356:c3/00, 358:02/00, 359:66/00, 360:40/00, 361:49/00, 362:75/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 363:94/00, 364:c3/00, 365:42/00, 366:4f/00, 367:4f/00, 368:54/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 369:4d/00, 370:47/00, 371:52/00, 372:20/00, 373:20/00, 374:20/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 375:20/00, 428:0d/00, 429:0a/00, 430:44/00, 431:69/00, 432:73/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 433:6b/00, 434:20/00, 435:65/00, 436:72/00, 437:72/00, 438:6f/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 439:72/00, 440:ff/00, 441:0d/00, 442:0a/00, 443:50/00, 444:72/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 445:65/00, 446:73/00, 447:73/00, 448:20/00, 449:61/00, 450:6e/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 451:79/00, 452:20/00, 453:6b/00, 454:65/00, 455:79/00, 456:20/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 457:74/00, 458:6f/00, 459:20/00, 460:72/00, 461:65/00, 462:73/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 463:74/00, 464:61/00, 465:72/00, 466:74/00, 467:0d/00, 468:0a/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   , 504:ac/00, 505:01/00, 506:b9/00, 507:01/00
Apr 14 12:03:48 maarten-arch systemd-fsck[506]:   Not automatically fixing this.
Apr 14 12:03:48 maarten-arch systemd-fsck[506]: /dev/sda1: 639 files, 16192/130812 clusters
Apr 14 12:03:48 maarten-arch systemd[1]: Finished File System Check on /dev/sda1.
Apr 14 12:03:48 maarten-arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-sda1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 14 12:03:48 maarten-arch systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.
Apr 14 12:03:48 maarten-arch systemd[1]: Mounting /boot...
Apr 14 12:03:48 maarten-arch kernel: audit: type=1130 audit(1586858628.888:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-sda1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 14 12:03:48 maarten-arch mount[507]: mount: /boot: unknown filesystem type 'vfat'.
Apr 14 12:03:48 maarten-arch systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
Apr 14 12:03:48 maarten-arch systemd[1]: boot.mount: Failed with result 'exit-code'.
Apr 14 12:03:48 maarten-arch systemd[1]: Failed to mount /boot.
Apr 14 12:03:48 maarten-arch systemd[1]: Dependency failed for Local File Systems.
Apr 14 12:03:48 maarten-arch systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.

I was wondering if Recover_GPT_header would fix the problem? Since it tells me my backup had differences from the boot sector.

"fdisk -l /dev/sda" outputs the following:

Disk /dev/sda: 232.91 GiB, 250059350016 bytes, 488397168 sectors
Disk model: Samsung SSD 850 
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 658DABA4-F14F-422E-86FB-DBC724116D13

Device       Start       End   Sectors   Size Type
/dev/sda1     2048   1050623   1048576   512M EFI System
/dev/sda2  1050624 488396799 487346176 232.4G Linux filesystem

Last edited by maartenvanschagen (2020-04-14 18:51:47)

Slithery · 2020-04-13 20:53:53

Please replace your pictures with text...
https://wiki.archlinux.org/index.php/Co … s_and_code
https://wiki.archlinux.org/index.php/Li … in_clients

maartenvanschagen · 2020-04-13 20:58:11

Slithery wrote:

Please replace your pictures with text...
https://wiki.archlinux.org/index.php/Co … s_and_code
https://wiki.archlinux.org/index.php/Li … in_clients

I'm sorry, my PC is in emergency mode right now, it doesn't seem to be connected to the internet. I'll do this as soon as it boots up.

Last edited by maartenvanschagen (2020-04-13 21:00:13)

loqs · 2020-04-13 21:05:32

Boot from installation media, setup networking if required. chroot in and post the journal to a pastebin using the tip box from slithery's second link.

maartenvanschagen · 2020-04-14 10:53:28

loqs wrote:

Boot from installation media, setup networking if required. chroot in and post the journal to a pastebin using the tip box from slithery's second link.

I didn't realize chrooting would allow for networking... It makes sense though. Thank you loqs

While doing a bit of looking around in the chroot environment I realized that I was not looking at the first failure, this is where it starts to go wrong:

Apr 14 12:03:48 maarten-arch systemd[1]: Finished Load Kernel Module drm.
Apr 14 12:03:48 maarten-arch systemd[1]: proc-sys-fs-binfmt_misc.automount: Got automount request for /proc/sys/fs/binfmt_misc, triggered by 411 (systemd-binfmt)
Apr 14 12:03:48 maarten-arch kernel: random: lvm: uninitialized urandom read (4 bytes read)
Apr 14 12:03:48 maarten-arch systemd[1]: Mounting Arbitrary Executable File Formats File System...
Apr 14 12:03:48 maarten-arch systemd[1]: Started LVM2 metadata daemon.
Apr 14 12:03:48 maarten-arch kernel: EXT4-fs (sda2): re-mounted. Opts: data=ordered
Apr 14 12:03:48 maarten-arch systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Apr 14 12:03:48 maarten-arch systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Apr 14 12:03:48 maarten-arch systemd[1]: Failed to start Load Kernel Modules.
Apr 14 12:03:48 maarten-arch systemd[1]: Finished Remount Root and Kernel File Systems.

I'm still not sure what causes it.

And in case I missed anything else, this is my full boot log.

Last edited by maartenvanschagen (2020-04-14 15:41:18)

Head_on_a_Stick · 2020-04-14 11:28:08

maartenvanschagen wrote:

Apr 14 12:03:48 maarten-arch systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.

^ This suggests that /boot was not mounted properly during a kernel upgrade. That would cause a failure to load the modules because of a mis-match between the installed and running kernels.

See if /boot/vmlinuz-linux exists on both your root and /boot partitions, use the file(1) command to determine the versions of the image(s).

maartenvanschagen · 2020-04-14 11:39:54

Head_on_a_Stick wrote:

That would cause a failure to load the modules because of a mis-match between the installed and running kernels.

You're right! I have a newer kernel version installed in the root partition. How would I fix this? Can I just copy the files?

Head_on_a_Stick · 2020-04-14 11:48:16

maartenvanschagen wrote:

How would I fix this?

Load the Arch live image, mount your root & /boot partitions correctly, (arch-)chroot in then reinstall the linux package.

Do you have any idea why it may not have been mounted correctly? This problem does seem to be fairly common and it would be nice to get to the bottom of it.

Check the filesystem on the /boot partition for errors, the standard options cause it to be remounted read-only if there are any problems.

maartenvanschagen · 2020-04-14 11:56:30

Head_on_a_Stick wrote:

Load the Arch live image, mount your root & /boot partitions correctly, (arch-)chroot in then reinstall the linux package.

Thank you very much! It worked.

Do you have any idea why it may not have been mounted correctly? This problem does seem to be fairly common and it would be nice to get to the bottom of it.

I'm not sure, I'll take a look into the logs.

maartenvanschagen · 2020-04-14 12:59:33

I found where it started failing in the journalctl logs.

First of all, this is what it looks like before it started failing (during boot):

Apr 12 18:37:27 maarten-arch systemd[1]: Mounted /boot.

The only line that refrences /boot:

Apr 12 18:41:59 maarten-arch sudo[6383]:  maarten : TTY=pts/2 ; PWD=/home/maarten ; USER=root ; COMMAND=/usr/bin/grub-mkconfig -o /boot/grub/grub.cfg

I think I was editing grub while following these instructions: https://linustechtips.com/main/topic/11 … n-windows/. I did step 3 eventhough I didn't need to (found out later)

The logs after /boot gets unmounted during the last shutdown show the following:

Apr 12 18:44:04 maarten-arch systemd[1]: Unmounting /boot...
Apr 12 18:44:04 maarten-arch systemd[1]: Unmounting /home/maarten/google-drive...
Apr 12 18:44:04 maarten-arch systemd[1]: Unmounting Temporary Directory (/tmp)...
Apr 12 18:44:04 maarten-arch systemd[1]: home-maarten-google\x2ddrive.mount: Succeeded.
Apr 12 18:44:04 maarten-arch systemd[1]: Unmounted /home/maarten/google-drive.
Apr 12 18:44:04 maarten-arch systemd[1]: tmp.mount: Succeeded.
Apr 12 18:44:04 maarten-arch systemd[1]: Unmounted Temporary Directory (/tmp).
Apr 12 18:44:04 maarten-arch systemd[1]: Stopped target Swap.
Apr 12 18:44:04 maarten-arch systemd[1]: Deactivating swap /swapfile...
Apr 12 18:44:04 maarten-arch systemd[1]: boot.mount: Succeeded.
Apr 12 18:44:04 maarten-arch systemd[1]: Unmounted /boot.
Apr 12 18:44:04 maarten-arch systemd[1]: systemd-fsck@dev-sda1.service: Succeeded.
Apr 12 18:44:04 maarten-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-sda1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 12 18:44:04 maarten-arch systemd[1]: Stopped File System Check on /dev/sda1.
Apr 12 18:44:04 maarten-arch systemd[1]: Removed slice system-systemd\x2dfsck.slice.
Apr 12 18:44:04 maarten-arch systemd[1]: Stopped target Local File Systems (Pre).
Apr 12 18:44:04 maarten-arch systemd[1]: Stopping Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...
Apr 12 18:44:04 maarten-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-tmpfiles-setup-dev comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 12 18:44:04 maarten-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-sysusers comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 12 18:44:04 maarten-arch systemd[1]: systemd-tmpfiles-setup-dev.service: Succeeded.
Apr 12 18:44:04 maarten-arch systemd[1]: Stopped Create Static Device Nodes in /dev.
Apr 12 18:44:04 maarten-arch systemd[1]: systemd-sysusers.service: Succeeded.
Apr 12 18:44:04 maarten-arch systemd[1]: Stopped Create System Users.
Apr 12 18:44:04 maarten-arch systemd[1]: swapfile.swap: Succeeded.
Apr 12 18:44:04 maarten-arch systemd[1]: Deactivated swap /swapfile.
Apr 12 18:44:04 maarten-arch systemd[1]: Reached target Unmount All Filesystems.
Apr 12 18:44:04 maarten-arch systemd[1]: systemd-remount-fs.service: Succeeded.
Apr 12 18:44:04 maarten-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-remount-fs comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 12 18:44:04 maarten-arch systemd[1]: Stopped Remount Root and Kernel File Systems.
Apr 12 18:44:04 maarten-arch systemd[1]: lvm2-monitor.service: Succeeded.
Apr 12 18:44:04 maarten-arch systemd[1]: Stopped Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling.
Apr 12 18:44:04 maarten-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 12 18:44:04 maarten-arch systemd[1]: Stopping LVM2 metadata daemon...
Apr 12 18:44:04 maarten-arch systemd[1]: lvm2-lvmetad.service: Succeeded.
Apr 12 18:44:04 maarten-arch systemd[1]: Stopped LVM2 metadata daemon.
Apr 12 18:44:04 maarten-arch systemd[1]: Reached target Shutdown.
Apr 12 18:44:04 maarten-arch systemd[1]: Reached target Final Step.
Apr 12 18:44:04 maarten-arch systemd[1]: lvm2-lvmetad.socket: Succeeded.
Apr 12 18:44:04 maarten-arch systemd[1]: Closed LVM2 metadata daemon socket.
Apr 12 18:44:04 maarten-arch systemd[1]: systemd-reboot.service: Succeeded.
Apr 12 18:44:04 maarten-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-lvmetad comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 12 18:44:04 maarten-arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 12 18:44:04 maarten-arch audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-reboot comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 12 18:44:04 maarten-arch systemd[1]: Finished Reboot.
Apr 12 18:44:04 maarten-arch systemd[1]: Reached target Reboot.
Apr 12 18:44:04 maarten-arch systemd[1]: Shutting down.
Apr 12 18:44:04 maarten-arch systemd-shutdown[1]: Syncing filesystems and block devices.
Apr 12 18:44:04 maarten-arch systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Apr 12 18:44:04 maarten-arch haveged[434]: haveged: Stopping due to signal 15
Apr 12 18:44:04 maarten-arch haveged[434]: haveged starting up
Apr 12 18:44:04 maarten-arch systemd-journald[435]: Journal stopped

That is when I started getting this error during startup.

Apr 12 18:44:29 maarten-arch systemd[1]: Mounting /boot...
Apr 12 18:44:29 maarten-arch kernel: audit: type=1130 audit(1586709869.619:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-sda1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 12 18:44:29 maarten-arch kernel: Bluetooth: Core ver 2.22
Apr 12 18:44:29 maarten-arch kernel: NET: Registered protocol family 31
Apr 12 18:44:29 maarten-arch kernel: Bluetooth: HCI device and connection manager initialized
Apr 12 18:44:29 maarten-arch kernel: Bluetooth: HCI socket layer initialized
Apr 12 18:44:29 maarten-arch kernel: Bluetooth: L2CAP socket layer initialized
Apr 12 18:44:29 maarten-arch kernel: Bluetooth: SCO socket layer initialized
Apr 12 18:44:29 maarten-arch kernel: FAT-fs (sda1): bogus number of reserved sectors
Apr 12 18:44:29 maarten-arch kernel: FAT-fs (sda1): Can't find a valid FAT filesystem
Apr 12 18:44:29 maarten-arch mount[548]: mount: /boot: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
Apr 12 18:44:29 maarten-arch kernel: snd_hda_intel 0000:27:00.1: Force to non-snoop mode
Apr 12 18:44:29 maarten-arch kernel: snd_hda_intel 0000:29:00.3: enabling device (0000 -> 0002)
Apr 12 18:44:29 maarten-arch systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
Apr 12 18:44:29 maarten-arch systemd[1]: boot.mount: Failed with result 'exit-code'.
Apr 12 18:44:29 maarten-arch systemd[1]: Failed to mount /boot.
Apr 12 18:44:29 maarten-arch systemd[1]: Dependency failed for Local File Systems.
Apr 12 18:44:29 maarten-arch systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Apr 12 18:44:29 maarten-arch systemd[1]: Starting Rebuild Dynamic Linker Cache...
Apr 12 18:44:29 maarten-arch systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Apr 12 18:44:29 maarten-arch systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Apr 12 18:44:29 maarten-arch systemd[1]: Starting Create Volatile Files and Directories...

Then it tries again, but failes:

Apr 12 18:44:31 maarten-arch systemd[1]: Mounting /boot...
Apr 12 18:44:31 maarten-arch systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Apr 12 18:44:31 maarten-arch systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Apr 12 18:44:31 maarten-arch NetworkManager[620]: <info>  [1586709871.9110] settings: (enp37s0): created default wired connection 'Wired connection 1'
Apr 12 18:44:31 maarten-arch systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Apr 12 18:44:31 maarten-arch systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Apr 12 18:44:31 maarten-arch NetworkManager[620]: <info>  [1586709871.9114] device (enp37s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Apr 12 18:44:31 maarten-arch mount[648]: mount: /boot: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
Apr 12 18:44:31 maarten-arch systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
Apr 12 18:44:31 maarten-arch systemd[1]: boot.mount: Failed with result 'exit-code'.
Apr 12 18:44:31 maarten-arch systemd[1]: Failed to mount /boot.
Apr 12 18:44:31 maarten-arch NetworkManager[620]: <info>  [1586709871.9147] ovsdb: Could not connect: No such file or directory
Apr 12 18:44:31 maarten-arch systemd[1]: Dependency failed for Local File Systems.
Apr 12 18:44:31 maarten-arch systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Apr 12 18:44:31 maarten-arch systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Apr 12 18:44:31 maarten-arch systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Apr 12 18:44:31 maarten-arch kernel: FAT-fs (sda1): bogus number of reserved sectors
Apr 12 18:44:31 maarten-arch kernel: FAT-fs (sda1): Can't find a valid FAT filesystem

I'm not sure if this is connected to the network device starting, but I did get an internet connection, so that doesn't fail.

But it didn't fail booting yet...

Then I get this a few times (during boot):

Apr 12 18:44:36 maarten-arch systemd[1]: boot.mount: Start request repeated too quickly.
Apr 12 18:44:36 maarten-arch systemd[1]: boot.mount: Failed with result 'exit-code'.
Apr 12 18:44:36 maarten-arch systemd[1]: Failed to mount /boot.
Apr 12 18:44:36 maarten-arch systemd[1]: Dependency failed for Local File Systems.
Apr 12 18:44:36 maarten-arch systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Apr 12 18:44:36 maarten-arch systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Apr 12 18:44:36 maarten-arch systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Apr 12 18:44:36 maarten-arch systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Apr 12 18:44:36 maarten-arch systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Apr 12 18:44:36 maarten-arch systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Apr 12 18:44:36 maarten-arch systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Apr 12 18:44:36 maarten-arch systemd[1]: Starting User Runtime Directory /run/user/978...
Apr 12 18:44:36 maarten-arch systemd[1]: boot.mount: Start request repeated too quickly.
Apr 12 18:44:36 maarten-arch systemd[1]: boot.mount: Failed with result 'exit-code'.
Apr 12 18:44:36 maarten-arch systemd[1]: Failed to mount /boot.
Apr 12 18:44:36 maarten-arch systemd[1]: Dependency failed for Local File Systems.
Apr 12 18:44:36 maarten-arch systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.

My pacman logs show I updated linux at 20:26:

[2020-04-12T20:26:49+0200] [ALPM] upgraded linux (5.5.8.arch1-1 -> 5.6.3.arch1-1)

After this the system wouldn't boot anymore:

Apr 13 20:35:14 maarten-arch systemd[1]: Reached target Local File Systems (Pre).
Apr 13 20:35:14 maarten-arch systemd[1]: Condition check resulted in Virtual Machine and Container Storage (Compatibility) being skipped.
Apr 13 20:35:14 maarten-arch systemd[1]: Starting File System Check on /dev/sda1...
Apr 13 20:35:14 maarten-arch kernel: audit: type=1130 audit(1586802914.200:5): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 13 20:35:14 maarten-arch systemd-fsck[510]: fsck.fat 4.1 (2017-01-24)
Apr 13 20:35:14 maarten-arch systemd-fsck[510]: There are differences between boot sector and its backup.
Apr 13 20:35:14 maarten-arch systemd-fsck[510]: This is mostly harmless. Differences: (offset:original/backup)
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   90:33/0e, 91:c9/1f, 92:8e/be, 93:d1/77, 94:bc/7c, 95:f4/ac, 96:7b/22
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 97:8e/c0, 98:c1/74, 99:8e/0b, 100:d9/56, 101:bd/b4, 102:00/0e, 103:7c/bb
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 104:88/07, 105:56/00, 106:40/cd, 107:88/10, 108:4e/5e, 109:02/eb
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 110:8a/f0, 111:56/32, 112:40/e4, 113:b4/cd, 114:41/16, 115:bb/cd
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 116:aa/19, 117:55/eb, 118:cd/fe, 119:13/54, 120:72/68, 121:10/69
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 122:81/73, 123:fb/20, 124:55/69, 125:aa/73, 126:75/20, 127:0a/6e
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 128:f6/6f, 129:c1/74, 130:01/20, 131:74/61, 132:05/20, 133:fe/62
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 134:46/6f, 135:02/6f, 136:eb/74, 137:2d/61, 138:8a/62, 139:56/6c
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 140:40/65, 141:b4/20, 142:08/64, 143:cd/69, 144:13/73, 145:73/6b
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 146:05/2e, 147:b9/20, 148:ff/20, 149:ff/50, 150:8a/6c, 151:f1/65
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 152:66/61, 153:0f/73, 154:b6/65, 155:c6/20, 156:40/69, 157:66/6e
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 158:0f/73, 159:b6/65, 160:d1/72, 161:80/74, 162:e2/20, 163:3f/61
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 164:f7/20, 165:e2/62, 166:86/6f, 167:cd/6f, 168:c0/74, 169:ed/61
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 170:06/62, 171:41/6c, 172:66/65, 173:0f/20, 174:b7/66, 175:c9/6c
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 176:66/6f, 177:f7/70, 178:e1/70, 179:66/79, 180:89/20, 181:46/61
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 182:f8/6e, 183:83/64, 184:7e/0d, 185:16/0a, 186:00/70, 187:75/72
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 188:39/65, 189:83/73, 190:7e/73, 191:2a/20, 192:00/61, 193:77/6e
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 194:33/79, 195:66/20, 196:8b/6b, 197:46/65, 198:1c/79, 199:66/20
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 200:83/74, 201:c0/6f, 202:0c/20, 203:bb/74, 204:00/72, 205:80/79
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 206:b9/20, 207:01/61, 208:00/67, 209:e8/61, 210:2c/69, 211:00/6e
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 212:e9/20, 213:a8/2e, 214:03/2e, 215:a1/2e, 216:f8/20, 217:7d/0d
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 218:80/0a, 219:c4/00, 220:7c/00, 221:8b/00, 222:f0/00, 223:ac/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 224:84/00, 225:c0/00, 226:74/00, 227:17/00, 228:3c/00, 229:ff/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 230:74/00, 231:09/00, 232:b4/00, 233:0e/00, 234:bb/00, 235:07/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 237:cd/00, 238:10/00, 239:eb/00, 240:ee/00, 241:a1/00, 242:fa/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 243:7d/00, 244:eb/00, 245:e4/00, 246:a1/00, 247:7d/00, 248:80/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 249:eb/00, 250:df/00, 251:98/00, 252:cd/00, 253:16/00, 254:cd/00
Apr 13 20:35:14 maarten-arch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-sda1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 255:19/00, 256:66/00, 257:60/00, 258:80/00, 259:7e/00, 260:02/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 262:0f/00, 263:84/00, 264:20/00, 266:66/00, 267:6a/00, 269:66/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 270:50/00, 271:06/00, 272:53/00, 273:66/00, 274:68/00, 275:10/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 277:01/00, 279:b4/00, 280:42/00, 281:8a/00, 282:56/00, 283:40/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 284:8b/00, 285:f4/00, 286:cd/00, 287:13/00, 288:66/00, 289:58/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 290:66/00, 291:58/00, 292:66/00, 293:58/00, 294:66/00, 295:58/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 296:eb/00, 297:33/00, 298:66/00, 299:3b/00, 300:46/00, 301:f8/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 302:72/00, 303:03/00, 304:f9/00, 305:eb/00, 306:2a/00, 307:66/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 308:33/00, 309:d2/00, 310:66/00, 311:0f/00, 312:b7/00, 313:4e/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 314:18/00, 315:66/00, 316:f7/00, 317:f1/00, 318:fe/00, 319:c2/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 320:8a/00, 321:ca/00, 322:66/00, 323:8b/00, 324:d0/00, 325:66/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 326:c1/00, 327:ea/00, 328:10/00, 329:f7/00, 330:76/00, 331:1a/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 332:86/00, 333:d6/00, 334:8a/00, 335:56/00, 336:40/00, 337:8a/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 338:e8/00, 339:c0/00, 340:e4/00, 341:06/00, 342:0a/00, 343:cc/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 344:b8/00, 345:01/00, 346:02/00, 347:cd/00, 348:13/00, 349:66/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 350:61/00, 351:0f/00, 352:82/00, 353:74/00, 354:ff/00, 355:81/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 356:c3/00, 358:02/00, 359:66/00, 360:40/00, 361:49/00, 362:75/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 363:94/00, 364:c3/00, 365:42/00, 366:4f/00, 367:4f/00, 368:54/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 369:4d/00, 370:47/00, 371:52/00, 372:20/00, 373:20/00, 374:20/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 375:20/00, 428:0d/00, 429:0a/00, 430:44/00, 431:69/00, 432:73/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 433:6b/00, 434:20/00, 435:65/00, 436:72/00, 437:72/00, 438:6f/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 439:72/00, 440:ff/00, 441:0d/00, 442:0a/00, 443:50/00, 444:72/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 445:65/00, 446:73/00, 447:73/00, 448:20/00, 449:61/00, 450:6e/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 451:79/00, 452:20/00, 453:6b/00, 454:65/00, 455:79/00, 456:20/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 457:74/00, 458:6f/00, 459:20/00, 460:72/00, 461:65/00, 462:73/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 463:74/00, 464:61/00, 465:72/00, 466:74/00, 467:0d/00, 468:0a/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   , 504:ac/00, 505:01/00, 506:b9/00, 507:01/00
Apr 13 20:35:14 maarten-arch systemd-fsck[510]:   Not automatically fixing this.
Apr 13 20:35:14 maarten-arch systemd-fsck[510]: /dev/sda1: 639 files, 16192/130812 clusters
Apr 13 20:35:14 maarten-arch kernel: audit: type=1130 audit(1586802914.247:6): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-fsck@dev-sda1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 13 20:35:14 maarten-arch systemd[1]: Finished File System Check on /dev/sda1.
Apr 13 20:35:14 maarten-arch systemd[1]: boot.mount: Directory /boot to mount over is not empty, mounting anyway.
Apr 13 20:35:14 maarten-arch systemd[1]: Mounting /boot...
Apr 13 20:35:14 maarten-arch mount[511]: mount: /boot: unknown filesystem type 'vfat'.
Apr 13 20:35:14 maarten-arch systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
Apr 13 20:35:14 maarten-arch systemd[1]: boot.mount: Failed with result 'exit-code'.
Apr 13 20:35:14 maarten-arch systemd[1]: Failed to mount /boot.
Apr 13 20:35:14 maarten-arch systemd[1]: Dependency failed for Local File Systems.
Apr 13 20:35:14 maarten-arch systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'.
Apr 13 20:35:14 maarten-arch systemd[1]: Starting Rebuild Dynamic Linker Cache...
Apr 13 20:35:14 maarten-arch systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Apr 13 20:35:14 maarten-arch systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Apr 13 20:35:14 maarten-arch systemd[1]: Starting Create Volatile Files and Directories...
Apr 13 20:35:14 maarten-arch systemd[1]: Finished Create Volatile Files and Directories.

I hope it helps, are there any other logs you need?

loqs · 2020-04-14 13:10:54

T20:26:49+0200 is 18:26:49 local time. Please post the whole journal for the boot covering that point in time.

journalctl --list-boots #to see the start time of recorded boots
journalctl -b x #replace x with the index from the previous commands output

Head_on_a_Stick · 2020-04-14 13:59:25

maartenvanschagen wrote:

Apr 12 18:44:31 maarten-arch mount[648]: mount: /boot: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
Apr 12 18:44:31 maarten-arch systemd[1]: boot.mount: Mount process exited, code=exited, status=32/n/a
Apr 12 18:44:31 maarten-arch systemd[1]: boot.mount: Failed with result 'exit-code'.
Apr 12 18:44:31 maarten-arch systemd[1]: Failed to mount /boot.

Okay, so the filesystem became corrupted and subsequently could not be mounted. I'm not sure why systemd-fsck didn't isolate emergency.target after detecting the errors though, that might be a bug.

To prevent this from happening again try frostshutz's advice in this post: https://bbs.archlinux.org/viewtopic.php … 9#p1890349

Might be best to wipe the filesystem on the /boot partition and re-create it afresh to make sure it's not corrupted. Re-install the kernel & bootloader back onto the partition afterwards.

If you're using systemd-boot then you can omit the /boot partition from /etc/fstab, systemd will then mount it automatically on demand and un-mount it after 120 seconds to help prevent corruption.

For GRUB it may be worth moving /boot back to the root partition and leaving the ESP completely un-mounted. If you do that then you will need to use the grub-install(8) command again to make sure that the UEFI loader is searching the correct partition for it's configuration file.

loqs · 2020-04-14 14:17:01

@Head_on_a_Stick the kernel is updated at 18:26:49 local-time without boot mounted then a boot afterwards at 18:44:31 fails to mount /boot as the module can not be loaded.

Last edited by loqs (2020-04-14 14:17:18)

Head_on_a_Stick · 2020-04-14 14:19:17

^ Oops, thanks loqs.

maartenvanschagen · 2020-04-14 15:14:48

loqs wrote:

T20:26:49+0200 is 18:26:49 local time. Please post the whole journal for the boot covering that point in time.

Sorry, I didn't realize. Here is the log you are looking for: https://pastebin.com/Pe3GyXud

The boot after: https://pastebin.com/WYxF08pz

Mounting /boot starts failing during the next boot, multiple boots look like this: https://pastebin.com/UkY7jZT4

Sorry for all the foldingathome stuff, it tends to fill the logs.

The first failed boot: https://pastebin.com/9CH9N7VP

I have no clue why it worked so many times before it failed. I only remember running foldingathome at this time.

Edit: And here are my pacman logs. The last part of this log was generated while I was in emergency mode.

Last edited by maartenvanschagen (2020-04-14 15:43:09)

Head_on_a_Stick · 2020-04-14 16:55:29

So this log shows a boot with kernel 5.5.8, the modules are loaded successfully by line 960 but /boot fails to mount between lines 1049 & 1064, presumably because of corruption ("bogus number of reserved sectors"). Several subsequent attempts are made but they all fail.

I've just checked the pacman log in my Arch chroot and it records the same times as are listed in the journal but adds "+0100" after the time because I am in the BST timezone, it does not indicate that the time should be corrected by that amount to allow comparison with the journal's timestamps.

loqs · 2020-04-14 17:02:03

https://github.com/systemd/systemd/comm … d975c45754 dropped OnFailure=emergency.target which would previously have made the failure much more noticeable.
Edit:
@Head_on_a_Stick apologies for the mistaken distraction about timezones.

Last edited by loqs (2020-04-14 17:11:56)

maartenvanschagen · 2020-04-14 18:04:35

Thank you both for all the help, I will recreate my /boot partition just to be sure, but the system does boot again (:. I have learned a lot from this experience and from all your help, thanks a lot!

Last edited by maartenvanschagen (2020-04-14 18:51:13)

Arch Linux

#1 2020-04-13 20:48:31

[SOLVED] Problems booting system: "Failed to mount /boot"

#2 2020-04-13 20:53:53

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#3 2020-04-13 20:58:11

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#4 2020-04-13 21:05:32

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#5 2020-04-14 10:53:28

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#6 2020-04-14 11:28:08

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#7 2020-04-14 11:39:54

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#8 2020-04-14 11:48:16

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#9 2020-04-14 11:56:30

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#10 2020-04-14 12:59:33

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#11 2020-04-14 13:10:54

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#12 2020-04-14 13:59:25

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#13 2020-04-14 14:17:01

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#14 2020-04-14 14:19:17

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#15 2020-04-14 15:14:48

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#16 2020-04-14 16:55:29

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#17 2020-04-14 17:02:03

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

#18 2020-04-14 18:04:35

Re: [SOLVED] Problems booting system: "Failed to mount /boot"

Board footer