# Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,17)

**URL:** <https://forum.endeavouros.com/t/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-8-17/34774>\
**Category:** Kernel, boot, graphics & hardware\
**Created:** [December 12, 2022, 1:19am UTC](https://forum.endeavouros.com/t/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-8-17/34774 "2022-12-12T01:19:17Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![handy](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/handy/32/68965_2.png) [@handy](https://forum.endeavouros.com/u/handy)\
**Post date:** [December 12, 2022, 1:19am UTC](https://forum.endeavouros.com/t/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-8-17/34774/1 "2022-12-12T01:19:17Z")

</div>

Updated system (–repo) today, it recommended that I restart due to core components having been upgraded. So I did.

I now can not boot with either the LTS kernel or the new kernel 6.\*\*\*.

I get the following kernel panic:

```auto
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,17)
```

I used arch-chroot & reinstalled GRUB2 & did the grub.cfg thing. Makes no difference?

Not getting any useful info’ when I search the web, so here I am.

Any help greatly appreciated. 🙂

Some system info:

Using Legacy - BIOS - GRUB2

sda: NTFS - Windows stuff  
sdb1: ext4 - EOS /boot/grub/grub.cfg (NO /boot partition)  
sdc: NTFS - Windows stuff

---

<div class="post-metadata">

**Author:** ![pebcak](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/pebcak/32/100472_2.png) [@pebcak](https://forum.endeavouros.com/u/pebcak)\
**Post date:** [December 12, 2022, 4:45am UTC](https://forum.endeavouros.com/t/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-8-17/34774/2 "2022-12-12T04:45:31Z")

</div>

You could try rebuilding your initramfs and see if you can get your system working again.

`arch-chroot` into your installed system and run:

`mkinitcpio -P`

If you get any error message post it back here.  
Quit chroot

`exit`

and reboot.

If that won’t work, I would try re- installing my kernels in chroot.

---

<div class="post-metadata">

**Author:** ![handy](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/handy/32/68965_2.png) [@handy](https://forum.endeavouros.com/u/handy)\
**Post date:** [December 12, 2022, 8:37pm UTC](https://forum.endeavouros.com/t/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-8-17/34774/3 "2022-12-12T20:37:19Z")

</div>

@pebcak, thanks for your reply. 🙂  
I chrooted & ran mkinitcpio -P , exited rebooted to the same kernel panic.

Then, again chrooted to reinstall the 2 kernels, exited/rebooted & got the exactly the same kernel panic?

The machine ran win7 for many hours yesterday (after the kernel panic). It is an EOS install problem.

I hope I don’t have to reinstall, I’ve spent a couple of days setting the system up…

_(Now I remember what I’d forgotten about the rolling release package management system & why I’ve lost so many linux skills whilst using MX for the past \>4.5 years. lol )_

As I continue to age & my faculties deteriorate I am drawn ever closer to the Apple OS retirement home… lol

---

<div class="post-metadata">

**Author:** ![mbod](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/mbod/32/16833_2.png) [@mbod](https://forum.endeavouros.com/u/mbod)\
**Post date:** [December 13, 2022, 6:29am UTC](https://forum.endeavouros.com/t/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-8-17/34774/4 "2022-12-13T06:29:32Z")

</div>

> [@handy](#):
>
> I chrooted & ran mkinitcpio -P , exited rebooted to the same kernel panic.

Can you please show the content of /boot. All of it please. recursive, with timestamps and file sizes.  
Also, please share `fdisk -l` information for that Linux drive as well as `df` output.

---

<div class="post-metadata">

**Author:** ![handy](https://forum.endeavouros.com/user_avatar/forum.endeavouros.com/handy/32/68965_2.png) [@handy](https://forum.endeavouros.com/u/handy)\
**Post date:** [December 14, 2022, 10:27pm UTC](https://forum.endeavouros.com/t/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-8-17/34774/5 "2022-12-14T22:27:16Z")

</div>

@mbod Thanks for your reply. 🙂

I think I’ll give EndeavourOS a miss. One of my first pacman updates caused GRUB to fail, making me to the arch-chroot routine.

Then an update or two later & I’m frozen out of my boot via a kernel panic. Which has cost me a lot of time in research & I don’t want to invest anymore time in it. I’ve had more trouble in a few days with EOS than I had in 4.5 + years of MX.

So I think I’ll go back to MX & just put up with having to do a reinstall every 4 years or so due to its semi-rolling release nature.

Take care. 🙂

---

<div class="post-metadata">

**Author:** ![system](https://forum.endeavouros.com/uploads/default/original/2X/9/9ea52f9fd5ef8e609e593c362d61a36295f48be8.png) [@system](https://forum.endeavouros.com/u/system)\
**Post date:** [December 16, 2022, 10:27pm UTC](https://forum.endeavouros.com/t/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block-8-17/34774/6 "2022-12-16T22:27:33Z")

</div>

Closed on December 16, 2022, 10:27pm UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
