Re: unable to boot with systemd (works with sysvinit)
On Sb, 10 ian 15, 12:33:36, Johannes Schauer wrote: Hi, I'm not subscribed, so please keep me CC-ed. I'm unable to boot my laptop with systemd which worked before. I'm unable to tell the changes I made since the last time it worked because according to my uptime, the last time I rebooted was September last year. cgroup /sys/fs/cgroup cgroup defaults 0 0 This is *probably* unrelated, but I would remove it anyway. It shouldn't be necessary unless you do fancy stuff with cgroups (other than what systemd already does). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: unable to boot with systemd (works with sysvinit)
On 01/13/2015 01:36 AM, Johannes Schauer wrote: Hi, Quoting Selim T. Erdoğan (2015-01-12 22:38:08) On Sat, Jan 10, 2015 at 12:33:36PM +0100, Johannes Schauer wrote: I'm unable to boot my laptop with systemd which worked before. I'm unable to tell the changes I made since the last time it worked because according to my uptime, the last time I rebooted was September last year. I see you already have a bug report, so including it for the list: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758808 this is the right bug report. Downgrading to 204-14 fixes the problem I encountered in my first email. My apologies for not having supplied that bug report in my initial email. I honestly forgot that I already faced the same problem in August last year. I eventually just re-installed Jessie fresh. Never a problem afterwards. If something updates, nothing goes boom. I assume it's still not quite ready for the dist-upgrade style of install. At least that was my way of resolving any potential future problems, and it worked for metm :) Ric -- My father, Victor Moore (Vic) used to say: There are two Great Sins in the world... ..the Sin of Ignorance, and the Sin of Stupidity. Only the former may be overcome. R.I.P. Dad. Linux user# 44256 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54b568ce.9010...@gmail.com
Re: unable to boot with systemd (works with sysvinit)
On Sat, Jan 10, 2015 at 12:33:36PM +0100, Johannes Schauer wrote: I'm not subscribed, so please keep me CC-ed. I'm unable to boot my laptop with systemd which worked before. I'm unable to tell the changes I made since the last time it worked because according to my uptime, the last time I rebooted was September last year. I see you already have a bug report, so including it for the list: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758808 (Also for reference, your older bug report, where you first saw this issue, indicates that this might have arisen between systemd 204-14 and systemd 208-6: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755581) The output of `journalctl -xb` in the systemd rescue console is here: https://mister-muffin.de/p/AabX.txt My system contains up-to-date package versions with Debian Jessie. This means I'm running systemd and udev version 215-8. Since the problem seems to be related to a failed fsck job, according to above log, here is my fstab (minus comment lines): It looks to me like it's not fsck as much as not being able to access /boot, /home and swap. If you want to check this, you can probably tell systemd not to run fsck at boot. (How to do this was the topic of some recent threads on debian-user, but I didn't follow them so I can't help with that.) proc/proc procdefaults0 0 /dev/mapper/volumegroup-root/ ext4errors=remount-ro 0 1 UUID=ac034ff5-d28a-4ad1-8bac-97d554395e3e /boot ext2defaults 0 2 /dev/mapper/volumegroup-home /home ext4defaults0 2 /dev/mapper/volumegroup-swap noneswapsw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 cgroup /sys/fs/cgroup cgroup defaults 0 0 tmpfs /tmptmpfs nodev,nosuid,size=8G 0 0 tmpfs /runtmpfs nodev,nosuid,size=8G 0 0 I also booted my system into the initramfs busybox by passing break to the kernel command line and did an `fsck -f` on my root and home partitions and everything seems to be clean. Booting my laptop with sysvinit instead works fine, so my fstab should be correct. How can I further debug this problem? The journalctl output seems inconclusive. I wonder if the problem is with decryption (under systemd), which then leads to the timeout when accessing everything inside it? Unfortunately, I don't know enough to suggest a good way to test this. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150112213808.GA11541@side
Re: unable to boot with systemd (works with sysvinit)
Hi, Quoting Selim T. Erdoğan (2015-01-12 22:38:08) On Sat, Jan 10, 2015 at 12:33:36PM +0100, Johannes Schauer wrote: I'm unable to boot my laptop with systemd which worked before. I'm unable to tell the changes I made since the last time it worked because according to my uptime, the last time I rebooted was September last year. I see you already have a bug report, so including it for the list: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758808 this is the right bug report. Downgrading to 204-14 fixes the problem I encountered in my first email. My apologies for not having supplied that bug report in my initial email. I honestly forgot that I already faced the same problem in August last year. It looks to me like it's not fsck as much as not being able to access /boot, /home and swap. If you want to check this, you can probably tell systemd not to run fsck at boot. (How to do this was the topic of some recent threads on debian-user, but I didn't follow them so I can't help with that.) Searching the archives you might've meant to add fsck.mode=skip to my kernel command line. I tried that but it didn't fix the problem. I wonder if the problem is with decryption (under systemd), which then leads to the timeout when accessing everything inside it? Unfortunately, I don't know enough to suggest a good way to test this. This is a possibility. Thank you for your help! cheers, josch signature.asc Description: signature
unable to boot with systemd (works with sysvinit)
Hi, I'm not subscribed, so please keep me CC-ed. I'm unable to boot my laptop with systemd which worked before. I'm unable to tell the changes I made since the last time it worked because according to my uptime, the last time I rebooted was September last year. The output of `journalctl -xb` in the systemd rescue console is here: https://mister-muffin.de/p/AabX.txt My system contains up-to-date package versions with Debian Jessie. This means I'm running systemd and udev version 215-8. Since the problem seems to be related to a failed fsck job, according to above log, here is my fstab (minus comment lines): proc/proc procdefaults0 0 /dev/mapper/volumegroup-root/ ext4errors=remount-ro 0 1 UUID=ac034ff5-d28a-4ad1-8bac-97d554395e3e /boot ext2defaults 0 2 /dev/mapper/volumegroup-home /home ext4defaults0 2 /dev/mapper/volumegroup-swap noneswapsw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 cgroup /sys/fs/cgroup cgroup defaults 0 0 tmpfs /tmptmpfs nodev,nosuid,size=8G 0 0 tmpfs /runtmpfs nodev,nosuid,size=8G 0 0 I also booted my system into the initramfs busybox by passing break to the kernel command line and did an `fsck -f` on my root and home partitions and everything seems to be clean. Booting my laptop with sysvinit instead works fine, so my fstab should be correct. How can I further debug this problem? The journalctl output seems inconclusive. Thanks! signature.asc Description: signature
