Linux file system, NTFS partition display read-only file system, prompt for super fast damage

background : One day when I opened my device, I suddenly found that the NTFS partition could not write to any file, prompting for read-only file system, the phenomenon is as follows:

Repair Process : Troubleshoot permissions issues, use fsck to repair without fruit, use e2fsck to repair

Show super fast damage, so it's good to do, re-repair can:

Solution :

The list is the Ubuntu installation process, I use the archlinux system, here do not repeat, if not installed, please self-solve

With the sudo apt-get install ntfs-3g installation ntfs-3g. Then run the Ntfsfix command on the NTFS partition.

[Email protected]:/home/sanduo> sudo ntfsfix/dev/sda2

Show repair successful, write file to NTFS partition again no error prompt

The following solutions to the Internet, I summarize, I hope to be useful to you

1, for the newer ubuntus you can use -b and options together -d . -btry to repair the bad cluster and -d to fix the dirty state. So the command can

sudo ntfsfix -b -d /dev/sda6

--helpShow them

ntfsfix v2015.3.14AR.1 (libntfs-3g)Usage: ntfsfix [options] device    Attempt to fix an NTFS partition.    --clear-bad-sectors Clear the bad sector list    -d, --clear-dirty       Clear the volume dirty flag    -h, --help              Display this help    -n, --no-action         Do not write anything    -V, --version Display version information

2.

Just to clear up some of your ideas.

My attempt to run FSCK results in the following:

[email protected]:~$ sudo fsck /dev/sda  ...  fsck.ext2: Bad magic number in super-block while trying to open /dev/sda 

Now, that's not surprising, because you're trying to fsck the disk, not its partition. What fsck is, it tries to identify the FS type. Because you have given it the raw disk surface, it does not recognize and use the default type –ext, called Fsck.ext.

Fsck.ext cannot find any FS signatures at that location and tries to find the Super block. Eventually it fails because its disk has only the NTFS partition type.

That's why you have this error.

The correct command is:

sudo fsck /dev/sda1

This will provide the first SATA hard drive with first partition instead of the initial SATA disk itself.

3.

I just fixed my USB drive with "TestDisk" (a Linux command-line (friendly)) utility. My drive is not even installed in Windows and Windows 8 found like 6 partitions (when the drive has only one).

To use the utility, install it:

sudo apt-get install testdisk

Then run it:

sudo testdisk

and follow the instructions. You must search for the partition and then write the changes.

Hope this helps anyone.

4, do a ntfsfix not help at all, just delay the following basic action:

1. Back up all data on the disk as soon as possible

2. Replace the disk with a new disk

It is not necessary to check the smart diagnostics exactly – they will only pick up the percentage of errors. The red flag is two lines:

[1019.726558]SD 0:0:0:0 : [SDA] add. sense: **unrecovered read error** - Span class= "Hljs-selector-tag" >auto reallocate  Failed[1019.726602] JBD: **failed to read block** at offset 462   

Once the disk begins to emit an unrecoverable read error (URE), it should be replaced immediately and only for data recovery. (Too many non-ures also indicate the need for replacement)

Disks should be considered as consumables that must be replaced every few years, so having a very good backup (automated, daily, complete, or at least an external drive) is critical.

Linux file system, NTFS partition display read-only file system, prompt for super fast damage