RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Retropie-kernel panic-not syncing: vfs: unable to mount root fs on unknown-block(179,2)

    Scheduled Pinned Locked Moved Help and Support
    retropie 4.2kernel panicmicro sd
    24 Posts 9 Posters 17.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • simonsterS
      simonster
      last edited by

      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

      1 Reply Last reply Reply Quote 0
      • J
        jedimumbo
        last edited by

        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.

        1 Reply Last reply Reply Quote 0
        • simonsterS
          simonster
          last edited by

          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

          1 Reply Last reply Reply Quote 0
          • J
            jedimumbo
            last edited by

            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!

            :)

            1 Reply Last reply Reply Quote 0
            • mr315M
              mr315
              last edited by mr315

              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 page

              I tried with a Sandisk 8gb card, but nothing changed
              Tried to partition the 64GB card, but I got the same result

              Win32DiskImager displays an error about the image being corrupted. But I saw the same error and everything happens well.

              I hope you have understood me =)

              jonnykeshJ 1 Reply Last reply Reply Quote 0
              • jonnykeshJ
                jonnykesh @mr315
                last edited by

                @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?

                mr315M 1 Reply Last reply Reply Quote 0
                • mr315M
                  mr315 @jonnykesh
                  last edited by

                  @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.

                  jonnykeshJ 2 Replies Last reply Reply Quote 0
                  • jonnykeshJ
                    jonnykesh @mr315
                    last edited by

                    @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.

                    1 Reply Last reply Reply Quote 0
                    • jonnykeshJ
                      jonnykesh @mr315
                      last edited by

                      @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. 
                      
                      1 Reply Last reply Reply Quote 0
                      • mr315M
                        mr315
                        last edited by mr315

                        @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 in

                        ps: 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

                        jonnykeshJ 1 Reply Last reply Reply Quote 0
                        • jonnykeshJ
                          jonnykesh @mr315
                          last edited by jonnykesh

                          @mr315 The /boot partition can be read from a windows computer. Plug the SD card into a Win PC and edit the cmdline.txtfrom there.

                          mr315M 2 Replies Last reply Reply Quote 0
                          • mr315M
                            mr315 @jonnykesh
                            last edited by

                            @jonnykesh Ok

                            1 Reply Last reply Reply Quote 0
                            • mr315M
                              mr315 @jonnykesh
                              last edited by

                              @jonnykesh
                              The error now changed the end of "179,2" to "179,6". Nothing but.

                              jonnykeshJ 1 Reply Last reply Reply Quote 0
                              • jonnykeshJ
                                jonnykesh @mr315
                                last edited by

                                @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.

                                mr315M 1 Reply Last reply Reply Quote 0
                                • S
                                  StevieJoe360
                                  last edited by

                                  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.)

                                  TMNTturtlguyT herb_fargusH 2 Replies Last reply Reply Quote 0
                                  • TMNTturtlguyT
                                    TMNTturtlguy @StevieJoe360
                                    last edited by

                                    @steviejoe360 this is not true, I have run several 128gb sd cards.

                                    1 Reply Last reply Reply Quote 0
                                    • herb_fargusH
                                      herb_fargus administrators @StevieJoe360
                                      last edited by

                                      @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.

                                      If you read the documentation it will answer 99% of your questions: https://retropie.org.uk/docs/

                                      Also if you want a solution to your problems read this first: https://retropie.org.uk/forum/topic/3/read-this-first

                                      1 Reply Last reply Reply Quote 3
                                      • mr315M
                                        mr315 @jonnykesh
                                        last edited by mr315

                                        @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?

                                        jonnykeshJ 1 Reply Last reply Reply Quote 0
                                        • jonnykeshJ
                                          jonnykesh @mr315
                                          last edited by

                                          @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.

                                          mr315M 1 Reply Last reply Reply Quote 0
                                          • mr315M
                                            mr315 @jonnykesh
                                            last edited by mr315

                                            @jonnykesh Bought on the internet.
                                            I bought another one now, and it worked fine. SanDisk Ultra 64gb. Thanks for all.

                                            jonnykeshJ 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            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.