RSS icon Home
  • How to bring your PC to catatrophe with and only with proper steps - []

    Dec 28, 2013 21:45 分区表 丢失 错误 修复

    版权声明:转载时请以超链接形式标明文章原始出处和作者信息及本声明
    http://www.blogbus.com/n-br-logs/246110928.html

    Microsoft and its Windows operating system has long been criticized as imperfect. One reason is that you can run into fatal errors by doing everything right (and even by doing nothing).

    I still remember a bug with Windows Media Player makes it unable to play MP3 files correctly. You buy MP3 from Amazon, download them using Internet Explorer (well it's Microsoft's product so it should be the most compatible browser), and drag them into WMP, but all you get is silence. Microsoft has published a wordaround for this, suggesting users to edit MP3 tags using rival products like WinAmp.

    THere are also cases when you set up Internet Connection Sharing exactly as stated by Windows Help but lose WiFi connectivity after a system reboot. Microsoft has admitted that this is a bug with theri VIrtual WiFi adapter but has no plan of incorporating the patch to Windows Update.

    Most of the time when Windows goes on strike, I can easily handle them using some registry tweaks, Command Prompt interations or some magic third-party tools. But today things are different, I ran into some catastrophic issues after normal operation and has been unable to recover from the error.

    It all started with disk management console. I wanted to create a new partition from the free space left in my extended partition, so that I can try out features of Windows 8 in a virtual machine. The free space has been there for almost a year since I deleted the original Linux Ext Partion under disk management console. I used its menus and buttons, follwed dialog instructions, told Windows to create an 64K NTFS volume on that free space with quick format.

    As you can see all these moves are pretty straightforward and normal, no hacking or scripting or third-party tools. But after a while what I get is an Extended partition with and only with this newly created logical drive and all other existing logical volumes becoming a 3xx GB span of free space, all in a sudden.

    THe only abnormal thing I can think of is that Comodo warned me of suspicious actions by VSS. Problem is I selected "Treat as Trusted Application". I wonder if a 5 or 10 second lag in VSS response would result as such partition table failure.

    ANyway, it's not the first time I come across partition problems, so I'm experienced. I used my laptop to download TestDisk, unloaded HD from my desktop and connected via eSATA to laptop and conducted recovery scans.

    Unfortunately TestDisk was not able to correctly identify all the partitions that should be on the drive. I could only get exFAT partitions recovered but not compressed NTFS. Even more weirdly, TestDisk reports a strange partition with a capacity of 200 GB and damaged file system. The total size of the free space and the two missing NTFS partitions add up to no more than 200 GB, so how does TestDisk worked out that partition entry? I've got no clue.

    THe real pain in the ass is the missing partitions contain the most important partition. My documents, program scripts, pictures (7000+ of about a dozen Gigs!) and saved articles, webpages, slides...are now unreadable thought I am sure they are physically safe.

    I wish the MFT on this partition was not damaged. If so professional engineers can restore data using this MFT. BUt this means having to carry the drive to some repair stations, which is rather costly.

    By the time this article was written I still could not figure out why partition information can be lost in such a dramatic manner.

    分享到: