search for: sector_layout

> > Looks like a disk sector to me too. However the partition table > is further on. See: > > https://en.wikipedia.org/wiki/Master_boot_record#Sector_layout So that reference says the "classical generic MBR" partition entry # 1 is offset 0x1BE. Which in this image is right in the error strings (?) section. 00000170 13 59 5A 58 72 09 40 75 01 42 03 5E 0B E2 CC C3 .YZXr.@u.B.^.âÌà 00000180 03 18 01 27 0D 0A 49 6E 76 61 6C 69 64 20 73 79...

> > The appliance kernel couldn't find any partitions at all on the disk. > > Is it a raw format disk image, or some other format that qemu can > reasonably be expected to read? I used the "Advanced Options" of Macrium Reflect (on Windows 7) to do a raw byte copy. If it is, then yes I'd say the image is corrupted. However you'd > probably want to hexdump

..... > 00000020 41 E0 3E 00 80 00 29 91 2C 95 24 20 20 20 20 20 Aà>.€.)‘,•$ > 00000030 20 20 20 20 20 20 46 41 54 31 36 20 20 20 F1 7D FAT16 ñ} Looks like a disk sector to me too. However the partition table is further on. See: https://en.wikipedia.org/wiki/Master_boot_record#Sector_layout Rich. > As for examining the rest of the image at the hex level and making an > assessment - that is beyond my scope of expertise. > But certainly it could have been corrupted. > I'll see if I can get access to the drive and use Linux (and dd) to make a > new image. > _____...

On Tue, Dec 16, 2014 at 11:33:00AM -0500, Skippy VonDrake wrote: > > > > Looks like a disk sector to me too. However the partition table > > is further on. See: > > > > https://en.wikipedia.org/wiki/Master_boot_record#Sector_layout > > > So that reference says the "classical generic MBR" partition entry # 1 is > offset 0x1BE. > Which in this image is right in the error strings (?) section. > > 00000170 13 59 5A 58 72 09 40 75 01 42 03 5E 0B E2 CC C3 .YZXr.@u.B.^.âÌà > 00000180 03 18 01...