NTFS drive corrupt
I have a 2TB external WD drive that I use for backup and movies/music such and so forth since back when I had windows running on my laptop. To be on the safe side, I unmounted the drive and ran a short test using smartctl which gave a result of completed: read error at 90%
$ sudo smartctl -l selftest /dev/sdc
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-36-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
1 Short offline Completed: read failure 90% 4876 9938552
2 Short offline Completed: read failure 90% 4876 9938552
Trying to fix the issue, I ran ntfsfix
$ sudo ntfsfix /dev/sdc
Mounting volume... NTFS signature is missing.
FAILED
Attempting to correct errors... NTFS signature is missing.
FAILED
Failed to startup volume: Invalid argument
NTFS signature is missing.
Trying the alternate boot sector
The alternate bootsector is usable
Set sector count to 3906963455 instead of 3906961407
Rewriting the bootsector
The boot sector has been rewritten
ntfs_mst_post_read_fixup_warn: magic: 0xffffffff size: 1024 usa_ofs: 65535 usa_count: 65534: Invalid argument
Record 0 has no FILE magic (0xffffffff)
Failed to load $MFT: Input/output error
Volume is corrupt. You should run chkdsk.
Now the drive is no longer mountable on Disks utility.
dmseg | tail returned the following result:
[ 1697.980340] scsi 7:0:0:1: Enclosure WD SES Device 1019 PQ: 0 ANSI: 6
[ 1697.982222] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 1697.982287] sd 7:0:0:0: [sdc] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 1697.982518] ses 7:0:0:1: Attached Enclosure device
[ 1697.982673] sd 7:0:0:0: [sdc] Write Protect is off
[ 1697.982684] sd 7:0:0:0: [sdc] Mode Sense: 47 00 10 08
[ 1697.982686] ses 7:0:0:1: Attached scsi generic sg4 type 13
[ 1697.983481] sd 7:0:0:0: [sdc] No Caching mode page found
[ 1697.983490] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 1711.399946] sd 7:0:0:0: [sdc] Attached SCSI disk
I thought about mounting the drive directly from the terminal, but I really cant afford to loose the data on this drive and didn't want to make another mistake.
What can I do to fix the issue? please keep in mind I am very new to linux. Thanks
mount hard-drive ntfs
edited Sep 15 '16 at 16:09
Byte Commander
64.5k27176295
asked Sep 15 '16 at 16:05
Karan KKaran K
1914
bumped to the homepage by Community♦ 8 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
|
show 2 more comments
I have a 2TB external WD drive that I use for backup and movies/music such and so forth since back when I had windows running on my laptop. To be on the safe side, I unmounted the drive and ran a short test using smartctl which gave a result of completed: read error at 90%
$ sudo smartctl -l selftest /dev/sdc
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-36-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
1 Short offline Completed: read failure 90% 4876 9938552
2 Short offline Completed: read failure 90% 4876 9938552
Trying to fix the issue, I ran ntfsfix
$ sudo ntfsfix /dev/sdc
Mounting volume... NTFS signature is missing.
FAILED
Attempting to correct errors... NTFS signature is missing.
FAILED
Failed to startup volume: Invalid argument
NTFS signature is missing.
Trying the alternate boot sector
The alternate bootsector is usable
Set sector count to 3906963455 instead of 3906961407
Rewriting the bootsector
The boot sector has been rewritten
ntfs_mst_post_read_fixup_warn: magic: 0xffffffff size: 1024 usa_ofs: 65535 usa_count: 65534: Invalid argument
Record 0 has no FILE magic (0xffffffff)
Failed to load $MFT: Input/output error
Volume is corrupt. You should run chkdsk.
Now the drive is no longer mountable on Disks utility.
dmseg | tail returned the following result:
[ 1697.980340] scsi 7:0:0:1: Enclosure WD SES Device 1019 PQ: 0 ANSI: 6
[ 1697.982222] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 1697.982287] sd 7:0:0:0: [sdc] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 1697.982518] ses 7:0:0:1: Attached Enclosure device
[ 1697.982673] sd 7:0:0:0: [sdc] Write Protect is off
[ 1697.982684] sd 7:0:0:0: [sdc] Mode Sense: 47 00 10 08
[ 1697.982686] ses 7:0:0:1: Attached scsi generic sg4 type 13
[ 1697.983481] sd 7:0:0:0: [sdc] No Caching mode page found
[ 1697.983490] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 1711.399946] sd 7:0:0:0: [sdc] Attached SCSI disk
I thought about mounting the drive directly from the terminal, but I really cant afford to loose the data on this drive and didn't want to make another mistake.
What can I do to fix the issue? please keep in mind I am very new to linux. Thanks
mount hard-drive ntfs
edited Sep 15 '16 at 16:09
Byte Commander
64.5k27176295
asked Sep 15 '16 at 16:05
Karan KKaran K
1914
bumped to the homepage by Community♦ 8 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
This drive is dying... There is no question. You can always mount read-only from terminal. That should never damage the filesystem, but honestly, I don't give it much chance. You might already have lost your files. Mainly because you used/dev/sdcforntfsfix. That is almost certainly wrong (and you might have destroyed your disk in the process)./dev/sdcrepresents the whole disk./dev/sdc1represents the first partition. In most cases partitions have filesystems. Not disks.
– jawtheshark
Sep 15 '16 at 16:14
@jawtheshark the entire drive is formatted to one partition only since its meant to just store files. I'll get a replacement harddisk in a couple of days, but anything I can do to get it back to normal now?
– Karan K
Sep 15 '16 at 16:25
1
Yes, but a partition is not a drive. /dev/sdc is not equal to /dev/sdc1... Even if /dev/sdc1 comprises the whole disk. /dev/sdc would contain the partition table plus all data in the partition. /dev/sdc1 is only the filesystem.
– jawtheshark
Sep 15 '16 at 19:20
You could try to recreate the partition table, if you know or can guess what it was.
– jawtheshark
Sep 15 '16 at 19:21
2
Possible duplicate of Recovering NTFS partitions that cannot be mounted
– Andrea Lazzarotto
Sep 17 '16 at 9:39
|
show 2 more comments
I have a 2TB external WD drive that I use for backup and movies/music such and so forth since back when I had windows running on my laptop. To be on the safe side, I unmounted the drive and ran a short test using smartctl which gave a result of completed: read error at 90%
$ sudo smartctl -l selftest /dev/sdc
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-36-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
1 Short offline Completed: read failure 90% 4876 9938552
2 Short offline Completed: read failure 90% 4876 9938552
Trying to fix the issue, I ran ntfsfix
$ sudo ntfsfix /dev/sdc
Mounting volume... NTFS signature is missing.
FAILED
Attempting to correct errors... NTFS signature is missing.
FAILED
Failed to startup volume: Invalid argument
NTFS signature is missing.
Trying the alternate boot sector
The alternate bootsector is usable
Set sector count to 3906963455 instead of 3906961407
Rewriting the bootsector
The boot sector has been rewritten
ntfs_mst_post_read_fixup_warn: magic: 0xffffffff size: 1024 usa_ofs: 65535 usa_count: 65534: Invalid argument
Record 0 has no FILE magic (0xffffffff)
Failed to load $MFT: Input/output error
Volume is corrupt. You should run chkdsk.
Now the drive is no longer mountable on Disks utility.
dmseg | tail returned the following result:
[ 1697.980340] scsi 7:0:0:1: Enclosure WD SES Device 1019 PQ: 0 ANSI: 6
[ 1697.982222] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 1697.982287] sd 7:0:0:0: [sdc] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 1697.982518] ses 7:0:0:1: Attached Enclosure device
[ 1697.982673] sd 7:0:0:0: [sdc] Write Protect is off
[ 1697.982684] sd 7:0:0:0: [sdc] Mode Sense: 47 00 10 08
[ 1697.982686] ses 7:0:0:1: Attached scsi generic sg4 type 13
[ 1697.983481] sd 7:0:0:0: [sdc] No Caching mode page found
[ 1697.983490] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 1711.399946] sd 7:0:0:0: [sdc] Attached SCSI disk
I thought about mounting the drive directly from the terminal, but I really cant afford to loose the data on this drive and didn't want to make another mistake.
What can I do to fix the issue? please keep in mind I am very new to linux. Thanks
mount hard-drive ntfs
edited Sep 15 '16 at 16:09
Byte Commander
64.5k27176295
asked Sep 15 '16 at 16:05
Karan KKaran K
1914
I have a 2TB external WD drive that I use for backup and movies/music such and so forth since back when I had windows running on my laptop. To be on the safe side, I unmounted the drive and ran a short test using smartctl which gave a result of completed: read error at 90%
$ sudo smartctl -l selftest /dev/sdc
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-36-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
1 Short offline Completed: read failure 90% 4876 9938552
2 Short offline Completed: read failure 90% 4876 9938552
Trying to fix the issue, I ran ntfsfix
$ sudo ntfsfix /dev/sdc
Mounting volume... NTFS signature is missing.
FAILED
Attempting to correct errors... NTFS signature is missing.
FAILED
Failed to startup volume: Invalid argument
NTFS signature is missing.
Trying the alternate boot sector
The alternate bootsector is usable
Set sector count to 3906963455 instead of 3906961407
Rewriting the bootsector
The boot sector has been rewritten
ntfs_mst_post_read_fixup_warn: magic: 0xffffffff size: 1024 usa_ofs: 65535 usa_count: 65534: Invalid argument
Record 0 has no FILE magic (0xffffffff)
Failed to load $MFT: Input/output error
Volume is corrupt. You should run chkdsk.
Now the drive is no longer mountable on Disks utility.
dmseg | tail returned the following result:
[ 1697.980340] scsi 7:0:0:1: Enclosure WD SES Device 1019 PQ: 0 ANSI: 6
[ 1697.982222] sd 7:0:0:0: Attached scsi generic sg3 type 0
[ 1697.982287] sd 7:0:0:0: [sdc] 3906963456 512-byte logical blocks: (2.00 TB/1.82 TiB)
[ 1697.982518] ses 7:0:0:1: Attached Enclosure device
[ 1697.982673] sd 7:0:0:0: [sdc] Write Protect is off
[ 1697.982684] sd 7:0:0:0: [sdc] Mode Sense: 47 00 10 08
[ 1697.982686] ses 7:0:0:1: Attached scsi generic sg4 type 13
[ 1697.983481] sd 7:0:0:0: [sdc] No Caching mode page found
[ 1697.983490] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 1711.399946] sd 7:0:0:0: [sdc] Attached SCSI disk
I thought about mounting the drive directly from the terminal, but I really cant afford to loose the data on this drive and didn't want to make another mistake.
What can I do to fix the issue? please keep in mind I am very new to linux. Thanks
mount hard-drive ntfs
mount hard-drive ntfs
edited Sep 15 '16 at 16:09
Byte Commander
64.5k27176295
asked Sep 15 '16 at 16:05
Karan KKaran K
1914
edited Sep 15 '16 at 16:09
Byte Commander
64.5k27176295
asked Sep 15 '16 at 16:05
Karan KKaran K
1914
edited Sep 15 '16 at 16:09
Byte Commander
64.5k27176295
edited Sep 15 '16 at 16:09
Byte Commander
64.5k27176295
edited Sep 15 '16 at 16:09
Byte Commander
64.5k27176295
64.5k27176295
asked Sep 15 '16 at 16:05
Karan KKaran K
1914
asked Sep 15 '16 at 16:05
Karan KKaran K
1914
asked Sep 15 '16 at 16:05
Karan KKaran K
1914
1914
bumped to the homepage by Community♦ 8 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 8 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
This drive is dying... There is no question. You can always mount read-only from terminal. That should never damage the filesystem, but honestly, I don't give it much chance. You might already have lost your files. Mainly because you used/dev/sdcforntfsfix. That is almost certainly wrong (and you might have destroyed your disk in the process)./dev/sdcrepresents the whole disk./dev/sdc1represents the first partition. In most cases partitions have filesystems. Not disks.
– jawtheshark
Sep 15 '16 at 16:14
@jawtheshark the entire drive is formatted to one partition only since its meant to just store files. I'll get a replacement harddisk in a couple of days, but anything I can do to get it back to normal now?
– Karan K
Sep 15 '16 at 16:25
1
Yes, but a partition is not a drive. /dev/sdc is not equal to /dev/sdc1... Even if /dev/sdc1 comprises the whole disk. /dev/sdc would contain the partition table plus all data in the partition. /dev/sdc1 is only the filesystem.
– jawtheshark
Sep 15 '16 at 19:20
You could try to recreate the partition table, if you know or can guess what it was.
– jawtheshark
Sep 15 '16 at 19:21
2
Possible duplicate of Recovering NTFS partitions that cannot be mounted
– Andrea Lazzarotto
Sep 17 '16 at 9:39
|
show 2 more comments
This drive is dying... There is no question. You can always mount read-only from terminal. That should never damage the filesystem, but honestly, I don't give it much chance. You might already have lost your files. Mainly because you used/dev/sdcforntfsfix. That is almost certainly wrong (and you might have destroyed your disk in the process)./dev/sdcrepresents the whole disk./dev/sdc1represents the first partition. In most cases partitions have filesystems. Not disks.
– jawtheshark
Sep 15 '16 at 16:14
@jawtheshark the entire drive is formatted to one partition only since its meant to just store files. I'll get a replacement harddisk in a couple of days, but anything I can do to get it back to normal now?
– Karan K
Sep 15 '16 at 16:25
1
Yes, but a partition is not a drive. /dev/sdc is not equal to /dev/sdc1... Even if /dev/sdc1 comprises the whole disk. /dev/sdc would contain the partition table plus all data in the partition. /dev/sdc1 is only the filesystem.
– jawtheshark
Sep 15 '16 at 19:20
You could try to recreate the partition table, if you know or can guess what it was.
– jawtheshark
Sep 15 '16 at 19:21
2
Possible duplicate of Recovering NTFS partitions that cannot be mounted
– Andrea Lazzarotto
Sep 17 '16 at 9:39
This drive is dying... There is no question. You can always mount read-only from terminal. That should never damage the filesystem, but honestly, I don't give it much chance. You might already have lost your files. Mainly because you used
/dev/sdc for ntfsfix. That is almost certainly wrong (and you might have destroyed your disk in the process). /dev/sdc represents the whole disk. /dev/sdc1 represents the first partition. In most cases partitions have filesystems. Not disks.– jawtheshark
Sep 15 '16 at 16:14
This drive is dying... There is no question. You can always mount read-only from terminal. That should never damage the filesystem, but honestly, I don't give it much chance. You might already have lost your files. Mainly because you used
/dev/sdc for ntfsfix. That is almost certainly wrong (and you might have destroyed your disk in the process). /dev/sdc represents the whole disk. /dev/sdc1 represents the first partition. In most cases partitions have filesystems. Not disks.– jawtheshark
Sep 15 '16 at 16:14
@jawtheshark the entire drive is formatted to one partition only since its meant to just store files. I'll get a replacement harddisk in a couple of days, but anything I can do to get it back to normal now?
– Karan K
Sep 15 '16 at 16:25
@jawtheshark the entire drive is formatted to one partition only since its meant to just store files. I'll get a replacement harddisk in a couple of days, but anything I can do to get it back to normal now?
– Karan K
Sep 15 '16 at 16:25
1
1
Yes, but a partition is not a drive. /dev/sdc is not equal to /dev/sdc1... Even if /dev/sdc1 comprises the whole disk. /dev/sdc would contain the partition table plus all data in the partition. /dev/sdc1 is only the filesystem.
– jawtheshark
Sep 15 '16 at 19:20
Yes, but a partition is not a drive. /dev/sdc is not equal to /dev/sdc1... Even if /dev/sdc1 comprises the whole disk. /dev/sdc would contain the partition table plus all data in the partition. /dev/sdc1 is only the filesystem.
– jawtheshark
Sep 15 '16 at 19:20
You could try to recreate the partition table, if you know or can guess what it was.
– jawtheshark
Sep 15 '16 at 19:21
You could try to recreate the partition table, if you know or can guess what it was.
– jawtheshark
Sep 15 '16 at 19:21
2
2
Possible duplicate of Recovering NTFS partitions that cannot be mounted
– Andrea Lazzarotto
Sep 17 '16 at 9:39
Possible duplicate of Recovering NTFS partitions that cannot be mounted
– Andrea Lazzarotto
Sep 17 '16 at 9:39
|
show 2 more comments
1 Answer
1
active
oldest
votes
I've fixed the issue and gotten the drive to mount.
Posting how I fixed it in case someone else has a similar issue.
I installed testdisk and ran it
sudo apt-get install testdisk
sudo testdisk
and basically followed the instructions choosing first to analyze which showed me the problem and applied the fix. Reboot system and the external harddisk is running fine.
Data intact.
answered Sep 15 '16 at 22:28
Karan KKaran K
1914
Dear brother, following your unspecific instructions, I just lost 4TB data.
– blueray
Nov 9 '18 at 5:31
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f825327%2fntfs-drive-corrupt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I've fixed the issue and gotten the drive to mount.
Posting how I fixed it in case someone else has a similar issue.
I installed testdisk and ran it
sudo apt-get install testdisk
sudo testdisk
and basically followed the instructions choosing first to analyze which showed me the problem and applied the fix. Reboot system and the external harddisk is running fine.
Data intact.
answered Sep 15 '16 at 22:28
Karan KKaran K
1914
Dear brother, following your unspecific instructions, I just lost 4TB data.
– blueray
Nov 9 '18 at 5:31
add a comment |
I've fixed the issue and gotten the drive to mount.
Posting how I fixed it in case someone else has a similar issue.
I installed testdisk and ran it
sudo apt-get install testdisk
sudo testdisk
and basically followed the instructions choosing first to analyze which showed me the problem and applied the fix. Reboot system and the external harddisk is running fine.
Data intact.
answered Sep 15 '16 at 22:28
Karan KKaran K
1914
Dear brother, following your unspecific instructions, I just lost 4TB data.
– blueray
Nov 9 '18 at 5:31
add a comment |
I've fixed the issue and gotten the drive to mount.
Posting how I fixed it in case someone else has a similar issue.
I installed testdisk and ran it
sudo apt-get install testdisk
sudo testdisk
and basically followed the instructions choosing first to analyze which showed me the problem and applied the fix. Reboot system and the external harddisk is running fine.
Data intact.
answered Sep 15 '16 at 22:28
Karan KKaran K
1914
I've fixed the issue and gotten the drive to mount.
Posting how I fixed it in case someone else has a similar issue.
I installed testdisk and ran it
sudo apt-get install testdisk
sudo testdisk
and basically followed the instructions choosing first to analyze which showed me the problem and applied the fix. Reboot system and the external harddisk is running fine.
Data intact.
answered Sep 15 '16 at 22:28
Karan KKaran K
1914
answered Sep 15 '16 at 22:28
Karan KKaran K
1914
answered Sep 15 '16 at 22:28
Karan KKaran K
1914
answered Sep 15 '16 at 22:28
Karan KKaran K
1914
1914
Dear brother, following your unspecific instructions, I just lost 4TB data.
– blueray
Nov 9 '18 at 5:31
add a comment |
Dear brother, following your unspecific instructions, I just lost 4TB data.
– blueray
Nov 9 '18 at 5:31
Dear brother, following your unspecific instructions, I just lost 4TB data.
– blueray
Nov 9 '18 at 5:31
Dear brother, following your unspecific instructions, I just lost 4TB data.
– blueray
Nov 9 '18 at 5:31
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f825327%2fntfs-drive-corrupt%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
This drive is dying... There is no question. You can always mount read-only from terminal. That should never damage the filesystem, but honestly, I don't give it much chance. You might already have lost your files. Mainly because you used
/dev/sdcforntfsfix. That is almost certainly wrong (and you might have destroyed your disk in the process)./dev/sdcrepresents the whole disk./dev/sdc1represents the first partition. In most cases partitions have filesystems. Not disks.– jawtheshark
Sep 15 '16 at 16:14
@jawtheshark the entire drive is formatted to one partition only since its meant to just store files. I'll get a replacement harddisk in a couple of days, but anything I can do to get it back to normal now?
– Karan K
Sep 15 '16 at 16:25
1
Yes, but a partition is not a drive. /dev/sdc is not equal to /dev/sdc1... Even if /dev/sdc1 comprises the whole disk. /dev/sdc would contain the partition table plus all data in the partition. /dev/sdc1 is only the filesystem.
– jawtheshark
Sep 15 '16 at 19:20
You could try to recreate the partition table, if you know or can guess what it was.
– jawtheshark
Sep 15 '16 at 19:21
2
Possible duplicate of Recovering NTFS partitions that cannot be mounted
– Andrea Lazzarotto
Sep 17 '16 at 9:39