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

2011-10-06 Thread pille
the hostname requires telling mdadm; 3. provide a debconf setting to disable the homehost feature (setting it to). 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 th

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

2011-10-05 Thread pille
t; Note that mdadm.conf in initrd contains name "hetzer", while actual arrays are named "file". that's what i'm talking about. Is your real hostname "file" ? yes. pille -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

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

2011-10-05 Thread pille
tem (normal) install grub finish snapshot2 reboot snapshot3==== cheers pille <>

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, d

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

2011-10-05 Thread pille
made up) disks used were new & empty and had no affiliation to hetzner online AG you can search the net for '"name=hetzner:" mdadm.conf' to yield probably the original UUIDs. pille --- initrd.img-2.6.32-5-amd64: 47498 blocks 3718babf31303bc28114430ec0182e14 ./etc/

Bug#618463: please backport mdadm-3.2.2-1 to current stable

2011-10-04 Thread pille
n this bug and reviewed the mdadm changelog, which fixes this bug. i sucessfully grew the array using the version from nightly install CD. please backport from testing to stable. thanks pille -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubs

Bug#327024: 127.000.000.001 is dead, long live 127.0.0.1, or "hostname: Unknown host"

2005-09-06 Thread Gerard H. Pille
Package: libc6 Version: 2.3.5-6 Severity: serious Hallo, I have the (bad, it seems) habitude of putting leading zeroes in the IP-addresses in /etc/hosts. eg. 127.000.000.001 localhost.localdomain localhost 192.168.001.002 ghp-medp4.ghp.be ghp-medp4 Since I ran aptitude last weekend (3/9/2005