Retropie-kernel panic-not syncing: vfs: unable to mount root fs on unknown-block(179,2)
-
Hello,
I am getting: kernel panic-not syncing: vfs: unable to mount root fs on unknown-block(179,2) on my raspberry pi 3 running Retropie 4.2.
Basically, everything was fine (used emulation station to play games) and then I made a genius move and removed my micro-sd card from my raspberry pi to put it in a samsung tablet to use (what? it's a boot drive?). Yes, I am a moron. I even deleted all of the files on the boot drive (G:) before I realized what I had done. Then, I tried to put it back in and got:
"kernel panic-not syncing: vfs: unable to mount root fs on unknown-block(179,2)"
I formatted the SD card and reimaged the SD card and the same happened. My computer stopped recognizing my SD card, so I bought a new one and imaged it just like I did from the get go and got the same message: "kernel panic-not syncing: vfs: unable to mount root fs on unknown-block(179,2)"
I am imaging with win32 and using a PC. I don't currently have a USB keyboard. That was my next plan. Any ideas on how I can recover from this and get back to emulation station?Thank you.
-
Hi @jedimumbo
Can you detail exactly how you are writing the image and which image you are using?
Can you try completing the details in the read-this-first section above?
Thanks
Si
-
Can you detail exactly how you are writing the image and which image you are using?
I am writing using Win32DiskImager. It did work for a few weeks before I pulled my bonehead move. MicroSD reader into PC, use Win32DiskImager to Write to Micro SD.Can you try completing the details in the read-this-first section above?
-Sorry.
Pi Model or other hardware: Raspberry Pi 3 Model B
Power Supply used: CanaKit 2.5A USB Power Supply with Micro USB Cable and Noise Filter
RetroPie Version Used: 4.2
Built From: retropie-4.2-rpi2_rpi3.img using Win32DiskImager
USB Devices connected: MIcrosoft Xbox controller- wireless
Controller used: See above.
Error messages received: kernel panic-not syncing: vfs: unable to mount root fs on unknown-block(179,2)
Log found in /dev/shm/runcommand.log (if relevant): ? Cannot get to this?
Guide used: https://retropie.org.uk/docs/First-Installation/
File: ?
Emulator: Emulation Station
Attachment of config files: ?
How to replicate the problem: Boot it up by plugging it in. -
Thanks for that,
If you aren't getting any issues as the Win32DiskImager step, then the first step I would try would be to redownload the image and try writing it to a known good SD card (to rule out a dodgy SD card).
Once you've imaged the card, do you get to the installation script for RetroPie open on first boot, or does it error immediately?
Si
-
Well... I did what you said. Which I had indeed done prior. And, now we're up and running. I don't know what I messed up on first, but thank you for asking me to do it again, because I'm back in business!
:)
-
Please! My English is bad. But this is also my problem.
My pack is:
Raspberry pi 3 v2
Samsung 64gb
Retropie 4.2
Using Win32DiskImager
Not connected USB
Error messages received: kernel panic-not syncing: vfs: unable to mount root fs in unknown-block (179,2)
Downloaded in the official Retropie pageI tried with a Sandisk 8gb card, but nothing changed
Tried to partition the 64GB card, but I got the same resultWin32DiskImager displays an error about the image being corrupted. But I saw the same error and everything happens well.
I hope you have understood me =)
-
@mr315 Just follow the advice given above. Re-download the image and burn it onto the card again. It worked for him, why wouldn't it work for you?
-
@jonnykesh , I do not know. Tried several times.
I tried partitioning the SD and with a different SD... =(
Downloaded it through Chrome and Internet Explorer.
I will try a download manager later. -
@mr315 Really odd. If you post exactly what you are doing and what software you are using to write the image to the card maybe someone will see where the problem is.
-
@mr315 try this:
If your error message ends with 2, like this: Kernel panic-not syncing: VFS: unable to mount root fs on unknown-block(179,2) it is likely that the problem is caused by an update bug. The fix involves switching that 2 into a 6: Start the Raspberry holding the Shift key. Click the Edit config (e) button or press e. Click the cmdline.txt tab or press the right arrow on the keyboard. Replace: root=/dev/mmcblk0p2 with root=/dev/mmcblk0p6 Click OK and then press escape on the keyboard to proceed with the boot sequence. Your Pi should now boot fine.
-
@jonnykesh , I format SD with "SD Formatter" -- or partition with 32gb with "Fat32Formatter" or other, but i dont remember now.
Download the image on "retropie.org.uk/download/";
Uncompressed with WinRar;
Write the image with "Win32DiskImager" on my sd.
I plug the card into the Raspberry and plug it inps: unzipping by 7zip generates an error that does not allow me to write the image.
And the keyboard does not work on the screen in question -
@mr315 The /boot partition can be read from a windows computer. Plug the SD card into a Win PC and edit the
cmdline.txt
from there. -
@jonnykesh Ok
-
@jonnykesh
The error now changed the end of "179,2" to "179,6". Nothing but. -
@mr315 Try using a program called
etcher
to write to the card. Link https://etcher.io/
It takes a bit longer but it checks the image. -
Hello,
I have a theory, I'm not quite sure, but I heard somewhere that a Raspberry Pi 3 can only use up to 32 GB on an SD/MicroSD card, if it's higher than that you have to do something different. I know I'm being very vauge(?) here, but I don't remember all the details. I suggest you look up something like "raspberry pi 3 64gb sd card." Hope this helps, but if not... Remember, it's just a theory, A GAME THEORY!! (Sorry, I had to.) -
@steviejoe360 this is not true, I have run several 128gb sd cards.
-
@steviejoe360 said in Retropie-kernel panic-not syncing: vfs: unable to mount root fs on unknown-block(179,2):
I'm not quite sure, but I heard somewhere
What my crazy relative says right before they quote something they saw on their Facebook feed.
-
@jonnykesh Thaks!
I tested with "H2testw" and found that the 64GB SDXC is fake. But the 8GB is not and it happened the same. I'll buy one like a friend's. If the error persists, can it be the image or the raspberry? -
@mr315 Where did you purchase the card from? Unfortunately there are a lot of fakes about. They all tend to be 4/8GB spoofing they are 64/128.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.