Comments on: How to Use ‘fsck’ to Repair Linux File System Errors

By: MisterX

MisterX — Sat, 13 Apr 2024 20:41:30 +0000

This is the wrong instruction, on a Debian system, the HDD will be broken.

By: Sam Kumar

Sam Kumar — Fri, 15 Sep 2023 05:41:54 +0000

Thank you for this. I used the first option of fsck command and it seems to have worked like a charm.

I appreciate your contributing to the community.

By: DaVince

DaVince — Mon, 30 Jan 2023 22:27:41 +0000

In reply to Potat. Capitalization and spelling matter on the shell. Device names are never capitalized (so sda, not SDA). unmount should be umount, too.

By: Potat

Potat — Thu, 19 Jan 2023 23:12:34 +0000

When I typed fsck /dev/SDA -a, it showed me this,

fsck from util-linux 2.38.1
fsck.ext2: Bad magic number in super-block while trying to open /dev/SDA
/dev/SDA :
the super-block 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 if 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 or e2fsck -b 32768

Found a dos partition table in /dev/SDA. When I try to run the e2fsck commands it gave, it shows sh: syntax error: unexpected newline. And then when I try to unmount /dev/SDA it can't unmount because it's an invalid argument? I'm a total beginner at Linux and I really don't know what to do now

By: Sarah

Sarah — Fri, 29 Jul 2022 13:52:32 +0000

I updated to the newest version of Ubuntu, now it will not boot. I get the BusyBox black screen and when I used the exit command, here’s the output:

/init: line 866: logsave: not found
Failure: File system check of the root filesystem failed
The root filesystem in /dev/sda6 requires a manual fsck

But when I attempt to do so, I get a text file busy error.

How can I fix this?