Bug#959018: Domain name queried during installation is not used
Package: debian-installer Version: 20190702+deb10u3 Severity: normal Tags: d-i During installation, I have to provide netcfg/domain. However, when the installation has finished and the system is booted, that domain name is not actually put in place anywhere. If I run # grep -r 'example\.org' /etc /var then the only reference I find is in /var/log/installer. At the very least, I'd expect the domain name to end up in /etc/hosts to ensure that `hostname --fqdn` works post-install. Whether to put it into /etc/hostname is another question… -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8), LANGUAGE=en_NZ:en (charmap=UTF-8) Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital GPG signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#750586: Problem continues to exist
also sprach Cyril Brulebois [2015-02-15 15:50 +0100]: > > I thought this issue was actually resolved? With the new d-i-n-a > > version, this now works for me. > > If you think we can infer “martin is using d-i-n-a” from “Unfortunately, > ldlinux.c32 is still being sought and not found. Any news?” then I can > assure you that we cannot… Yeah, sorry about that. I now took another look and I think that when I wrote in to the bug, I actually didn't have much of a clue about the issue at hand and the problem wasn't applicable to me in the first place. -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems whatever you do will be insignificant, but it is very important that you do it. -- mahatma gandhi digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#750586: Problem continues to exist
also sprach Cyril Brulebois [2015-02-15 15:21 +0100]: > martin f krafft (2015-01-29): > > Unfortunately, ldlinux.c32 is still being sought and not found. Any > > news? > > It would be helpful if either of you could try and figure out what's > going on/why Ron's patch is insufficient/what needs to be changed to > get your usecase to work. At least Chris Kuehl (cc'd) was happy with > the change. I thought this issue was actually resolved? With the new d-i-n-a version, this now works for me. -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems kill ugly radio -- frank zappa digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#776565: Please verify which patch version is fine
also sprach Andreas B. Mundt [2015-01-30 18:48 +0100]: > * Jonas provided patches in https://bugs.debian.org/759424#57 > * I had to modify Jonas' patch slightly to make it work here: >https://bugs.debian.org/759424#33 > * Jonas disagrees with that modification, the diffence is diskussed in >https://bugs.debian.org/759424#62 from my POV. I seem to remember that the files are indeed looked up under ./debian-installer/, which would mean Andi's modifications are needed. Right now, I am setting up a fresh install, so let's see what we can make of all your work. FTR, I have TFTPROOT set to /srv/tftp in di-netboot-assistant.conf, and I use atftpd from xinetd like so (as user nobody): in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 \ --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 /srv/tftp and I have it all configured so that I don't have to be root (cf. README file). Also, I don't do anything fancy in the DHCP config (cf. #776670), except serving next-server and filename=debian-installer/pxelinux.0 After applying Jonas' five patches and running install, I am left with . ├── debian-installer │ ├── daily │ │ └── i386 │ │ ├── boot-screens │ │ │ ├── […] │ │ ├── initrd.gz │ │ ├── linux │ │ ├── pxelinux.0 │ │ ├── pxelinux.cfg │ │ │ └── default -> ../boot-screens/syslinux.cfg │ │ └── version.info │ ├── pxelinux.0 │ ├── pxelinux.cfg │ │ ├── default │ │ ├── menu.c32 │ │ └── vesamenu.c32 │ └── README.txt ├── ldlinux.c32 ├── libcom32.c32 └── libutil.c32 Unfortunately, PXE does not work. Here are the files requested from the TFTP server: atftpd[12256]: Serving debian-installer/pxelinux.0 to 192.168.17.133:43759 atftpd[12256]: Serving debian-installer/ldlinux.c32 to 192.168.17.133:49152 atftpd[12256]: Serving debian-installer//boot/isolinux/ldlinux.c32 to 192.168.17.133:49153 atftpd[12256]: Serving debian-installer//isolinux/ldlinux.c32 to 192.168.17.133:49154 atftpd[12256]: Serving debian-installer//boot/syslinux/ldlinux.c32 to 192.168.17.133:49155 atftpd[12256]: Serving debian-installer//syslinux/ldlinux.c32 to 192.168.17.133:49156 atftpd[12256]: Serving debian-installer//ldlinux.c32 to 192.168.17.133:49157 So yes, ldlinux.c32 is looked up under debian-installer/ldlinux.c32. So now, let's change the /bin/cp destination, as suggested by Andi. Now the install yields: . └── debian-installer ├── daily │ └── i386 │ ├── boot-screens │ │ ├── […] │ ├── initrd.gz │ ├── linux │ ├── pxelinux.0 │ ├── pxelinux.cfg │ │ └── default -> ../boot-screens/syslinux.cfg │ └── version.info ├── ldlinux.c32 ├── libcom32.c32 ├── libutil.c32 ├── pxelinux.0 ├── pxelinux.cfg │ ├── default │ ├── menu.c32 │ └── vesamenu.c32 └── README.txt The TFTP server now sees the following requests: atftpd[13592]: Serving debian-installer/pxelinux.0 to 192.168.17.133:37488 atftpd[13592]: Serving debian-installer/ldlinux.c32 to 192.168.17.133:49152 atftpd[13592]: Serving debian-installer/pxelinux.cfg/4274295f-9f3c-4e8b-8c6a-166b2f0241d1 to 192.168.17.133:49153 atftpd[13592]: Serving /debian-installer/pxelinux.cfg/menu.c32 to 192.168.17.133:49164 atftpd[13592]: Serving debian-installer/libutil.c32 to 192.168.17.133:49165 atftpd[13592]: Serving debian-installer/pxelinux.cfg/default to 192.168.17.133:49166 and the menu is shown and installation works! So to this point, I have to say that Andi's modification seems necessary. > * I sent some minor improvement patches in > https://bugs.debian.org/759424#67 and > https://bugs.debian.org/759424#72 Both of these patches make sense to have included and work just fine, mainly because Andi's original patch doesn't apply anymore (Jonas included some changes). Attached is the combined patch against di-n-a which I tested. The di-sources.list patch (the last one) applies fine So my verdict: I think Jonas patches fix a good chunk of the problems, but Andi's modification is required. His other patches also make sense and can/should be included, even for a jessie release. And yes, I think it would be better to fix this for jessie than to leave it as is, or remove the package. This is a package used by hardcore sysadmins only anyway, so I think it's okay to run the risk and simply expect them to use a backport later if there are some bugs we didn't see or introduce here. -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems --- /tmp/di-netboot-assistant 2015-01-30 21:4
Bug#776565: Please verify which patch version is fine
also sprach Andreas B. Mundt [2015-01-30 18:48 +0100]: > * Jonas provided patches in https://bugs.debian.org/759424#57 > * I had to modify Jonas' patch slightly to make it work here: >https://bugs.debian.org/759424#33 > * Jonas disagrees with that modification, the diffence is diskussed in >https://bugs.debian.org/759424#62 from my POV. I seem to remember that the files are indeed looked up under ./debian-installer/, which would mean Andi's modifications are needed. Right now, I am setting up a fresh install, so let's see what we can make of all your work. FTR, I have TFTPROOT set to /srv/tftp in di-netboot-assistant.conf, and I use atftpd from xinetd like so (as user nobody): in.tftpd --tftpd-timeout 300 --retry-timeout 5 --mcast-port 1758 \ --mcast-addr 239.239.239.0-255 --mcast-ttl 1 --maxthread 100 --verbose=5 /srv/tftp and I have it all configured so that I don't have to be root (cf. README file). Also, I don't do anything fancy in the DHCP config (cf. #776670), except serving next-server and filename=debian-installer/pxelinux.0 After applying Jonas' five patches and running install, I am left with . ├── debian-installer │ ├── daily │ │ └── i386 │ │ ├── boot-screens │ │ │ ├── […] │ │ ├── initrd.gz │ │ ├── linux │ │ ├── pxelinux.0 │ │ ├── pxelinux.cfg │ │ │ └── default -> ../boot-screens/syslinux.cfg │ │ └── version.info │ ├── pxelinux.0 │ ├── pxelinux.cfg │ │ ├── default │ │ ├── menu.c32 │ │ └── vesamenu.c32 │ └── README.txt ├── ldlinux.c32 ├── libcom32.c32 └── libutil.c32 Unfortunately, PXE does not work. Here are the files requested from the TFTP server: atftpd[12256]: Serving debian-installer/pxelinux.0 to 192.168.17.133:43759 atftpd[12256]: Serving debian-installer/ldlinux.c32 to 192.168.17.133:49152 atftpd[12256]: Serving debian-installer//boot/isolinux/ldlinux.c32 to 192.168.17.133:49153 atftpd[12256]: Serving debian-installer//isolinux/ldlinux.c32 to 192.168.17.133:49154 atftpd[12256]: Serving debian-installer//boot/syslinux/ldlinux.c32 to 192.168.17.133:49155 atftpd[12256]: Serving debian-installer//syslinux/ldlinux.c32 to 192.168.17.133:49156 atftpd[12256]: Serving debian-installer//ldlinux.c32 to 192.168.17.133:49157 So yes, ldlinux.c32 is looked up under debian-installer/ldlinux.c32. So now, let's change the /bin/cp destination, as suggested by Andi. Now the install yields: . └── debian-installer ├── daily │ └── i386 │ ├── boot-screens │ │ ├── […] │ ├── initrd.gz │ ├── linux │ ├── pxelinux.0 │ ├── pxelinux.cfg │ │ └── default -> ../boot-screens/syslinux.cfg │ └── version.info ├── ldlinux.c32 ├── libcom32.c32 ├── libutil.c32 ├── pxelinux.0 ├── pxelinux.cfg │ ├── default │ ├── menu.c32 │ └── vesamenu.c32 └── README.txt The TFTP server now sees the following requests: atftpd[13592]: Serving debian-installer/pxelinux.0 to 192.168.17.133:37488 atftpd[13592]: Serving debian-installer/ldlinux.c32 to 192.168.17.133:49152 atftpd[13592]: Serving debian-installer/pxelinux.cfg/4274295f-9f3c-4e8b-8c6a-166b2f0241d1 to 192.168.17.133:49153 atftpd[13592]: Serving /debian-installer/pxelinux.cfg/menu.c32 to 192.168.17.133:49164 atftpd[13592]: Serving debian-installer/libutil.c32 to 192.168.17.133:49165 atftpd[13592]: Serving debian-installer/pxelinux.cfg/default to 192.168.17.133:49166 and the menu is shown and installation works! So to this point, I have to say that Andi's modification seems necessary. > * I sent some minor improvement patches in > https://bugs.debian.org/759424#67 and > https://bugs.debian.org/759424#72 Both of these patches make sense to have included and work just fine, mainly because Andi's original patch doesn't apply anymore (Jonas included some changes). Attached is the combined patch against di-n-a which I tested. The di-sources.list patch (the last one) applies fine So my verdict: I think Jonas patches fix a good chunk of the problems, but Andi's modification is required. His other patches also make sense and can/should be included, even for a jessie release. And yes, I think it would be better to fix this for jessie than to leave it as is, or remove the package. This is a package used by hardcore sysadmins only anyway, so I think it's okay to run the risk and simply expect them to use a backport later if there are some bugs we didn't see or introduce here. -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems --- /tmp/di-netboot-assistant 2015-01-30 21:4
Bug#776670: Questionable dhcpd configuration options
Package: di-netboot-assistant Version: 0.38a Severity: minor I don't think all the options under pxelinux.* are necessary at all (cf. README file). It works fine without them. Specifically, the line option pxelinux.configfile "debian-installer/pxelinux.cfg/default"; causes a request to "debian-installer/debian-installer/pxelinux.cfg/default" which obviously does not exist — the config file is looked up relative to pxelinux.0 it seems. That option disables the ability to override the configuration per-client based on UUID or IP and so it's doubtful whether there is a benefit in using it anyway. My suggestion: remove all the options. dhcpd (v4 here) works fine with just next-server and filename. -- System Information: Debian Release: 8.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages di-netboot-assistant depends on: ii curl 7.38.0-4 ii wget 1.16-3 Versions of packages di-netboot-assistant recommends: ii atftpd 0.7.git20120829-1 Versions of packages di-netboot-assistant suggests: pn dhcp3-server | udhcpd | dnsmasq pn elilo ii syslinux 3:6.03+dfsg-5 ii vim-addon-manager0.5.3 -- Configuration Files: /etc/di-netboot-assistant/di-netboot-assistant.conf changed [not included] /etc/di-netboot-assistant/di-sources.list changed [not included] -- no debconf information -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#776565: Booting does not currently work
also sprach Cyril Brulebois [2015-01-29 18:58 +0100]: > I'm not sure it's reasonable to expect fixing di-n-a at this point of > the release cycle, frankly. Of course, but maybe the fix is trivial… on the other hand, I looked and tried already… there is a patch. Lemme at least verify that one on the weekend. -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems tempt not a desperate man. -- william shakespeare digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#776565: Booting does not currently work
also sprach Cyril Brulebois [2015-01-29 16:44 +0100]: > Latest news (hrm) are: > [2013-07-17] Accepted 0.38a in unstable (low) (Christian Perrier) > [2013-07-28] di-netboot-assistant 0.38a MIGRATED to testing (Britney) > > At this stage, it'd probably be a good idea to have it removed > from testing; Yeah, except I'd love to have it. :( But it seems obviously broken. Let's wait another day or two and hope that maybe Christian, Franklin or Joey have a say? -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems "this sentence contradicts itself -- no actually it doesn't." -- douglas hofstadter digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#776566: Please cater to serial consoles
/ftp.debian.org/dists/squeeze/main/installer-amd64/current/images/
netboot/gtk/netboot.tar.gz
squeeze-gtk i386
http://ftp.debian.org/dists/squeeze/main/installer-i386/current/images/
netboot/gtk/netboot.tar.gz
testing amd64
http://ftp.debian.org/dists/testing/main/installer-amd64/current/images/
netboot/netboot.tar.gz
testing i386
http://ftp.debian.org/dists/testing/main/installer-i386/current/images/
netboot/netboot.tar.gz
testing ia64
http://ftp.debian.org/dists/testing/main/installer-ia64/current/images/
netboot/netboot.tar.gz
testing sparc
http://ftp.debian.org/dists/testing/main/installer-sparc/current/images/
netboot/boot.img
testing-gtk amd64
http://ftp.debian.org/dists/testing/main/installer-amd64/current/images/
netboot/gtk/netboot.tar.gz
testing-gtk i386
http://ftp.debian.org/dists/testing/main/installer-i386/current/images/
netboot/gtk/netboot.tar.gz
daily alpha http://d-i.debian.org/daily-images/alpha/daily/ netboot/boot.img
daily amd64 http://d-i.debian.org/daily-images/amd64/daily/
netboot/netboot.tar.gz
daily hppahttp://d-i.debian.org/daily-images/hppa/daily/
netboot/2.6/boot.img
daily i386http://d-i.debian.org/daily-images/i386/daily/
netboot/netboot.tar.gz
daily ia64http://d-i.debian.org/daily-images/ia64/daily/
netboot/netboot.tar.gz
daily sparc http://d-i.debian.org/daily-images/sparc/daily/ netboot/boot.img
daily-gtk amd64 http://d-i.debian.org/daily-images/amd64/daily/
netboot/gtk/netboot.tar.gz
daily-gtk i386http://d-i.debian.org/daily-images/i386/daily/
netboot/gtk/netboot.tar.gz
lenny alpha
http://archive.debian.org/dists/lenny/main/installer-alpha/current/images/
netboot/boot.img
lenny amd64
http://archive.debian.org/dists/lenny/main/installer-amd64/current/images/
netboot/netboot.tar.gz
lenny hppa
http://archive.debian.org/dists/lenny/main/installer-hppa/current/images/
netboot/2.6/boot.img
lenny i386
http://archive.debian.org/dists/lenny/main/installer-i386/current/images/
netboot/netboot.tar.gz
lenny ia64
http://archive.debian.org/dists/lenny/main/installer-ia64/current/images/
netboot/netboot.tar.gz
lenny sparc
http://archive.debian.org/dists/lenny/main/installer-sparc/current/images/
netboot/boot.img
lenny-gtk amd64
http://archive.debian.org/dists/lenny/main/installer-amd64/current/images/
netboot/gtk/netboot.tar.gz
lenny-gtk i386
http://archive.debian.org/dists/lenny/main/installer-i386/current/images/
netboot/gtk/netboot.tar.gz
hardy i386
http://archive.ubuntu.com/ubuntu/dists/hardy/main/installer-i386/current/images/
netboot/netboot.tar.gz
hardy amd64
http://archive.ubuntu.com/ubuntu/dists/hardy/main/installer-amd64/current/images/
netboot/netboot.tar.gz
lucid i386
http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-i386/current/images/
netboot/netboot.tar.gz
lucid amd64
http://archive.ubuntu.com/ubuntu/dists/lucid/main/installer-amd64/current/images/
netboot/netboot.tar.gz
precise i386
http://archive.ubuntu.com/ubuntu/dists/precise/main/installer-i386/current/images/
netboot/netboot.tar.gz
precise amd64
http://archive.ubuntu.com/ubuntu/dists/precise/main/installer-amd64/current/images/
netboot/netboot.tar.gz
trusty i386
http://ftp.ubuntu.com/ubuntu/dists/trusty/main/installer-i386/current/images/
netboot/netboot.tar.gz
trusty amd64
http://ftp.ubuntu.com/ubuntu/dists/trusty/main/installer-amd64/current/images/
netboot/netboot.tar.gz
utopic i386
http://ftp.ubuntu.com/ubuntu/dists/utopic/main/installer-i386/current/images/
netboot/netboot.tar.gz
utopic amd64
http://ftp.ubuntu.com/ubuntu/dists/utopic/main/installer-amd64/current/images/
netboot/netboot.tar.gz
saucy i386
http://archive.ubuntu.com/ubuntu/dists/saucy/main/installer-i386/current/images/
netboot/netboot.tar.gz
saucy amd64
http://archive.ubuntu.com/ubuntu/dists/saucy/main/installer-amd64/current/images/
netboot/netboot.tar.gz
raring i386
http://archive.ubuntu.com/ubuntu/dists/raring/main/installer-i386/current/images/
netboot/netboot.tar.gz
raring amd64
http://archive.ubuntu.com/ubuntu/dists/raring/main/installer-amd64/current/images/
netboot/netboot.tar.gz
quantal i386
http://archive.ubuntu.com/ubuntu/dists/quantal/main/installer-i386/current/images/
netboot/netboot.tar.gz
quantal amd64
http://archive.ubuntu.com/ubuntu/dists/quantal/main/installer-amd64/current/images/
netboot/netboot.tar.gz
oneiric i386
http://archive.ubuntu.com/ubuntu/dists/oneiric/main/installer-i386/current/images/
netboot/netboot.tar.gz
oneiric amd64
http://archive.ubuntu.com/ubuntu/dists/oneiric/main/installer-amd64/current/images/
netboot/netboot.tar.gz
-- debconf-show failed
--
.'
Bug#776565: Booting does not currently work
rchive.ubuntu.com/ubuntu/dists/oneiric/main/installer-amd64/current/images/ netboot/netboot.tar.gz -- debconf-show failed -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#750586: Problem continues to exist
Unfortunately, ldlinux.c32 is still being sought and not found. Any news? -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#769406: Serial console not set up after serial install
Package: debian-installer Version: 20141112-00:20 Severity: important Following an install with auto console=tty0 console=ttyS0,115200n8 on the command line and using yesterday's amd64 daily jessie installer, the /etc/default/grub file had GRUB_TERMINAL=serial enabled, but it does not append the above console parameters to GRUB_CMDLINE_LINUX. Cf. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683124 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#769407: Should set up Grub for serial and console
Package: debian-installer Version: 20141112-00:20 Severity: wishlist Following an install with auto console=tty0 console=ttyS0,115200n8 on the command line and using yesterday's amd64 daily jessie installer, the /etc/default/grub file had GRUB_TERMINAL=serial enabled. Please set that to GRUB_TERMINAL="console serial" to allow Grub to display on both, which it has supported for a while. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft @martinkrafft : :' : proud Debian developer `. `'` http://people.debian.org/~madduck `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#734690: Language-chooser: C is not a language
also sprach Christian PERRIER [2014-03-04 07:54 +0100]: > If so, that's (or that was) on purpose given that there is no > guarantee that a serial console can properly display non pure ASCII > characters. I am not talking about "character sets". I am talking about language names. "C" is not a human language, so it should not appear in any list about languages next to "English". That we know it as a form of localization doesn't play a role because the average user doesn't even know what localization means. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "moderation is a fatal thing. enough is as bad as a meal. more than enough is as good as a feast." -- oscar wilde digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#734690: Language-chooser: C is not a language
also sprach Samuel Thibault [2014-03-03 17:28 +0100]: > > martin f krafft (2014-03-03): > > > I am not using GTK, but dialog. > > On a serial console. Yes, sorry. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "my father, a good man, told me: 'never lose your ignorance; you cannot replace it.'" -- erich maria remarque digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#740271: d-i fails to purge LVM despite preseeding
anna[3345]: DEBUG: retrieving partman-ext3 74 Mar 3 09:26:08 anna[3345]: DEBUG: retrieving partman-jfs 38 Mar 3 09:26:08 anna[3345]: DEBUG: retrieving partman-md 64 Mar 3 09:26:09 anna[3345]: DEBUG: retrieving partman-partitioning 91 Mar 3 09:26:10 anna[3345]: DEBUG: retrieving partman-target 82 Mar 3 09:26:10 anna[3345]: DEBUG: retrieving partman-ufs 14 Mar 3 09:26:11 anna[3345]: DEBUG: retrieving partman-xfs 50 Mar 3 09:26:21 main-menu[2522]: INFO: Menu item 'partman-base' selected Mar 3 09:26:21 anna-install: Installing partman-auto-lvm Mar 3 09:26:21 anna[5810]: DEBUG: retrieving lvm2-udeb 2.02.95-8 Mar 3 09:26:21 anna[5810]: DEBUG: retrieving partman-auto-lvm 47 Mar 3 09:26:22 anna[5810]: DEBUG: retrieving partman-lvm 82 Mar 3 09:26:23 anna-install: Installing partman-auto-crypto Mar 3 09:26:23 anna[5914]: DEBUG: retrieving partman-auto-crypto 19 Mar 3 09:26:23 anna[5914]: DEBUG: retrieving partman-crypto 57 Mar 3 09:26:25 partman: No matching physical volumes found Mar 3 09:26:25 partman: Reading all physical volumes. This may take a while... Mar 3 09:26:25 partman: Mar 3 09:26:25 partman: No volume groups found Mar 3 09:26:25 partman: Mar 3 09:26:25 partman-lvm: Mar 3 09:26:25 partman-lvm: No volume groups found Mar 3 09:26:25 partman-lvm: Mar 3 09:26:25 partman-auto: Available disk space (2147) too small for expert recipe (14465); skipping Mar 3 09:26:26 partman-lvm: Mar 3 09:26:26 partman-lvm: Physical volume '/dev/vda3' is already in volume group 'orange' Mar 3 09:26:26 partman-lvm: Mar 3 09:26:26 partman-lvm: Mar 3 09:26:26 partman-lvm: Unable to add physical volume '/dev/vda3' to volume group 'purple'. Mar 3 09:26:26 partman-lvm: Mar 3 09:26:58 main-menu[2522]: (process:5796): /var/lib/partman/devices/=dev=vda Mar 3 09:26:58 main-menu[2522]: INFO: Menu item 'partman-base' succeeded but requested to be left unconfigured. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "die menschen drängen sich zum lichte, nicht um besser zu sehen, sondern um besser zu glänzen." - friedrich nietzsche digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#740271: d-i fails to purge LVM despite preseeding
also sprach Dimitri John Ledkov [2014-03-03 09:31 +0100]: > Indeed just use an lvm-preseed, twice in a row, and delete partition > table between the two runs. What do you mean with that? > wiping / zeroing out the drive before installation would be slow, > but would fix this... It's what I am doing now, but it sucks. Logs coming… -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "a bank is an institution will to lend you money, provided you can prove that you don't need it." -- mark twain digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#734690: Language-chooser: C is not a language
also sprach Cyril Brulebois [2014-03-03 09:45 +0100]: > Finally, I'm not sure why you're insisting we drop support for non- > localized installations. I am not, I am just saying that "C" isn't a language to most people. > All in all, it looks like everything confirms -done@ was right. As you wish, I don't care, I just thought it was important to pass on a message. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "there was silence for a moment, and then out of the scrambled mess of arthur's brain crawled some words." -- hitchhiker's guide to the galaxy digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#740589: Complains it cannot find device
Package: partman-lvm Version: 82 Severity: normal partman-lvm / LVM cannot find /dev/vda3, yet it exists: Mar 3 08:34:14 partman: No matching physical volumes found Mar 3 08:34:14 partman: Reading all physical volumes. This may take a while... Mar 3 08:34:14 partman: Mar 3 08:34:14 partman: No volume groups found Mar 3 08:34:14 partman: Mar 3 08:34:14 partman-lvm: Mar 3 08:34:14 partman-lvm: No volume groups found Mar 3 08:34:14 partman-lvm: Mar 3 08:34:14 partman-auto: Available disk space (2147) too small for expert recipe (14465); skipping Mar 3 08:34:15 partman-lvm: Mar 3 08:34:15 partman-lvm: Device /dev/vda3 not found (or ignored by filtering). Mar 3 08:34:15 partman-lvm: Switching to the console: # ls /dev/vda* /dev/vda/dev/vda1/dev/vda2/dev/vda3 # pvcreate /dev/vda3 Writing physical volume data to disk "/dev/vda3" Physical volume "/dev/vda3" successfully created -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.12-1-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#734690: Language-chooser: C is not a language
also sprach Cyril Brulebois [2014-03-02 23:18 +0100]: > Err, please clarify what “that was not the case, it just said "C"” > means. I'm attaching a screenshot of the current state. (And > Christian mentioned that was the case, so it's not clear to me > what you're trying to say.) I am not using GTK, but dialog. Here's the "screenshot": ┌───┤ [!!] Select a language ├┐ │ │ │ Choose the language to be used for the installation process. The│ │ selected language will also be the default language for the installed │ │ system. │ │ │ │ Language: │ │ │ │ C │ │ English │ │ │ ││ │ │ └─┘ moves; selects; activates buttons Sure, English is preselected and most people won't expend a second thought, but C is not a language, and I don't think it should appear in the list of choices. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "if a man treats life artistically, his brain is his heart." -- oscar wilde digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#740271: d-i fails to purge LVM despite preseeding
Package: debian-installer Version: 20130613+deb7u1+b2 Severity: normal Despite d-i partman-auto/purge_lvm_from_device boolean true d-i partman-lvm/device_remove_lvm boolean true d-i partman-lvm/confirm boolean true d-i partman-lvm/confirm_nooverwrite boolean true d-i fails to install a machine when libvirt passes it a storage volume that has previously been used as PV by another host. What happens (in my case) is that partman creates a new GPT, but often that will be exactly the same as the one used by the previous host using the volume. Therefore, /dev/vda3 will be a valid LVM PV, meaning that LVM will find the previous VG. Now, depending on whether the hostname is (a) the same, or (b) different, d-i will fail to install claiming (a) a VG with the same name is already present; (b) the PV is already in use by another VG. Even if I fix the situation from within d-i manually, I cannot resume the installation — re-entering partman from the menu will just make it display "No root filesystem… [Continue]" and hitting "Continue" will just bring up the same dialog again, endlessly. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.13-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#734690: Language-chooser: C is not a language
Package: debian-installer Severity: normal It was just pointed out in a LCA2014 presentation that it's a bit silly to ask the user to choose the language between "C" and "English". Maybe this could be moved to a lower priority or rephrased? Sorry I did not verify this or check. The network here is slow and I just wanted to make sure that this isn't forgotten. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.11-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#444026: use multiple terminals instead
The --timeout option no longer exists. By now, grub supports setting GRUB_TERMINAL="serial console" and will show the Grub menu on both, allowing both to be used. I think this should become the default when a serial console is detected during install. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Re: d-i mount/umounting /target/proc
also sprach Cyril Brulebois [2013.04.07.2358 +0200]: > #704931 wasn't the right place, so you needed to make more noise > on this list, where bug traffic lands already? (You supposedly > know the latter already since you're setting MFT to the list, > right?) I am genuinely interested in the reasons for the current design. You will note that this thread is highly focused. If you have better things to do, please do them. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems no keyboard present. press f1 to continue. zen engineering. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
d-i mount/umounting /target/proc
Hello, I found that during a preseeded wheezy install, /target/proc gets mounted and umounted more than 20 times (caused by chroot_setup and chroot_cleanup) Why? Why isn't /target/proc (and /target/sys) mounted after the /target-filesystem is mounted and unmounted before /target gets unmounted? -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "'oh, that was easy,' says Man, and for an encore goes on to prove that black is white and gets himself killed on the next zebra crossing." -- douglas adams, "the hitchhiker's guide to the galaxy" digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#704931: chroot_cleanup should not unmount /proc
also sprach Cyril Brulebois [2013.04.07.2257 +0200]: > AFAICT you're the only one having such an issue with the > mount/umount dance (it might be suboptimal as far as > “performances” are concerned, but that's certainly not serious); > having that issue with grub-installer, which already got > a fix-or-workaround in the meanwhile, makes me think it's nowhere > like a serious bug. So there is a "dance" being performed for no apparent reason, and you prefer to hack a fix into grub-installer rather than to fix the root's cause? What if the next d-i component fails, will you hack it too? I can demonstrate how I can break d-i using only the preseed.cfg file's interface and you don't consider this serious? Attached is the log you wanted. I could not find anything therein. The d-i is from the mirrors at stable/main/installer-amd64/current/images/netboot downloaded yesterday and updated today. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems (on the statement print "42 monkeys"+"1 snake") btw, both perl and python get this wrong. perl gives 43 and python gives "42 monkeys1 snake", when the answer is clearly "41 monkeys and 1 fat snake". -- jim fulton syslog.xz Description: Binary data digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#704931: chroot_cleanup should not unmount /proc
Package: src:debian-installer-utils Severity: serious For a reason unknown to me, helpers like in-target and apt-install, by way of chroot_setup and chroot_cleanup, might actually cause /target/proc to be unmounted. This then breaks grub-install. Arguably, commit 795bfde of grub-installer hacks around this problem, when actually I don't think there is any reason why /target/proc (or /target/sys, etc.) should ever be unmounted before it's time to unmount the /target tree. In my case, I was experimenting with preseeding when suddenly, grub-install failed. The reason was a missing /target/proc. Thinking that /target/proc should not have been unmounted, I used the console to chdir() to it, thereby causing umount to fail. Here is what syslog documented: Apr 7 15:05:07 in-target: Setting up popularity-contest (1.56) ... Apr 7 15:05:08 pkgsel: umount: can't umount /target/proc: Device or resource busy Apr 7 15:05:08 /bin/in-target: warning: Unable to umount '/target/proc' Apr 7 15:05:08 in-target: (Reading database ...· Apr 7 15:05:08 in-target: 14789 files and directories currently installed.) Apr 7 15:05:08 in-target: Removing popularity-contest ... Apr 7 15:05:08 in-target: Purging configuration files for popularity-contest ... Later, I used network-console and a while loop to track the state of /proc/mounts and I found that /target/proc randomly appeared and disappeared. By the time grub-install is run, it isn't present. I don't know whether the above, popcon-associated instance of umount is at fault, but I do question why /target/proc ever gets unmounted. The version of d-i I am using doesn't have Steve's commit yet, so grub-install just fails. I can reproduce this, I can even give network-console access to the host I am using for testing, and stand by on IRC for debugging. It's a KVM instance provisioned by virt-install and preseeded, so it's trivial to work with… -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#704881: Method to obtain minimum preseed file
Package: src:debian-installer Severity: wishlist It would be nice if d-i could store information about exactly which questions the user explicitly answered during an install, such that the result can be used as a baseline for creating a corresponding preseed.cfg file. As far as I can tell, d-i has all the information, and even leaving a fully-commented pressed.cfg file in /var/log/installer after the installation should be doable. Thanks, -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.8-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#690487: default alignment of partitions
reassign 690487 cfdisk thanks also sprach Samuel Thibault [2012.10.14.2206 +0200]: > AFAWK, this is already the case in the latest installers (including > the Squeeze installer). If you noticed it not to be the case in some > situation, please describe the situation, otherwise it will be an > "unreproducible" for us. You know what, I am an idiot. I had used cfdisk manually before d-i. Let's repurpose this bug report in the hope that the cfdisk guys are open to this suggestion. Sorry… -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#690488: mark packages as auto-installed
Package: debian-installer Severity: wishlist I wish that a fresh installation would have most packages marked as auto-installed – all except the ones that are explicitly installed or needed (e.g. tasks, lvm2, mdadm, cryptsetup, etc.) and the absolutely required packages (Priority:important and above). -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#690487: default alignment of partitions
Package: debian-installer Severity: wishlist In cases where d-i creates partition tables or disk labels, it should do so using 4k boundaries, as most new disks use 4k physical sectors. Misaligning the filesystem would result in 50 % degraded drive performance in those case. Essentially, instead of 63, put the first partition at block 64. Or just leave 1M free before the first partition, which is a safe bet for the future. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-3-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#668139: falls over a missing directory /var/lib/os-prober/mount
Package: os-prober Version: 1.49 Severity: minor I don't know what os-prober does, but # os-prober ls: reading directory /var/lib/os-prober/mount: Input/output error ls: reading directory /var/lib/os-prober/mount: Input/output error ls: reading directory /var/lib/os-prober/mount: Input/output error ls: reading directory /var/lib/os-prober/mount: Input/output error ls: reading directory /var/lib/os-prober/mount: Input/output error ls: reading directory /var/lib/os-prober/mount: Input/output error ls: reading directory /var/lib/os-prober/mount: Input/output error strikes me as unnecessary (the backup didn't contain the directory for some reason). Maybe a simple check and mkdir() could mitigate this? Thanks, -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.3.0-trunk-amd64 (SMP w/8 CPU cores) Locale: LANG=en_NZ, LC_CTYPE=en_NZ.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages os-prober depends on: ii libc6 2.13-27 os-prober recommends no packages. os-prober suggests no packages. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)
Bug#601440: installer components menu not available with default debconf priority
Package: debian-installer Version: 20101025 Severity: normal When asked to enter the root password, I chose 'Go back' to be able to load the network-console. The menu item 'Download installer components' is present, but selecting it eventually just causes d-i to ask me for the root password — confusing unless you know what's going on. I suggest that the menu item be hidden if the debconf priority is 'high' and only shown if it's set to 'medium'. Or maybe the installer components could be temporarily lowered from high to medium if selected explicitly? -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-rc6-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#601439: warn when /boot will be inaccessible to boot loader
Package: debian-installer Version: 20101025 Severity: wishlist grub2 can do a lot already, i.e. boot off LVM on RAID6 and other fun stuff, but there are certain things it cannot do (yet): - boot off a partitioned md device (e.g. boot is /dev/md0p1) - boot when /boot is somehow encrypted lilo can't boot off LVM or RAID, but if /boot is RAID1, it can access the underlying devices directly (read-only). It would be really nice if d-i included a check for this stuff… -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.36-rc6-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#524342: Problem might be related to raid metadata version
also sprach bugrep...@public-files.de [2010.10.04.0208 +0200]: > grub-pc segfaults when raid is root. As mentioned before the boot > partition is seperate of that raid in the first 500MB of the first > disk (ext3). Lilo runs fine. Please try to remove the spare and see if the segfault persists. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "when a gentoo admin tells me that the KISS principle is good for 'busy sysadmins', and that it's not an evolutionary step backwards, i wonder whether their tape is already running backwards." digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#524342: Problem might be related to raid metadata version
also sprach bugrep...@public-files.de [2010.10.03.1638 +0200]: > from the installation system. After that I booted into the > installation and tried to install Grub again on the MBR, but even > though I had a simple boot partition that Lilo was able to boot > from I got a segfault from both Grub-legacy and Grub-PC trying to > install those. Does the segfault go away if you let the array synchronise fully first? -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: [RFC] Dealing with mdadm superblock metadata default change
also sprach Frans Pop [2010.05.29.1756 +0200]: > But is that realistic for Squeeze? Colin Watson says Grub2 is not too badly out of shape. Upstream would be willing to introduce a compile-time flag. I think I'll go the latter path. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems obviously i was either onto something, or on something. -- larry wall on the creation of perl digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: [RFC] Dealing with mdadm superblock metadata default change
also sprach Frans Pop [2010.03.14.0811 +0100]: > > Yes, I think it should be in mdadm. It should be as easy as > > reverting > > http://git.debian.org/?p=pkg-mdadm/mdadm.git;a=commitdiff;h=7d5c3964ccfa > >ace123f7b75e15d38c2650e013d8 > > What's the status of this? Upstream has since moved the default to 1.2. I am hesitant to revert all of that. I only see three ways: 1. Ask upstream to provide a compile-time switch to keep the default at 0.9. 2. Default to 0.9 in the mdadm.conf file. 3. Expect and require the bootloaders to catch up. I prefer 3 over 1 over 2. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "what's your conceptual continuity? -- well, it should be easy to see: the crux of the bisquit is the apopstrophe!" -- frank zappa digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: [RFC] Dealing with mdadm superblock metadata default change
also sprach Frans Pop [2010.02.12.1238 +1300]: > > but I think we should make 0.9 the default for squeeze and move > > to 1.1 only afterwards, once grub-pc knows how to deal with it. > > Do you want to do that in mdadm itself, or should D-I do it? For > consistency mdadm seems more logical. Yes, I think it should be in mdadm. It should be as easy as reverting http://git.debian.org/?p=pkg-mdadm/mdadm.git;a=commitdiff;h=7d5c3964ccfaace123f7b75e15d38c2650e013d8 -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "the college students who are using lsd and marijuana today do not comprise a criminal class. they are not drug addicts seeking to escape. they're your best educated, your most creative, and your most couragious, young people. and like it or not, they might build you a new civilisation." -- porcupine tree, voyage 34 digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: [RFC] Dealing with mdadm superblock metadata default change
also sprach Frans Pop [2010.02.12.0427 +1300]: > This seems to be causing some problems. I am aware, but going to a conference right now and flying back to Europe next week, so I am unlikely going to be able to do much about it for now. > 1) offer the choice to users > I see from the Lenny mdadm man page that there are 4 (!) different metadata > versions: 0.90, 1.0, 1.1 and 1.2. > - Is there any reason to allow users to choose between those (for Squeeze)? > - If so, should all 4 versions be offered or only 0.90 and 1.2? I think they should all be offered, but I think we should make 0.9 the default for squeeze and move to 1.1 only afterwards, once grub-pc knows how to deal with it. > Main problem is that we don't know how an array will be used at > the time the choice will be made. A user may or may not create > a separate /boot partition on a regular partition. mdadm does warn about /boot on array creation btw. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "i love deadlines. i like the whooshing sound they make as they fly by." -- douglas adams digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: [RFH] Errata and announcement help need
also sprach Martin Michlmayr [2010.02.12.0107 +1300]: > /dev/md/0 doesn't exist - only /dev/md0 does. This is a common problem, and it sucks. I am going to have to work with upstream on this. Fwiw, I think that the incremental assembly in the experimental repository should get rid of this problem, but it hasn't really received a whole lot of testing. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "the difference between genius and stupidity is that genius has it's limits." -- albert einstein digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: [RFH] Errata and announcement help need
also sprach Martin Michlmayr [2010.02.11.1147 +1300]: > Actually, it seems that root on RAID made with the new mdadm > doesn't boot. I'll try to investigate soon. The problem could be #492897? Also see: http://neil.brown.name/git?p=mdadm;a=commit;h=cc86f89c855fcfe9820d0621ede1575adc317155 -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems the unix philosophy basically involves giving you enough rope to hang yourself. and then some more, just to be sure. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: [RFH] Errata and announcement help need
also sprach Martin Michlmayr [2010.02.11.0659 +1300]: > RAID won't work on machines using flash-kernel (i.e. armel) because > /dev/disk/by-uuid is not populated because of a missing udev rule in > the udeb. This is apparently fixed in the version in unstable but I'm > not sure it's safe to push that into testing. I'd say it is. I have just asked for an unblock. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems if god had meant for us to be naked, we would have been born that way. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#552560: locale selection incomplete
also sprach Frans Pop [2009.10.29.1147 +]: > But maybe it's time to drop support for non-UTF-8 locales altogether? +1, but there are people who will not like it. I think Peter Palfrader is just one of those who (pretend to) not want/need Unicode. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#552563: auto-create preseed.cfg file
also sprach Philip Hands [2009.10.29.1303 +]: > If we were to add some hints to the question templates to indicate how > relevant a question is to preseeding, along with perhaps a udeb for > asking the intent questions that are vital to an auto-install, but will > never get asked in a manual install, then we might be able to generate > a preseed.cfg that would be at least a useful starting point. I like! This sounds very Debianish. Not sure it's worth the trouble, of course, but… -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "... and so he killed Miguel in a rit of fealous jage." -- inspector clouseau digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#552560: locale selection incomplete
also sprach Frans Pop [2009.10.29.1015 +0100]: > A possible solution could be to invert the two expert questions: first ask > which extra locales to install and then offer to select a default from the > selected locales. This is precisely what locales' postinst will do. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems beware of bugs in the above code; i have only proved it correct, not tried it. -- donald e. knuth digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#552563: auto-create preseed.cfg file
also sprach Holger Levsen [2009.10.28.1121 +0100]: > On Dienstag, 27. Oktober 2009, martin f krafft wrote: > > Since debconf-get-selections is not the appropriate way to create > > preseed.cfg files, > > why not? because you think it's hackish, suboptimal or..? So says the documentation. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems above all, we should not wish to divest our existence of its rich ambiguity. --friedrich nietzsche digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#552560: locale selection incomplete
also sprach Frans Pop [2009.10.27.2305 +0100]: > You can choose en_GB if you install in expert mode (or with > priority=medium). I don't think we want to set defaults for unofficial > languages. The number of possible combinations would be insane, and its > also more a matter of personal preference than any real rule. > > As what you want is already possible, I'm closing your report. No, I can *add* the en_GB locale later. I cannot chose it as system default, and I tried expert mode. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#552560: locale selection incomplete
also sprach Christian Perrier [2009.10.28.0726 +0100]: > - write an en_CH locale and convince glibc maintainers to include it > in locales You should know me better, Christian! #552561 ;) Thanks for your other replies. It all makes sense, of course. Yes, I installed as expert. Yes, I think we can improve Debian even for experts. No, I do not expect anyone to do invasive changes for me, and no, I probably won't do them myself anytime soon — if at all. Cheers, -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "wovon man nicht sprechen kann, darüber muß man schweigen." -- wittgenstein digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#552563: auto-create preseed.cfg file
Package: debian-installer Version: 20091026-1 Severity: wishlist Usertags: debianbook Since debconf-get-selections is not the appropriate way to create preseed.cfg files, but d-i should know what keys to save (or not to save), why not extend d-i so that it automatically drops a preseed.cfg file into /root (next to the installation-report template), just in case the user is interested or would like to use that file? Thanks, -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-rc6-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#552560: locale selection incomplete
Package: debian-installer Version: 20091026-1 Severity: wishlist Usertags: debianbook I chose English/Switzerland in the language & country selection dialogs, and d-i then offered only the en_US locales. Arguably, there should be en_CH, given the international orientation of Switzerland, but while that does not exist, en_GB would be a better match for Switzerland. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-rc6-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
mdadm and udev (was: udev 146 in experimental)
also sprach Marco d'Itri [2009.08.22.1402 +0200]: > I uploaded to experimental[1] udev 146, considering the major changes I > recommend extended testing by anybody who can, especially d-i > developers. > Current status: "installs and boots in a kvm image". > > It will make mdadm uninstallable until it will be fixed to use blkid. Thanks, Marco, for the heads-up, for uploading to experimental, and for #541884. I do not see myself in the position to work on mdadm in the next weeks. NMUs (and co-maintainers) welcome. #537993 -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems time wounds all heels. -- groucho marx digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#539512: prevent running kernel warning during d-i
Package: debian-installer Severity: wishlist After d-i installs the kernel, it connects to security.d.o and possibly upgrades the kernel. This elicits a warning that the currently running kernel is the same as the new one. Maybe this warning could/should be prevented, either by preseeding it (if possible), or by adding security.d.o early enough so that the non-security kernel is not even considered? Thanks, -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-rc3-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#539502: n2100: base install fails due to time not set properly
Package: installation-reports Severity: normal The N2100 installer does not set the time properly during installation, which causes gpgv to assume all keys have expired and eventually the installation fails: in-target: WARNING: The following packages cannot be authenticated! in-target: mdadm Running apt-get update in the chroot showed this: W: GPG error: http://mirror.switch.ch lenny Release: The following signatures were invalid: KEYEXPIRED 1356982504 KEYEXPIRED 1337087218 After I set the time, I could simply re-run the base install and it all worked. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.31-rc3-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: wait for the boot device
also sprach Marco d'Itri [2009.07.20.1023 +0200]: > > 1. use --run to start arrays as soon as possible, or only start an > > array when it's completely assembled? > Why wait? If you run before it's assembled, any additional members added afterwards will have to be resynchronised. > > 2. when can we assume that the arrays are ready to be started? > When all members have appeared. Okay, so this is means *not* to use --run, but it also means that the current behaviour, which is to assemble the array if it is degraded, will no longer work. If you lose a disk and reboot, currently the array assembles fine. With the incremental approach, it would need manual interaction *or* --run, which introduced the aforementioned problem. > > 4. How do we properly deal with the device node change? What > > previously was /dev/md2 with normal assembly is now /dev/md_d2? > How do other distributions do? Either they take any sort of choice away from the user (Ubuntu), do not (seem to) have a migration path (Ubuntu, Suse), or just don't deal with it at all. > > It's not quite as easy as just deprecating udevsettle on > > a distro scale. > I am quite sure that I always discouraged the use of udevsettle by > other packages, but policy does not allow me to shoot people who > do it... I think you did. However, there was no other way to do it for mdadm until --incremental was implemented. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "zwei monologe, die sich gegenseitig immer und immer wieder störend unterbrechen, nennt man eine diskussion." -- charles tschopp digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: wait for the boot device
also sprach Marco d'Itri [2009.07.19.2309 +0200]: > > Really? So is /usr/share/initramfs-tools/scripts/local-top/mdadm > > (from the mdadm package) wrong, or something else buggy or broken by > > design? I also experienced the need for udevsettle when booting from > > LVM over partitioned multipath devices. I thought it was the kpartx > > invocation which I had to wait for before the lvm2 script. I'd be > > grateful for some advice on how to handle such cases properly. > > In an event driven model everything should happen as a reaction to a > kevent, introducing a serialization point is just a workaround for a > broken design. > Other distributions (SuSE at least) mount file systems with udev RUN > rules as a side effect of the relevant device appearing. Yeah, that sounds great, and mdadm has recently grown the bits to support that (incremental assembly). However, that does not mean that it's ready for production use or that anyone has had the time to really make it happen in Debian. The Ubuntu patch is mostly useless for Debian as it's one big lump that touches other things and introduces dependencies, and Suse did some weird udev stuff the last time I checked. Then there is udev, which is so contrary to my understanding of how Unix works that it always takes me ages to get anything done with it. Plus, udev's deprecation period wasn't very clearly communicated either, and there are no usable docs that would make a migration easier. It would be good if you could help and provide something to work of. Basically it's just calling `mdadm --incremental` for all component devices. But then there are things to work out: 1. use --run to start arrays as soon as possible, or only start an array when it's completely assembled? 2. when can we assume that the arrays are ready to be started? 3. how does the rest of the operating system find out when /dev/md0 is ready to be used? 4. How do we properly deal with the device node change? What previously was /dev/md2 with normal assembly is now /dev/md_d2? It's not quite as easy as just deprecating udevsettle on a distro scale. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "the truth is rarely pure and never simple. modern life would be very tedious if it were either, and modern literature a complete impossibility!" -- oscar wilde digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: partman-md/mdcfg merge
also sprach Colin Watson [2009.07.17.2209 +0200]: > It looks as if this is too difficult for people to test without it > being in the archive, so in the absence of objections I've gone > ahead and committed this. Let's see how it goes. I am sorry, I just couldn't. Fundamentally, there shouldn't be anything in the way of running debconf outside of d-i to test this on a running system, right? Btw, I do have a sophisticated mdadm test system with a lot of hardware that can be (ab)used for all kinds of testing. I'd be happy to hand out root access to someone who'd like to pursue the challenge to make partman-* testable outside of d-i. It's virtualised and I can always restore from snapshot. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems all software projects are done by iterative prototyping. some companies call their prototypes "releases", that's all. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: partman-md/mdcfg merge
also sprach Colin Watson [2009.07.15.1805 +0200]: > Version 4 fixes unlocking of units on array deletion. > > Anyone? Anyone? Bueller? :-) Um, he's sick. My best friend's sister's boyfriend's brother's girlfriend heard from this guy who knows this kid who's going with the girl who saw Ferris pass out at 31 Flavors last night. I guess it's pretty serious. Is it possible to test partman-md without going through an installation? I have an mdadm test system, but I don't have physical access to it right now nor a particular desire to play around with netboot remotely. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "it is only the modern that ever becomes old-fashioned." -- oscar wilde digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: unblock request: mdadm 2.6.9-3
also sprach Don Armstrong [2009.07.14.1125 +0200]: > > Hm, so the BTS pays attention to changelog stanza order (which is > > chronological) > > It's not necessarily chronological. It was in this case. > If you're uploading experimental packages, the penultimate version > should either be the preceeding experimental upload, or the > unstable version which the experimental upload is based on. If > you're uploading an unstable version, the experimental uploads > should not show up in the changelog unless the unstable version is > based upon a version which is in experimental. Serious time to start auto-generating changelogs from commit messages... -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems officer, arrest that man! he's whistling a copyrighted song. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: unblock request: mdadm 2.6.9-3
also sprach Adam D. Barratt [2009.07.14.1020 +0200]: > Not quite. It needs to be marked as /fixed/ in 2.6.9-3, rather than > "notfound". > > "notfound" simply removes the version from the list of versions in > which the bug has been explicitly marked as present; it has no effect > on the changelog parsing so 2.6.9-3 is still believed to contain the > bug. Marking it as fixed in that version isn't right since the bug > never existed there, but in this case it is the means of telling the > BTS that it shouldn't be treated as containing the bug. Done. Thanks. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "she is absolutely inadmissible into society. many a woman has a past, but I am told that she has at least a dozen, and that they all fit." -- oscar wilde digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: unblock request: mdadm 2.6.9-3
also sprach Adam D. Barratt [2009.07.13.1938 +0200]: > Looking more closely, the reason it's not migrating is that the > changelog has made the BTS believe that mdadm 2.6.9-3 is > a descendent of 3.0~devel3-1, and thus affected by #526806. Hm, so the BTS pays attention to changelog stanza order (which is chronological) without differentiating between experimental and unstable? Thanks for spotting this. I hope I fixed it now. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems there are two groups of people in the world: those who believe that the world can be divided into two groups of people, and those who don't. -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
unblock request: mdadm 2.6.9-3
Please unblock mdadm 2.6.9-3 to that I can move 3.0 into unstable. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems don't hate yourself in the morning -- sleep till noon. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
unblock request: mdadm 2.6.9-3
... has been in testing for 20 days. Should not affect d-i. mdadm (2.6.9-3) unstable; urgency=low * Fix the multipath prereq patch (#516605) and make it exit after printing the prerequisites (closes: #526793). * Change my previous recommendation for postfix over to the new virtual package default-mta (see #522300 and #508644). * Enhance bugscript, which now asks to run as root (sudo/su) if invoked by a normal user. * Include MD5 sums of md-related files in initrd in bug reports. * Add grub2 information retrieval to bugscript. * Trap SIGINT and thus prevent ctrl-c from terminating the bugscript prematurely. -- martin f. krafft Tue, 05 May 2009 11:46:22 +0200 mdadm (2.6.9-2) unstable; urgency=low * Fix the check of whether mdadm.conf defines all devices known to the system; thanks Cristian Ionescu-Idbohrn (closes: #525655). * No longer pass -k to modprobe, which has been deprecated for a long time; thanks to Jan Hudec (closes: #51). * Remove Mario Joußen from the uploaders list, since his email started bouncing. * Prepare mdadm source to use quilt, with the long-term goal to switch to TopGit, once I find the time. * Cherry-pick caa0f6c & 667e66d from Neil into a quilt patch to fix gcc-4.4 compiler issues (closes: #505375). -- martin f. krafft Sun, 26 Apr 2009 16:08:28 +0200 mdadm (2.6.9-1) unstable; urgency=low * New upstream release. * Do not set -eu in the bugscript to maximise information output in the case of errors. * Make initramfs script depend on multipath to ensure its script is run before ours (closes: #516605). * Provide an alternative (postfix) for mail-transport-agent (closes: #522300). I chose postfix because that's the only one I could recommend, and since the alternative does not affect people who already have an MTA installed, or have a preference, it won't affect them. * Honour debconf pre-selection of mdadm/initrdstart (closes: #516802). * Incorporate patch from Adrian Bridgett: the initramfs hook now checks to see if all known arrays are listed in mdadm.conf and issues a warning if this is not the case (closes: #519328). * Make checkarray skip over arrays still marked auto-read-only (closes: #510641). * Add cron.daily snippet from Paul Slootman to run one-shot scans every day to ensure that failed arrays don't go unnoticed (closes: #497949). * Bumped Standards-Version to 3.8.1; no changes necessary. -- martin f. krafft Sat, 25 Apr 2009 19:04:47 +0200 -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems it is better to have loved a short man than never to have loved a tall. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Lenny boot fails with /root in MD on LVM; patch included
also sprach Alexis Rosen [2009.05.04.1952
+0200]:
> A1 and B1 are mirrored together by md, making "md0" for use as /boot.
> A2 and B2 EACH and SEPARATELY become an LVM2 PV ("PV1" and "PV2").
> PV1 and PV2 EACH and SEPARATELY become an LVM2 LVG ("LVG1" and "LVG2").
> LVG1 and LVG2 are carved up into a bunch of LVs each.
> /root, /usr, /tmp, and /var are each formed by mirroring together 2 LVs, 1
> each from LVG1 and LVG2, becoming "md1" through "md4".
So you are running RAID on LVM. This is backwards in my world. I am
not sure we should even support that use case, but I'll leave it up
to the LVM people to decide about your patch; if they agree, I'll
include the mdadm change you propose.
Anyway...
> /home is formed by striping together 2 LVs, 1 each from LVG1 and
> LVG2, to become "md5".
[...]
> Why am I not simply using md to mirror the whole disk and then
> making LVM volumes on top of that? Because I don't want the whole
> thing mirrored. /home needs to be striped.
Why don't you then put the main system on LVM-over-RAID on
partitions 2 and use partitions 3 as a /home strip set? You might
argue that you want full flexibility to move space between the
different filesystems, but realistically speaking, /, /usr, and
/boot are mostly fixed in size. Put those on LVM-over-RAID (or just
pure RAID) and then use the rest for stripe sets or whatever else
you might need to accomodate /home and /var.
> The heart of the problem, I think, is that there's no easy way to
> figure out which /dev/mdNs need to be up before which LVs, and
> vice-versa. You could have mdN inside an LV inside another mdN
> (and so on).
Exact analysis, this is in fact the heart of the problem. But as
you say yourself, without a dependency graph, we cannot properly
cater to the situation. I am not sure whether this complexity would
be justified, given that I would never suggest anyone to run RAID
off non-physical devices, unless you are doing testing and/or are
prepared to deal with the pain.
But as I said above, if the LVM folks think your patch is sensible,
I won't object. If I feel belligerent, I might throw in a pinch of
cryptsetup though. "My LVM on RAID on encrypted LVM doesn't work!"
> Do I need to send this patch somewhere else to have it considered?
File a bug against LVM and put me on X-Debbugs-Cc. If they fix it,
I'll add the prerequisite to mdadm.
Thanks,
--
.''`. martin f. krafft Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
"we should have a volleyballocracy.
we elect a six-pack of presidents.
each one serves until they screw up,
at which point they rotate."
-- dennis miller
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
mdadm 2.6.7.2-1 uploaded, please unblock
Following my recent call for testers, I've had 7 positive and 0 negative reports, so I've uploaded mdadm 2.6.7.2-1 to unstable, which should hopefully take care of those RC bugs once and for all. The new version should not have any effect on the operation within D-I at all. Please unblock. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "i wish i hadn't slept all day, it's really lowered my productivity" -- robert mcqueen digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#505111: Proposed (naive) patch for mdadm RAID auto-assembly in rescue mode
also sprach Jérémy Bobbio <[EMAIL PROTECTED]> [2008.11.30.1613 +]: > One of the main usage for the installer rescue mode for now is to > easily fix a broken bootloader configuration or other packages > which might prevent the system from booting. The auto-assembly of > RAID arrays easily allow such usage for systems using RAID. This is why I provided /usr/share/mdadm/startall to do that if the user so desires. In my case, calling it would have caused the same problems, but I wouldn't have even thought about calling it. :) I agree that fixing this would endanger RC2, especially since I don't have a true solution. However, documenting this would basically require us to say "refrain from the use of rescue mode to heal RAID problems." -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Proposed updated errata file for D-I upcoming RC2
also sprach Christian Perrier <[EMAIL PROTECTED]> [2008.11.30.1033 +]: > Martin: same request for the RAID auto-assembling in rescue. Would it be much trouble to add a boot option with which the auto-assembly could be disabled on a case-by-case basis? Anyway, I suggest a slightly different formulation: --- errata-new.wml.orig 2008-12-01 10:56:07.0 + +++ errata-new.wml 2008-12-01 10:56:01.0 + @@ -13,10 +13,10 @@ Auto-assembly of RAID arrays in rescue mode can corrupt data - The rescue mode should be used with great care when logical RAID + Rescue mode should be used with great care when software RAID arrays were in use on the system to rescue. The rescue mode scripts -do arrays auto-assembly, which could lead to data corruption in -case the RAID IDs are invalid. +automatically assemble arrays, which could lead to data corruption in +the presence of invalid or obsolete RAID superblocks. Corrupted display of messages in Dzongkha installs -- .''`. martin f. krafft <[EMAIL PROTECTED]> Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems "auch der mutigste von uns hat nur selten den mut zu dem, was er eigentlich weiß." - friedrich nietzsche digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#505111: reassign to proper package
reassign 505111 rescue
thanks
RAID auto-assembly may be desirable from the installer. But for
a rescue image, it's definitely a bad idea ("rescue" and anything
"auto" just don't go together). In my case, it caused data loss,
which was unexpected since I was booting a "rescue" image, which
gives the strong indication that it's there to help you, but no
more.
mdadm's auto-assembly, the way it works in the rescue postinst, is
too fragile to be used on systems that may not be properly
configured. Those are the systems where one boots rescue images
though.
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#505113: rescue-mode requires a root filesystem to be useful
Package: rescue Version: 20081029 Severity: normal In trying to rescue my system, which had a screwed up RAID/LVM configuration (#505111), I gave the d-i rescue image a shot. I tried to install the cfdisk and network-console components, but d-i wouldn't let me unless I told it where my root filesystem was. Unfortunately, I could not answer that question, since I first had to rescue the root filesystem. As a whole, rescue mode was completely unhelpful. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#505111: rescue-mode md auto-assembly could cause data loss
Package: debian-installer
Version: 20081029
Severity: grave
I have a system with /dev/sd{a1,b2} and /dev/sd{a2,b3} being two
separate RAID1s, /dev/md[01] respectively.
Due to historic reasons, /dev/sdb1 is a small partition with
something else.
Also, historically, /dev/sd[ab] used to be part of an array
themselves (the whole disk, not just a partition). As a result,
mdadm could identify three arrays on this system:
1. /dev/sd[ab]
2. /dev/sd{a1,b2}
3. /dev/sd{a2,b3}
I wanted to run mdadm --zero-superblock on /dev/sd[ab] to clear up
the mess and because I have a working netboot setup, I thought I'd
just use the Debian-installer's rescue mode to get exclusive access
to the disks, which mdadm needs.
I started rescue mode and was surprised that only /dev/sd[ab] were
created, but no partitions. A glance into /proc/mdstat shows that
the installer had auto-assembled /dev/sd[ab] into /dev/md0 and md
was happily synchronising and overwriting my /dev/sdb1 partition.
Arguably, since /dev/sd[ab] held valid superblocks, they could have
been assembled. However, the other two pairs also held valid
superblocks, yet the installer didn't care.
I strongly oppose to any form of RAID auto-assembly in rescue mode,
which is only a sure-fire way to wreck your data. Auto-assemble
should not take place especially when there are nested superblocks.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://debiansystem.info
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#505000: Transtec Calleo 331: Install OK, volatile not added to sources.list
Package: installation-reports Boot method: netboot amd64 Image version: 20081029 Date: 8 Nov 2008 Machine: Transtec Calleo 331 Partitions: /dev/sd[abcd] identical: # partition table of /dev/sda unit: sectors /dev/sda1 : start= 63, size= 497952, Id=fd, bootable /dev/sda2 : start= 498015, size=1953022050, Id=fd /dev/sda3 : start=0, size=0, Id= 0 /dev/sda4 : start=0, size=0, Id= 0 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[E] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [ ] Install boot loader:[O] Overall install:[O] Comments/Problems: I selected volatile.debian.org during package manager configuration, but the resulting sources.list did not include it. Everything else worked like a charm. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems report-hw.dump.bz2 Description: Binary data digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#499934: software-raid, full encrypted system, lvm
also sprach Matthias Köhne <[EMAIL PROTECTED]> [2008.09.23.2051 +0200]: > Is it necessary to resync the new raid _at_ the installation? It > took more than 12 hours to check my software-raid. > > Sep 20 20:41:43 mdcfg: mdadm: array /dev/md2 started. > Sep 21 08:54:00 kernel: [50499.929621] md: md2: resync done. > > (Normally I don't wait at the installation until the raid resync is done.) You don't have to. Just go on doing what you are doing. http://www.spinics.net/lists/raid/msg14089.html has more information on this topic. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#497223: Package: installation-reports
also sprach Jérémy Bobbio <[EMAIL PROTECTED]> [2008.09.01.1458 +0100]: > > While the md devices were creating & formatting inside the installer, > > the seemingly long delays left me wondering if the installation was > > going to hang. A message informing a user that these steps could take a > > while might ease concern. What seemingly long delay? Creation should be quick, and the formatting should take as long as with any other filesystem. Please be a lot more precise with your reports. > > After installation, "cat /proc/mdstat" showed md1 : active(auto-read-only). > > Had to issue "sudo mdadm --readwrite /dev/md1" to correct. It will turn off auto-read-only as soon as you write to it. > > md1 is not listed in mount output. Is it maybe your swap? > > gparted (GUI) does not recognize all partitions correctly and > > lists several of them as 'unknown'.\ > > > > fdisk -l complained of invalid partitions (listed above). Which ones? Also note that /dev/md* are not partitions. > > Not 100% confident these arrays are safe for data. They seem fine. You provide very little information and expect us to read between lines or to ask questions. This steals a lot of time. Please try in the future to provide everything that's relevant. For instance, you claim that "md1 is not listed in mount output" but you don't show us the mount output or /etc/fstab. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "friendships last when each friend thinks he has a slight superiority over the other." -- honoré de balzac digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#462617: [patch 3/4] fastboot: make the raid autodetect code wait for all devices to init
[EMAIL PROTECTED] added to Cc] also sprach Neil Brown <[EMAIL PROTECTED]> [2008.07.22.0124 +0200]: > > It was my understanding that write-intent bitmaps slow down all > > operations and are not suggested on e.g. workstations. No? > > Well, they don't slow down reads. > If you have a separate root filesystem (i.e. /home and /var are > elsewhere), it is likely to be read-mostly, so bitmaps probably won't > hurt much. > And an external bitmap on a dedicated device has minimal performance > cost. > > However I neither suggest having nor not-having bitmaps. The choice to > use them involves a trade-off which I cannot make for other people. Ok, in the light of http://bugs.debian.org/462617, this answers my question and Debian will not make them default. It would be nice to have the option though, during installation. Including the rest of your reply for the sake of the bug record, which is on Cc: > They would, however, be very useful to cover the gap when assembling > arrays incrementally. > If, for example, you have a 6 disk raid5 array and 5 disks have been > found, what do you do? > - wait for the 6th, that might never arrive > - start degraded and if a write happens before the 6th disk arrives, > have to rebuild the 6th disk completely. > > Neither is a good option. > An alternate is > - add an internal bitmap, and remove it after the 6th disk has > arrived, or after we are sure there are no more disks to find. > > Doing this means that if a recovery is needed when the 6th disk > arrives, it will be very fast. > > It's not hard to notice that the bitmap proposed here does not need to > be on stable storage. It is not protecting against a crash, just > against a window when the array is degraded. So if we could support > bitmaps on a tmpfs, we could use an external bitmap in /tmp instead of > an internal bitmap. > Or even - we could enhance the md code to always use a bitmap, but > simply not write it to storage if no such was configured. This would be very nice. In fact, everything that makes md better and requires less complexity in the mdadm packaging is nice. :) > (If a crash happens during that window between writing to the degraded > array and recovering the few blocks needed on the final device, then > you would be in an unfortunate position. For raid1/10 you would just > need a full resync, which you would have needed anyway, so no loss. > For raid4/5/6, you have a potential for dataloss, so I probably would > not make this behaviour the default for those levels...) -- martin | http://madduck.net/ | http://two.sentenc.es/ drink canada dry! you might not succeed, but it *is* fun trying. spamtraps: [EMAIL PROTECTED] digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: [PATCH] RAID10 and RAID6
also sprach Ryan Niebur <[EMAIL PROTECTED]> [2008.07.17.2137 +0200]: > Here is a patch that adds support for RAID6 and RAID10 to the > debian installer. Wow! Thanks! > +_Description: Number of active devices for the RAID6 array: > + The RAID6 array will consist of both active and spare partitions. The active > + partitions are those used, while the spare devices will only be used if one > or > + more of the active devices fail. A minimum of three active devices is > + required. I think it's four, isn't it? > + NOTE: this setting cannot be changed later. It can, but not trivially. > +Template: mdcfg/raid10devcount > +Type: string > +# :sl3: > +_Description: Number of active devices for the RAID10 array: > + The RAID10 array will consist of both active and spare partitions. The > active > + partitions are those used, while the spare devices will only be used if one > or > + more of the active devices fail. A minimum of four active devices is > + required. You can have RAID10 across two devices, although it makes no sense, really. I haven't had time to look at your patch in depth, but it's looking good. Unfortunately it's probably too late for lenny... -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "let me take you down, 'cause i'm going to strawberry fields. nothing is real and nothing to get hungabout. strawberry fields forever." -- the beatles digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Bug report: installer messed up mdadm.conf
also sprach Tito <[EMAIL PROTECTED]> [2008.05.07.2027 +0100]: > 1) using the script in /usr/share/mdadm/mkconf (which uses mdadm --examine > --scan --config=partitions) i get > > # definitions of existing MD arrays > ARRAY /dev/md2 level=raid1 num-devices=2 > UUID=95261952:6a58368f:9d4deba6:47ca997f > ARRAY /dev/md0 level=raid1 num-devices=4 > UUID=2928f68e:5d9adc5b:3fbebe5a:bce56b15 > ARRAY /dev/md1 level=raid1 num-devices=2 > UUID=e16b4bf9:f0dbce60:04894333:532a878b spares=2 > ARRAY /dev/md1 level=raid5 num-devices=3 > UUID=fd0b1c0e:f10deae6:11c6bfd4:055cd56a spares=1 This means that mdadm found two devices (or partitions) with superblocks that set super-minor=1, thus /dev/md1. You probably want to find the device/partition which defines the unwanted array and call --zero-superblock on it, after making sure you know what you're doing. > 2) while with mdadm --detail --scan i get: This actually inspects only arrays which are assembled. Therefore, it's logical you don't find the /dev/md1 raid1. > So seems that i did something stupid (forgot to delete an array?) > that i don't know how to fix at the moment. :-( You can try mdadm -Esvcpartitions and see which devices have the unwanted superblock, then zero it on each. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems god is real, unless declared integer. (dedicated to gabriel gómez) digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Please explain status/background of /dev/mdX versus /dev/md/X
also sprach Neil Brown <[EMAIL PROTECTED]> [2008.04.28.0857 +0200]: > I would like to make mdadm work equally well with both usages, and let > system-integrators make the decisions :-) > So anything I can do to make mdadm work more nicely for you I will > seriously consider. > > --use-dev-subdir ??? Well, an mdadm.conf entry would be easier to work with, probably best together with such an option. Is there any reason why we don't just make it default? As you said, /dev/mdX works just as well, but that doesn't mean that mdadm needs to support it. We'd need a migration strategy though... -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems unix, because rebooting is for adding new hardware. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#477648: Bug in debian-archive-keyring
See #476689 and feel free to merge, or block by, at your discretion. Sorry for not checking around; I was doing all this work offline and thus didn't have BTS access. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#477648: gpg not installed, fails [i386 on amd64]
retitle 477648 gpg not installed, fails severity 477648 grave found 477648 1.0.8 thanks This also happens when I create a sid chroot on i386, and with debootstrap in sid. #477765 might be related. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#477648: gpg not installed, fails [i386 on amd64]
Package: debootstrap Version: 0.3.3.2etch1 Severity: normal On etch: debootstrap --variant=buildd --arch i386 sid `pwd`/sid-i386 ... fails on amd64 because gnupg does not get installed. /usr/bin/apt-key: line 24: gpg: command not found Adding --include=gnupg to the command fixes that. The problem does not happen when I set up an amd64 chroot on amd64 (not using --arch). System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.24-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages debootstrap depends on: ii binutils2.18.1~cvs20080103-4 The GNU assembler, linker and bina ii wget1.11.1-1 retrieves files from the web debootstrap recommends no packages. -- no debconf information -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Please explain status/background of /dev/mdX versus /dev/md/X
also sprach Frans Pop <[EMAIL PROTECTED]> [2008.04.22.1843 +0200]: > I suspect that should have read /dev/md$MD_NUM. Of course. :) -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "perhaps debian is concerned more about technical excellence rather than ease of use by breaking software. in the former we may excel. in the latter we have to concede the field to microsoft. guess where i want to go today?" -- manoj srivastava digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Please explain status/background of /dev/mdX versus /dev/md/X
also sprach Frans Pop <[EMAIL PROTECTED]> [2008.04.22.1820 +0200]: > What's responsible for creating them: udev or mdadm itself? mdadm. > We do. The superblock is version-0, but mdcfg does use /dev/md/X (and has > done since its original upload in 2004). > > What we do for new RAID devices is: > mdadm --create /dev/md/$MD_NUM --auto=yes --force -R -l That's the problem. You should be able to change that to md/$MD_NUM and then just use mdX everywhere without much trouble. You can control the creation mode with mdadm.conf like this: CREATE owner=root group=disk mode=0660 > > But in any case, mdadm should not create /dev/md/X files if you tell > > it to create /dev/mdX instead (passing --auto=yes). > > Sure, but it does when the above call is used, or when you have >ARRAY /dev/md/X ... > in the config file. Yes. That's expected, although probably not desirable or sensible or whatever... > It seems that maybe we should currently not be using /dev/md/X at all in the > installer. Especially since the installed system will probably also _not_ > have them since it creates a new config file based on output of > 'mdadm --detail --scan'... > > What do you think? Yes, I think /dev/mdX for now should do. In the long-run, /dev/md/* might be cleaner. However, to get there, it has to be default, and when it is, I have to provide a migration path. Yay! -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "the scientific paper in its orthodox form does embody a totally mistaken conception, even a travesty, of the nature of scientific thought." -- sir peter medawar digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Please explain status/background of /dev/mdX versus /dev/md/X
Frans, all I know is documented in http://git.debian.org/?p=pkg-mdadm/mdadm.git;a=blob;f=debian/FAQ, item 3. Anything else, Neil (on Cc) will have to explain... full mail further down, with more inline comments from me. also sprach Frans Pop <[EMAIL PROTECTED]> [2008.04.22.1725 +0200]: > Hi Martin, > > Over the past few weeks I've solved several issues in D-I related to the use > of /dev/mdX versus /dev/md/X and I've been wondering what the official > status is of both as it seems there are at least some inconsistencies. > > Partman currently prefers the use of /dev/md/X and uses that when creating > new RAID devices. This results in both /dev/md/X and /dev/mdX block device > files being created. The latter should be symlinks. > I've been working on the assumption that /dev/md/X is the "newer" form and > that the intention is to transition to that. Is that correct? Sort of. /dev/md/* corresponds to version-1 superblocks, which are supposed to be default in the future, but still are not. I suggest you ensure that partman creates version-0 superblocks for now, until upstream changes the default. But in any case, mdadm should not create /dev/md/X files if you tell it to create /dev/mdX instead (passing --auto=yes). > Here are some of the inconsistencies I've noticed: > - /dev/mdX and /dev/md/X are created with different permissions This is weird. All I've ever seen were /dev/mdX symlinks to /dev/md/X. Are you sure those are created by the same process? > - if a new RAID device is created using /dev/mdX, the "new" block device > files are _not_ created > - 'mdadm --examine --scan --config=partitions' outputs the "old" block > device names which again means that the "new" block devices are not > created if that is used as input to assemble existing RAID devices > > Especially the last issue affected partman when the system being installed > had a pre-existing RAID partition setup. I've now worked around that in > mdcfg by converting old to new using sed before doing the assemble. > > Could you provide some insight into what the current status is from an mdadm > (and maybe kernel) upstream PoV and how the transition is expected to > proceed? Neil? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "i feel sorry for people who don't drink. when they wake up in the morning, that's as good as they're going to feel all day." -- frank sinatra digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: RAID size mismatch
also sprach Ferenc Wagner <[EMAIL PROTECTED]> [2008.04.07.0111 +0200]: > After this partman presents me with the following menu items: > > 6. RAID1 device #0 - 8.3 MB Software RAID device > 7. > #1 4.2 MB > > What are those two different sizes? What does fdisk or cfdisk say? Do they also only see half the space? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "a compliment is like a kiss through a veil." -- victor hugo digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#462617: debian-installer: need RAID bitmap support (mdadm -b internal)
also sprach Otavio Salvador <[EMAIL PROTECTED]> [2008.01.26.1834 +0700]: > Please Martin, could you comment on that? I have: http://lists.debian.org/debian-devel/2008/01/msg00929.html -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems save the plankton - eat a whale. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
unblock mdadm/2.6.3+200709292116+4450e59-3
subject says it all; please. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems la lune, c'est comme les canards il faut aimer caresser les chats pour avoir envie d'y aller. digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#426943: *_crypt naming causes df to line-wrap
also sprach David Härdeman <[EMAIL PROTECTED]> [2007.06.01.1347 +0200]: > I'm not sure what the point is...is it merely cosmetic? Yes, merely cosmetic. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#426943: *_crypt naming causes df to line-wrap
Package: partman-crypto Severity: wishlist The naming of crypto devices as hda1_crypt causes df to use two lines for each filesystem. Please consider using just cr_hda1 instead. -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.20-1-amd64 (SMP w/1 CPU core) Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#417407: debian-installer: d-i destroyed existing raid device
also sprach martin f krafft <[EMAIL PROTECTED]> [2007.04.03.1028 +0200]: > After the mount, both of sd[ab]1 would have to be recovered and > usable, but out of sync. Actually, as Sesse claims, it's entirely likely that md didn't think the partitions were out of sync. That would explain some pretty bad data screwage. But an empty filesystem? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#417407: debian-installer: d-i destroyed existing raid device
also sprach Jim Paris <[EMAIL PROTECTED]> [2007.04.02.2345 +0200]: > If those two disks were part of a RAID mirror and they were > written to individually, they could end up inconsistent, which may > have caused problems with the RAID later? Absolutely. Now we need to figure out how to get from here to an empty data partition. After the mount, both of sd[ab]1 would have to be recovered and usable, but out of sync. So when the raid was force-reassembled, md would sync the older from the newer. This should, in my book, result in a valid and full filesystem. I would assume that the fsck -b run then somehow screwed up the data. Maybe it's even a bug in fsck -b. And the other question of course is why the kernel decided it had any business doing recovery on an fs that was marked for ro mount. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#417407: debian-installer: d-i destroyed existing raid device
also sprach Peter Nuttall <[EMAIL PROTECTED]> [2007.04.03.0020 +0200]: > mdadm --assemble /dev/md0 works, as does your command above. The > array is fine after resyncing, its just its contents that are > gone. I honestly have no idea what could have gone wrong. Can you check whether the array's UUID (mdadm -D /dev/md0) was changed or whether it's still the same as before the disaster? /etc/mdadm/mdadm.conf should list it. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#417407: debian-installer: d-i destroyed existing raid device
Can you force-start the degraded array, using something like mdadm --assemble --auto=yes --force /dev/md0 /dev/sd[ab]1 mdadm --run /dev/md0 ? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#417407: debian-installer: d-i destroyed existing raid device
also sprach Peter Nuttall <[EMAIL PROTECTED]> [2007.04.02.1833 +0200]: > If you have any questions, or I can help further, please ask. I'm psn on > oftc. Any suggestions as to what I did wrong or how to recover would be > really nice. Please also pass the output of /usr/share/bug/mdadm/script 3>&1 run as root. Note that RAID superblocks and fsck -b have nothing to do with each other. Do you have backups? Did you do anything else to the partitions? What does mdadm -E output for /dev/sd[ab]1 ? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#403240: installation-report: raid1 and lvm as root-fs doesn't work with d-i: not fully bootable
also sprach Johannes Wiedersich <[EMAIL PROTECTED]> [2006.12.15.1845 +0100]: > On reboot the kernel booted partially, leading to a busybox > console. I don't know how I could have proceeded from there, so > I restarted installation and put root and swap on partitions Did you get any additional information about why the RAID didn't start? Could you reproduce the problem? I can try to do so next week, but I am not sure I'll manage as I am too busy these days. If you reproduce, please share the contents of /conf/md.conf from within the busybox shell with me. Thanks, -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#398464: root on ext3 over lvm over dm-crypt over raid 1 fails to boot
reassign 398464 cryptsetup thanks also sprach Mario Schubert <[EMAIL PROTECTED]> [2006.11.13.2314 +0100]: > device-mapper: ... initialised ... > Volume group "vg0" not found > No cryptroot configured, skipping cryptroot is defined to run after lvm, for whatever reason. The cryptsetup people can probably tell you why and suggest a fix. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#393893: More info
tags 393893 moreinfo owner 393893 ! thanks Please provide more information. It would help if you could attach your /etc/mdadm/mdadm.conf file and also the output of /usr/share/bug/mdadm/script 3>&1 Thanks, -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#251898: Fwd: Re: avoiding the initial resync on --create
I guess this is a no to skip the inital sync. Included for completeness: - Forwarded message from Neil Brown <[EMAIL PROTECTED]> - There is no real need to perform the sync of a raid1 at creation. However it seems to be a good idea to regularly 'check' an array to make sure that all blocks on all disks get read to find sleeping bad blocks early. If you didn't sync first, then every check will find lots of errors. Ofcourse you could 'repair' instead of 'check'. Or do that once. Or something. --> checkarray, which runs regularly, would go berserk. For raid6 it is also safe to not sync first, though with the same caveat as raid1. Raid6 always updates parity by reading all blocks in the stripe that aren't known and calculating P and Q. So the first write to a stripe will make P and Q correct for that stripe. This is current behaviour. I don't think I can guarantee it will never changed. For raid5 it is NOT safe to skip the initial sync. It is possible for all updates to be "read-modify-write" updates which assume the parity is correct. If it is wrong, it stays wrong. Then when you lose a drive, the parity blocks are wrong so the data you recover using them is wrong. In summary, it is safe to use --assume-clean on a raid1 or raid1o, though I would recommend a "repair" before too long. For other raid levels it is best avoided. - End forwarded message - -- martin; (greetings from the heart of the sun.) \ echo mailto: !#^."<*>"|tr "<*> mailto:"; [EMAIL PROTECTED] spamtraps: [EMAIL PROTECTED] "man kann die menschen nur von ihren eigenen meinungen überzeugen." -- charles tschopp signature.asc Description: Digital signature (GPG/PGP)
Bug#392042: it *could*
mdadm can create partitionable arrays, but has to be specifically told. I am not sure whether it's worth the extra trouble actually. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#369747: (no subject)
retitle 369747 please add support for levels 6 and 10 thanks RAID6 and RAID10 would be nice to have. With RAID10, an additional configuration option for the layout needs to be added. -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems signature.asc Description: Digital signature (GPG/PGP)
Bug#251898: (no subject)
submitter 251898 [EMAIL PROTECTED] thanks Wolfgang, I cannot imagine how partman would hang due to the resync of RAIDs. Can you please try to reproduce this problem? -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems "in any hierarchy, each individual rises to his own level of incompetence, and then remains there." -- murphy (after dr. laurence j. peter) signature.asc Description: Digital signature (GPG/PGP)
