Bug#806718: Additional hints
In the meantime, I also observed such endless "A start job is running for ..." and the moving red asterix with another Linux distribution (for interests: This happened with CentOS's boot CD, but the network installer CD only). So I suppose a typical systemd problem where too many start processes run in parallel which better should run sequentially. If somebody can explain me how to change this behavior (beware: all steps must be done from the emergence environment!) I will give a try for it. Andreas -- Andreas Meile Hauptstrasse 63 CH-8242 Hofen SH Tel. +41 52 640 04 72 * i...@andreas-meile.ch smime.p7s Description: S/MIME cryptographic signature
Bug#806718: Additional details (Test with 7/Wheezy and 9/Stretch, upgrading from Wheezy to Jessie)
In the meantime, I also made some additional tests about this issue. Jessie with default partitioning: I completely wiped out the MBR with zeros and allowed the installer to use a default partition layout. Result is exactly the same, i.e. the "A start job is running for dev-mapper-isw_djiacbdbae_VolLxDebx device". I extracted the "journalctl -xb" output at http://beilagen.dreael.ch/Diverses/Details_Debian_8_Jessie_20151130/journalctl.txt For completeness, I also tested the new Debian 9 Stretch release on the same hardware and same configuration. Results and details see http://beilagen.dreael.ch/Diverses/Details_Debian_9_Stretch_20151207/ i.e. installation works fine but the first boot fails with exactly the same behaviour. I then made a third test with Debian 7 Wheezy (the oldstable distribution): There I got my system working successfully but I had to do the following corrections: /etc/fstab: There is an extra "p" which must be removed, i.e. /dev/mapper/isw_djiacbdbae_VolLxDebp1 / ext4 errors=remount-ro 0 1 /dev/mapper/isw_djiacbdbae_VolLxDebp9 /home ext4defaults 0 2 /dev/mapper/isw_djiacbdbae_VolLxDebp8 /tmpext4defaults 0 2 /dev/mapper/isw_djiacbdbae_VolLxDebp5 /usrext4defaults 0 2 /dev/mapper/isw_djiacbdbae_VolLxDebp6 /varext4defaults 0 2 must be changed into /dev/mapper/isw_djiacbdbae_VolLxDeb1 / ext4 errors=remount-ro 0 1 /dev/mapper/isw_djiacbdbae_VolLxDeb9 /home ext4defaults 0 2 /dev/mapper/isw_djiacbdbae_VolLxDeb8 /tmpext4defaults 0 2 /dev/mapper/isw_djiacbdbae_VolLxDeb5 /usrext4defaults 0 2 /dev/mapper/isw_djiacbdbae_VolLxDeb6 /varext4defaults 0 2 And of course, modifying /etc/default/grub (enabling GRUB_DISABLE_LINUX_UUID=true) and "update-grub" is also necessary from the emergency system to get the system booting successfully. Then I tried out a dist-upgrade from 7 (Wheezy) to 8 (Jessie). Result: The "apt-get dist-upgrade" step will fail with a Fehler traten auf beim Bearbeiten von: /var/cache/apt/archives/linux-image-3.16.0-4-amd64_3.16.7-ckt11-1+deb8u6_amd64.debE: Sub-process /usr/bin/dpkg returned an error code (1)Complete details seehttp://beilagen.dreael.ch/Diverses/Details_Debian_7to8_Upgrade_20151207/The complete upgrade process is documented inUpgrading_Wheezy2Jessie_x64_ThinkCentreM57_fakeraid.txtA reboot results in a kernel panic (P1330209_KernelPanic_Deb7to8.JPG) => Invar_log_komplett.tgz I collected all logs for deep analysis before.Conclusion: There must be a general problem with dmraid affecting all newerversions based on systemd. Andreas--meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SHPC/Netzwerk-Support, Web-Entwicklung und -HostingTel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
Bug#806718: [Jessie/stable/amd64] dmraid issues on Lenovo ThinkCentre M57 (Intel Matrix Storage)
Package: dmraid (or other?) Version: (current in Debian 8 Jessie/amd64/dpkg -l not possible in emergency shell) Severity: important Full details see http://beilagen.dreael.ch/Diverses/Details_Debian_8_Jessie_20151130/ First problem is the "module dm-raid45 not found in modules.dep" (P1330002_BUG_dmraid_issue.JPG). This problem is minor only since I got rid it using the GRUB_DISABLE_LINUX_UUID=true in /etc/default/grub paramter (see bug report #699437). The actual problem is shown in P1330009_boot_failure_after_disabling_UUID_in_Grub.JPG Before this happens, a task "A start job is running for dev-mapper-isw_djiacbdbae_VolLxDeb device s / 1min 30s" is running first for 90 sec. I made a video from the complete boot process, watch it at https://www.youtube.com/watch?v=DcwKr24NiSI (the yellow error messages appearing at 2:06 may be interesting) At http://beilagen.dreael.ch/Diverses/Details_Debian_8_Jessie_20151130/dmesg.txt I also was able to extract the "dmesg" details from this emergency root shell. Used hardware is a Lenovo ThinkCentre M57 (type 6075-BQG, latest BIOS update applied) with two SATA hard (Western Digital Caviar Red 1 TB NAS) drives configured as RAID-1 volume with the BIOS built-in RAID functionality. I hope this helps to fix the problem. Andreas -- meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH PC/Netzwerk-Support, Web-Entwicklung und -Hosting Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67 Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
Bug#775108: samba: reverse DNS registration / creating associated PTR not working
Package: samba Version: 2:4.1.13+dfsg-2 Severity: important Dear Maintainer, I set up a Samba 4 DC using apt-get install samba and then samba-tool domain provision using SAMBA_INTERNAL - this worked fine. To enable reverse DNS I use a samba-tool dns zonecreate localhost 0.1.10.in-addr.arpa -U Administrator which successfully creates a reverse DNS zone for my test network. The problem: Dynamically registered domain member don't register the PTR record, only the forward DNS record is updated. See details at http://beilagen.dreael.ch/Diverses/Debian_8_Jessie_20150111_Samba_Reverse_DNS/ Create_forward_DNS.png: Even when set Create assocatiated pointer (PTR) record, the PTR is _not_ created as shown at Reverse_entry_test123_missing.png Only when explicitely creating a PTR (Make_reverse_entry_explicitely.png) using Browse (Make_reverse_entry_explicitely_using_Browse.png), then I get the necessary PTRs as shown in Make_reverse_entry_explicitely_visible.png To consider: In a original Microsoft ActiveDirectory environment, any host is automatically registering as PTR as soon as the reverse DNS zone has been created on the AD's DNS server(s). -- System Information: Debian Release: 8.0 APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages samba depends on: ii adduser 3.113+nmu3 ii dpkg 1.17.23 ii libasn1-8-heimdal1.6~rc2+dfsg-8+b1 ii libbsd0 0.7.0-2 ii libc62.19-13 ii libcomerr2 1.42.12-1 ii libhdb9-heimdal [heimdal-hdb-api-8] 1.6~rc2+dfsg-8+b1 ii libkdc2-heimdal 1.6~rc2+dfsg-8+b1 ii libkrb5-26-heimdal 1.6~rc2+dfsg-8+b1 ii libldb1 1:1.1.17-1 ii libpam-modules 1.1.8-3.1 ii libpam-runtime 1.1.8-3.1 ii libpopt0 1.16-10 ii libpython2.7 2.7.8-11 ii libroken18-heimdal 1.6~rc2+dfsg-8+b1 ii libtalloc2 2.1.1-2 ii libtdb1 1.3.1-1 ii libtevent0 0.9.21-1 ii lsb-base 4.1+Debian13+nmu1 ii multiarch-support2.19-13 ii procps 2:3.3.9-8 ii python 2.7.8-2 ii python-dnspython 1.12.0-1 ii python-ntdb 1.0-5 ii python-samba 2:4.1.13+dfsg-2 pn python2.7:anynone ii samba-common 2:4.1.13+dfsg-2 ii samba-common-bin 2:4.1.13+dfsg-2 ii samba-dsdb-modules 2:4.1.13+dfsg-2 ii samba-libs 2:4.1.13+dfsg-2 ii tdb-tools1.3.1-1 ii update-inetd 4.43 Versions of packages samba recommends: ii attr 1:2.4.47-2 ii logrotate 3.8.7-1+b1 ii samba-vfs-modules 2:4.1.13+dfsg-2 Versions of packages samba suggests: pn bind9 none pn bind9utils none pn ctdb none pn ldb-tools none ii ntp1:4.2.6.p5+dfsg-3.2 pn smbldap-tools none pn winbindnone -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#774131: Missing kernel modules (mini.iso / Jessie / amd64)
Package: Installer (mini.iso) Version: 02-Oct-2014 09:01 (Jessie) Severity: important When I try to install a Debian testing version using http://ftp.ch.debian.org/debian/dists/testing/main/installer-amd64/current/images/netboot/mini.iso I always get an error message about missing kernel modules as shown at http://beilagen.dreael.ch/Diverses/Details_Debian_8_Jessie_29141229/Jessie_mini_iso_Fehler_Kernelversion.png When I try to continue without kernel modules then the setup process cannot continued on the installation target selection: http://beilagen.dreael.ch/Diverses/Details_Debian_8_Jessie_29141229/Jessie_mini_iso_Folgefehler_keine_HD.png This error still appears when using a primary mirror as installation source. I believe there was done a kernel version change in the meantime without updating mini.iso accordingly so simply recompose mini.iso would fix this issue. Note: uname -a reports 3.16-2-amd64 as kernel version. Andreas -- meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH PC/Netzwerk-Support, Web-Entwicklung und -Hosting Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67 Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
Bug#774131: Missing kernel modules (mini.iso / Jessie / amd64)
Hello Ben You're using an old netboot image and this failure is expected. Thanks for your reply. I exactly supposed the same issue (obsoleted mini.iso). The actual problem is not a developement issue, it's an issue that some folders on the official FTP sources are not updated. For example the folder http://mirror.switch.ch/ftp/mirror/debian/dists/testing/main/installer-amd64/current/images/netboot/ (same on any other mirror) still contains the obsolete mini.iso Note: Two years ago when Squeeze was the current stable release and Wheezy was the testing release, I always found an updated mini.iso so probably something is wrong in the FTP server update process concerning the testing release. Current temporary workaround by myself: https://www.debian.org/devel/debian-installer/ points to the larger netinst files which seem to work correctly. Thanks for forwarding this to those guys who manage the FTP repository. Andreas -- meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH PC/Netzwerk-Support, Web-Entwicklung und -Hosting Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67 Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
Bug#732675: pure-ftpd: invalid PTR hostnames without corresponding A/AAAA forward entry in logfile
Package: pure-ftpd Version: 1.0.36-1.1 Severity: normal Dear Maintainer, During a security incident with a compromised FTP account I needed to lookup the IP address inside the /var/log/messages log file. Issue: When the foreign host has set bad DNS entries, for example $ORIGIN 2.0.192.in-addr.arpa. 45 IN PTR customer.example.net. 46 IN PTR customer.example.net. 47 IN PTR customer.example.net. $ORIGIN example.net. ; there is no customer IN A record then I get a log entry like Dec 19 10:13:06 kundwebs pure-ftpd: (?@customer.example.net) [WARNING] Authentication failed for user [user001] instead Dec 19 10:13:06 kundwebs pure-ftpd: (?@192.0.2.45) [WARNING] Authentication failed for user [user001] Needed fix: pure-ftpd always must also resolve the host name received from the PTR record in forward direction to ensure that it is not a bogus hostname, i.e. they must be identical. In all cases of wrong DNS configuration, pure-ftpd always must show the naked IP address even if DontResolv=no is set. Workaround by myself: DNS resolution disabled, i.e. echo yes /etc/pure-ftpd/conf/DontResolve To the Debian package maintainers: I recommend to set this behaviour as the package default. -- System Information: Debian Release: 7.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/1 CPU core) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages pure-ftpd depends on: ii libc6 2.13-38 ii libcap2 1:2.22-1.2 ii libpam0g 1.1.3-7.1 ii libssl1.0.0 1.0.1e-2 ii lsb-base 4.1+Debian8+deb7u1 ii openbsd-inetd [inet-superserver] 0.20091229-2 ii pure-ftpd-common 1.0.36-1.1 pure-ftpd recommends no packages. pure-ftpd suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#699437: Feedback Wheezy test setup with current mini.iso
Hello Quentin Thanks for your hints. Because there is a new mini.iso online in the meantime, I repeated a basic out of the box setup on my hardware (IBM NetVista A40 model 6840-QDG, Promise Fastrak TX2300, two Western Digital Caviar Red 2 TB NAS disks). All partitions are deleted, MBR is zeroed completely, i.e. classic starting from green grass (bare metal) scenario. - boot parameters on CD: removed the vga=788 parameter, added dmraid=true according [1]. - partitioning: Guided - Use complete disk, RAID volume detected correctly, option Use separate /usr, /home, /var, ... (gives a very large /home) - packet selection as usual, i.e. SSH server, unselection Desktop environment in my case - question about GRUB's location answered with Yes into MBR - Continue - finishing installation as usual and reboot Everything worked flawlessly until this point BTW small minor bug (offtopic): CD drive drawer stays locked - sending eject command like the GParted CD does may helpful - I built a small MS-DOS start floppy tool containing a CD-ROM driver and a QBasic tool[2] for that to avoid unnecessary power off/on cycles as temporary workaround... First boot from hard drive: GRUB menu appears correctly but boot fails with the message as shown (Device or resource busy and BusyBox prompt) in the past. = Ctrl+Alt+Del, booting from mini.iso CD, Advanced options, Rescue mode Tab dmraid=true instead vga=788 - After successful loading: /dev/dm-1 as root system, start a shell *** First important bug: Wrong special device file names in /etc/fstab; there is a extra p which must be removed, i.e. # ls -al /dev/mapper drwxr-xr-x 2 root root 200 Jun 29 14:44 . drwxr-xr-x 15 root root 3740 Jun 29 14:44 .. crw--T 1 root root 10, 236 Jun 29 14:44 control brw-rw 1 root disk 254, 0 Jun 29 14:44 pdc_ehdiebaf brw-rw 1 root disk 254, 1 Jun 29 14:44 pdc_ehdiebaf1 brw-rw 1 root disk 254, 2 Jun 29 14:44 pdc_ehdiebaf5 brw-rw 1 root disk 254, 3 Jun 29 14:44 pdc_ehdiebaf6 brw-rw 1 root disk 254, 4 Jun 29 14:44 pdc_ehdiebaf7 brw-rw 1 root disk 254, 5 Jun 29 14:44 pdc_ehdiebaf8 brw-rw 1 root disk 254, 6 Jun 29 14:44 pdc_ehdiebaf9 but # cat /etc/fstab ... file system mount point type options dump pass /dev/mapper/pdc_ehdiebafp1 / ext4errors=remount-ro 0 1 /dev/mapper/pdc_ehdiebafp9 /home ext4defaults0 2 /dev/mapper/pdc_ehdiebafp8 /tmpext4defaults0 2 /dev/mapper/pdc_ehdiebafp5 /usrext4defaults0 2 /dev/mapper/pdc_ehdiebafp6 /varext4defaults0 2 /dev/mapper/pdc_ehdiebafp7 noneswapsw 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 (look to the extra p at the end in all pdc_ehdiebafpX entries!) = must be changed into # file system mount point type options dump pass /dev/mapper/pdc_ehdiebaf1 / ext4errors=remount-ro 0 1 /dev/mapper/pdc_ehdiebaf9 /home ext4defaults0 2 /dev/mapper/pdc_ehdiebaf8 /tmpext4defaults0 2 /dev/mapper/pdc_ehdiebaf5 /usrext4defaults0 2 /dev/mapper/pdc_ehdiebaf6 /varext4defaults0 2 /dev/mapper/pdc_ehdiebaf7 noneswapsw 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0/media/floppy0 autorw,user,noauto 0 0 = bash mount -o remount / mount /dev/mapper/pdc_ehdiebaf9 /home mount /dev/mapper/pdc_ehdiebaf8 /tmp mount /dev/mapper/pdc_ehdiebaf5 /usr mount /dev/mapper/pdc_ehdiebaf6 /var pico /etc/fstab (removing the extra ps) Applying UUID disabling (Quentin's hint): pico /etc/default/grub = enabling GRUB_DISABLE_LINUX_UUID=true by uncommenting update-grub grub-install /dev/mapper/pdc_ehdiebaf (the second command is also important else you get a mess [and the boot failure issue still remains!] with some extra entries in the GRUB boot menu) = exit twice from rescue mode and reboot - removing CD with the trick (start floppy tool) above - et voilà - it successfully boots. :-) Done several root logins and shutdown -r now - it always boots successfully - i.e. the problem seems to be fixed. :-) To the Debian maintainers: Changing the last installation step to allow selection GRUB UUID on/off (or automatically disabling UUID in case of dmraid=true before creating GRUB) seems to be a useful way to getting rid with this bug. Also don't forget to fix this extra p issue in /etc/fstab and sending an CD drawer unlock (or even eject) command to the CD/DVD drive at the tidy up end stage of installation. Andreas [1] http://wiki.debian.org/DebianInstaller/SataRaid [2] http://beilagen.dreael.ch/QB/CDSCHUBL.BAS -- meile.biz IT solutions, Hauptstrasse
Bug#611082: apcupsd causes kernel/daemon crash on IBM 6840-QDG hardware
Package: apcupsd Version: 3.14.8-2 Severity: normal After apcupsd installation and configuration I get the following messages in /var/log/kern.log (daemon/kernel crash): ** May 10 11:31:36 deb6test kernel: [ 37.132161] usb 1-2: New USB device found, idVendor=051d, idProduct=0002 May 10 11:31:36 deb6test kernel: [ 37.132174] usb 1-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2 May 10 11:31:36 deb6test kernel: [ 37.132182] usb 1-2: Product: Back-UPS 500 FW: 6.4.I USB FW: c1 May 10 11:31:36 deb6test kernel: [ 37.132189] usb 1-2: Manufacturer: American Power Conversion May 10 11:31:36 deb6test kernel: [ 37.132195] usb 1-2: SerialNumber: JB0307013375 May 10 11:31:36 deb6test kernel: [ 37.132548] usb 1-2: configuration #1 chosen from 1 choice May 10 11:31:36 deb6test kernel: [ 37.655400] generic-usb 0003:051D:0002.0002: hiddev0,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS 500 FW: 6.4.I USB FW: c1 ] on usb-:00:1f.2-2/input0 May 10 11:32:41 deb6test kernel: [ 102.080068] usb 1-2: USB disconnect, address 3 May 10 11:32:45 deb6test kernel: [ 106.036096] usb 1-2: new low speed USB device using uhci_hcd and address 4 May 10 11:32:45 deb6test kernel: [ 106.227949] usb 1-2: New USB device found, idVendor=051d, idProduct=0002 May 10 11:32:45 deb6test kernel: [ 106.227960] usb 1-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2 May 10 11:32:45 deb6test kernel: [ 106.227967] usb 1-2: Product: Back-UPS 500 FW: 6.4.I USB FW: c1 May 10 11:32:45 deb6test kernel: [ 106.227973] usb 1-2: Manufacturer: American Power Conversion May 10 11:32:45 deb6test kernel: [ 106.227979] usb 1-2: SerialNumber: JB0307013375 May 10 11:32:45 deb6test kernel: [ 106.230424] usb 1-2: configuration #1 chosen from 1 choice May 10 11:32:46 deb6test kernel: [ 106.750083] generic-usb 0003:051D:0002.0003: hiddev0,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS 500 FW: 6.4.I USB FW: c1 ] on usb-:00:1f.2-2/input0 May 10 11:33:50 deb6test kernel: [ 171.024155] usb 1-2: USB disconnect, address 4 May 10 11:33:54 deb6test kernel: [ 175.128055] usb 1-2: new low speed USB device using uhci_hcd and address 5 May 10 11:33:54 deb6test kernel: [ 175.319951] usb 1-2: New USB device found, idVendor=051d, idProduct=0002 May 10 11:33:54 deb6test kernel: [ 175.319961] usb 1-2: New USB device strings: Mfr=3, Product=1, SerialNumber=2 May 10 11:33:54 deb6test kernel: [ 175.319968] usb 1-2: Product: Back-UPS 500 FW: 6.4.I USB FW: c1 May 10 11:33:54 deb6test kernel: [ 175.319974] usb 1-2: Manufacturer: American Power Conversion May 10 11:33:54 deb6test kernel: [ 175.319980] usb 1-2: SerialNumber: JB0307013375 May 10 11:33:54 deb6test kernel: [ 175.322203] usb 1-2: configuration #1 chosen from 1 choice May 10 11:33:55 deb6test kernel: [ 175.844150] generic-usb 0003:051D:0002.0004: hiddev0,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS 500 FW: 6.4.I USB FW: c1 ] on usb-:00:1f.2-2/input0 May 10 11:34:59 deb6test kernel: [ 240.216093] usb 1-2: USB disconnect, address 5 May 10 11:34:59 deb6test kernel: [ 240.242205] BUG: unable to handle kernel NULL pointer dereference at (null) May 10 11:34:59 deb6test kernel: [ 240.242361] IP: [e0a8aaf7] hiddev_ioctl+0x26/0x56f [usbhid] May 10 11:34:59 deb6test kernel: [ 240.242473] *pde = May 10 11:34:59 deb6test kernel: [ 240.242556] Oops: [#1] SMP May 10 11:34:59 deb6test kernel: [ 240.242668] last sysfs file: /sys/devices/pci:00/:00:1f.2/usb1/1-2/1-2:1.0/0003:051D:0002.0004/hidraw/hidraw0/uevent May 10 11:34:59 deb6test kernel: [ 240.242756] Modules linked in: nfsd lockd nfs_acl auth_rpcgss sunrpc exportfs nls_utf8 nls_cp437 vfat fat loop osst st snd_intel8x0 snd_ac97_codec ac97_bus snd_pcm snd_timer snd psmouse i2c_i801 soundcore shpchp parport_pc snd_page_alloc pcspkr serio_raw evdev parport i2c_core rng_core pci_hotplug button processor ext3 jbd mbcache dm_mirror dm_region_hash dm_log dm_mod sg sr_mod cdrom sd_mod crc_t10dif usbhid ata_generic hid ata_piix aic7xxx uhci_hcd sata_promise e100 libata scsi_transport_spi ehci_hcd thermal floppy mii scsi_mod usbcore nls_base thermal_sys [last unloaded: scsi_wait_scan] May 10 11:34:59 deb6test kernel: [ 240.244958] May 10 11:34:59 deb6test kernel: [ 240.245012] Pid: 1135, comm: apcupsd Not tainted (2.6.32-5-686 #1) 6840QDG May 10 11:34:59 deb6test kernel: [ 240.245074] EIP: 0060:[e0a8aaf7] EFLAGS: 00010286 CPU: 0 May 10 11:34:59 deb6test kernel: [ 240.245138] EIP is at hiddev_ioctl+0x26/0x56f [usbhid] May 10 11:34:59 deb6test kernel: [ 240.245198] EAX: EBX: 400c4807 ECX: bf9190f4 EDX: fffb May 10 11:34:59 deb6test kernel: [ 240.245259] ESI: de3af680 EDI: dede1000 EBP: bf9190f4 ESP: df99fea0 May 10 11:34:59 deb6test kernel: [ 240.245320] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 May 10 11:34:59 deb6test kernel: [ 240.245381] Process apcupsd (pid:
Bug#699437: Test with the first Wheezy stable release
Severity: grave Package: initrd(?) In the meantime, I tested the first stable Wheezy release on the hardware as described in the previous messages of this bug, i.e. IBM NetVista A40 (model 6840-QDG), Promise Fastrak TX2300 PCI and two Western Digital Caviar Red 2 TB SATA drives configured as RAID-1 (mirror). Result: Still the same problem. :-( Because this bug affects Debian's basic setup (=getting a bootable and running system where one can do the first root login and applying further apt-get install/configuration), the severity level should be increased. Because dmraid itself always works fine in the emergency system as well as in the installation environment, I strongly believe that the dmraid package itself is 100% ok but something in the initrd boot configuration creation process causes that bug (probably a missing insmod dmraid, wrong special device file for root system or something similar). It's also to note that dmraid on the same hardware works flawlessly withing Debian Squeeze (the old-stable release now) when applying the steps at [1]. To exclude any hardware specific issue from the IBM motherboard (the 6840-QDG is an older model), I moved the Fastrak TX2300 controller and the two hard drives into another hardware equipped with an Asus P5B-VM motherboard and Intel Pentium Core Duo CPU (full x64 capable) and retested the basic setup using a Debian default partitioning layout. Result: Installation also succeeds but booting the installed system fails. Details: http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Asus_P5B-VM_20130508/ Differences to the IBM NetVista hardware: - the boot failure message is a little another one, see the .jpg in the link above - exit in the BusyBox does not produce a kernel panic, it just calls the BusyBox again - While installation, the question for placing GRUB into the MBR didn't appear, I directly had to complete the /dev/mapper/pdc_cacjhiccia there I hope this helps fix the bug for the next 7.0.1 release so I don't need to use an oldstable Debian release on this kind of hardware. :-) Andreas [1] http://wiki.debian.org/DebianInstaller/SataRaid -- meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67 Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
Bug#699437: Addition: No successful boot when using 2 TB disks and/or ext4 file system
After fixing bug #704635 I tested a new Debian Wheezy setup today. To exclude any partition layout specific issues, I allowed Debian to use the whole disk with the automatic partitioning layout including ext4. Result: Setup (using mini.iso, FTP source=mirror.switch.ch) completely runs fine but startup of the installed system fails after OS selection in GRUB: http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Boot_failure_20130407.jpg Difference to the earlier tests with the small disks: It always fails (I repeated booting several times). More details: http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Kernel_panic_after_exit_20130407.jpg http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Promise_BIOS_details_20130407.jpg http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/dmesg_20130407.txt http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/proc_partitions_20130407.txt http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/ls_dev_mapper_20130407.txt http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/proc_bus_pci_devices_20130407.txt Hardware is a IBM NetVista A40 (model 6840-QDG) equipped with a Promise Fastrak TX2300 PCI RAID controller and two Western Digital 2 TB Caviar Red NAS SATA hard drives configured as RAID-1. I hope this hint better helps to reproduce this bug. Also worth to note: On the CD boot, using dmraid=yes always works fine, this bug occurs only when booting from hard drive. Andreas -- meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67 Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
Bug#704635: [Wheezy] Package authentication issue during base installation: BusyBox
Hello Didier - Original Message - From: Didier 'OdyX' Raboud o...@debian.org To: Andreas Meile i...@andreas-meile.ch; 704...@bugs.debian.org Sent: Thursday, April 04, 2013 10:22 AM Subject: Re: Bug#704635: [Wheezy] Package authentication issue during base installation: BusyBox Control: reassign -1 debootstrap 1.0.47 Control: forcemerge 703889 -1 Hi Andreas, and thanks for your bugreport. Le mercredi, 3 avril 2013 21.45:43, Andreas Meile a écrit : During the setup of a Debian Box (hardware: IBM NetVista A40 model To exclude a hardware / dmraid specific issue, I just tested a Debian installation inside VMware Player. Result: http://beilagen.dreael.ch/Diverses/Bug_Wheezy_Install_BusyBox/Wheezy_Bug_VMware.png http://beilagen.dreael.ch/Diverses/Bug_Wheezy_Install_BusyBox/Wheezy_Bug_VMware_syslog.png i.e. exactly the same error so there's a general problem. BTW a general problem: In the past, I got package download errors several times during a Debian installation where I always had to just repeat the installation some hours later. That means that any running FTP mirror updates (I often browse inside http://mirror.switch.ch/ftp/mirror/debian/dists/testing/ and take a look on the last modified dates. This way I check for any updated mini.iso file) overwrite the files my Debian installer process is just needing so package download lists or dependencies get invalid during the installation... A good solution to avoid that might be something like a snapshot concept where there is always at least one complete copy on the FTP mirror inside a folder named according the release date/timestamp so the installation process (the same also for apt-get update and apt-get upgrade later) always finds a consistent copy of the installation files and the current symbolic link always points to the current _complete_ distribution folder. = FTP mirror updates always should create a new folder. At the end of the FTP mirror update, the testing symbolic link can be updated = from this moment, a newly started Debian installation uses the very new version. The previous folder should be kept for some hours (or days for slow Internet connections) at least so any running installation processes can finish properly. The base installation never must use current in the FTP fetch URL, it has to query the snapshot date as the very first step and then use download links containing the time stamp folder name. An alternative is something like a This FTP mirror is being updated now; try installation or update later flag file where there is also something like a orange traffic light state (=FTP mirror update will be started in some hours - any new installation cannot be started but already running installations can finish) necessary. Andreas -- meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67 Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
Bug#704635: [Wheezy] Package authentication issue during base installation: BusyBox
Package: base-installer Version: 1.130 During the setup of a Debian Box (hardware: IBM NetVista A40 model 6840-QDG, 512 MB RAM, Promise Fastrak TX2300 SATA RAID and two Western Digital Caviar Red NAS 2 TB SATA hard drives configured as RAID-1 on it = dmraid=yes option at CD boot. Installation done using mini.iso and mirror.switch.ch as FTP source) I get a Apr 3 18:32:02 in-target: WARNING: The following packages cannot be authenticated! Apr 3 18:32:02 in-target: busybox Apr 3 18:32:02 in-target: E: There are problems and -y was used without --force-yes Apr 3 18:32:03 base-installer: error: exiting on error base-installer/kernel/failed-package-install error and the installation aborts during the base system phase with a red screen. Full details including syslog see http://beilagen.dreael.ch/Diverses/Bug_Wheezy_Install_BusyBox/ I hope this helps improve the next Debian release. :-) Andreas -- meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67 Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
Bug#699437: Addiditions: Same issue with Promise Fastrak TX2300
Today, I tested a similar installation with a Promise Fastrak TX2300 controller and two SATA hard drives as RAID-1. Result is exactly the same: Installation fully suceeds including GRUB but the system randomly produces the same mount: mounting /dev/disk/by-uuid/x on /root failed: Device or resource busy while booting as shown at http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Boot_Fehler_sporadisch.jpg Details see http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/dmesg_fastrak2300_erfolg.txt http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/dmesg_fastrak2300_fehlgeschlagen.txt http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/lsmod_fastrak2300_busybox.txt Note: The hardware is the same IBM NetVista A40 model. Installation was done with mini.iso from a FTP mirror. Andreas -- meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67 Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
Bug#699437: [Wheezy] dmraid (Promise Fastrak 100) boot issue
Package: dmraid / OS setup general Version: 1.0.0.rc16-4.2 root@smbserv:~# dpkg -l|grep dmraid ii dmraid 1.0.0.rc16-4.2 i386 Device-Mapper Software RAID support tool ii libdmraid1.0.0.rc16 1.0.0.rc16-4.2 i386 Device-Mapper Software RAID support tool - shared library root@smbserv:~# _ Detailed description: I set up a small server according to the hints shown at http://wiki.debian.org/DebianInstaller/SataRaid Hardware is a IBM NetFinity A40 tower PC (model 6840-QDG) with a Promise Fastrak 100 RAID controller, two EIDE hard drives on it (configured as RAID-1 mirror) and a SCSI tape drive. Details about the setup itself: As shown at http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Fata_Morgana_Partitionen.jpg I cannot use the partitions shown below pdc_iicbbhfc (mirror) (I even must unselect the swap partition there), instead using the separate entries shown at http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Partitionen_korrekt.jpg works fine. Note: For Norton Ghost compatibility I prepartitioned and formatted the hard drive first before starting the Debian setup. GRUB installs successfully with the right special device (note: I use a separate /boot parition with bootable flag so a standard MBR will work, i.e. fdisk /mbr at MS-DOS 6.22 does not destroy GRUB) as shown at http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/GRUB_Partition.jpg The actual issue: Each second time, my Debian box fails to boot with the message shown at http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Boot_Fehler_sporadisch.jpg http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/dmesg.txt When I do exit the BusyBox, I even get a kernel panic: http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/Kernelpanic_bei_BusyBox_exit.jpg Details about the Promise controller and RAID setup: http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/BIOS_Meldung_Promise.jpg Note: The PXE boot shown there is a known issue on the Intel Pro 100S NICs and has nothing to do with the bug described before. In case of a successful boot (no update-grub needed - just powering off and on), dmesg shows like http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/dmesg_Start_erfolgreich.txt Used partitioning layout (run after successful boot): root@smbserv:~# fdisk -l /dev/mapper/pdc_iicbbhfc Disk /dev/mapper/pdc_iicbbhfc: 250.0 GB, 2500 bytes 255 heads, 63 sectors/track, 30394 cylinders, total 488281250 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x Device Boot Start End Blocks Id System /dev/mapper/pdc_iicbbhfc1 63 514079 257008+ 6 FAT16 /dev/mapper/pdc_iicbbhfc2 * 514080 194 409657+ 83 Linux /dev/mapper/pdc_iicbbhfc3 195 4417874 1542240 83 Linux /dev/mapper/pdc_iicbbhfc4 4417875 488279609 241930867+ f W95 Ext'd (LBA) /dev/mapper/pdc_iicbbhfc5 441793822860494 9221278+ 83 Linux /dev/mapper/pdc_iicbbhfc622860558 10479199440965718+ 83 Linux /dev/mapper/pdc_iicbbhfc7 104792058 110944889 3076416 83 Linux /dev/mapper/pdc_iicbbhfc8 110944953 114430994 1743021 82 Linux swap / Solaris /dev/mapper/pdc_iicbbhfc9 114431058 13491386910241406 83 Linux /dev/mapper/pdc_iicbbhfc10 134913933 142094924 3590496 83 Linux /dev/mapper/pdc_iicbbhfc11 142094988 488279609 173092311 83 Linux root@smbserv:~# _ For more details (I hope to have collected all important details inside the BusyBox state) see all additional files at http://beilagen.dreael.ch/Diverses/dmraid_Wheezy_Bugs/ I hope these informations will help you improve the next Debian release. :-) Andreas -- meile.biz IT solutions, Hauptstrasse 63, CH-8242 Hofen SH PC/Netzwerk-Support, Web-Entwicklung und -Hosting, IT Security Tel. +41 52 640 04 72 * Fax +41 52 640 04 73 * Mobile +41 79 334 05 67 Postfach 169, CH-8240 Thayngen * i...@meile.biz * http://www.meile.biz smime.p7s Description: S/MIME cryptographic signature
Bug#604033: Bug report: Installing Squeeze on a Intel Matrix BIOS RAID1 volume
Package: installation-reports Boot method: Used mini-iso burnt on CD-RW Image version: http://mirror.switch.ch/ftp/mirror/debian/dists/squeeze/main/installer-i386/current/images/netboot/mini.iso Date: 2010-11-19T16:20 Machine: HP Pavillion m9060.ch Partitions: see debug logs 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: [E] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: This motherboard supports Intel Matrix BIOS RAID so I inserted two HDD's, activated RAID in the BIOS SATA settings, then created a logical volume with Ctrl+I (Intel's built-in BIOS RAID manager). Then I created several Linux ext3 partitions using Partition Magic 8.0 for /, /usr, /home and so on. Problem: The RAID Volume with partitions is detected correctly as /dev/md126 together with all /dev/md126px partitions but as read-only (so Debian's partition manager part can't format the swap area. = Continuation of installation is not possible. Also a problem: The physical volumes behind appear, too. = The installer marks for example formating the swap partition on three locations (/dev/sde8, /dev/sdf8 and /dev/md126p8 in this example). These shouldn't be offered for partitioning because they are part of the RAID volume The full debug logs details are saved at http://beilagen.dreael.ch/Diverses/Bug_Debian_Squeeze_Intel_Matrix_BIOS_RAID/ Andreas -- Teste die PC-Sicherheit mit www.sec-check.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
