openSUSE 12.3 RC1 reboots into emergency mode right after installation

taytong888 · February 13, 2013, 2:11pm

Hello,

Toshiba laptop with Intel Celeron M CPU, ATI Radeon Xpress 200M video and 2 GB RAM.

Installed GRUB2 into MBR and root partition as suggested default option. After installation and reboot, the computer screen shows text-based emergency mode (e.g. sysctl reboot suggestion, etc.).

Any suggestions?

Thanks a lot for your help.

arvidjaar · February 13, 2013, 2:18pm

Login into emergency mode and post output of “journalctl -b”

ijbreakey · February 13, 2013, 6:18pm

Hello,

Check out a solution I gave in the 12.3RC1 Comment thread here: http://forums.opensuse.org/english/get-technical-help-here/pre-release-beta/483056-12-3rc1-comment-thread-4.html#post2526607

arvidjaar’s suggestion to check the the output of journalctl -b will help you determine what mount point is messed up.

Thank You,

Ian

crimarova64 · February 14, 2013, 2:24am

What i did was:

After login I mounted /home partitionmount /dev/sda /home*
And thensystemctl default
And the installation continued.

taytong888 · February 14, 2013, 8:24am

Thanks for your reply. Today I reinstalled 12.3RC1 with the following changes compared to previous settings:

Fstab options: boot by device LABEL: sda9_home, sda9_root (Previously, by DeviceID as default)

GRUB2 in MBR, root partition, extended partition (Left Custom Boot Partition unchecked)

After reboot, screen shows emergency mode. The following are error messages in RED as shown by journalctl -b:

unable to open rtc device
timed out waiting for device dev-disk-by-\x2dlabel-suse12.3_home.device
dependency failed for /home
dependency failed for Local File Systems
dependency failed for Remote File Systems (Pre)

Then I tried:


#mount /dev/sda9 /home
#systemctl default

The screen then shows a green band at the bottom with green “openSUSE12.3 (Dartmouth) i586”. The rest of the screen is black. This seems to stay forever.

When I reboot again, I was able to boot into openSUSE 12.2 which uses legacy GRUB to chainload into Windows 7 and other Linux distros. I am in Suse12.2 to reply to your post.

Any ideas or suggestions? Thank you.

arvidjaar · February 14, 2013, 8:40am

If this is indeed the message shown, device name is wrong. Please, **always **copy and paste exact strings. Manually editing just makes it harder to understand what’s going on.

Please reboot into 12.3, enter emergency mode (if it still stops there) and post exact output of

blkid
cat /etc/fstab
ls -l /dev/disk/by-label

pajdina · February 14, 2013, 9:16am

The same problem here

arvidjaar · February 14, 2013, 9:25am

And how this “mee too” helps to troubleshoot the problem? Please provide at least output of “journalctl -b” after entering emergency mode.

jla2 · February 14, 2013, 10:05am

I too had this issue and installed 12.2 back for now. But here’s the output of “journalctl -b” from my computer if it helps fixing this for RC2: http://jla.kapsi.fi/files/journalctloutput

pajdina · February 14, 2013, 10:20am

I’m sorry I wiped openSUSE 12.3, but the output of “journalctl-b” is the same as from user jla2,I think that the error with udev

arvidjaar · February 14, 2013, 12:23pm

Yes, udev coldplug service seems to be not run. Could folks, who have this problem, check that you have /usr/lib/systemd/system/systemd-udev-trigger.service and /usr/lib/systemd/system/sysinit.target.wants/systemd-udev-trigger.service as well as udev version and status of this service?

