[Eisfair] E1 LILO Duplicated Volume ID

[Jürgen Witt]

Hallo NG,

ich habe einen Eisfair-1-Server (base 2.3.0, eiskernel 2.5.3) mit 2 
Festplatte, die zu einem Software-Raid-1 gespiegelt wurde.
Ich habe die beiden Platten dann aus Ihren Schächten entfernt und im 3. 
der 4 Laufwerksschächten auf eine weitere Platte auch eine komplette 
Eisfair-1-Installation vorgenommen. Von dieser Platte kann ich also zur 
Not ebenfalls booten, aber im Normalfall wird nur /data dieser 3. Platte 
unter /mnt der beiden Raid-Platten gemountet.

Wenn ich den Server nun mit 3 Platten starte, bekomme ich kurz die LILO 
Meldung

LILO ERROR
Duplicated Volume ID
nach 1 Sec. geht es weiter und der Server läuft.

Hier weitere Daten zu dem Server:

eis # cat /etc/lilo.conf
lba32
disk = /dev/sda
   bios = 0x80
boot = /dev/md1
raid-extra-boot = /dev/sda,/dev/sdb
read-only
prompt
timeout = 50
vga = normal
menu-scheme = wr:bw:wr:Yr
image = /boot/kernel
root = /dev/md3
label = eis
initrd = /boot/initrd.gz
append = "raid=noautodetect"
image = /boot/old-kernel
root = /dev/md3
label = oldeis
initrd = /boot/old-initrd.gz
append = "raid=noautodetect"
image = /boot/kernel-2.6.32-SMP
root = /dev/md3
label = 2.6.32-SMP
initrd = /boot/initrd-2.6.32-SMP.gz
append = "raid=noautodetect"

eis # lilo -T vol-ID


   BIOS     Volume ID

   0x80     39EE015C
   0x81     39EE015C *
   0x82     5A9CC3E5

Volume ID's are NOT unique.
    '*' marks a volume ID which is duplicated.  Duplicated ID's must be
         resolved before installing a new boot loader.  The volume ID may
         be cleared using the '-z' and '-M' switches.

eis # gdisk -l /dev/sda
GPT fdisk (gdisk) version 0.8.10

Partition table scan:
   MBR: protective
   BSD: not present
   APM: not present
   GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sda: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 21A985BA-51FE-434F-BA15-0B2C52B0325C
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 22494 sectors (11.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
    1            2048          100351   48.0 MiB    FD00  boot
    2          100352         8488959   4.0 GiB     FD00  swap
    3         8488960        71403519   30.0 GiB    FD00  root
    4        71403520      1953504654   897.5 GiB   FD00  data

eis # gdisk -l /dev/sdb
GPT fdisk (gdisk) version 0.8.10

Partition table scan:
   MBR: protective
   BSD: not present
   APM: not present
   GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 1953525168 sectors, 931.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): 4DE53CEB-7FD6-454C-B593-3DA7F4E928E1
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 1953525134
Partitions will be aligned on 2048-sector boundaries
Total free space is 22494 sectors (11.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
    1            2048          100351   48.0 MiB    FD00  boot
    2          100352         8488959   4.0 GiB     FD00  swap
    3         8488960        71403519   30.0 GiB    FD00  root
    4        71403520      1953504654   897.5 GiB   FD00  data

eis # gdisk -l /dev/sdc
GPT fdisk (gdisk) version 0.8.10

Partition table scan:
   MBR: protective
   BSD: not present
   APM: not present
   GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdc: 3907029168 sectors, 1.8 TiB
Logical sector size: 512 bytes
Disk identifier (GUID): 3D228C4B-C9FF-45C3-B2C3-72B2D29FF27A
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 22494 sectors (11.0 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
    1            2048          100351   48.0 MiB    8300  boot
    2          100352         8488959   4.0 GiB     8200  swap
    3         8488960        29460479   10.0 GiB    8300  root
    4        29460480      3907008654   1.8 TiB     8300  data

eis # mount
/dev/md3 on / type ext4 (rw,errors=remount-ro,acl,user_xattr)
/dev/md1 on /boot type ext4 (rw,errors=remount-ro)
/dev/md4 on /data type ext4 (rw,acl,user_xattr)
devpts on /dev/pts type devpts (rw)
usbfs on /proc/bus/usb type usbfs (rw)
/sys on /sys type sysfs (rw)
/dev/sdc4 on /mnt type ext4 (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
192.168.150.200:/mnt/data on /backup type nfs 
(ro,noexec,nosuid,nodev,vers=4,addr=192.168.150.200,clientaddr=192.168.150.200,user)

Wieso kommt es zu dieser doppelten Volume ID? Ist das problematisch?
Was tue ich dagegen?

Gruß
Jürgen