It's not the wrong hostname, it is what was current when the array
was created.

yes, but i think it's the hostname when the initramfs was created for the installer.

At least we should make sure this is the case. Could
you investigate what the 'hostname' command outputs on the d-i
shell, just before creating an array in partman during the install?

i checked and it behaves like expected:
it reports '(none)' up to the point where i set it to 'file'. afterwards it reports 'file'.

i installed _without_ RAID and used guided partitioning this time.
after the system is installed i took a look into /target and
there was the hetzner-mdadm.conf

more evidence for the d-i deploys standard initramfs with broken/suspect/unupdated mdadm.conf:

1) initramfs has an old timestamp (2011-08-27)
   and contains a comment that it was autogenerated that day
sha1sum is: a8f016e70843f108ae05ab0ef874eaad231005c8 initrd.img-2.6.32-5-amd64

2) last time i configured two arrays, but mdadm.conf contains three.

my problem is, that i cannot find it on the install medium (or a file big enough to hold it, tat actually contains it).

There are three ways forward, really:

   1. figure out a way by which the initramfs is updated when the
      hostname is changed;


there's only one way and it's updating the initramfs when nessessary (RAID config) and remove it when not needed.

   2. make sure the admin knows that changing the hostname requires
      telling mdadm;

   3. provide a debconf setting to disable the homehost feature
      (setting it to<ignore>).

the UUIDs are different, that's why the array don't get assembled.

since you should now be able to reproduce (even without RAID) i'll trash those VM images.

cheers
  pille
DEVICE partitions
HOMEHOST <system>
ARRAY /dev/md/0 metadata=1.2 UUID=f6de5584:d9dbce39:090f16ff:f795e54c 
name=hetzner:0
ARRAY /dev/md/1 metadata=1.2 UUID=0e065fee:15dea43e:f4ed7183:70d519bd 
name=hetzner:1
ARRAY /dev/md/2 metadata=1.2 UUID=ce4dd5a8:d8c2fdf4:4612713e:06047473 
name=hetzner:2
# mdadm.conf
#
# Please refer to mdadm.conf(5) for information about this file.
#

# by default, scan all partitions (/proc/partitions) for MD superblocks.
# alternatively, specify devices to scan, using wildcards if desired.
DEVICE partitions

# auto-create devices with Debian standard permissions
CREATE owner=root group=disk mode=0660 auto=yes

# automatically tag new arrays as belonging to the local system
HOMEHOST <system>

# instruct the monitoring daemon where to send mail alerts
MAILADDR root

# definitions of existing MD arrays
ARRAY /dev/md/0 metadata=1.2 UUID=f6de5584:d9dbce39:090f16ff:f795e54c 
name=hetzner:0
ARRAY /dev/md/1 metadata=1.2 UUID=0e065fee:15dea43e:f4ed7183:70d519bd 
name=hetzner:1
ARRAY /dev/md/2 metadata=1.2 UUID=ce4dd5a8:d8c2fdf4:4612713e:06047473 
name=hetzner:2

# This file was auto-generated on Sat, 27 Aug 2011 19:16:33 +0000
# by mkconf 3.1.4-1+8efb9d1

Reply via email to