Hello All,
I had to Power off the virtual machine running SLES 12 SP2, as the virtual machine is not responsive. Now, I am having issues to start the same. It’s failing with error “[COLOR="#FF0000"]Failed to start System Logging Service.[/COLOR]”. Below is the screen shot of the error. Is there a way to boot this machine successfully?
thank you,
SB
Hi SB,
Failed to start System Logging Server
judging from the prompt, you seem to be in a rescue system, not your live system. Looking at the unit file path suggests so, too. So why ever it is failing may not have to do anything with your server not booting correctly, but be a consequence of running in rescue mode.
Regards,
J
Hi J,
thanks for the reply. Yes, I have booted to the rescue mode as the regular boot from disc doesn’t work. Let me know what and where should I check? I have installed some SAP applications on this and have spent some good amount of time, and don’t want to loose that work.
Thanks,
SB
Hi SB
Yes, I have booted to the rescue mode as the regular boot from disc doesn’t work
can you share any details on what’s going wrong during the regular boot? It may well be we’re barking up the wrong tree regarding these “syslogd n rescue mode” problems.
Regards,
J
[QUOTE=jmozdzen;55145]Hi SB
Yes, I have booted to the rescue mode as the regular boot from disc doesn’t work
can you share any details on what’s going wrong during the regular boot? It may well be we’re barking up the wrong tree regarding these “syslogd n rescue mode” problems.
Regards,
J[/QUOTE]
Hi J,
When I boot in the regular mode, I get the below error:
and the journalctl -xb gives me the following log. I have uploaded the screens where there were error messages:
Let me know if this helps to identify the issue.
Regards,
SB
sbnukala25 Wrote in message:
[color=blue]
When I boot in the regular mode, I get the below error:
‘[image: http://thumbs2.imagebam.com/de/56/a9/1a3adf1026372604.jpg]’
(http://www.imagebam.com/image/1a3adf1026372604)
and the
Code:journalctl -xb
gives me the following log. I have uploaded the screens where there
were error messages:
‘[image: http://thumbs2.imagebam.com/6f/c4/64/dd42881026372584.jpg]’
(http://www.imagebam.com/image/dd42881026372584)
‘[image: http://thumbs2.imagebam.com/a7/5f/2f/4aa60c1026372594.jpg]’
(http://www.imagebam.com/image/4aa60c1026372594)
‘[image: http://thumbs2.imagebam.com/de/56/a9/1a3adf1026372604.jpg]’
(http://www.imagebam.com/image/1a3adf1026372604)
Let me know if this helps to identify the issue.[/color]
Some of those screen shots suggest some disk issues (swap & home)
except this is a virtual machine. Are you using VMDK files or
mounting physical storage?
Given this started when you powered off your VM after it locked up
what steps had you been doing before then?
Simon Flood
SUSE Knowledge Partner
----Android NewsGroup Reader----
http://usenet.sinaapp.com/
[QUOTE=smflood;55169]sbnukala25 Wrote in message:
[color=blue]
When I boot in the regular mode, I get the below error:
‘[image: http://thumbs2.imagebam.com/de/56/a9/1a3adf1026372604.jpg]’
(http://www.imagebam.com/image/1a3adf1026372604)
and the
Code:journalctl -xb
gives me the following log. I have uploaded the screens where there
were error messages:
‘[image: http://thumbs2.imagebam.com/6f/c4/64/dd42881026372584.jpg]’
(http://www.imagebam.com/image/dd42881026372584)
‘[image: http://thumbs2.imagebam.com/a7/5f/2f/4aa60c1026372594.jpg]’
(http://www.imagebam.com/image/4aa60c1026372594)
‘[image: http://thumbs2.imagebam.com/de/56/a9/1a3adf1026372604.jpg]’
(http://www.imagebam.com/image/1a3adf1026372604)
Let me know if this helps to identify the issue.[/color]
Some of those screen shots suggest some disk issues (swap & home)
except this is a virtual machine. Are you using VMDK files or
mounting physical storage?
Given this started when you powered off your VM after it locked up
what steps had you been doing before then?
Simon Flood
SUSE Knowledge Partner
----Android NewsGroup Reader----
http://usenet.sinaapp.com/[/QUOTE]
Hi Simon,
Thanks for the reply. I’m booting the VM from the VMDK file. Before I powered it off, it was idle but consumed all the memory and CPU. So, I had to forceflly power it off. Then the problem started.
Regards,
Sai
Hi Sai,
as Simon already pointed out, systemd is complaining about “missing filesystems”. A typical cause would be file system corruption, but also it could be some general problem with the disk image.
When in rescue mode, please try to check what file systems it is trying to find, and try to locate the according block devices. Does your system disk look like what you’d expect from your earlier work (virtual disks, partitions, file systems on them)? Have you probably changed the type of disk, as configured in VMware, so that device assignments, required drivers or alike may have changed? (I don’t recall having ever seen a virtual disk appear as “FAST-40 WIDE SCSI” in a VMware VM, but maybe I just overlooked it…)
Regards,
J