You are not logged in.
I have a PC with Arch Linux, it doesn't load or start, it stays with a black screen, the black screen says:
dev/sda3/:UNEXPECTED INCONSISTENCY; RUN fsck Manually
ERROR: bailing out run fsckI connected the hard drive to another PC to save data.
First the folders appeared with a red X and could not be accessed
I ran the command from the console
sudo badblocks -v /dev/sdbI got these results
Revisando los bloques del 0 al 488386583
Se están revisando los bloques dañados (prueba de solo lectura):
38240760
38240761
38240762
38240763
49909304
49909305
49909306
49909307
49909488
49909489
49909490
49909491
191774708
191774709
191774710
191774711
248598532
248598533
248598534
248598535
248606656
248606657
248606658
248606659
248607300
248607301
248607302
248607303
248608140
248608141
248608142
248608143
248611332
248611333
248611334
248611335
248613724
248613725
248613726
248613727
248615236
248615237
248615238
248615239
248617204
248617205
248617206
248617207
248617276
248617277
248617278
248617279
hecho
Paso terminado, se encontraron 52 bloques dañados. (52/0/0 errores)After checking the hard drive, I can access the arch folders like home/david/Desktop but when I want to copy and paste in another place I get an error like this:
Error opening file
Also I can't open .jpg or pdf files, I can only open folders
The last thing I did on the PC was
sudo pacman -Syubut it was too slow in updating
then i updated this
sudo reflector --country Colombia --protocol https --latest 10 --sort rate --save /etc/pacman.d/mirrorlistHow can I use the fsck command to save my data?
Last edited by utilisima.online (2025-01-28 14:01:02)
Offline
How can I use the fsck command to save my data?
man fscknot enough explanation?
Never argue with an idiot, they will drag you down to their level and then beat you with experience.
It is better to light a candle than curse the darkness.
A journey of a thousand miles begins with a single step.
Offline
I assuming you have ext4 filesystem, boot from arch live iso or any linux and run with root rights:
fdisk -l /dev/sdb # first list and check partition table
e2fsck -p /dev/sdbX # should fix what can be safly fixed, else will ask what to do; X is number of your partition
e2fsck -cc /dev/sdbX # e2fsck will run badblocks with non-destructive read-write test. If any bad blocks are found, they are
added to the bad block inode to prevent them from being allocated to a file or directory.Last edited by xerxes_ (2025-01-29 17:18:27)
Offline