Can not boot, today.

[him81]

This may be the fourth time I flash the 2012-12-16 rom on my SD. After one or two days my raspberry does not boot again. Sometimes it was a sintax error in a script (after an apt-get update of the ditro), sometimes a io error. This time my boot process hangs for some minutes after the usb ethernet init and then I get the following lines:
EXT4-fs (mmcblk0p2): error count: 11
EXT4-fs (mmcblk0p2): initial error at 1356660810: ext4_ext_find_extent:692: inode 1938
EXT4-fs (mmcblk0p2): last error at 2: ext4_lookup:1343 inode 8194

after some more minutes my tv screen becomes blank.

The error count seems to increase at each power up.

I tried to change my power supply several times: I am now using iPad2 10W power supply.

I am a new linux user so I did not modify scripts or config files.

I saw other lines that may help to understand the problem:
warning: mounting fs with errors, runing e2fsck is recommened
recovery complete
mounted filesystem wih ordered data mode

How can I run e2fsck if the system does not boot? Is there a way to start it during boot if needed?
Is there something that I can do to recover this situation other than uploading a new image to sd?

[DirkS]

Looks as if the SD card is corrupted. Did you select overclocking (turbo mode) when you used the Pi the first time after flashing? That is the most common cause of card corruption.

If that's the case then I would try running the Pi at standard speed for a while.

Gr.
Dirk.

[him81]

No, I did not modify the clock speed.

I read somewhere that the sd card corruption may be a bug introduced with a new raspbian release.

After some days of holidays I reconnect my PI. I found out that my SD is not fully allocated so I used the raspi-config to allocate the whole space. Then I clicked on Finish. The program asked me to Reboot: so I did. Now PI can not boot. There are a lot of errors.

I am a bit tired of this. This is a low budget computer and I am a noob with linux but I simply used the official raspi-config and press ENTER twice. I feel that the system is a bit too buggy to be used, even for educational purposes.

[pjc123]

Your errors indicate a corrupted file system. Are you shutting down the pi properly in software (shutdown, init, etc.) and not just pulling the plug? Have you tried a different SD card, preferably a brand and model that other users have had good luck with on the wiki and forums?

[him81]

I always call the sudo halt or sudo shutdown or sudo reboot.

This time I did not touch nor use command line: everything happened from raspi-config: by setting the enlarge partition to entire SD option. After the reboot I see some EXT4-fs errors (ext4_mb_generate_buddy, JBD2...):
ext4_mb_generate_buddy:739: group 4, 998 clusters in bitmap, 705 in gd.
JBD2: Spotted dirty metadata buffer (dev = mmcblk02p2, blocknr = 0). There's a rick of filesystem corruption in case of system crash.
exr2fs_check_mount_point: Can't check if filesystem is mounted due to missing mtab file while determining wheter...

Since the time to enlarge the partition was quite low I am not sure that raspi-config really formatted and zeroed my SD card in the empty space (my SD card is 8GB, the used space was about 2GB I think). So the dirty metadata may be in the previous un-allocated space? If it is instead in the previously allocated space then it was ok in the previous mount. So the enlarge-partition and standard reboot corrupt my SD.

I may try to format my card on windows and start a scandisk on it to detect bad sectors.

The SD card was new, 8GB class 10. I don't have other SD cards to use right now.