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

2011-10-06 Thread martin f krafft
also sprach pille pille+debian+bug-rep...@struction.de [2011.10.05.2133 +0200]: i completely understand what happens as i'm able to boot the system by manually assembling the array and fixing the problem, but how the wrong hostname slips into the initramfs should be investigated by debians

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

2011-10-06 Thread pille
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,

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

2011-10-05 Thread pille
Package: mdadm Version: 3.1.4-1+8efb9d1 Severity: critical Tags: d-i Justification: breaks the whole system during install of squeeze i partitioned my disks and setup different MD-RAID devices using the partition tool. the corresponding /dev/mdX devices were created properly and i went on

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

2011-10-05 Thread martin f krafft
tags 644389 moreinfo unreproducible thanks also sprach pille pille+debian+bug-rep...@struction.de [2011.10.05.1458 +0200]: i assembled my RAID devices by hand How? but all names were prefixed with hostname 'hetzner'. What names? You mean the name= attribute in the mdadm --examine output?

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

2011-10-05 Thread pille
i assembled my RAID devices by hand How? something like: mdadm --assemble /dev/md1 /dev/sd[abcd]4 but all names were prefixed with hostname 'hetzner'. What names? You mean the name= attribute in the mdadm --examine output? excactly. Please provide the exact original and new UUIDs,

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

2011-10-05 Thread martin f krafft
also sprach pille pille+debian+bug-rep...@struction.de [2011.10.05.1819 +0200]: Please provide the exact original and new UUIDs, don't expect me to search the Net for them (I am offline right now). unfortunately i cannot provide you with those. if i could i would have done so, already. the

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

2011-10-05 Thread pille
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

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

2011-10-05 Thread 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

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

2011-10-05 Thread pille
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. i' don't know if it's the initramfs shipped with d-i, but today i did an offline