Raspberry Pi Superblock Damage Repair

"0x00"

One day I was about to practice writing HTML5, but did not want to make computer files too confusing, so on the Raspberry Pi set up a server, ready to build a small website to practice practiced hand.

After the configuration, wrote a point HTML5 added a bit of JavaScript, and later switched power after the boot does not. Before it was a bit unstable, initially thought to be the power cord contact bad,

After changing the line also not, the SD card pulled down, found that the SD card has a block of plastic angle dropped, but look at contact with the contact should be no problem, I used alcohol to rub a touch point

, and then start or not. Because there is no monitor, do not bother to get, put a few days wait for the monitor to get again.

"0X01"

Today, the monitor doesn't have any output, so I'm sure it didn't start at all. So I found a previous play XBMC SD card, plugged in, started.

The problem with the SD card is determined. I plugged the SD card into the computer and the computer automatically mounted the boot volume, but the other volume was not automatically mounted. So the Manual Check

Checked the mmcxxx0,mmcxxx0p1,mmcxxx0p2 in the/dev directory.

The first two can be mounted normally, and the third mount will prompt for superblock errors.

So Baidu a bit

0 byte 1024x768  bytes), or it may be in block 0. The data in the Super block is actually the control information part of the file volume, or it is a volume resource table, and most of the information about the file volume is stored here. For example, the size of each block in a hard disk partition, the number of block group on the hard disk partition, and the number of Inode in each block group.

And then

Fsck.ext4-v/DEV/MMCXXX0P2

MMCXXX0P2 represents specific equipment files, depending on the actual situation.

Plug it into the Raspberry Pi and start successfully.

But there is error output, forget ...

The above-mentioned bird probably means either enter Ctrl+d reboot or give me the root user password.

Press CTRL+D after the discovery is a dead loop, and then I decided to enter the root password (the problem is the password I forgot, usually use PI users).

Try a few successful login, randomly lost some shell command found that some can use some not to use, a bit like safe mode.

Then I entered fsck decisively and checked for the next disk error, and after a series of Yes, the reboot was successful.

"0X02"

This Raspberry Pi is a generation B type, from 13 on my side, it's a few years ... Due to the performance of the outdated, it has been from my

The board was relegated to the second line ... Miss this board to bring me a lot of happiness (although it is a bit of speed I am crazy), the original teeth spent

The 300 oceans are also counted.

Raspberry Pi Superblock Damage Repair