Package: lilo Version: 1:22.8-6 Hello,
lilo should use Volume-IDs on real MBRs, i.e. sectors flagged with 0x55 0xaa at the end, only. I have a md (Linux Software RAID) RAID1 spanning two disks without any partitions. Consequently, both disks have an identical sector 0 and this sector is not a MBR (I checked it, there is no accidental 0x55 0xaa at the end). On boot I get: | LILO | Error: Duplicated Volume ID | O 22.8 Loading Linux...<more dots> And even worse: when I try to update my image map via `lilo' I get: | Fatal: volid write error If I understand lilo.conf(5) correctly (the noraid part...), this should not happen at all with md volumes, since lilo should mark them inaccessible itself, but obviously lilo does not and it happens. And - no, I have no noraid directive in my lilo.conf and even marking both disks as inaccessible myself doesn't change anything. I have to pull one of the mirrors to get `lilo' to run. IMHO, it should be safe to simply ignore disks with no 0x55 0xaa signature in their "MBR", i.e. sector 0, since if it's missing, any other information stored there is not reliable anyways. This is most likely something to be forwarded upstream. And this are probably two bugs: - one wishlist regarding the MBR signature and another one regarding the non-working inacessible-marking of lilo. regards Mario -- There are two major products that come from Berkeley: LSD and UNIX. We don't believe this to be a coincidence. -- Jeremy S. Anderson
signature.asc
Description: Digital signature
