I got a new hard drive and cloned the old one onto it using clonezilla, as I was planning on using testdisk to rebuild the boot sector. (I have a windows ntfs and a mac hfs+) However, the Mac partition still works fine. If you want to eliminate the warnings, your only options are to convince TestDisk's authors to do this or to modify the software yourself.I accidentally shut off my computer while resizing partitions, (battery ran out) and now one of the partitions is screwed. Asking TestDisk's authors to de-emphasize CHS in favor of LBA may be worth doing, too. Tools that write MBR data structures must continue to populate the CHS fields, but on disks over about 8 GB in size, those fields are likely to be maxed out or contain bogus values there's simply no helping that fact on over-8GB disks.Īs a practical matter, you should simply ignore TestDisk's warnings about CHS values unless you're using really ancient software (like very old versions of DOS). On GPT disks, 64-bit LBA values are used, so the limit is 2^64 sectors (8 ZiB, assuming 512-byte sectors). LBA can handle up to 2^32 sectors on MBR disks, which works out to 2 TiB, given 512-byte sectors. Most modern tools - even tools for manipulating MBR disks - today use logical block addressing (LBA) almost exclusively, or at least in preference to CHS addressing. This is pointless and potentially confusing. When I have used it, I've been appalled at its continuing use of CHS values in prominent locations of its user interface. TestDisk is a useful tool, but I admit I haven't used it a lot. In fact, even many USB flash drives now exceed the CHS limitations! The newer GUID Partition Table (GPT) data structures don't even use CHS values, except on one area (the "protective MBR") that exists solely to signal to older software that it shouldn't mess with the disk - and in practice, the CHS values used in the protective MBR are often completely bogus, by either MBR or GPT standards. CHS values (as stored in the Master Boot Record, or MBR data structures) max out at about 8 GB, so CHS cannot represent any but the tiniest partitions on a modern disk. Long answer: Cylinder/head/sector (CHS) values have passed through several stages, from an accurate representation to a convenient fiction to an inconvenient fiction to worse than useless to abandoned. Short answer: Ignore the warnings or contact the program's author. How can I remove the initial mismatch warnings? Note that the sector 6527 is now "shared" which doesn't seem right. I/O size (minimum/optimal): 512 bytes / 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes Warning: number of heads/cylinder mismatches 255 (FAT) != 64 (HD) I'm getting the following output when running testdisk's Analyze on a 64GB SD card: TestDisk 6.14, Data Recovery Utility, July 2013ĭisk /dev/sdb - 63 GB / 59 GiB - CHS 60906 64 32 TL DR: How do I get rid of the warnings in the subject line when everything else looks sweet?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |