I have an external HDD that appears to be broken. Cannot be opened in Windows nor in Ubuntu (it is a NTFS file system).
On Windows I have run (two times now) the command
chkdsk. There it identifies certain memory segments which are unreadable. I thought that it would 'flag' these, and avoid them while trying to read in the HDD.
But after I ran that program, Windows was still unable to open it. So either I am wrong, or my disk is beyond repair.
Assuming that I am wrong, I turned to Ubuntu to see if
fsck could be of any help.
The 'check' function in
gparted gave me an error... and not much additional information.
First checking where the partition is, running
sdb 8:16 0 298,1G 0 disk └─sdb1 8:17 0 298,1G 0 part
Moving on to
fsck, I ran the following command
root@...# fsck /dev/sdb1 -y fsck from util-linux 2.31.1
Nothing more. So that was quite strange. Therefore I tried the whole disk and not one partition. This gave
root@...# fsck /dev/sdb -y fsck from util-linux 2.31.1 e2fsck 1.44.1 (24-Mar-2018) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb The superblock 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 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> or e2fsck -b 32768 <device> Found a dos partition table in /dev/sdb
Thus the stated error is
fsck.ext2: Bad magic number in super-block while trying to open /dev/sdb
Since I am sure (thanks to
gparted) that I am dealing with an
ntfs file system, and not
ext[0-9].. I think that the proposed solution (running
ef2fsck is not applicable to me.
I don't know how to continue from here. I believe if certain memory segments can be avoided to read in.. I think I can retrieve some data from it. But I don't know how to do this.