Fix corrupt NTFS partition without WindowsRepair NTFS without Windows?How to repair bad sectors on ntfs...
What do the pedals on grand pianos do?
How to acknowledge an embarrassing job interview, now that I work directly with the interviewer?
A "strange" unit radio astronomy
What's the purpose of these copper coils with resistors inside them in A Yamaha RX-V396RDS amplifier?
Must a tritone substitution use a dominant seventh chord?
What am I? I am in theaters and computer programs
Is the set of paths between any two points moving only in units on the plane countable or uncountable?
What is the difference between ashamed and shamed?
I can't die. Who am I?
What is this waxed root vegetable?
How do ISS astronauts "get their stripes"?
Reason Why Dimensional Travelling Would be Restricted
Called into a meeting and told we are being made redundant (laid off) and "not to share outside". Can I tell my partner?
Use comma instead of & in table
Is there a frame of reference in which I was born before I was conceived?
Six real numbers so that product of any five is the sixth one
Accessing something inside the object when you don't know the key
What if I store 10TB on azure servers and then keep the vm powered off?
Equivalent to "source" in OpenBSD?
CBP Reminds Travelers to Allow 72 Hours for ESTA. Why?
Whom do I have to contact for a ticket refund in case of denied boarding (in the EU)?
Can you use a beast's innate abilities while polymorphed?
Has the Isbell–Freyd criterion ever been used to check that a category is concretisable?
Is there a German word for “analytics”?
Fix corrupt NTFS partition without Windows
Repair NTFS without Windows?How to repair bad sectors on ntfs partitionExternal HDD not unmounted properly and now not working correctlyUnable to access my other partition (volume)Unable to mount NTFS external hard driveCannot access windows partition from ubuntuCan't mount NTFS drive - “NTFS signature is missing.”Repair whole NTFS filesystemproblem in accessing NTFS drive: “The disk contains an unclean file system”Can't mount or fix corrupt NTFS partition on working HDDWhy does my NTFS partition mount as read only?USB stick bad superblock. Works absolutely fine in WindowsForce mount Fat16 partiton?Problem booting the Ubuntu 12.04.01 OS due to bad sectors on the HDDDrive damaged during VMWare copyHelp with corrupted NTFS partitionCan't mount a partitionSuperblock invalid, disk in useRepairing corrupt superblock in crypto_LUKS filesystemHow can I run fsck on ntfs partitions on my hard drive?
MY NTFS Partition has gotten corrupt somehow (it's a relic from the days when I had Windows installed).
I'm putting the debug output of fdisk and blkid here.
At the same time, any OS is unable to mount my root partition, which is located next to my NTFS partition. I'm not sure if this has anything to do with it, though. I get the following error while trying to mount my root partition (sda5)
mount: wrong fs type, bad option, bad superblock on /dev/sda5,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
ubuntu@ubuntu:~$ dmesg | tail
[ 1019.726530] Descriptor sense data with sense descriptors (in hex):
[ 1019.726533] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 1019.726551] 1a 3e ed 92
[ 1019.726558] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
[ 1019.726568] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 1a 3e ed 40 00 01 00 00
[ 1019.726584] end_request: I/O error, dev sda, sector 440331666
[ 1019.726602] JBD: Failed to read block at offset 462
[ 1019.726609] ata1: EH complete
[ 1019.726612] JBD: recovery failed
[ 1019.726617] EXT4-fs (sda5): error loading journal
When I open gparted (using live CD), I get an exclamation next to my NTFS drive which states
Is there a way to run chkdsk
without using windows ?
My attempt to run fsck
results in the following :
ubuntu@ubuntu:~$ sudo fsck /dev/sda
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and 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 <device>
Update: I was able to fix the NTFS partition running chkdsk off Hiren's BootCD, but it seems that the superblock problem still remains.
Update 2: Fixed superblock issue using e2fsck -c /dev/sda5
partitioning hard-drive ntfs fsck
add a comment |
MY NTFS Partition has gotten corrupt somehow (it's a relic from the days when I had Windows installed).
I'm putting the debug output of fdisk and blkid here.
At the same time, any OS is unable to mount my root partition, which is located next to my NTFS partition. I'm not sure if this has anything to do with it, though. I get the following error while trying to mount my root partition (sda5)
mount: wrong fs type, bad option, bad superblock on /dev/sda5,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
ubuntu@ubuntu:~$ dmesg | tail
[ 1019.726530] Descriptor sense data with sense descriptors (in hex):
[ 1019.726533] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 1019.726551] 1a 3e ed 92
[ 1019.726558] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
[ 1019.726568] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 1a 3e ed 40 00 01 00 00
[ 1019.726584] end_request: I/O error, dev sda, sector 440331666
[ 1019.726602] JBD: Failed to read block at offset 462
[ 1019.726609] ata1: EH complete
[ 1019.726612] JBD: recovery failed
[ 1019.726617] EXT4-fs (sda5): error loading journal
When I open gparted (using live CD), I get an exclamation next to my NTFS drive which states
Is there a way to run chkdsk
without using windows ?
My attempt to run fsck
results in the following :
ubuntu@ubuntu:~$ sudo fsck /dev/sda
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and 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 <device>
Update: I was able to fix the NTFS partition running chkdsk off Hiren's BootCD, but it seems that the superblock problem still remains.
Update 2: Fixed superblock issue using e2fsck -c /dev/sda5
partitioning hard-drive ntfs fsck
1
Link to a related question: askubuntu.com/q/58755/31592
– blong
Apr 10 '13 at 22:24
add a comment |
MY NTFS Partition has gotten corrupt somehow (it's a relic from the days when I had Windows installed).
I'm putting the debug output of fdisk and blkid here.
At the same time, any OS is unable to mount my root partition, which is located next to my NTFS partition. I'm not sure if this has anything to do with it, though. I get the following error while trying to mount my root partition (sda5)
mount: wrong fs type, bad option, bad superblock on /dev/sda5,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
ubuntu@ubuntu:~$ dmesg | tail
[ 1019.726530] Descriptor sense data with sense descriptors (in hex):
[ 1019.726533] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 1019.726551] 1a 3e ed 92
[ 1019.726558] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
[ 1019.726568] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 1a 3e ed 40 00 01 00 00
[ 1019.726584] end_request: I/O error, dev sda, sector 440331666
[ 1019.726602] JBD: Failed to read block at offset 462
[ 1019.726609] ata1: EH complete
[ 1019.726612] JBD: recovery failed
[ 1019.726617] EXT4-fs (sda5): error loading journal
When I open gparted (using live CD), I get an exclamation next to my NTFS drive which states
Is there a way to run chkdsk
without using windows ?
My attempt to run fsck
results in the following :
ubuntu@ubuntu:~$ sudo fsck /dev/sda
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and 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 <device>
Update: I was able to fix the NTFS partition running chkdsk off Hiren's BootCD, but it seems that the superblock problem still remains.
Update 2: Fixed superblock issue using e2fsck -c /dev/sda5
partitioning hard-drive ntfs fsck
MY NTFS Partition has gotten corrupt somehow (it's a relic from the days when I had Windows installed).
I'm putting the debug output of fdisk and blkid here.
At the same time, any OS is unable to mount my root partition, which is located next to my NTFS partition. I'm not sure if this has anything to do with it, though. I get the following error while trying to mount my root partition (sda5)
mount: wrong fs type, bad option, bad superblock on /dev/sda5,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
ubuntu@ubuntu:~$ dmesg | tail
[ 1019.726530] Descriptor sense data with sense descriptors (in hex):
[ 1019.726533] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 1019.726551] 1a 3e ed 92
[ 1019.726558] sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
[ 1019.726568] sd 0:0:0:0: [sda] CDB: Read(10): 28 00 1a 3e ed 40 00 01 00 00
[ 1019.726584] end_request: I/O error, dev sda, sector 440331666
[ 1019.726602] JBD: Failed to read block at offset 462
[ 1019.726609] ata1: EH complete
[ 1019.726612] JBD: recovery failed
[ 1019.726617] EXT4-fs (sda5): error loading journal
When I open gparted (using live CD), I get an exclamation next to my NTFS drive which states
Is there a way to run chkdsk
without using windows ?
My attempt to run fsck
results in the following :
ubuntu@ubuntu:~$ sudo fsck /dev/sda
fsck from util-linux-ng 2.17.2
e2fsck 1.41.14 (22-Dec-2010)
fsck.ext2: Superblock invalid, trying backup blocks...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and 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 <device>
Update: I was able to fix the NTFS partition running chkdsk off Hiren's BootCD, but it seems that the superblock problem still remains.
Update 2: Fixed superblock issue using e2fsck -c /dev/sda5
partitioning hard-drive ntfs fsck
partitioning hard-drive ntfs fsck
edited May 22 '17 at 20:21
wjandrea
9,28842664
9,28842664
asked Jun 8 '11 at 19:18
NemoNemo
6,63654163
6,63654163
1
Link to a related question: askubuntu.com/q/58755/31592
– blong
Apr 10 '13 at 22:24
add a comment |
1
Link to a related question: askubuntu.com/q/58755/31592
– blong
Apr 10 '13 at 22:24
1
1
Link to a related question: askubuntu.com/q/58755/31592
– blong
Apr 10 '13 at 22:24
Link to a related question: askubuntu.com/q/58755/31592
– blong
Apr 10 '13 at 22:24
add a comment |
10 Answers
10
active
oldest
votes
Install ntfs-3g with sudo apt-get install ntfs-3g
.
Then run the ntfsfix command on your NTFS partition.
For example:
ntfsfix /dev/hda6
ntfsfix v2.0.0 (libntfs 10:0:0)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-h, --help Display this help
-V, --version Display version information
Developers' email address:
linux-ntfs-dev@lists.sf.net
Linux NTFS
homepage: http://www.linux-ntfs.org
For newer Ubuntus You can use -b
and -d
option together. -b
tries to fix bad clusters and -d
to fix dirty states. So the command can be
sudo ntfsfix -b -d /dev/sda6
--help
shows them
ntfsfix v2015.3.14AR.1 (libntfs-3g)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-b, --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
Do you have any suggestions for the superblock issue ? I've fixed the NTFS partition.
– Nemo
Jun 8 '11 at 20:25
5
This is not a helpful answer unfortunately - the problem is not in fact how to fix the NTFS filesystem structures, but the unrecoverable read errors at the block device level (below NTFS). This means that (as psusi already said) "your disk is toast" - the only option is to buy a new hard drive and restore from backup. If you don't have up to date backups you can try using GNU ddrescue ("apt-get install gddrescue") to recover as much data as possible to a disk image file. Google for Ubuntu disk recovery for more help.
– RichVel
Oct 16 '11 at 6:00
3
@RolandTaylor: I'm sure it was intended to be helpful, but telling someone to run a filesystem check when there is a visible unrecoverable read error in the logs is not going to help them. They might be able to fix their error temporarily but the disk hardware really is failing and the ntfix isn't helping that.
– RichVel
Oct 17 '11 at 8:01
5
Sorry, that's not correct: the first version of the question included the line "sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed" in the logs - the Unrecovered Read Error (URE) is what indicates the drive is failing. If you get unrecovered write errors, that can be lived with for a while (drive remaps the blocks), but UREs are not OK. See superuser.com/questions/114675/… for a similar error. See en.wikipedia.org/wiki/S.M.A.R.T.#cite_note-labs.google.com-1 - huge Google analysis.
– RichVel
Oct 19 '11 at 6:57
1
One more good link on the URE issue is this answer on another Stack Exchange site: unix.stackexchange.com/questions/1869/…
– RichVel
Oct 19 '11 at 7:01
|
show 6 more comments
I've just fixed my USB drive using "testdisk", a Linux command line (yet friendly) utility. My drive was not even mounting in Windows and Windows 8 discovered like 6 partitions (when the drive had 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 partitions and then write the changes.
Hope this help anyone.
2
this was great..fixed a broken partition table on my external hard disk! Thank you! V
– vellvisher
Jan 15 '13 at 14:43
add a comment |
Just to clear some of your points up.
My attempt to run fsck results in the following :
ubuntu@ubuntu:~$ sudo fsck /dev/sda
...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
Now, thats not wonder, because you are trying to fsck the disk, and not its partition.
What fsck does is, it tries to recognize the FS type. Because you have given it raw disk surface, it fails to recognize and resorts to default type - ext, calling fsck.ext.
fsck.ext does not find any FS signature in the location and tries to find superblocks. Ultimately it fails, because its disk with only NTFS partition type.
This is why you have this error.
The correct command would be:
sudo fsck /dev/sda1
That would feed the FIRST partition of first sata hard drive, not the first sata disk itself.
this might not be the answer solving the OPs problem, its information is pure gold, though. Thanks a bunch!
– oliverjkb
Feb 13 '17 at 18:11
is you sda1ntfs
?
– Adi Prasetyo
Nov 29 '17 at 11:40
add a comment |
Your disk is toast. Check the SMART diagnostics in the disk utility to confirm; it should say you have a ton of bad sectors and need to replace the drive.
add a comment |
I agree with @psusi: the disk needs replacing, see my comment under accepted answer. Doing an ntfsfix
will not help at all, and just delays the essential action of:
- backing up all data on the disk ASAP
- replacing the disk with a new one
There's no need really to check the SMART diagnostics - they only pick up a percentage of errors anyway. The red flags are the two lines:
[ 1019.726558] sd 0:0:0:0: [sda] Add. Sense: **Unrecovered read error** - auto reallocate failed
[ 1019.726602] JBD: **Failed to read block** at offset 462
As soon as a disk starts giving unrecoverable read errors (UREs), it should be replaced immediately and only used for data recovery. (An excessive level of non-UREs also indicates replacement is needed.)
Disks should be viewed as consumables that must be replaced every few years, hence having really good backups (automated, daily, complete, and at least to an external drive) is crucial.
add a comment |
In Ubuntu 14.04 Just try this
sudo ntfsfix /dev/sdXY
Where XY
is your partition. (/dev/sda2
in your case)
add a comment |
As the other answers have said, in this case it's probably a bad disk..
But for the benefit of others facing actual NTFS corruption - unfortunately the ntfsfix tool is very limited compared to Microsoft's chkdsk. Try to get a Windows install going - preferably with the newest version of Windows as Microsoft is presumably constantly improving chkdsk (I hope..) Newer versions of Windows are often available for free as trials. If the problem is in a USB disk you can try installing Windows in something like VirtualBox and give the VM control of the USB device.
add a comment |
Unfortunately the free tools available on Linux are very limited with regards to fixing NTFS partitions.
Most likely you can still recover your data by using the secondary MFT stored at the end of the disk. It is usually not used, but it should contain an up-to-date version of your directory structure. There is a good chance it was not affected by the disk errors.
In the past, I have used Runtime Software's (commercial, 79$) product GetDataBack NTFS with great success for this. It is one of the few NTFS tools (the only?) that runs in WINE and as a Linux LiveCD, and the free demo should be enough to see if your data is still there. If it is, your data might just be worth buying the tool.
The LiveCD runs Knoppix Linux and has all their tools preinstalled. Note that you'll still need a license key to actually use the tools, but it should be enough to see if it works on your computer.
Disclaimer: I have no affiliation with Runtime software other than having bought their product a few years ago.
+1 not because I have experience with what's in this answer; the up is for raising awareness of lesser known alternatives to things such as Parted Magic.
– Graham Perrin
Jul 16 '16 at 14:23
add a comment |
This answer will probably just work for 10.04 (lucid) and later versions of Ubuntu!
Try sudo ntfsfix -b /dev/sda2
.
You need ntfs-3g installed. If you don't have it, you can install it in the Software Center by clicking that link, or from the Terminal (Ctrl+Alt+T) by running these commands:
sudo apt-get update
sudo apt-get install ntfs-3g
4
Why use NTFSProgs when NTFS-3g is installed by default? NTFSProgs is dead, as it has been completely merged into NTFS-3g. Switching to the former might cause more problems than it solves.
– TSJNachos117
Sep 21 '13 at 20:16
1
NTFSProgs is no longer part of the package archives after 12.04 precise.
– kynan
Jan 3 '15 at 16:43
add a comment |
I just had the same problem on a 3TB NTFS USB. Big drama, as you can imagine.
I first tried to fix it on my wife's Windows box. No joy.
sudo ntfsfix /dev/sdcx extremely quickly fixed it.
Hooray! Back in business. Really must get a new disk and promptly re-format it to a proper, adult filesystem.
add a comment |
protected by Community♦ May 6 '15 at 19:24
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
10 Answers
10
active
oldest
votes
10 Answers
10
active
oldest
votes
active
oldest
votes
active
oldest
votes
Install ntfs-3g with sudo apt-get install ntfs-3g
.
Then run the ntfsfix command on your NTFS partition.
For example:
ntfsfix /dev/hda6
ntfsfix v2.0.0 (libntfs 10:0:0)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-h, --help Display this help
-V, --version Display version information
Developers' email address:
linux-ntfs-dev@lists.sf.net
Linux NTFS
homepage: http://www.linux-ntfs.org
For newer Ubuntus You can use -b
and -d
option together. -b
tries to fix bad clusters and -d
to fix dirty states. So the command can be
sudo ntfsfix -b -d /dev/sda6
--help
shows them
ntfsfix v2015.3.14AR.1 (libntfs-3g)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-b, --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
Do you have any suggestions for the superblock issue ? I've fixed the NTFS partition.
– Nemo
Jun 8 '11 at 20:25
5
This is not a helpful answer unfortunately - the problem is not in fact how to fix the NTFS filesystem structures, but the unrecoverable read errors at the block device level (below NTFS). This means that (as psusi already said) "your disk is toast" - the only option is to buy a new hard drive and restore from backup. If you don't have up to date backups you can try using GNU ddrescue ("apt-get install gddrescue") to recover as much data as possible to a disk image file. Google for Ubuntu disk recovery for more help.
– RichVel
Oct 16 '11 at 6:00
3
@RolandTaylor: I'm sure it was intended to be helpful, but telling someone to run a filesystem check when there is a visible unrecoverable read error in the logs is not going to help them. They might be able to fix their error temporarily but the disk hardware really is failing and the ntfix isn't helping that.
– RichVel
Oct 17 '11 at 8:01
5
Sorry, that's not correct: the first version of the question included the line "sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed" in the logs - the Unrecovered Read Error (URE) is what indicates the drive is failing. If you get unrecovered write errors, that can be lived with for a while (drive remaps the blocks), but UREs are not OK. See superuser.com/questions/114675/… for a similar error. See en.wikipedia.org/wiki/S.M.A.R.T.#cite_note-labs.google.com-1 - huge Google analysis.
– RichVel
Oct 19 '11 at 6:57
1
One more good link on the URE issue is this answer on another Stack Exchange site: unix.stackexchange.com/questions/1869/…
– RichVel
Oct 19 '11 at 7:01
|
show 6 more comments
Install ntfs-3g with sudo apt-get install ntfs-3g
.
Then run the ntfsfix command on your NTFS partition.
For example:
ntfsfix /dev/hda6
ntfsfix v2.0.0 (libntfs 10:0:0)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-h, --help Display this help
-V, --version Display version information
Developers' email address:
linux-ntfs-dev@lists.sf.net
Linux NTFS
homepage: http://www.linux-ntfs.org
For newer Ubuntus You can use -b
and -d
option together. -b
tries to fix bad clusters and -d
to fix dirty states. So the command can be
sudo ntfsfix -b -d /dev/sda6
--help
shows them
ntfsfix v2015.3.14AR.1 (libntfs-3g)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-b, --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
Do you have any suggestions for the superblock issue ? I've fixed the NTFS partition.
– Nemo
Jun 8 '11 at 20:25
5
This is not a helpful answer unfortunately - the problem is not in fact how to fix the NTFS filesystem structures, but the unrecoverable read errors at the block device level (below NTFS). This means that (as psusi already said) "your disk is toast" - the only option is to buy a new hard drive and restore from backup. If you don't have up to date backups you can try using GNU ddrescue ("apt-get install gddrescue") to recover as much data as possible to a disk image file. Google for Ubuntu disk recovery for more help.
– RichVel
Oct 16 '11 at 6:00
3
@RolandTaylor: I'm sure it was intended to be helpful, but telling someone to run a filesystem check when there is a visible unrecoverable read error in the logs is not going to help them. They might be able to fix their error temporarily but the disk hardware really is failing and the ntfix isn't helping that.
– RichVel
Oct 17 '11 at 8:01
5
Sorry, that's not correct: the first version of the question included the line "sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed" in the logs - the Unrecovered Read Error (URE) is what indicates the drive is failing. If you get unrecovered write errors, that can be lived with for a while (drive remaps the blocks), but UREs are not OK. See superuser.com/questions/114675/… for a similar error. See en.wikipedia.org/wiki/S.M.A.R.T.#cite_note-labs.google.com-1 - huge Google analysis.
– RichVel
Oct 19 '11 at 6:57
1
One more good link on the URE issue is this answer on another Stack Exchange site: unix.stackexchange.com/questions/1869/…
– RichVel
Oct 19 '11 at 7:01
|
show 6 more comments
Install ntfs-3g with sudo apt-get install ntfs-3g
.
Then run the ntfsfix command on your NTFS partition.
For example:
ntfsfix /dev/hda6
ntfsfix v2.0.0 (libntfs 10:0:0)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-h, --help Display this help
-V, --version Display version information
Developers' email address:
linux-ntfs-dev@lists.sf.net
Linux NTFS
homepage: http://www.linux-ntfs.org
For newer Ubuntus You can use -b
and -d
option together. -b
tries to fix bad clusters and -d
to fix dirty states. So the command can be
sudo ntfsfix -b -d /dev/sda6
--help
shows them
ntfsfix v2015.3.14AR.1 (libntfs-3g)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-b, --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
Install ntfs-3g with sudo apt-get install ntfs-3g
.
Then run the ntfsfix command on your NTFS partition.
For example:
ntfsfix /dev/hda6
ntfsfix v2.0.0 (libntfs 10:0:0)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-h, --help Display this help
-V, --version Display version information
Developers' email address:
linux-ntfs-dev@lists.sf.net
Linux NTFS
homepage: http://www.linux-ntfs.org
For newer Ubuntus You can use -b
and -d
option together. -b
tries to fix bad clusters and -d
to fix dirty states. So the command can be
sudo ntfsfix -b -d /dev/sda6
--help
shows them
ntfsfix v2015.3.14AR.1 (libntfs-3g)
Usage: ntfsfix [options] device
Attempt to fix an NTFS partition.
-b, --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
edited Nov 21 '16 at 14:31
Anwar
56.8k22146254
56.8k22146254
answered Jun 8 '11 at 19:56
RolandiXor♦RolandiXor
44.6k25140231
44.6k25140231
Do you have any suggestions for the superblock issue ? I've fixed the NTFS partition.
– Nemo
Jun 8 '11 at 20:25
5
This is not a helpful answer unfortunately - the problem is not in fact how to fix the NTFS filesystem structures, but the unrecoverable read errors at the block device level (below NTFS). This means that (as psusi already said) "your disk is toast" - the only option is to buy a new hard drive and restore from backup. If you don't have up to date backups you can try using GNU ddrescue ("apt-get install gddrescue") to recover as much data as possible to a disk image file. Google for Ubuntu disk recovery for more help.
– RichVel
Oct 16 '11 at 6:00
3
@RolandTaylor: I'm sure it was intended to be helpful, but telling someone to run a filesystem check when there is a visible unrecoverable read error in the logs is not going to help them. They might be able to fix their error temporarily but the disk hardware really is failing and the ntfix isn't helping that.
– RichVel
Oct 17 '11 at 8:01
5
Sorry, that's not correct: the first version of the question included the line "sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed" in the logs - the Unrecovered Read Error (URE) is what indicates the drive is failing. If you get unrecovered write errors, that can be lived with for a while (drive remaps the blocks), but UREs are not OK. See superuser.com/questions/114675/… for a similar error. See en.wikipedia.org/wiki/S.M.A.R.T.#cite_note-labs.google.com-1 - huge Google analysis.
– RichVel
Oct 19 '11 at 6:57
1
One more good link on the URE issue is this answer on another Stack Exchange site: unix.stackexchange.com/questions/1869/…
– RichVel
Oct 19 '11 at 7:01
|
show 6 more comments
Do you have any suggestions for the superblock issue ? I've fixed the NTFS partition.
– Nemo
Jun 8 '11 at 20:25
5
This is not a helpful answer unfortunately - the problem is not in fact how to fix the NTFS filesystem structures, but the unrecoverable read errors at the block device level (below NTFS). This means that (as psusi already said) "your disk is toast" - the only option is to buy a new hard drive and restore from backup. If you don't have up to date backups you can try using GNU ddrescue ("apt-get install gddrescue") to recover as much data as possible to a disk image file. Google for Ubuntu disk recovery for more help.
– RichVel
Oct 16 '11 at 6:00
3
@RolandTaylor: I'm sure it was intended to be helpful, but telling someone to run a filesystem check when there is a visible unrecoverable read error in the logs is not going to help them. They might be able to fix their error temporarily but the disk hardware really is failing and the ntfix isn't helping that.
– RichVel
Oct 17 '11 at 8:01
5
Sorry, that's not correct: the first version of the question included the line "sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed" in the logs - the Unrecovered Read Error (URE) is what indicates the drive is failing. If you get unrecovered write errors, that can be lived with for a while (drive remaps the blocks), but UREs are not OK. See superuser.com/questions/114675/… for a similar error. See en.wikipedia.org/wiki/S.M.A.R.T.#cite_note-labs.google.com-1 - huge Google analysis.
– RichVel
Oct 19 '11 at 6:57
1
One more good link on the URE issue is this answer on another Stack Exchange site: unix.stackexchange.com/questions/1869/…
– RichVel
Oct 19 '11 at 7:01
Do you have any suggestions for the superblock issue ? I've fixed the NTFS partition.
– Nemo
Jun 8 '11 at 20:25
Do you have any suggestions for the superblock issue ? I've fixed the NTFS partition.
– Nemo
Jun 8 '11 at 20:25
5
5
This is not a helpful answer unfortunately - the problem is not in fact how to fix the NTFS filesystem structures, but the unrecoverable read errors at the block device level (below NTFS). This means that (as psusi already said) "your disk is toast" - the only option is to buy a new hard drive and restore from backup. If you don't have up to date backups you can try using GNU ddrescue ("apt-get install gddrescue") to recover as much data as possible to a disk image file. Google for Ubuntu disk recovery for more help.
– RichVel
Oct 16 '11 at 6:00
This is not a helpful answer unfortunately - the problem is not in fact how to fix the NTFS filesystem structures, but the unrecoverable read errors at the block device level (below NTFS). This means that (as psusi already said) "your disk is toast" - the only option is to buy a new hard drive and restore from backup. If you don't have up to date backups you can try using GNU ddrescue ("apt-get install gddrescue") to recover as much data as possible to a disk image file. Google for Ubuntu disk recovery for more help.
– RichVel
Oct 16 '11 at 6:00
3
3
@RolandTaylor: I'm sure it was intended to be helpful, but telling someone to run a filesystem check when there is a visible unrecoverable read error in the logs is not going to help them. They might be able to fix their error temporarily but the disk hardware really is failing and the ntfix isn't helping that.
– RichVel
Oct 17 '11 at 8:01
@RolandTaylor: I'm sure it was intended to be helpful, but telling someone to run a filesystem check when there is a visible unrecoverable read error in the logs is not going to help them. They might be able to fix their error temporarily but the disk hardware really is failing and the ntfix isn't helping that.
– RichVel
Oct 17 '11 at 8:01
5
5
Sorry, that's not correct: the first version of the question included the line "sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed" in the logs - the Unrecovered Read Error (URE) is what indicates the drive is failing. If you get unrecovered write errors, that can be lived with for a while (drive remaps the blocks), but UREs are not OK. See superuser.com/questions/114675/… for a similar error. See en.wikipedia.org/wiki/S.M.A.R.T.#cite_note-labs.google.com-1 - huge Google analysis.
– RichVel
Oct 19 '11 at 6:57
Sorry, that's not correct: the first version of the question included the line "sd 0:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed" in the logs - the Unrecovered Read Error (URE) is what indicates the drive is failing. If you get unrecovered write errors, that can be lived with for a while (drive remaps the blocks), but UREs are not OK. See superuser.com/questions/114675/… for a similar error. See en.wikipedia.org/wiki/S.M.A.R.T.#cite_note-labs.google.com-1 - huge Google analysis.
– RichVel
Oct 19 '11 at 6:57
1
1
One more good link on the URE issue is this answer on another Stack Exchange site: unix.stackexchange.com/questions/1869/…
– RichVel
Oct 19 '11 at 7:01
One more good link on the URE issue is this answer on another Stack Exchange site: unix.stackexchange.com/questions/1869/…
– RichVel
Oct 19 '11 at 7:01
|
show 6 more comments
I've just fixed my USB drive using "testdisk", a Linux command line (yet friendly) utility. My drive was not even mounting in Windows and Windows 8 discovered like 6 partitions (when the drive had 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 partitions and then write the changes.
Hope this help anyone.
2
this was great..fixed a broken partition table on my external hard disk! Thank you! V
– vellvisher
Jan 15 '13 at 14:43
add a comment |
I've just fixed my USB drive using "testdisk", a Linux command line (yet friendly) utility. My drive was not even mounting in Windows and Windows 8 discovered like 6 partitions (when the drive had 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 partitions and then write the changes.
Hope this help anyone.
2
this was great..fixed a broken partition table on my external hard disk! Thank you! V
– vellvisher
Jan 15 '13 at 14:43
add a comment |
I've just fixed my USB drive using "testdisk", a Linux command line (yet friendly) utility. My drive was not even mounting in Windows and Windows 8 discovered like 6 partitions (when the drive had 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 partitions and then write the changes.
Hope this help anyone.
I've just fixed my USB drive using "testdisk", a Linux command line (yet friendly) utility. My drive was not even mounting in Windows and Windows 8 discovered like 6 partitions (when the drive had 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 partitions and then write the changes.
Hope this help anyone.
answered Dec 17 '12 at 18:35
Diego JancicDiego Jancic
30039
30039
2
this was great..fixed a broken partition table on my external hard disk! Thank you! V
– vellvisher
Jan 15 '13 at 14:43
add a comment |
2
this was great..fixed a broken partition table on my external hard disk! Thank you! V
– vellvisher
Jan 15 '13 at 14:43
2
2
this was great..fixed a broken partition table on my external hard disk! Thank you! V
– vellvisher
Jan 15 '13 at 14:43
this was great..fixed a broken partition table on my external hard disk! Thank you! V
– vellvisher
Jan 15 '13 at 14:43
add a comment |
Just to clear some of your points up.
My attempt to run fsck results in the following :
ubuntu@ubuntu:~$ sudo fsck /dev/sda
...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
Now, thats not wonder, because you are trying to fsck the disk, and not its partition.
What fsck does is, it tries to recognize the FS type. Because you have given it raw disk surface, it fails to recognize and resorts to default type - ext, calling fsck.ext.
fsck.ext does not find any FS signature in the location and tries to find superblocks. Ultimately it fails, because its disk with only NTFS partition type.
This is why you have this error.
The correct command would be:
sudo fsck /dev/sda1
That would feed the FIRST partition of first sata hard drive, not the first sata disk itself.
this might not be the answer solving the OPs problem, its information is pure gold, though. Thanks a bunch!
– oliverjkb
Feb 13 '17 at 18:11
is you sda1ntfs
?
– Adi Prasetyo
Nov 29 '17 at 11:40
add a comment |
Just to clear some of your points up.
My attempt to run fsck results in the following :
ubuntu@ubuntu:~$ sudo fsck /dev/sda
...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
Now, thats not wonder, because you are trying to fsck the disk, and not its partition.
What fsck does is, it tries to recognize the FS type. Because you have given it raw disk surface, it fails to recognize and resorts to default type - ext, calling fsck.ext.
fsck.ext does not find any FS signature in the location and tries to find superblocks. Ultimately it fails, because its disk with only NTFS partition type.
This is why you have this error.
The correct command would be:
sudo fsck /dev/sda1
That would feed the FIRST partition of first sata hard drive, not the first sata disk itself.
this might not be the answer solving the OPs problem, its information is pure gold, though. Thanks a bunch!
– oliverjkb
Feb 13 '17 at 18:11
is you sda1ntfs
?
– Adi Prasetyo
Nov 29 '17 at 11:40
add a comment |
Just to clear some of your points up.
My attempt to run fsck results in the following :
ubuntu@ubuntu:~$ sudo fsck /dev/sda
...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
Now, thats not wonder, because you are trying to fsck the disk, and not its partition.
What fsck does is, it tries to recognize the FS type. Because you have given it raw disk surface, it fails to recognize and resorts to default type - ext, calling fsck.ext.
fsck.ext does not find any FS signature in the location and tries to find superblocks. Ultimately it fails, because its disk with only NTFS partition type.
This is why you have this error.
The correct command would be:
sudo fsck /dev/sda1
That would feed the FIRST partition of first sata hard drive, not the first sata disk itself.
Just to clear some of your points up.
My attempt to run fsck results in the following :
ubuntu@ubuntu:~$ sudo fsck /dev/sda
...
fsck.ext2: Bad magic number in super-block while trying to open /dev/sda
Now, thats not wonder, because you are trying to fsck the disk, and not its partition.
What fsck does is, it tries to recognize the FS type. Because you have given it raw disk surface, it fails to recognize and resorts to default type - ext, calling fsck.ext.
fsck.ext does not find any FS signature in the location and tries to find superblocks. Ultimately it fails, because its disk with only NTFS partition type.
This is why you have this error.
The correct command would be:
sudo fsck /dev/sda1
That would feed the FIRST partition of first sata hard drive, not the first sata disk itself.
edited Dec 21 '14 at 5:03
muru
1
1
answered May 9 '12 at 17:18
Who caresWho cares
11112
11112
this might not be the answer solving the OPs problem, its information is pure gold, though. Thanks a bunch!
– oliverjkb
Feb 13 '17 at 18:11
is you sda1ntfs
?
– Adi Prasetyo
Nov 29 '17 at 11:40
add a comment |
this might not be the answer solving the OPs problem, its information is pure gold, though. Thanks a bunch!
– oliverjkb
Feb 13 '17 at 18:11
is you sda1ntfs
?
– Adi Prasetyo
Nov 29 '17 at 11:40
this might not be the answer solving the OPs problem, its information is pure gold, though. Thanks a bunch!
– oliverjkb
Feb 13 '17 at 18:11
this might not be the answer solving the OPs problem, its information is pure gold, though. Thanks a bunch!
– oliverjkb
Feb 13 '17 at 18:11
is you sda1
ntfs
?– Adi Prasetyo
Nov 29 '17 at 11:40
is you sda1
ntfs
?– Adi Prasetyo
Nov 29 '17 at 11:40
add a comment |
Your disk is toast. Check the SMART diagnostics in the disk utility to confirm; it should say you have a ton of bad sectors and need to replace the drive.
add a comment |
Your disk is toast. Check the SMART diagnostics in the disk utility to confirm; it should say you have a ton of bad sectors and need to replace the drive.
add a comment |
Your disk is toast. Check the SMART diagnostics in the disk utility to confirm; it should say you have a ton of bad sectors and need to replace the drive.
Your disk is toast. Check the SMART diagnostics in the disk utility to confirm; it should say you have a ton of bad sectors and need to replace the drive.
answered Jun 9 '11 at 1:36
psusipsusi
31.3k15090
31.3k15090
add a comment |
add a comment |
I agree with @psusi: the disk needs replacing, see my comment under accepted answer. Doing an ntfsfix
will not help at all, and just delays the essential action of:
- backing up all data on the disk ASAP
- replacing the disk with a new one
There's no need really to check the SMART diagnostics - they only pick up a percentage of errors anyway. The red flags are the two lines:
[ 1019.726558] sd 0:0:0:0: [sda] Add. Sense: **Unrecovered read error** - auto reallocate failed
[ 1019.726602] JBD: **Failed to read block** at offset 462
As soon as a disk starts giving unrecoverable read errors (UREs), it should be replaced immediately and only used for data recovery. (An excessive level of non-UREs also indicates replacement is needed.)
Disks should be viewed as consumables that must be replaced every few years, hence having really good backups (automated, daily, complete, and at least to an external drive) is crucial.
add a comment |
I agree with @psusi: the disk needs replacing, see my comment under accepted answer. Doing an ntfsfix
will not help at all, and just delays the essential action of:
- backing up all data on the disk ASAP
- replacing the disk with a new one
There's no need really to check the SMART diagnostics - they only pick up a percentage of errors anyway. The red flags are the two lines:
[ 1019.726558] sd 0:0:0:0: [sda] Add. Sense: **Unrecovered read error** - auto reallocate failed
[ 1019.726602] JBD: **Failed to read block** at offset 462
As soon as a disk starts giving unrecoverable read errors (UREs), it should be replaced immediately and only used for data recovery. (An excessive level of non-UREs also indicates replacement is needed.)
Disks should be viewed as consumables that must be replaced every few years, hence having really good backups (automated, daily, complete, and at least to an external drive) is crucial.
add a comment |
I agree with @psusi: the disk needs replacing, see my comment under accepted answer. Doing an ntfsfix
will not help at all, and just delays the essential action of:
- backing up all data on the disk ASAP
- replacing the disk with a new one
There's no need really to check the SMART diagnostics - they only pick up a percentage of errors anyway. The red flags are the two lines:
[ 1019.726558] sd 0:0:0:0: [sda] Add. Sense: **Unrecovered read error** - auto reallocate failed
[ 1019.726602] JBD: **Failed to read block** at offset 462
As soon as a disk starts giving unrecoverable read errors (UREs), it should be replaced immediately and only used for data recovery. (An excessive level of non-UREs also indicates replacement is needed.)
Disks should be viewed as consumables that must be replaced every few years, hence having really good backups (automated, daily, complete, and at least to an external drive) is crucial.
I agree with @psusi: the disk needs replacing, see my comment under accepted answer. Doing an ntfsfix
will not help at all, and just delays the essential action of:
- backing up all data on the disk ASAP
- replacing the disk with a new one
There's no need really to check the SMART diagnostics - they only pick up a percentage of errors anyway. The red flags are the two lines:
[ 1019.726558] sd 0:0:0:0: [sda] Add. Sense: **Unrecovered read error** - auto reallocate failed
[ 1019.726602] JBD: **Failed to read block** at offset 462
As soon as a disk starts giving unrecoverable read errors (UREs), it should be replaced immediately and only used for data recovery. (An excessive level of non-UREs also indicates replacement is needed.)
Disks should be viewed as consumables that must be replaced every few years, hence having really good backups (automated, daily, complete, and at least to an external drive) is crucial.
edited Oct 17 '11 at 8:03
answered Oct 16 '11 at 6:02
RichVelRichVel
18518
18518
add a comment |
add a comment |
In Ubuntu 14.04 Just try this
sudo ntfsfix /dev/sdXY
Where XY
is your partition. (/dev/sda2
in your case)
add a comment |
In Ubuntu 14.04 Just try this
sudo ntfsfix /dev/sdXY
Where XY
is your partition. (/dev/sda2
in your case)
add a comment |
In Ubuntu 14.04 Just try this
sudo ntfsfix /dev/sdXY
Where XY
is your partition. (/dev/sda2
in your case)
In Ubuntu 14.04 Just try this
sudo ntfsfix /dev/sdXY
Where XY
is your partition. (/dev/sda2
in your case)
edited Oct 9 '14 at 12:53
αғsнιη
24.7k2396159
24.7k2396159
answered Oct 9 '14 at 12:12
user335969user335969
511
511
add a comment |
add a comment |
As the other answers have said, in this case it's probably a bad disk..
But for the benefit of others facing actual NTFS corruption - unfortunately the ntfsfix tool is very limited compared to Microsoft's chkdsk. Try to get a Windows install going - preferably with the newest version of Windows as Microsoft is presumably constantly improving chkdsk (I hope..) Newer versions of Windows are often available for free as trials. If the problem is in a USB disk you can try installing Windows in something like VirtualBox and give the VM control of the USB device.
add a comment |
As the other answers have said, in this case it's probably a bad disk..
But for the benefit of others facing actual NTFS corruption - unfortunately the ntfsfix tool is very limited compared to Microsoft's chkdsk. Try to get a Windows install going - preferably with the newest version of Windows as Microsoft is presumably constantly improving chkdsk (I hope..) Newer versions of Windows are often available for free as trials. If the problem is in a USB disk you can try installing Windows in something like VirtualBox and give the VM control of the USB device.
add a comment |
As the other answers have said, in this case it's probably a bad disk..
But for the benefit of others facing actual NTFS corruption - unfortunately the ntfsfix tool is very limited compared to Microsoft's chkdsk. Try to get a Windows install going - preferably with the newest version of Windows as Microsoft is presumably constantly improving chkdsk (I hope..) Newer versions of Windows are often available for free as trials. If the problem is in a USB disk you can try installing Windows in something like VirtualBox and give the VM control of the USB device.
As the other answers have said, in this case it's probably a bad disk..
But for the benefit of others facing actual NTFS corruption - unfortunately the ntfsfix tool is very limited compared to Microsoft's chkdsk. Try to get a Windows install going - preferably with the newest version of Windows as Microsoft is presumably constantly improving chkdsk (I hope..) Newer versions of Windows are often available for free as trials. If the problem is in a USB disk you can try installing Windows in something like VirtualBox and give the VM control of the USB device.
answered Jan 1 '12 at 5:05
eugeug
30015
30015
add a comment |
add a comment |
Unfortunately the free tools available on Linux are very limited with regards to fixing NTFS partitions.
Most likely you can still recover your data by using the secondary MFT stored at the end of the disk. It is usually not used, but it should contain an up-to-date version of your directory structure. There is a good chance it was not affected by the disk errors.
In the past, I have used Runtime Software's (commercial, 79$) product GetDataBack NTFS with great success for this. It is one of the few NTFS tools (the only?) that runs in WINE and as a Linux LiveCD, and the free demo should be enough to see if your data is still there. If it is, your data might just be worth buying the tool.
The LiveCD runs Knoppix Linux and has all their tools preinstalled. Note that you'll still need a license key to actually use the tools, but it should be enough to see if it works on your computer.
Disclaimer: I have no affiliation with Runtime software other than having bought their product a few years ago.
+1 not because I have experience with what's in this answer; the up is for raising awareness of lesser known alternatives to things such as Parted Magic.
– Graham Perrin
Jul 16 '16 at 14:23
add a comment |
Unfortunately the free tools available on Linux are very limited with regards to fixing NTFS partitions.
Most likely you can still recover your data by using the secondary MFT stored at the end of the disk. It is usually not used, but it should contain an up-to-date version of your directory structure. There is a good chance it was not affected by the disk errors.
In the past, I have used Runtime Software's (commercial, 79$) product GetDataBack NTFS with great success for this. It is one of the few NTFS tools (the only?) that runs in WINE and as a Linux LiveCD, and the free demo should be enough to see if your data is still there. If it is, your data might just be worth buying the tool.
The LiveCD runs Knoppix Linux and has all their tools preinstalled. Note that you'll still need a license key to actually use the tools, but it should be enough to see if it works on your computer.
Disclaimer: I have no affiliation with Runtime software other than having bought their product a few years ago.
+1 not because I have experience with what's in this answer; the up is for raising awareness of lesser known alternatives to things such as Parted Magic.
– Graham Perrin
Jul 16 '16 at 14:23
add a comment |
Unfortunately the free tools available on Linux are very limited with regards to fixing NTFS partitions.
Most likely you can still recover your data by using the secondary MFT stored at the end of the disk. It is usually not used, but it should contain an up-to-date version of your directory structure. There is a good chance it was not affected by the disk errors.
In the past, I have used Runtime Software's (commercial, 79$) product GetDataBack NTFS with great success for this. It is one of the few NTFS tools (the only?) that runs in WINE and as a Linux LiveCD, and the free demo should be enough to see if your data is still there. If it is, your data might just be worth buying the tool.
The LiveCD runs Knoppix Linux and has all their tools preinstalled. Note that you'll still need a license key to actually use the tools, but it should be enough to see if it works on your computer.
Disclaimer: I have no affiliation with Runtime software other than having bought their product a few years ago.
Unfortunately the free tools available on Linux are very limited with regards to fixing NTFS partitions.
Most likely you can still recover your data by using the secondary MFT stored at the end of the disk. It is usually not used, but it should contain an up-to-date version of your directory structure. There is a good chance it was not affected by the disk errors.
In the past, I have used Runtime Software's (commercial, 79$) product GetDataBack NTFS with great success for this. It is one of the few NTFS tools (the only?) that runs in WINE and as a Linux LiveCD, and the free demo should be enough to see if your data is still there. If it is, your data might just be worth buying the tool.
The LiveCD runs Knoppix Linux and has all their tools preinstalled. Note that you'll still need a license key to actually use the tools, but it should be enough to see if it works on your computer.
Disclaimer: I have no affiliation with Runtime software other than having bought their product a few years ago.
edited Oct 9 '14 at 13:13
answered Oct 9 '14 at 13:06
jmiserezjmiserez
2,98511421
2,98511421
+1 not because I have experience with what's in this answer; the up is for raising awareness of lesser known alternatives to things such as Parted Magic.
– Graham Perrin
Jul 16 '16 at 14:23
add a comment |
+1 not because I have experience with what's in this answer; the up is for raising awareness of lesser known alternatives to things such as Parted Magic.
– Graham Perrin
Jul 16 '16 at 14:23
+1 not because I have experience with what's in this answer; the up is for raising awareness of lesser known alternatives to things such as Parted Magic.
– Graham Perrin
Jul 16 '16 at 14:23
+1 not because I have experience with what's in this answer; the up is for raising awareness of lesser known alternatives to things such as Parted Magic.
– Graham Perrin
Jul 16 '16 at 14:23
add a comment |
This answer will probably just work for 10.04 (lucid) and later versions of Ubuntu!
Try sudo ntfsfix -b /dev/sda2
.
You need ntfs-3g installed. If you don't have it, you can install it in the Software Center by clicking that link, or from the Terminal (Ctrl+Alt+T) by running these commands:
sudo apt-get update
sudo apt-get install ntfs-3g
4
Why use NTFSProgs when NTFS-3g is installed by default? NTFSProgs is dead, as it has been completely merged into NTFS-3g. Switching to the former might cause more problems than it solves.
– TSJNachos117
Sep 21 '13 at 20:16
1
NTFSProgs is no longer part of the package archives after 12.04 precise.
– kynan
Jan 3 '15 at 16:43
add a comment |
This answer will probably just work for 10.04 (lucid) and later versions of Ubuntu!
Try sudo ntfsfix -b /dev/sda2
.
You need ntfs-3g installed. If you don't have it, you can install it in the Software Center by clicking that link, or from the Terminal (Ctrl+Alt+T) by running these commands:
sudo apt-get update
sudo apt-get install ntfs-3g
4
Why use NTFSProgs when NTFS-3g is installed by default? NTFSProgs is dead, as it has been completely merged into NTFS-3g. Switching to the former might cause more problems than it solves.
– TSJNachos117
Sep 21 '13 at 20:16
1
NTFSProgs is no longer part of the package archives after 12.04 precise.
– kynan
Jan 3 '15 at 16:43
add a comment |
This answer will probably just work for 10.04 (lucid) and later versions of Ubuntu!
Try sudo ntfsfix -b /dev/sda2
.
You need ntfs-3g installed. If you don't have it, you can install it in the Software Center by clicking that link, or from the Terminal (Ctrl+Alt+T) by running these commands:
sudo apt-get update
sudo apt-get install ntfs-3g
This answer will probably just work for 10.04 (lucid) and later versions of Ubuntu!
Try sudo ntfsfix -b /dev/sda2
.
You need ntfs-3g installed. If you don't have it, you can install it in the Software Center by clicking that link, or from the Terminal (Ctrl+Alt+T) by running these commands:
sudo apt-get update
sudo apt-get install ntfs-3g
edited Mar 11 '17 at 19:00
Community♦
1
1
answered May 9 '12 at 17:32
DeGeDeGe
172
172
4
Why use NTFSProgs when NTFS-3g is installed by default? NTFSProgs is dead, as it has been completely merged into NTFS-3g. Switching to the former might cause more problems than it solves.
– TSJNachos117
Sep 21 '13 at 20:16
1
NTFSProgs is no longer part of the package archives after 12.04 precise.
– kynan
Jan 3 '15 at 16:43
add a comment |
4
Why use NTFSProgs when NTFS-3g is installed by default? NTFSProgs is dead, as it has been completely merged into NTFS-3g. Switching to the former might cause more problems than it solves.
– TSJNachos117
Sep 21 '13 at 20:16
1
NTFSProgs is no longer part of the package archives after 12.04 precise.
– kynan
Jan 3 '15 at 16:43
4
4
Why use NTFSProgs when NTFS-3g is installed by default? NTFSProgs is dead, as it has been completely merged into NTFS-3g. Switching to the former might cause more problems than it solves.
– TSJNachos117
Sep 21 '13 at 20:16
Why use NTFSProgs when NTFS-3g is installed by default? NTFSProgs is dead, as it has been completely merged into NTFS-3g. Switching to the former might cause more problems than it solves.
– TSJNachos117
Sep 21 '13 at 20:16
1
1
NTFSProgs is no longer part of the package archives after 12.04 precise.
– kynan
Jan 3 '15 at 16:43
NTFSProgs is no longer part of the package archives after 12.04 precise.
– kynan
Jan 3 '15 at 16:43
add a comment |
I just had the same problem on a 3TB NTFS USB. Big drama, as you can imagine.
I first tried to fix it on my wife's Windows box. No joy.
sudo ntfsfix /dev/sdcx extremely quickly fixed it.
Hooray! Back in business. Really must get a new disk and promptly re-format it to a proper, adult filesystem.
add a comment |
I just had the same problem on a 3TB NTFS USB. Big drama, as you can imagine.
I first tried to fix it on my wife's Windows box. No joy.
sudo ntfsfix /dev/sdcx extremely quickly fixed it.
Hooray! Back in business. Really must get a new disk and promptly re-format it to a proper, adult filesystem.
add a comment |
I just had the same problem on a 3TB NTFS USB. Big drama, as you can imagine.
I first tried to fix it on my wife's Windows box. No joy.
sudo ntfsfix /dev/sdcx extremely quickly fixed it.
Hooray! Back in business. Really must get a new disk and promptly re-format it to a proper, adult filesystem.
I just had the same problem on a 3TB NTFS USB. Big drama, as you can imagine.
I first tried to fix it on my wife's Windows box. No joy.
sudo ntfsfix /dev/sdcx extremely quickly fixed it.
Hooray! Back in business. Really must get a new disk and promptly re-format it to a proper, adult filesystem.
answered 15 mins ago
MonkeybusMonkeybus
524
524
add a comment |
add a comment |
protected by Community♦ May 6 '15 at 19:24
Thank you for your interest in this question.
Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).
Would you like to answer one of these unanswered questions instead?
1
Link to a related question: askubuntu.com/q/58755/31592
– blong
Apr 10 '13 at 22:24