|
From: SourceForge.net <no...@so...> - 2005-10-11 12:50:09
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3377567 By: szaka Fdisk has two major problems. 1) sometimes it aligns partitions to some imaginary and non-sense cylinder boundary ==> NTFS is "gone", it becomes inaccessible. 2) if logical partitions are modified then it reorders them thus greatly confusing Windows, etc. The default fdisk output is not much use, please send the fdisk -lu output. Could you also send the end of the debug log (last 30 lines should be ok) why the tools refuse to mount the volume? For this you must compile the latest tools with debugging enabled or donwload this statically linked, debug version: wget -nd http://mlf.linux.rulez.org/mlf/ezaz/ntfsresize-static-1.12.0.tgz tar xzvf ntfsresize-static-1.12.0.tgz cd ntfsresize-static-1.12.0 ./ntfsresize -dffi <partition> Download, run and send the output of findntfs as well wget -nd http://mlf.linux.rulez.org/mlf/ezaz/findntfs-1.3.tgz tar xzvf findntfs-1.3.tgz cd findntfs-1.3 ./findntfs The current partition table recovery tools (testdisk, gpart, parted) are not very good. The best way is doing partition table backups. Logical partition are stored scattered around the disk. When fdisk pointlessly aligned them then it's possible it overwrote real NTFS data. Since version 1.12.0, ntfsresize explicitely warns that one should use sector as the unit when editing the partition table. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44085 |