linux-vmd4:~ # rpm -q udev
udev-195-13.4.1.x86_64
linux-vmd4:~ # systemctl status systemd-udev-trigger.service
systemd-udev-trigger.service - udev Coldplug all Devices
          Loaded: loaded (/usr/lib/systemd/system/systemd-udev-trigger.service; static)
          Active: active (exited) since Thu, 2013-02-14 11:23:24 MSK; 3h 58min ago
            Docs: man:udev(7)
                  man:systemd-udevd.service(8)
         Process: 285 ExecStart=/usr/bin/udevadm trigger --type=devices --action=add (code=exited, status=0/SUCCESS)
         Process: 283 ExecStart=/usr/bin/udevadm trigger --type=subsystems --action=add (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/systemd-udev-trigger.service

Feb 14 11:23:24 linux-vmd4.site systemd[1]: Starting udev Coldplug all Devic....
Feb 14 11:23:24 linux-vmd4.site systemd[1]: Started udev Coldplug all Devices.

machanch · February 14, 2013, 2:56pm

arvidjaar:

Yes, udev coldplug service seems to be not run. Could folks, who have this problem, check that you have /usr/lib/systemd/system/systemd-udev-trigger.service and /usr/lib/systemd/system/sysinit.target.wants/systemd-udev-trigger.service as well as udev version and status of this service?

linux-vmd4:~ # rpm -q udev
udev-195-13.4.1.x86_64
linux-vmd4:~ # systemctl status systemd-udev-trigger.service
systemd-udev-trigger.service - udev Coldplug all Devices
          Loaded: loaded (/usr/lib/systemd/system/systemd-udev-trigger.service; static)
          Active: active (exited) since Thu, 2013-02-14 11:23:24 MSK; 3h 58min ago
            Docs: man:udev(7)
                  man:systemd-udevd.service(8)
         Process: 285 ExecStart=/usr/bin/udevadm trigger --type=devices --action=add (code=exited, status=0/SUCCESS)
         Process: 283 ExecStart=/usr/bin/udevadm trigger --type=subsystems --action=add (code=exited, status=0/SUCCESS)
          CGroup: name=systemd:/system/systemd-udev-trigger.service

Feb 14 11:23:24 linux-vmd4.site systemd[1]: Starting udev Coldplug all Devic....
Feb 14 11:23:24 linux-vmd4.site systemd[1]: Started udev Coldplug all Devices.

This is the exact problem I am having with installing LiveKDE 12.3… 5+ times I have installed on various partitions… makes not difference
Output of rpm -q udev re-directed to file

udev-195-13.4.1.x86_64

Output of systemctl status re-directed to file

systemd-udev-trigger.service - udev Coldplug all Devices
      Loaded: loaded (/usr/lib/systemd/system/systemd-udev-trigger.service; static)
      Active: inactive (dead)
        Docs: man:udev(7)
              man:systemd-udevd.service(8)
      CGroup: name=systemd:/system/systemd-udev-trigger.service

Feb 14 13:36:13 linux.site systemd[1]: Stopped udev Coldplug all Devices.

arvidjaar · February 14, 2013, 3:27pm

Could you please boot with systemd.log_level=debug added to kernel parameters, enter emergency shell and upload full output of “journalctl -b -a” to SUSE Paste

machanch · February 14, 2013, 4:09pm

I hope you can see it… ‘openSUSE12.3_systemd_log_level’

taytong888 · February 14, 2013, 4:58pm

arvidjaar:

If this is indeed the message shown, device name is wrong. Please, **always **copy and paste exact strings. Manually editing just makes it harder to understand what’s going on.

Please reboot into 12.3, enter emergency mode (if it still stops there) and post exact output of
blkid
cat /etc/fstab
ls -l /dev/disk/by-label

Hello arvidjaar,

That’s indeed the message shown.

How do I copy and paste screen content while in the emergency mode?

I am waiting for your instruction so that I can post the exact output of:

blkid
cat /etc/fstab
ls -l /dev/disk/by-label

Thanks for your help.

arvidjaar · February 14, 2013, 5:11pm

Yes, I can.

Feb 14 14:58:17 linux.site systemd[1]: Failed to load configuration for udev-trigger.service: No such file or directory

Please show output “ls -l /usr/lib/systemd/system/.wants" and "ls -l /etc/systemd/system/.wants”

machanch · February 14, 2013, 5:58pm

arvidjaar:

Yes, I can.
Feb 14 14:58:17 linux.site systemd[1]: Failed to load configuration for udev-trigger.service: No such file or directory
Please show output “ls -l /usr/lib/systemd/system/.wants" and "ls -l /etc/systemd/system/.wants”

here are the outputs

RE: ls -l usr/lib/systemd/system](http://susepaste.org/view/45482638)ls -l /etc/systemd/system

It appears as though I have hijacked this thread. As taytong888 ] has the exact same issues, hope the solution here will fix both our problem**…**

arvidjaar · February 14, 2013, 6:22pm

Seems that service that is expected to start before udev trigger is not started. Could you additionally paste output of “systemctl show systemd-udev-trigger.service” and “systemctl show systemd-vconsole-setup.service”? The former waits for the latter which is never started. I have here minimal text mode install of 12.3 so probably there is something missing on my system.

machanch · February 14, 2013, 7:14pm

The outputs:

Id=systemd-udev-trigger.device
Names=systemd-udev-trigger.device
Description=systemd-udev-trigger.device
LoadState=loaded
ActiveState=inactive
SubState=dead
InactiveExitTimestampMonotonic=0
ActiveEnterTimestampMonotonic=0
ActiveExitTimestampMonotonic=0
InactiveEnterTimestampMonotonic=0
CanStart=no
CanStop=no
CanReload=no
CanIsolate=no
StopWhenUnneeded=no
RefuseManualStart=no
RefuseManualStop=no
AllowIsolate=no
DefaultDependencies=yes
OnFailureIsolate=no
IgnoreOnIsolate=yes
IgnoreOnSnapshot=yes
NeedDaemonReload=no
JobTimeoutUSec=1min 30s
ConditionTimestampMonotonic=0
ConditionResult=no

systemd-vconsole-setup.service

taytong888 · February 14, 2013, 7:31pm

Hello machanch

No problems! I appreciate your efforts in providing info so that our “emergency mode” problem will be resolved. I look forward to seeing this to become reality! By the way, have you submitted or seen any relevant bug report?

Have a nice day!