Bug 10182 - After running mageia-prepare-upgrade system doesn't boot
Summary: After running mageia-prepare-upgrade system doesn't boot
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-20 19:15 CEST by Sorin Toma
Modified: 2013-05-22 10:21 CEST (History)
2 users (show)

See Also:
Source RPM: mageia-prepare-upgrade2-2.mga2
CVE:
Status comment:


Attachments

Description Sorin Toma 2013-05-20 19:15:16 CEST
$ urpmi mageia-prepare-upgrade2-2.mga2

At the first boot, the messages from dracut shows that the move is done cleanly, but sysctl gives an error when trying to start /var/tmp
Dependency failed. Aborted start of Setup links in /... running kernel [ABORT]
Dependency failed. Aborted start of Mark the need to...el after reboot [ABORT]
Dependency failed. Aborted start of Relabel all file...s, if necessary [ABORT]

$ systemctl status var-tmp.mount:
Failed to get D-Bus connection: Failed to connect to socket /run/systemd/private: No such file or directory

$ ls -la /run shows the existence of only one directory inside: /run/udev/

dmesg shows multiple lines containing:
systemd-cgroups-agent[PID]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused

same message after rebooting with the standard kernel
starting dbus-launcher by hand, followed by /bin/systemd creates the directory /run/systemd, but there is no socket inside, just 2 empty subdirs "ask-password" and "system"

- I've tried twice, it seems consistent( https://forums.mageia.org/en/viewtopic.php?f=7&t=4967 )
- There are eight third party installed packages on the system: 
teamviewer
fluendo-dvd (from Mandriva)
tv-maxe
bleachbit
google-chrome-stable
rar (Mandrivaclub.nl)
flashplugin
skype

Reproducible: 

Steps to Reproduce:
Sander Lepik 2013-05-20 19:26:56 CEST

CC: (none) => sander.lepik
Assignee: bugsquad => mageia

Comment 1 Sorin Toma 2013-05-20 19:33:44 CEST
Hardware: HP EliteBook 6930p, Core2Duo P8600, 4GB Ram, HDD Seagate Momentus 750GB
sda1 650GB ntfs (win7 32bit)
sda3 2GB vfat -HP recovery
sda2 ext
        sda5 88GB ext4 / (Mageia 2 i586 - default boot)
        sda6 4.5GB swap
kernel 3.4.45-tmb-laptop1.mga2
repos enabled (i586): Core, Core Updates, NonFree, NonFree Updates, Tainted, Tainted Updates, google-chrome 
- all packages have been updated this morning.

Assignee: mageia => bugsquad

Comment 2 Colin Guthrie 2013-05-21 10:09:31 CEST
Hmm, interesting. I think it might be the existence of a /var/tmp mount that is confusing things. I'll have to do some tests with a similar FS layout to say for sure.

Are you able to comment out this mount point in the fstab and see if the boot proceeds OK?

CC: (none) => mageia

Comment 3 Sorin Toma 2013-05-22 01:33:39 CEST
thank you Colin, 
It's looking good all the way, I consider this bug closed.
I've totally forgot about mounting /tmp and /var/tmp as tmpfs, can somebody append the errata for online upgrade with this info?
Comment 4 Sorin Toma 2013-05-22 02:10:36 CEST
Closed

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX

Comment 5 Colin Guthrie 2013-05-22 10:21:54 CEST
Just FYI, /var/tmp shouldn't really be tmpfs. It's being designated as a semi-permanent tmp space that will survive across reboots. /tmp on the other hand is getting nuked on every boot.

Thanks for reporting back.

Note You need to log in before you can comment on or make changes to this bug.