You are not logged in.
Pages: 1
HDD is new and in good shape. After I run fsck.ext4 on his one partition, fsck said, that everything is ok.
But now partition table is corrupted.
Before fsck:
Start: 2048
End: 3.907.029.167
Id: 83
System: Linux
After fsck:
Start: 0
End: 370.687
Id: 17
System: Hidden HPFS/NTFS
Is there a way, to repair this, and don't lose data?
EDIT:
I have got second identical HDD, with identical partition table. Maybe I can somehow copy-pasted it?
Last edited by dext (2012-01-12 18:24:27)
Offline
Modifying the partition table doesn't affect the data directly, though fsck still could have caused some damage. Since you know how the partition was laid out before the corruption:
Start: 2048
End: 3.907.029.167
Id: 83
You can just use fdisk or the like to change it back to that layout. Again, any changes you make to the partition table will not risk damaging your data.
However, something bad happened to cause the corruption in the first place. If you have a drive to spare, it might be worth it to dd the corrupted one onto the spare, so a mistake when trying to fix the corrupted one won't be the end of your data. Keep in mind that this will destroy any data currently on the spare.
A more practical method would be to fix the p.t. then boot into a live CD. From there, try to mount the fixed partition read-only. If it mounts, do what is necessary to check the integrity of the data. It might also be a good idea to copy anything irreplacable over to the other drive and reformat the fixed partition. If you really have no idea what lead to the corruption (fsck corrupted it, but why?), maybe you should run a thorough drive diagnostic, such as badblocks or the manufacturer's utility.
Last edited by alphaniner (2012-01-12 19:26:01)
But whether the Constitution really be one thing, or another, this much is certain - that it has either authorized such a government as we have had, or has been powerless to prevent it. In either case, it is unfit to exist.
-Lysander Spooner
Offline
Offline
Pages: 1