search for: aa55

...1 242252 1953514583+ ee GPT % dd if=/dev/sdj count=1 2> /dev/null | hexdump 0000000 0000 0000 0000 0000 0000 0000 0000 0000 * 00001c0 0002 ffee ffff 0001 0000 88af e8e0 0000 00001d0 0000 0000 0000 0000 0000 0000 0000 0000 * 00001f0 0000 0000 0000 0000 0000 0000 0000 aa55 0000200 So far, so normal. This works fine under 2.6.32-220.23.1.el6.x86_64 Personalities : [raid1] [raid10] [raid6] [raid5] [raid4] md127 : active raid5 sdj3[2] sdi2[1] sdk4[3] sdh1[0] 5860537344 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU] However, I just patched to Cent...

...t;http://www.ludd.ltu.se/~ams/tmp/isodavid.tgz> > > > * <CARRY> > > > * AX > > > * BX > > > * CX > > > * DX > > > * I die now. i wrote: > > I place my bet on CX value 4. :)) David Christensen wrote: > No carry. > 3000 > AA55 > 0004 > 0080 > I die now Hah ! CX announces no LBA addressing but Enhanced Disk Drive Support. https://en.wikipedia.org/wiki/INT_13H#INT_13h_AH.3D41h:_Check_Extensions_Present So isohdpfc pushed CX = 4 onto the stack, because it skipped andw 1,%xc So isolinux.bin read in "EHD...

...y rate, it came back up... and /dev/sdc is on as /dev/md127, and no /dev/md4, nothing in /etc/mdadm.conf, and, oh, yes, mdadm -A /dev/md4 /dev/sdd mdadm: Cannot assemble mbr metadata on /dev/sdd mdadm: /dev/sdd has no superblock - assembly aborted Oh, and mdadm -E /dev/sdd /dev/sdd: MBR Magic : aa55 Partition[0] : 4294967295 sectors at 1 (type ee) ee? A quick google says that indicates a legacy MBR, followed by an EFI.... I *REALLY* don't want to loose all that data. Any ideas? mark

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

Sure, I don't mind testing it out on there for you, but, where do I find the pre releases to try then? At least we know it's between 2.13 and 3.00. That narrows it a bit I would think. Mind you, if it jumps up a major revision number, I guess that means a lot of changes went in. On 8/2/05, syslinux-request at zytor.com <syslinux-request at zytor.com> wrote: > Send SYSLINUX