Your message dated Tue, 13 Jun 2023 04:48:16 +0000
with message-id <[email protected]>
and subject line Bug#1037326: Removed package(s) from unstable
has caused the Debian Bug report #502783,
regarding lilo: should use volume id on real MBRs only
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
502783: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502783
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Version: 1:24.2-5.1+rm
Dear submitter,
as the package lilo has just been removed from the Debian archive
unstable we hereby close the associated bug reports. We are sorry
that we couldn't deal with your issue properly.
For details on the removal, please see https://bugs.debian.org/1037326
The version of this package that was in Debian prior to this removal
can still be found using https://snapshot.debian.org/.
Please note that the changes have been done on the master archive and
will not propagate to any mirrors until the next dinstall run at the
earliest.
This message was generated automatically; if you believe that there is
a problem with it please contact the archive administrators by mailing
[email protected].
Debian distribution maintenance software
pp.
Scott Kitterman (the ftpmaster behind the curtain)
--- End Message ---
