IMBACalimba
Posts: 4
Joined: Thu Jun 18, 2015 8:28 am
Location: Vienna
Contact: Website

ERROR: kernel panic (179,2)

Thu Jun 18, 2015 11:58 am

Hello everybody,

my Raspberry Pi 2 worked 2 weeks with absolutely no problems. So since yesterday after a usual restart this error message appears while the Pi is booting.

[quote]Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,2)[/quote]

The only thing iv'e done was mounting a SMB network drive.

The Pi was always controlled over xRDP and so it hasn't connected any peripherals (no mouse or Keyboard) so it cant be a Power problem

Are there any ideas what encountered this error and how can i fix it?.

I would prefer to not re-install the image because (i'm a linux noob) it was a loot of work for me to do the configuration on it like i want it.

So i hope that somebody can help me out with this issue :(

greetings
IMBACalimba

IMBACalimba
Posts: 4
Joined: Thu Jun 18, 2015 8:28 am
Location: Vienna
Contact: Website

Re: ERROR: kernel panic (179,2)

Sat Jun 20, 2015 8:25 am

Are there absolutely no ideas how to fix this issue :(?

User avatar
DougieLawson
Posts: 41955
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: ERROR: kernel panic (179,2)

Sun Jun 21, 2015 7:13 am

Your filesystem on /dev/mmcblk0p2 is trashed. You'll need to boot to a root shell to fsck it. Or you'll need to boot a different SDCard (or another Linux system) and mount the broken system in a USB reader to be able to fsck it.
Languages using left-hand whitespace for syntax are ridiculous

DMs sent on Twitter/LinkedIn will be answered next month.
Fake doctors - are all on my foes list.

The use of crystal balls and mind reading is prohibited.

IMBACalimba
Posts: 4
Joined: Thu Jun 18, 2015 8:28 am
Location: Vienna
Contact: Website

Re: ERROR: kernel panic (179,2)

Mon Jun 22, 2015 4:26 pm

I've tried to fsck it but i only get the following message

Code: Select all

fsck.ext2: No such file or directory while trying to open /dev/mmcblk0p2
Possibly non-existent device?
You got any tips for me so far?

diederik
Posts: 394
Joined: Wed Mar 26, 2014 11:17 pm

Re: ERROR: kernel panic (179,2)

Mon Jun 22, 2015 5:07 pm

If you plug the SD card in another machine, it likely won't be named '/dev/mmcblk0p2', but something else.
After plugging in the SD card in another machine, do 'dmesg | tail' and it should show you which device names are assigned to it.
Then do the fsck command again, but this time with the right device name.

IMBACalimba
Posts: 4
Joined: Thu Jun 18, 2015 8:28 am
Location: Vienna
Contact: Website

Re: ERROR: kernel panic (179,2)

Tue Jun 23, 2015 12:39 pm

First of all thank you very much for your help!!

i released the command like you told me this is the result, but i dont realy know what to do now with that information.

Code: Select all

[ 7485.323461] mmc0: card 59b4 removed
[ 7489.929829] mmc0: new SDHC card at address 59b4
[ 7489.929991] mmcblk0: mmc0:59b4 SD16G 14.5 GiB 
[ 7489.931181]  mmcblk0: [CUMANA/ADFS] p1 [ADFS] p1
I also tried the command "sudo fdisk -l" where i got that information.

Code: Select all

Device         Boot    Start      End  Sectors  Size Id Type
/dev/mmcblk0p1          8192  1685546  1677355  819M  e W95 FAT16 (LBA)
/dev/mmcblk0p2       1687552 30472191 28784640 13,7G 85 Linux extended
/dev/mmcblk0p3      30472192 30537727    65536   32M 83 Linux
/dev/mmcblk0p5       1695744  1818623   122880   60M  c W95 FAT32 (LBA)
/dev/mmcblk0p6       1826816 30472191 28645376 13,7G 83 Linux
But i also cant do anything with this information... its kind of frustrating for me now :(

greetings
IMBA

diederik
Posts: 394
Joined: Wed Mar 26, 2014 11:17 pm

Re: ERROR: kernel panic (179,2)

Tue Jun 23, 2015 1:13 pm

/dev/mmcblk0p2 isn't a normal partition, but an extended one which sole role is to hold other partitions.
You should be able to fsck /dev/mmcblk0p3 and /dev/mmcblk0p6 to see whether that helps.

Joe Schmoe
Posts: 4277
Joined: Sun Jan 15, 2012 1:11 pm

Re: ERROR: kernel panic (179,2)

Tue Jun 23, 2015 1:45 pm

Note that there are two parallel threads-of-advice being bandied about here:
  1. The idea of booting into some form a of "recovery shell" on the Pi itself and then working with the card directly.
  2. The idea of booting some other Linux system (e.g., another Pi or a desktop PC) and then mounting the Pi's SD card in a USB care reader/writer, and then working with it there.
In case 1, it will still be /dev/mmcblkSomething. In case 2, it will be /dev/sd{a or b}Something.

AFAIK, it is simply not possible for an SD card to show up as /dev/mmcblkSomething unless it is the "built in" card (i.e., boot device) for the device.
And some folks need to stop being fanboys and see the forest behind the trees.

(One of the best lines I've seen on this board lately)

User avatar
DougieLawson
Posts: 41955
Joined: Sun Jun 16, 2013 11:19 pm
Location: A small cave in deepest darkest Basingstoke, UK
Contact: Website Twitter

Re: ERROR: kernel panic (179,2)

Tue Jun 23, 2015 4:02 pm

If you mount /dev/mmcblk0p1 and /dev/mmcblkp5 can you find a config.txt on either of them?

Your config.txt that was used when you booted the Raspberry Pi from that card has the wrong partition for the root filesystem (hence why you can't mount it and hence why the kernel panics and dies).

For NOOBS the active config.txt needs to have

Code: Select all

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p6 rootfstype=ext4 elevator=deadline rootwait
For plain Raspbian your config has

Code: Select all

dwc_otg.lpm_enable=0 console=ttyAMA0,115200 kgdboc=ttyAMA0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline rootwait
It looks like you may have mixed a plain Raspbian command line on a NOOBS card.
Languages using left-hand whitespace for syntax are ridiculous

DMs sent on Twitter/LinkedIn will be answered next month.
Fake doctors - are all on my foes list.

The use of crystal balls and mind reading is prohibited.

HariOm
Posts: 1
Joined: Fri Aug 28, 2015 7:51 am

Re: ERROR: kernel panic (179,2)

Fri Aug 28, 2015 8:07 am

put the sd card in an adapter attach it in another linux system. fdisk -l in the command prompt. it will list all the devices which are mounted on the system.
see last lines of the commands
then fsck the last device(i.e. the sd cards partition).
(in my sys)

Code: Select all

root@shubhashish-HP-Compaq-8000-Elite-CMT-PC:/home/shubhashish# fdisk -l

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x3b2b3b2b

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      206847      102400    7  HPFS/NTFS/exFAT
/dev/sda2          206848    83888127    41840640    7  HPFS/NTFS/exFAT
/dev/sda3        83888128   288686079   102398976    7  HPFS/NTFS/exFAT
/dev/sda4       288690174   488396799    99853313    5  Extended
/dev/sda5       474236928   482537471     4150272   83  Linux
/dev/sda6       482539520   488396799     2928640   82  Linux swap / Solaris
/dev/sda7       288690176   474236927    92773376   83  Linux

Partition table entries are not in disk order

Disk /dev/sdb: 8026 MB, 8026849280 bytes
247 heads, 62 sectors/track, 1023 cylinders, total 15677440 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0009bf4f

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            8192      122879       57344    c  W95 FAT32 (LBA)
/dev/sdb2          122880    15677439     7777280   83  Linux
root@shubhashish-HP-Compaq-8000-Elite-CMT-PC:/home/shubhashish# fsck /dev/sdb
sdb   sdb1  sdb2  
root@shubhashish-HP-Compaq-8000-Elite-CMT-PC:/home/shubhashish# fsck /dev/sdb2
fsck from util-linux 2.20.1
e2fsck 1.42.9 (4-Feb-2014)
ext2fs_open2: Bad magic number in super-block
fsck.ext2: Superblock invalid, trying backup blocks...
/dev/sdb2: recovering journal
fsck.ext2: unable to set superblock flags on /dev/sdb2


/dev/sdb2: ***** FILE SYSTEM WAS MODIFIED *****

/dev/sdb2: ********** WARNING: Filesystem still has errors **********

root@shubhashish-HP-Compaq-8000-Elite-CMT-PC:/home/shubhashish#
unmount the sd card and boot it in your raspberry pi.

Return to “Raspberry Pi OS”