Am Montag, 10. Juni 2013, 00:00:08 schrieb Michael Biebl: > Am 09.06.2013 19:22, schrieb Martin Steigerwald: > > Package: systemd > > Version: 44-11 > > Severity: important > > > > Dear Maintainer, > > > > Today I build a 3.10-rc5 kernel from upstream and rebooted in order to use > > it. > > > > Then systemd hung on mounting or checking /boot/efi (FAT32) > > > > I booted into system rescue mode and commented out /boot/efi in fstab. > > > > Then on reboot systemd hung on mounting or checking /boot (Ext4). > > > > Then I used /sbin/init to boot up the system which comes up just fine. > > > > > > /etc/fstab entries for both: > > > > LABEL=boot /boot ext4 noatime > > 0 1 > > /dev/sda2 /boot/efi vfat noatime > > 0 0 > > > > > > merkaba:~> blkid | egrep "(boot|msdos)" > > /dev/sda2: SEC_TYPE="msdos" UUID="[…]" TYPE="vfat"· > > /dev/sda3: LABEL="boot" UUID="[…]" TYPE="ext4" > > > > I am not reporting upstream, since the systemd version in Debian is > > outdated. > > > > > > Since it worked so far I bet some recent update broke it. Can be just a > > few days since I successfully rebooted into a new kernel a few days ago > > with systemd. > > The systemd package itself hasn't changed for quite a while, so I > suspect a change in another package. > Can you try to use the Debian kernel from sid or wheezy?
Happens also with linux-image-3.9-1-amd64 (3.9.4-1). With 3.10-rc5 I waited a bit longer for it to happen and got some additional messages from systemd: About 9th second of booting: Started /boot... EXT4.fs (sda3): mounted filesystem with ordered data mode. Opts: (null) Started /boot/efi... FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems will be case sensitive! FAT-fs (sda2): Volume is not properly unmounted. Some data may be corrupt. Please run fsck. [... some kernel messages about psmouse serio2 and IBM Trackpoint ...] About 15th second of booting: Dependency failed. Aborted start of /mnt/home-zeit Welcome to emergency mode. Use "systemctl default" or ^D to enter default mode. Give root password for maintenance (or type Control-D to continue): I give root password. Then do mount /mnt/home-zeit which works just well. No errors in dmesg. /mnt/home-zeit has the root subvol of the /home BTRFS filesystem mounted, which contains the snapshots so that they can easily be excluded on backup. LABEL=home /home btrfs noatime,space_cache,compress=lzo 0 0 LABEL=home /mnt/home-zeit btrfs noatime,space_cache,compress=lzo,subvolid=5 0 0 The filesystem scrubbed just well last Saturday, so I think it is okay. Will scrub it again today to make sure. Last update of btrfs-progs was Start-Date: 2013-05-20 20:32:27 Commandline: apt-get upgrade Upgrade: libavformat53:amd64 (0.8.6-1, 0.8.7-1), libavformat54:amd64 (9.5-1, 9.6-1), libstartup-notification0:amd64 (0.12-1, 0.12-3), libevent-2.0-5:amd64 (2.0.19-stable-3, 2.0.21-stable-1), libavresample1:amd64 (9.5-1, 9.6-1), libavfilter2:amd64 (0.8.6-1, 0.8.7-1), libpython2.7-stdlib:amd64 (2.7.5-3, 2.7.5-4), luatex:amd64 (0.70.1.20120524-3, 0.76.0-1), python-pylibacl:amd64 (0.5.1-1.1, 0.5.1-1.1+b1), libavcodec-extra-53:amd64 (0.8.6-1, 0.8.7-1), libattr1:amd64 (2.4.46-8, 2.4.47-1), libattr1:i386 (2.4.46-8, 2.4.47-1), libattr1-dev:amd64 (2.4.46-8, 2.4.47-1), python2.7:amd64 (2.7.5-3, 2.7.5-4), libswscale2:amd64 (9.5-1, 9.6-1), ffmpeg:amd64 (0.8.6-1, 0.8.7-1), python-pyxattr:amd64 (0.5.1-1.1, 0.5.1-1.1+b1), libav-tools:amd64 (0.8.6-1, 0.8.7-1), libpython2.7:amd64 (2.7.5-3, 2.7.5-4), libpostproc52:amd64 (0.8.6-1, 0.8.7-1), dnsmasq-base:amd64 (2.66-1, 2.66-2), libdlrestrictions1:amd64 (0.15.6, 0.15.7), libgps20:amd64 (3.6-5, 3.9-1), libkpathsea6:amd64 (2012.20120628-4, 2013.20130516.30500-1), cmake:amd64 (2.8.9-1, 2.8.11-2), pkg-kde-tools:amd64 (0.15.6, 0.15.7), python2.7-minimal:amd64 (2.7.5-3, 2.7.5-4), libavcodec54:amd64 (9.5-1, 9.6-1), libavdevice53:amd64 (0.8.6-1, 0.8.7-1), cmake-curses-gui:amd64 (2.8.9-1, 2.8.11-2), tex-common:amd64 (4.02, 4.03), btrfs-tools:amd64 (0.19+20130131-3+really20121004-1, 0.19+20130315-2), cmake-data:amd64 (2.8.9-1, 2.8.11-2), printer-driver-m2300w:amd64 (0.51-7, 0.51-9), ethtool:amd64 (3.4.2-1, 3.9-1), attr:amd64 (2.4.46-8, 2.4.47-1), libptexenc1:amd64 (2012.20120628-4, 2013.20130516.30500-1), libdbd-mysql-perl:amd64 (4.021-1+b1, 4.023-1), libpython2.7-minimal:amd64 (2.7.5-3, 2.7.5-4), libavutil51:amd64 (0.8.6-1, 0.8.7-1), libavutil52:amd64 (9.5-1, 9.6-1), printer-driver-ptouch:amd64 (1.3-4, 1.3-6) Error: Sub-process /usr/bin/dpkg returned an error code (1) End-Date: 2013-05-20 20:33:28 I don´t remember the error. Ah according to term.log.1.gz it was tex: Log started: 2013-05-20 20:32:27 […] tex-common (4.03) wird eingerichtet ... Running mktexlsr. This may take some time... done. Running updmap-sys. This may take some time... updmap-sys failed. Output has been stored in /tmp/updmap.gCKEIuGr Please include this file if you report a bug. Sometimes, not accepting conffile updates in /etc/texmf/updmap.d causes updmap-sys to fail. Please check for files with extension .dpkg-dist or .ucf-dist in this directory dpkg: Fehler beim Bearbeiten von tex-common (--configure): Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück dpkg: Abhängigkeitsprobleme verhindern Konfiguration von luatex: luatex hängt ab von tex-common (>= 4); aber: Paket tex-common ist noch nicht konfiguriert. I fixed this one later on. Any other package that might be related? Any way to ask systemd for more about *why* the dependency failed (that error message does not appear very helpful for me)? Thanks, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
signature.asc
Description: This is a digitally signed message part.
