[Eisfair] E1 LILO Duplicated Volume ID

Holger Bruenjes holgerbruenjes at gmx.net
Do Jun 19 23:08:05 CEST 2014


Am 2014-06-19 22:48, schrieb Holger Bruenjes:

>> Vorsicht, eventuell hat das weitere Auswirkungen, da das Raid ja nun 
>> schon erstellt ist. Der Installer macht das _vor_ Zusammenbau des Raids 
>> mit mdadm...

Das ganze aus dem lilo.Readme



1. Duplicate Volume ID's

LILO will complain if two disks have duplicate Volume ID's.  This
happens when the Volume ID field is a residue of a low-level format,
or a
residue of some older boot program which overwrites the Volume ID field.
With duplicated Volume ID's, LILO will be unable to distinguish the two
offending disks at boot-time, hence it may make an error and read
the wrong
disk.  Thus, it will refuse to install a boot loader as long as this
condition persists.  Unassigned ID's are automatically overwritten,
and a
backup copy of the sector is created, so the fix is to write an
value to one of the duplicated fields.  Say /dev/hda and /dev/hdb have
duplicate Volume ID's.  Choose the disk with the higher BIOS device
since it will not be a Windows NT or 2000 disk, and set the Volume ID to
zero; viz.,

        lilo -z -M /dev/hdb

The disk will receive a new Master Boot Record (which boots the
first active
partition), and the Volume ID will be set to zero.  A subsequent
installation of LILO:

        lilo -v

Should no longer complain about duplicated Volume ID's on /dev/hda and
/dev/hdb.  /dev/hdb will at this time receive a newly generated
Volume ID,
which will be checked for uniqueness against all other disks in the


Windows NT, 2000, and XP (presumably), all use the Volume ID during
the boot
process.  Changing the ID can render Windows unbootable.  Recovery
seems to
be possible by zeroing the Volume ID, although Windows would prefer
that the
Boot Volume ID remain unchanged.  No trouble has been encountered with
changing the Volume ID of Windows 2000 data disks, other than the
of resetting the drive letter to its former value.  Basically, if
you run
Windows NT or later, your disks probably already have Volume ID's
by Windows.  If they do, leave them alone.  The Windows ID's are
compatible with the LILO scheme, and vice versa.

2.  Volume ID check

The following command was added in LILO 22.5.4:

        lilo -T vol-ID

The volume ID's will be printed in BIOS order (as of the most recent
boot), based upon the BIOS data check information.  If you did not
boot with
LILO the last time, then the information as of the last boot will not be
available.  Any conflicts will be noted, along with the corrective
LILO will take the next time a boot loader is installed (/sbin/lilo
command).  This is the preferred check of the state of Volume ID's
on the

Sample output from "lilo -T vol-id":

  BIOS     Volume ID

  0x80     B21AB21A
  0x81     EBF5EB74
  0x82     EBF5EB7B
  0x83     34225390
  0x84     78711C09

Volume ID's are all unique.

A volume ID check (Volume S/N) will be printed with the following

        lilo -t -v2

The "-t" switch means a "test mode" install, with no boot record
and your system unmodified.  The "-v2" is needed to set the
verbosity of the
output high enough to print the table of BIOS device codes used by
LILO (not
necessarily the same as the BIOS itself), and the corresponding disk
ID's.  This information indicates the order of the BIOS device code
translate table, as it would be set up for the next boot.  Disks are
indicated by major/minor device numbers, in hex.

Sample output from "lilo -t -v2 | tail":

Mapped 6 (4+1+1) sectors.
Added Windows

 BIOS  Volume S/N  Device
  80    B21AB21A    0300
  81    EBF5EB74    0340
  82    EBF5EB7B    1600
  83    34225390    2100
  84    78711C09    0800
The boot sector and the map file have *NOT* been altered.

In the two examples above, the Volume ID's are in the same BIOS order,
indicating that the BIOS device codes are being assigned by LILO for the
boot loader in the correct sequence on this 5 disk system.

Mehr Informationen über die Mailingliste Eisfair