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
