Updating bad block inode
I decided to change this to every boot, so problems will be found and possibly fixed earlier.To set up an fsck at every boot, execute the following command: This lowers the amount of disk space used, the amount of packages updated and the amount of services running on the machine, saving both RAM and disk space. The Raspberry Pi was reinstalled and the software was set up again.
But when it’s your home drive, and we’re talking here about 13 faulty blocks out of several zillion blocks, it suddenly seems a bit stupid to just throw the hard drive, when 99.9999993% of the remaining blocks are perfectly okay (yes, this is the actual ratio).(referral link) The machine was running as an FM transmitter so that my regular sound system could play podcasts (Please note that it is probably illegal to transmit without having your HAM license).I't would sync up my feeds and, when turned on, started playing them.It is a destructive write operation, you will lose your data.So most of the writes (292 of 294) failed, meaning the SD card is broken, beyond repair I guess. To prevent your Raspberry Pi's from writing a lot of data, and thus, wearing the SD card, you can do a couple of things.If you like this article, consider sponsoring me by trying out a Digital Ocean VPS.
With this link you'll get a $5 VPS for 2 months free (as in, you get $10 credit).
(Or the filesystem superblock is corrupt) The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem.
If the device is valid and it really contains an ext2/ext3/ext4 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 The superblock contains information about the file system such as the file system type, size, status, information about other metadata structures, block counts, inode counts, supported features, maintenance information, and more and so on (source).
However, even spinrite failed: Booting Spinrite on a spare laptop with a cardreader with this SD card gave the same error. Spinrite has helped me multiple times recover drives, but this one might be to much for it.
Badblocks is a *NIX utility to search for bad blocks on a device.
The file system consistency check utility most of the time is able to find and recover damaged filesystems.