If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
boot
On bootup "invalid partition table" comes up but then boots normally
after pressing enter. how to fix? |
Ads |
#2
|
|||
|
|||
boot
F Murtz wrote:
On bootup "invalid partition table" comes up but then boots normally after pressing enter. how to fix? The message is coming from the BIOS. If a computer is set to "UEFI+CSM", it can do two boot analysis before presenting the popup boot menu. The MBR on a UEFI disk, has a "protective" 0xEE partition that spans the disk surface. This is intended to prevent legacy OSes from editing the partition table (as the disk looks "full" with the giant slze partition so declared). If the CSM portion of a BIOS sniffs the protective partition, it might be annoyed that no boot materials are present. The UEFI analysis concludes something different, namely that the disk has an ESP and materials suitable for booting. The message could amount to a "warning" from the CSM half of the BIOS (Compatibility Support Module). If you enter the BIOS and change the BIOS type to "UEFI only" instead of "UEFI+CSM", there's a good chance that warning message will disappear. However, this may screw up some of your bootable OSes (the ones made in the legacy era perhaps). The message is probably not an actual "broken" partition table or missing materials. You can use "disktype.exe /dev/sda" (Cygwin version) to check out the partition table. You can do the same from Linux (sans .exe). What disktype will show you, is a 16MB partition that Windows won't admit to, which appears to have no recognizable file system and contains "binary data". This is probably the equivalent of a track 0 storage area, only larger. A track might be a size around 8MB, and the 16MB GPT partition for it, ensures the contents can be held without issue. I've also seen a GPT disk that TestDisk marked some of the partitions as being the wrong size. Fooling around with Disk Management and resizing some stuff, may have pulled that back into condition again. This only seemed to be an issue for TestDisk. Nothing else noticed. Paul |
Thread Tools | |
Display Modes | Rate This Thread |
|
|