| 1 |
On Sun, Jan 27, 2013 at 12:31 PM, João Matos <jaoneto@×××××.com> wrote: |
| 2 |
> |
| 3 |
> |
| 4 |
> |
| 5 |
> 2013/1/26 Canek Peláez Valdés <caneko@×××××.com> |
| 6 |
>> |
| 7 |
>> On Sat, Jan 26, 2013 at 7:08 PM, João Matos <jaoneto@×××××.com> wrote: |
| 8 |
>> > Hi list, |
| 9 |
>> > |
| 10 |
>> > I'm having this problem for a while, but I've decided to solve it know. |
| 11 |
>> > Every time I boot my system (couple times a day), I have to hid Ctrl + D |
| 12 |
>> > when the boot process is interrupted by the "emergency mode". |
| 13 |
>> > |
| 14 |
>> > I think it started when I was compiling the kernel myself, and removing |
| 15 |
>> > lot |
| 16 |
>> > of stuff. Although, I checked and the mandatory options for systemd are |
| 17 |
>> > ok. |
| 18 |
>> > |
| 19 |
>> > When I run "journalctl -b -p err" the only information I get is: |
| 20 |
>> > |
| 21 |
>> > Jan 26 20:29:20 KONOHA NetworkManager[1497]: claim_connection: assertion |
| 22 |
>> > `nm_connection_get_path (NM_CONNECTION (connection)) == NULL' failed |
| 23 |
>> > Jan 26 20:29:24 localhost dhcpcd[1557]: wlan0: sendmsg: Cannot assign |
| 24 |
>> > requested address |
| 25 |
>> > Jan 26 20:30:42 localhost pulseaudio[2073]: [pulseaudio] pid.c: Daemon |
| 26 |
>> > already running. |
| 27 |
>> > Jan 26 20:30:42 localhost pulseaudio[2080]: [pulseaudio] pid.c: Daemon |
| 28 |
>> > already running. |
| 29 |
>> > |
| 30 |
>> > It give me no clue. |
| 31 |
>> > |
| 32 |
>> > Attached the .conf from my gentoo-3.7.1 |
| 33 |
>> > |
| 34 |
>> > After I hit Ctrl + D, the system works normally. |
| 35 |
>> > |
| 36 |
>> > Any help will be appreciated :) |
| 37 |
>> |
| 38 |
>> Are you using udev-197 with systemd-197? mgorny masked it, and said |
| 39 |
>> this in package.mask: |
| 40 |
> |
| 41 |
> |
| 42 |
> I'm using them. Last time I updated my system there weren't any warning. |
| 43 |
> Anyway, this problem is happening since the previous version. |
| 44 |
> |
| 45 |
>> |
| 46 |
>> # Does not boot. Something with udev is probably broken. Feel free |
| 47 |
>> # to unmask, debug and provide me with a patch. |
| 48 |
>> |
| 49 |
>> You need to be using the same version for udev and systemd (they are |
| 50 |
>> the same package). If you are using the same version for udev and |
| 51 |
>> systemd, are you using an initramfs? When was the last time you built |
| 52 |
>> it, if you do? |
| 53 |
> |
| 54 |
> |
| 55 |
> I don't have initramfs. Just the kernel. But it used to work normaly. |
| 56 |
>> |
| 57 |
>> |
| 58 |
>> Could you boot with "systemd.log_target=kmsg" and |
| 59 |
>> "systemd.log_level=debug", and post the whole output of "journalctl |
| 60 |
>> -b"? It prints only the logs from the last boot. |
| 61 |
>> |
| 62 |
> |
| 63 |
> journalctl -b attached. |
| 64 |
|
| 65 |
From your logs: |
| 66 |
|
| 67 |
Jan 27 15:16:27 KONOHA systemd[1]: Activating default unit: emergency.target |
| 68 |
|
| 69 |
You have emergency.target as default unit. The default.target can be |
| 70 |
set in different ways: |
| 71 |
|
| 72 |
- Check /usr/lib64/systemd/system/default.target |
| 73 |
- Check /etc/systemd/system/default.target |
| 74 |
- Check if you use --unit=emergency.target in your grub config |
| 75 |
- Check if you pass the "emergency" kernel parametr in your grub config |
| 76 |
|
| 77 |
udev-197 in the tree installs everything to /; systemd-197 installs to |
| 78 |
/usr. I'm pretty sure that is not going to end well; I haven't |
| 79 |
upgraded to 197 in neither package. |
| 80 |
|
| 81 |
Check your default.target; for some reason is set to emergency. |
| 82 |
|
| 83 |
Regards. |
| 84 |
-- |
| 85 |
Canek Peláez Valdés |
| 86 |
Posgrado en Ciencia e Ingeniería de la Computación |
| 87 |
Universidad Nacional Autónoma de México |
Archives