search for: ndhf4

...rs, the resulting >> boot sector will differ by one bit. > > Hrmm I can't reproduce this in a VM with identical drives. OK I did a CentOS 5 installation to raid1s, and it also boots either drive fine. But there's no log telling me how it installed the bootloader. http://ur1.ca/ndhf4 At offset 0x1B8 you'll notice 3 bytes of difference, but this is the disk signature. But what's interesting, this is not grub stage 1. This is a simple parted boot strap code that looks for the active bit in the MBR (the boot flag). When I do this: http://ur1.ca/ndhi3 There's the gru...

On 08/05/2015 10:23 AM, Chris Murphy wrote: > Nothing about hd0 or hd1 gets baked into the bootloader code. It's an > absolute reference to a physical drive at the moment in time the > command is made. Is that true? If I have a system with two disks, where device.map labels one as hd0 and the other as hd1, and I swap those numbers, the resulting boot sector will differ by one bit.