search for: master_boot_record

> > 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...

> > 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

...e would be wasted. But maybe one should rather state that if a BIOS is too dumb for uneven partiton endings, then it is probably too dumb for large partitions, too. Any experience around ? Any opinions ? The advise to set large drive ends to 1023,254,63 is taken from http://en.wikipedia.org/wiki/Master_boot_record#Partition_table_entries --------------------------------------------------------- To the wiki admins: I acquired a SYSLINUX wiki account: "scdbackup" Please enable editing. Have a nice day :) Thomas _______________________________________________ Syslinux mailing list Submissions t...

On 01/19/2014 03:47 PM, Ronald F. Guilmette wrote: > > Doesn't the Syslinux project provide (hopefully strong) specific > reccomendations, to its user base, for how these things should best > be done, you know, in order to insure maximal interoperability? > We try (see our wiki), but those recommendations can only come from mass testing across many, many systems -- which we

...a section, but possibly i am already too much spoiled by detail knowledge. Does anybody know comprehensive existing user documentation about the topic, to which the wiki could link ? (Wikipedia is too detailed and scattered to be of help during a computer crisis. See http://en.wikipedia.org/wiki/Master_boot_record http://en.wikipedia.org/wiki/File_Allocation_Table ) Maybe one should also swap the positions of the links on the left edge of the general wiki: "Help" http://www.syslinux.org/wiki/index.php/Help:Contents and "Common Problems" http://www.syslinux.org/wiki/index.php/C...

...00 .....øü.?.@.?... > 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 imag...

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.^.âÌà > 00000...

...one should rather state that if a BIOS is too dumb for > uneven partiton endings, then it is probably too dumb for large > partitions, too. > Any experience around ? Any opinions ? > > The advise to set large drive ends to 1023,254,63 is taken from > http://en.wikipedia.org/wiki/Master_boot_record#Partition_table_entries Excellent point. Thank you. I was merely thinking of a relatively easy scenario that could confuse BIOSs/firmwares and cause them to ignore the drive. > --------------------------------------------------------- > To the wiki admins: > > I acquired a SYSLINUX...

Hi, I have a laptop with 2 hard drives. The first has Fedora 20 (no windows or anything else) and the second is unused. I would like to install CentOS7 on the unused drive so I can dual boot with the choice of the 2 OS's on the Grub menu. I am comfortable in partitioning drives and installing Linux distributions. I am afraid I may mess up the MBR and/or set up Grub incorrectly so I

Thomas Schmitt wrote: > I ponder whether it would be possible to create a diagnostic MBR > which does not necessarily have to boot but rather tells what the > isohybrid MBR would perceive: Presence of partition table, > EBIOS or CBIOS, block address used with INT 13, content of the block > read by the first INT 13, ... ... > The diagnostic MBR should only use 432 bytes because at

...;s most likely is isolinux as it has confirmed the signature (the part that fails for David which started this thread), right? > I know the number 0x7c0 (i.e. with one "0" less) as the default > "Load Segment" of El Torito. > http://wiki.osdev.org/Boot_Sequence#Master_Boot_Record > says "0x0000:0x7c00" and "0x7c0:0x0000 " are the same. Shrug. Welcome to more gifts from Intel. Read <https://en.wikipedia.org/wiki/Real_mode>. In short every address has sixteen diffent aliases: 0x7c0:0x0000, 0x7bf:0x0010, 0x7be:0x0020, 0x7bd:0x0030, etc is the sa...

Hi, funny or enlightening observation: With my qemu-system-i386 it would work if the detected Heads/Cylinder and Sectors/Head factors would change positions ! The effective read operation seems to use H/C = 32 , S/H = 63. The correct LBA would be addressed by H/C = 63 , S/H = 32. -------------------------------------------------------------------------- Reasoning: I have transplanted the

...e would be wasted. But maybe one should rather state that if a BIOS is too dumb for uneven partiton endings, then it is probably too dumb for large partitions, too. Any experience around ? Any opinions ? The advise to set large drive ends to 1023,254,63 is taken from http://en.wikipedia.org/wiki/Master_boot_record#Partition_table_entries --------------------------------------------------------- To the wiki admins: I acquired a SYSLINUX wiki account: "scdbackup" Please enable editing. Have a nice day :) Thomas

...ne should rather state that if a BIOS is too dumb for > uneven partiton endings, then it is probably too dumb for large > partitions, too. > Any experience around ? Any opinions ? > > The advise to set large drive ends to 1023,254,63 is taken from > http://en.wikipedia.org/wiki/Master_boot_record#Partition_table_entries > > A relatively modern partitioning tool (not from the '80s) would already include adequate support for LBA, and for MiB alignment. If we are trying to help non-technical users, we shouldn't be adding information that could make their lives more complex...

> Hi, > > > For instance, if a common user reads a section about a general > > concept, then introducing commands of specific tools (even with the > > intention of clarity) could make the reader (mis)understand that such > > tool or such commands are part of the general concept. > > The first example with "xorriso ... -isohybrid-mbr" serves the

...325055 and its C/H/S (646, 63, 32) address tell that the partition table was made under the assumption H/C= 64 and S/H= 32. That's what hpa prescribed to me for smaller sized isohybrids. The EFI partition bears the CHS value which says that it is not valid. See: https://en.wikipedia.org/wiki/Master_boot_record#Partition_table_entries which says: "When a CHS address is too large to fit into these fields, the tuple (1023, 254, 63) is typically used today," Since the only intended audience of the partition is UEFI firmware, i'd say it is safe to assume that it can address by LBA. I wil...

In message <70229.1390169666 at server1.tristatelogic.com>, I wrote: >In message <52DC29E3.7080004 at mattiasschlenker.de>, >Mattias Schlenker <ms at mattiasschlenker.de> wrote: > >>To cut a log story short, we probably should write some advices for best >>practices of creating bootable media... >... >

...am already too much spoiled by detail knowledge. > Does anybody know comprehensive existing user documentation about > the topic, to which the wiki could link ? > (Wikipedia is too detailed and scattered to be of help during a > computer crisis. See > http://en.wikipedia.org/wiki/Master_boot_record > http://en.wikipedia.org/wiki/File_Allocation_Table > ) > > > Maybe one should also swap the positions of the links on the > left edge of the general wiki: > "Help" > http://www.syslinux.org/wiki/index.php/Help:Contents > and > "Common Problem...

Some simple refactoring of virt-resize. I originally had the idea that we could turn virt-resize into a library (cf. virt-customize) and use it from virt-builder, but I now don't think that would make any meaningful difference. In particular we'd still have to open the handle the same number of times. These two patches are left over from my work on that. Rich.

Hallo, linux-btrfs, please delete the option "-L" (for labelling) in "mkfs.btrfs", in some configurations it doesn''t work as expected. My usual way: mkfs.btrfs -d raid0 -m raid1 /dev/sdb /dev/sdc /dev/sdd ... One call for some devices. Wenn I add the option "-L mylabel" then each device gets the same label, and therefore some other programs