0

My Raspberry Pi 3 Model B outputs the following when trying to initially boot:

Kernel panic-not syncing: VFS: unable to mount root fs on unknown- block(179,2)

After rebooting, I still receive the same error. The Pi is unable to "shift boot" to do a filesystem check and repair. This is a new installation without ever going through installation or setup.

Previously I had Ubuntu MATE installed on this SDHC 16GB card. During that installation, I had problems with formatting the filesystem(ext4), memory build up, half of the memory being completely unusable, and slow and jittery graphics. After turning off the compositors but still using the Marco WM, I still saw the same graphics errors.

After confirming to switch to a different Operating System, I (successfully?) installed Raspbian (wanting a more Debian based environment) on Mac OS X with:

sudo dd if=sudo dd if=/Users/[username]/Downloads/2016-05-27-raspbian-jessie.img of=/dev/disk1 bs=1m count=1024

with [username] being my username of course.

I have no idea whether any of this is useful in effectively diagnosing and correcting this error, but I am still willing to add any info if someone asks in the comments.

  • Have you verified that the SD card is good? Tried it with a different card? – Ron Beyer Aug 29 '16 at 21:49
  • I haven't tried it with another card. Is there any way to test the condition of the card? –  Aug 29 '16 at 23:02
  • Possible duplicate of [Kernel panic-not syncing: VFS: unable to mount root fs on unknown- block(179,6) running Raspbian on top of NOOBS](http://raspberrypi.stackexchange.com/questions/40854/kernel-panic-not-syncing-vfs-unable-to-mount-root-fs-on-unknown-block179-6) – Milliways Aug 29 '16 at 23:49
  • I already check it. The first step of fixing that issue is shift booting (which as I specified above) I am unable to do. –  Aug 30 '16 at 00:04

1 Answers1

0

I never figured out what was wrong, but I am now using Raspbian just fine on another SD card without error of any kind. Not sure if I corrupted the previous one or if it was the fault of the actual SD card hardware.