Bug#644389: suspect non-working mdadm.conf created during install

[Michael Tokarev]

On 05.10.2011 22:53, pille wrote:
>> In this case there is very little I can do. I have done multiple
>> squeeze installs with RAID, and upgrades, and I have not seen this
>> problem. Unless you can reproduce this bug, I cannot do anything but
>> keep this report open.
> 
> i've just reproduced such a failing install inside a KVM.
> see (combined) screenshot attached from first boot.
> 
> i've snapshotted the VM at different stages and can provide you with one that just boots for the first time (snapshot3, see screenshot).
> tell me if you're interrested in investigating it.
> 
> 
> here's a log of what i did:
> 
> booted http://cdimage.debian.org/debian-cd/current-live/amd64/iso-hybrid/debian-live-6.0.2-amd64-rescue.iso (sha1=0e5d9409719e657de4cbd9f355545cdc4c869038)
> expert text install
> selected some udebs (parted, reiserfs, squash, virtio)
> hostname = file.lan
> partition
>   manual
>     for all 4 disks:
>       GPT
>       p1: 6MB   BIOS BOOT
>       p2: 250MB RAID1 BOOT
>       p3: 768MB SWAP
>       p4: 3.3GB RAID6 VG/PV
>     configure sw raid:
>       md0: RAID1 /dev/sd[a-d]2: /boot (ext2)
>       md1: RAID6 /dev/sd[a-d]4: LVM PV (VG=vg-sys)
>     configure LVM:
>       LV system: /dev/md1 (4GB) / (reiserfs)
> ====snapshot1====
> install system (normal)
> install grub
> finish
> ====snapshot2====
> reboot
> ====snapshot3====

So it looks like during install time, in d-i, the system were named "hetzer" (most likely
due to DHCP), and all md arrays were created using that name.  And later on, it fails to
boot with actual hostname.  Note that mdadm.conf in initrd contains name "hetzer", while
actual arrays are named "file".

Is your real hostname "file" ?

/mjt