corrupted file system(?) - driving me crazy

Pyjamarama

Thank you BuZz !!

Do you know if/how can I fix that?

Or I am doomed having a image that is corrupted and need to re-do five months work from scratch?

The strange thing is that I am encountering it only when I have to deal with this golang library..

BuZz

make sure you have a backup

then from terminal

sudo touch /forcefsck

and reboot.

if you get the error again, it''s likely your sd card is faulty or fake (smaller than it claims to be). Can test it on a PC with something like https://sosfakeflash.wordpress.com/2008/09/02/h2testw-14-gold-standard-in-detecting-usb-counterfeit-drives/

Pyjamarama

Unfortunately the forcefsck did not fix the issue.

Also the h2testw found the card OK:

Warning: Only 29811 of 29812 MByte tested.
Test finished without errors.
You can now delete the test files *.h2w or verify them again.
Writing speed: 18.4 MByte/s
Reading speed: 18.9 MByte/s
H2testw v1.4

So it remains a mystery...

Pyjamarama

Shameless bump :)

Any clues of what else to check?

meleu

@Pyjamarama shameless suggestion that surely won't solve your problem: change the topic title to something like "corrupted file system - my source of problems" or "how can I recover a corrupted file system?".
It's just a way to improve the forum quality... ;-)

Pyjamarama

I got your shameless suggestion and did a shameless title rename hahahahahaha

Anyway it is strange that I get this when this golang thingy is involved...

BuZz

@Pyjamarama have you tried another sdcard?

meleu

@Pyjamarama
do you have another linux machine? It can help if you plug your SD card on another linux and google about "repair corrupted file system linux fsck".

Two links that might be useful:

Pyjamarama

I have a VirtualBox running CentOS 7 but I do not know how to have it see my laptop's sdcard reader

Pyjamarama

Buzz once again you were right. Changed the bloody Kingston with a SanDisk and workd like a charm

SOLVED