Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to mount root fs on unknown-block (179,2) #167

Closed
tjain90 opened this issue Jan 11, 2014 · 16 comments

Comments

Projects
None yet
9 participants
@tjain90
Copy link

commented Jan 11, 2014

Hi ,
I have:
Respberry Pi Model B
8 GB micro SD Kingston
NOOBS v1_3_3
Window 7(On Computer)

I tried to install Noobs and it worked smoothly on respberry pi but i am unable to boot any OS it shows: "Unable to mount root fs on unknown-block (179,2) Entering kdb (current=0xcb846c80, pid 1) due to Keyboard Entry ". Please help me in this issue , I need to start my college project and i m feeling helpless.

@lurch

This comment has been minimized.

Copy link
Collaborator

commented Jan 11, 2014

Sorry to hear that. Can you try the latest NOOBS 1.3.4 and let us know if that produces the same error?
If you do still get the same error, does it continue to happen if you try booting with everything removed from the USB ports?
Which OSes have you tried to install/boot from within NOOBS?

@tjain90

This comment has been minimized.

Copy link
Author

commented Jan 12, 2014

Hi lurch,

I have used the latest version Noobs 1.3.4 but still the error is same and i have tried removing after eberything from USB port. So please suggest what to do next ?

@lurch

This comment has been minimized.

Copy link
Collaborator

commented Jan 12, 2014

Which OSes have you tried installing/booting from within NOOBS?
If you use the 'Edit config' button in NOOBS https://github.com/raspberrypi/noobs#easy-config-file-editor after rebooting and pressing SHIFT to enter recovery mode, can you tell us what the cmdline.txt says for the non-working OSes? While still in recovery mode, can you press Alt and F2 (at the same time) to get to a text console, login with username 'root' and password 'raspberry' and then let us know what the output of fdisk -l /dev/mmcblk0 says?

If you then switch off the Pi and place the SD card into your PC, can you paste the contents of the BUILD-DATA file here?

@lurch

This comment has been minimized.

Copy link
Collaborator

commented Jan 12, 2014

Just for reference: related forum thread here http://www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=66134

@lurch

This comment has been minimized.

Copy link
Collaborator

commented Feb 18, 2014

From the forum thread, it sounds like perhaps /dev/mmcblk0p5 was being mounted read-only (?) and thus the changes to cmdline.txt (to set the real location of the root filesystem) weren't being saved. The user was able to workaround this by editing the file on a (different) Linux PC.
No idea what the root cause was though. I'll leave this bug open (but reclassify it as minor) in case anybody else comes across the same problem.

@lurch lurch added the minor label Feb 18, 2014

@maxnet

This comment has been minimized.

Copy link
Collaborator

commented Feb 18, 2014

From the forum thread, it sounds like perhaps /dev/mmcblk0p5 was being mounted read-only (?)

I doubt that Linux falls back to mounting read-only automatically.
(that some Linux distributions show behaviour that resembles that on startup, is caused by startup scripts that explicitly mount read-only first, and then do "mount -o remount rw /"
If the latter fails, you still have access to the file system read-only due to the earlier mount command.)

NOOBS does have proper error checking for the mount commands.
So if those fail it should error out here on installation: https://github.com/raspberrypi/noobs/blob/master/recovery/multiimagewritethread.cpp#L254
And here if using the GUI to edit cmdline.txt: https://github.com/raspberrypi/noobs/blob/master/recovery/confeditdialog.cpp#L81

Did the old bug that also affected raspi-config where it seemed that writes to a FAT partition sometimes do not actually make it to the SD card ever got solved?
If not, that might be a more likely candidate.

@lurch

This comment has been minimized.

Copy link
Collaborator

commented Feb 18, 2014

Thanks for the info @maxnet

Did the old bug that also affected raspi-config where it seemed that writes to a FAT partition sometimes do not actually make it to the SD card ever got solved?

From what I've heard, that should have been fixed by updated firmware, but that's more @ghollingworth 's area of expertise ;-)

@popcornmix

This comment has been minimized.

Copy link

commented Feb 19, 2014

I believe the corruption to FAT partition bug is solved.

@lurch

This comment has been minimized.

Copy link
Collaborator

commented Feb 19, 2014

@popcornmix Is that bug fixed just by updated firmware, or does it rely on kernel fixes too? If it makes any difference, NOOBS is still using the 3.6.y kernel branch, with uname -a reporting:
Linux recovery 3.6.11-rescue #1 PREEMPT Sun Oct 13 19:14:50 BST 2013 armv6l GNU/Linux

@popcornmix

This comment has been minimized.

Copy link

commented Feb 19, 2014

It was purely a firmware fix. That kernel shouldn't be a problem.

@Ruffio

This comment has been minimized.

Copy link

commented Jun 27, 2015

@tjain90 @popcornmix is this still an issue?

@NikolaMandic

This comment has been minimized.

Copy link

commented Aug 13, 2015

I just got this error with raspbian it worked just fine now it gave this
but I have not used noobs

@lurch

This comment has been minimized.

Copy link
Collaborator

commented Aug 13, 2015

@NikolaMandic If you're not using NOOBS, then there's not much point adding a comment on the NOOBS bug-tracker ;-)

If you're getting the error using standalone Raspbian, then perhaps your root partition has become corrupt somehow. You could try inserting your SD card into a desktop / laptop Linux PC, and running e2fsck against the faulty root partition?

@rraghu214

This comment has been minimized.

Copy link

commented Feb 4, 2018

Formatting the SD Card with "SD Card Formatter" worked for me. After which copied the image to it using DIsk Imager WIn 32 and then could use it normally.

@JamesH65

This comment has been minimized.

Copy link

commented Feb 5, 2018

This issue is pretty ancient, and seems to be resolved, so closing.

@JamesH65 JamesH65 closed this Feb 5, 2018

@VipulKapoor

This comment has been minimized.

Copy link

commented Aug 10, 2018

mostly because of not well Formatted or not correct partitions (of sd card), occurs this Panic problem.
can be solved using GParted software. which formats the sd card in a correct manner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.