Arch Linux

polando

Member

Registered: 2021-03-28

Posts: 2

UNEXPECTED INCOSISTIENCY, run fsck manually after a reboot.

Hello,

my system froze when i was playing a video game so i rebooted my PC. After the reboot an error message showed up telling me "UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY".
So I did "fsck /dev/nvme0n1p2" and it said "Superblock needs_recovery flag is clear but journal has data. Run journaly anyway?" so i pressed y, it said "fsck.ext4: Input/output error while recovering journal of /dev/nvme0n1p2" and "fsck.ext4: unable to set superblock flags on /dev/nvme0n1p2".
I have tried every combination of y and n after the fsck command and it still outputs the same message.

I have made a ddrescue image of the drive and it didn't show any errors. Smartctl shows no errors.
The disk is not old and still on warranty.

Lone_Wolf

Member

From: Netherlands, Europe

Registered: 2005-10-04

Posts: 11,911

Re: UNEXPECTED INCOSISTIENCY, run fsck manually after a reboot.

Have you tried BadBlocks ?

---

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

(A works at time B)  && (time C > time B ) ≠  (A works at time C)

polando

Member

Registered: 2021-03-28

Posts: 2

Re: UNEXPECTED INCOSISTIENCY, run fsck manually after a reboot.

I have done some stuff, testing the disk and such and smartctl has reported that it has encountered some issue and the disk is in read-only mode, I've backed up all my data and decided to put the disk on warranty.