search for: lba1

...ms/tmp/isohdpfx.force_cbios.bin> Back to Thomas' debug prints. You can download my logger version of isohdpfx called isohdpfd here: <http://www.ludd.ltu.se/~ams/tmp/isohdpfd.bin> <http://www.ludd.ltu.se/~ams/tmp/isohdpfd.S> In the EBIOS case it will print: E<LBA0>/<LBA1>/<LBA2>/<LBA3>/ <Big dump of first loaded sector> Key? and wait for a key press. In the CBIOS case it will print C<LBA0>/<C0>/<H0>/<S0> <LBA1>/<C1>/<H1>/<S1> <LBA2>/<C2>/<H2>/<S2> <LBA3>/<C3>...

Hi, MartinS wrote: > I want to say I've managed to simulate David's error in > qemu by forcing isohdpfx.bin to fail the EBIOS test. Wow. This could mean that the C/H/S related code is generally unsuitable for the job. > C<LBA0>/<C0>/<H0>/<S0> > <LBA1>/<C1>/<H1>/<S1> > <LBA2>/<C2>/<H2>/<S2> > <LBA3>/<C3>/<H3>/<S3> Anything strange to see with this sequence of addresses which are supposed to be consequtive ? Whatever, if this was only about confused addresses, then David...

...eeds but doesn't return correct value in BX. Please try this new isohdpfd.bin that indicates which part of EBIOS detection fails: <http://www.ludd.ltu.se/~ams/tmp/isohdpf_dump.2.tgz> * If an EBIOS is not detected outputs: * <X><LBA0>/<C0>/<H0>/<S0> * <LBA1>/<C1>/<H1>/<S1> * <LBA2>/<C2>/<H2>/<S2> * <LBA3>/<C3>/<H3>/<S3> * <Big hex dump of first loaded sector> * Key? * * and waits for a key press. * <X> is A if the EBIOS detection failed the extended disk access *...

...uestfish and try using, for example, part-get-disk-guid command on affected disk (or assign disk to a loop or nbd device and use sgdisk on affected disk directly from your host). In both cases you will get "Invalid partition data!". Why it happens? After step #4: GPT partition table at LBA1 is created and Protective MBR partition table at LBA0 is created as well. More over Windows automatically creates Microsoft Reserved Partition but this actually doesn't matter: we can delete this partition or pretend it doesn't exist. At this step sgdisk works as expected: it finds both Pro...

Thomas Schmitt wrote: > My main point of interest is which block is really loaded as first one > of isolinux.bin. [Program snipped.] > (It could be shorter if i did not insist in big endian words.) Why insisting? Anyway appended is a dumper version. I could put up a binery version if needed. Let me know if so. -- MartinS /*

...Nowadays there are hard drives and operating systems which support "4K native" sector size. In this mode physical and logical block size exposed to the operating system is equal to 4096 bytes. GPT partition table (as a known example) being created in this mode will place GPT header at LBA1 which is 4096 bytes. libguetfs is unable to recognize partition table on such physical block devices or disk images. The reason is that libguestfs appliance will look for a GPT header at LBA1 which is seen at 512 byte offset. In order to fix the issue we need a way to provide correct logical bloc...

...Nowadays there are hard drives and operating systems which support "4K native" sector size. In this mode physical and logical block size exposed to the operating system is equal to 4096 bytes. GPT partition table (as a known example) being created in this mode will place GPT header at LBA1 which is 4096 bytes. libguetfs is unable to recognize partition table on such physical block devices or disk images. The reason is that libguestfs appliance will look for a GPT header at LBA1 which is seen at 512 byte offset. In order to fix the issue we need a way to provide correct logical bloc...

Hi, Geert Stappers wrote: > Contact David off-list, he did unsubscribe. Can you tell when he unsubscribed (i.e. which of the messages he got as last one) ? > Martin posted elsewhere in this thread "Thomas, you found the bug" > and provided a patch. Open question is whether the fix helps with David's BIOS. The newest answer from Martin indicates that a failure to read

This is a bit updated set of chain.c32 changes that simplifies a few things (and in partiter part), fixes few minor issues and adds a few new features. Details are in the following commits, below is the summary and pull details at the end. Shao - any chance to peek over them ? Most of those are relatively simple changes and well tested, though of course something might have slipped my attention.

From: Nikolay Ivanets <stenavin@gmail.com> I faced with situation where libguestfs cannot recognize partitions on a disk image which was partitioned on a system with "4K native" sector size support. In order to fix the issue we need to allow users to specify desired physical and/or logical block size per drive basis. It is definitely not a complete patch but rather a way to