0008517: VM unbootable after upgrade from CentOS 7 to 7.1

ID	Project	Category	View Status	Date Submitted	Last Update

0008517	CentOS-7	systemd	public	2015-04-20 15:48	2015-04-21 10:29

Reporter	msteamix	Assigned To
Priority	high	Severity	major	Reproducibility	always
Status	new	Resolution	open
Platform	VMware ESX hypervisor	OS	CentOS	OS Version	7.1
Product Version	7.1-1503

Summary	0008517: VM unbootable after upgrade from CentOS 7 to 7.1
Description	I just get piix4_smbus 0000:00:07.3: SMBus base address uninitialized - upgrade BIOS or use force_addr=0xaddr, but this is a non critical warning. Then systemd drops to emergency. I booted with quiet from kernel command line removed, but also no obvious errors. This happens with latest -229 (I think) Centos 7.1 kernel, and an way earlier CentOS 7.0 kernel (-123).
Steps To Reproduce	Upgrade VMware ESX CentOS machine from 7.0 to 7.1. Boot.
Additional Information	There has been a VMware ESX upgrade from 5.1 to 5.5, and well the machine was booted from VMware ESX 5.5 now, so this may be related as well. Unfortunately systemd does not reveal on the boot output why it dropped into emergency mode, not even with kernel command line parameter "quiet" removed. I ran systemctl and systemctl status and didn´t find anything obvious. Also I saw several successful XFS mounts with quiet parameter removed, so… do you have any tipps what commands to run to get a clearer impression on where it might have failed?
Tags	No tags attached.

abrt_hash
URL

msteamix 2015-04-20 15:51 reporter ~0022838	okay, with non quiet I see XFS mounts at 15 seconds. And then at 100 seconds systemd-journal Received request to flush runtime journal from PID something then one audit log entry and then it says "Welcome to emergency mode" without any kind of explaination as to why. Not booting is one thing, not even telling why that is, another…

msteamix 2015-04-21 08:53 reporter ~0022842	Okay, I have three different bugs here: 1) Machine doesn´t boot. See: - boot.png: Thats a boot without "quiet" argument. - mount.png: It does have all mounts just fine. Despite it still does not boot. 2) It doesn´t show any error message at all. - see above 3) It even does not let me start a ssh server to dig out debug information from it. - starting-ssh.png As for the versions see: - versions.png Will upload all files in a moment.

msteamix 2015-04-21 08:54 reporter	boot.png (234,002 bytes) boot.png (234,002 bytes)

msteamix 2015-04-21 08:55 reporter	mount.png (191,876 bytes) mount.png (191,876 bytes)

msteamix 2015-04-21 08:57 reporter	starting-ssh.png (31,121 bytes) starting-ssh.png (31,121 bytes)

msteamix 2015-04-21 08:58 reporter	versions.png (127,378 bytes) versions.png (127,378 bytes)

msteamix 2015-04-21 09:21 reporter ~0022843	Okay, I can start sshd via /usr/bin/sshd manually, so I am able to digout debug information. Any hints on where to start? systemctl and systemctl status show nothing unusual. Okay, I found it. I mounted /boot as LABEL bootfs, and well, it didn´t have this label. So it is a misconfiguration, yet: - /boot is by no means critical for startup - there is still no error message - systemctl start can´t even start sshd in that case Here is the output from journalctl -xb: -- The start-up result is done. Apr 21 10:13:27 lintraincentos7 systemd[1]: Job dev-disk-by\x2dlabel-bootfs.device/start timed out. Apr 21 10:13:27 lintraincentos7 systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-bootfs.device. -- Subject: Unit dev-disk-by\x2dlabel-bootfs.device has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit dev-disk-by\x2dlabel-bootfs.device has failed. -- -- The result is timeout. Apr 21 10:13:27 lintraincentos7 systemd[1]: Dependency failed for /boot. -- Subject: Unit boot.mount has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit boot.mount has failed. -- -- The result is dependency. Apr 21 10:13:27 lintraincentos7 systemd[1]: Dependency failed for Local File Systems. -- Subject: Unit local-fs.target has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit local-fs.target has failed. -- -- The result is dependency. Apr 21 10:13:27 lintraincentos7 systemd[1]: Dependency failed for Relabel all filesystems, if necessary. -- Subject: Unit rhel-autorelabel.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- The result is dependency. Apr 21 10:13:27 lintraincentos7 systemd[1]: Dependency failed for Mark the need to relabel after reboot. -- Subject: Unit rhel-autorelabel-mark.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rhel-autorelabel-mark.service has failed. -- -- The result is dependency. Apr 21 10:13:27 lintraincentos7 systemd[1]: Triggering OnFailure= dependencies of local-fs.target. Apr 21 10:13:27 lintraincentos7 systemd[1]: Dependency failed for /boot/efi. -- Subject: Unit boot-efi.mount has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit boot-efi.mount has failed. -- -- The result is dependency. Apr 21 10:13:27 lintraincentos7 systemd[1]: Dependency failed for File System Check on /dev/disk/by-label/bootfs. -- Subject: Unit systemd-fsck@dev-disk-by\x2dlabel-bootfs.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit systemd-fsck@dev-disk-by\x2dlabel-bootfs.service has failed. -- -- The result is dependency.

msteamix 2015-04-21 09:23 reporter ~0022844	I would like to rename this ticket, but it does not seem to be possible. Well, in any case, this sounds like an upstream issue, thus I think will report with bugzilla.redhat.

msteamix 2015-04-21 09:40 reporter ~0022845	Reported as: Bug 1213781 - does not start ssh service if a filesystem in /etc/fstab cannot be mounted https://bugzilla.redhat.com/show_bug.cgi?id=1213781 Bug 1213778 - drops into emergency mode without any error message if it cannot find a filesystem in /etc/fstab https://bugzilla.redhat.com/show_bug.cgi?id=1213778 Feel free to close, as I think thats no CentOS specific issue. Thanks, Martin

joopbraak 2015-04-21 10:29 reporter ~0022846	Is this the same bug? https://bugs.centos.org/view.php?id=8523

Date Modified	Username	Field
2015-04-20 15:48	msteamix	New Issue
2015-04-20 15:51	msteamix	Note Added: 0022838
2015-04-21 08:53	msteamix	Note Added: 0022842
2015-04-21 08:54	msteamix	File Added: boot.png
2015-04-21 08:55	msteamix	File Added: mount.png
2015-04-21 08:57	msteamix	File Added: starting-ssh.png
2015-04-21 08:58	msteamix	File Added: versions.png
2015-04-21 09:21	msteamix	Note Added: 0022843
2015-04-21 09:23	msteamix	Note Added: 0022844
2015-04-21 09:40	msteamix	Note Added: 0022845
2015-04-21 10:29	joopbraak	Note Added: 0022846

View Issue Details

Activities

Issue History