bharathyes
Posts: 5
Joined: Sat Jul 26, 2014 2:25 pm

Stuck at boot up

Sun Nov 16, 2014 5:04 am

I have been using the RPi B+ as a torrent box for a couple of weeks without any glitch. I used transmission to download torrents and saved on a pen drive, I used remote client to add new torrents, etc. After a while I couldn't access the Pi. Couldn't login through ssh or use the client. But the power, activity, network LED's seems to be working fine. Then when I plugged it into the TV I saw that a particular error keeps on being repeated and the boot up seems to be in a infinite loop without going to the command line. The error is something like,
EXT4-fs error (device nmbclkop2): ext4_ext_check_inode:481:(something) pblk 0 bad header/extent: too large eh_max - magic f30a, entries 16385, max (SOMETHING)
Can someone say what the trouble is?
Can I recover without having to reinstall everything on SD card ?
If yes, please help recover from it. I don't want to reinstall from scrap once again.

User avatar
lmarmisa
Posts: 1265
Joined: Thu Feb 14, 2013 2:22 am
Location: Jávea, Spain

Re: Stuck at boot up

Sun Nov 16, 2014 1:44 pm

The file system of the (Raspbian?) root partition has errors and they should to be repaired.

The easiest way to repair that partition would be to use a PC (with card reader) running Linux. You do not need to install Linux on your PC. You can run Linux from a LiveCD. You can use Ubuntu, Linux Mint or any other distro:

http://www.linuxmint.com/edition.php?id=159

Boot up your PC from the LiveCD, open a terminal and type this command:

Code: Select all

sudo fdisk -l
You have to identify the device where your SD card has been mapped. I will suppose it will be /dev/sdb. Change to /dev/sdc, /dev/sdd, etc if necessary.

According to the error message (mmcblk0p2), the root partition should be /dev/sdb2. If the automount feature of Linux opened some windows showing the files of the partitions on your SD card, close those windows. Finally type these commands:

Code: Select all

sudo umount /dev/sdb2
sudo fsck -f -a /dev/sdb2
Switch off your PC and check if you RPi runs properly after this repair process.

Return to “Troubleshooting”