Hi experts,
I just rebooted our SLES server and the login interface became the image below:
This happen when I update the operating system using Yast. But now, the Yast also has a problem. I think it has missing menu.
I don’t know what to do. Hope to hear positive response from you guys.
On 10/14/2016 03:04 AM, bryan1207 wrote:[color=blue]
I just rebooted our SLES server and the login interface became the image
below:
[image: https://s18.postimg.org/nvjtub51l/image.jpg][/color]
This looks like Gnome or KDE is not starting, but that’s not exactly a bad
thing unless you think it should start.
[color=blue]
This happen when I update the operating system using Yast. But now, the[/color]
Which version of SLES, with which SPs? How exactly did you update in
Yast, and from what version, or just simple intra-SP patches?
[color=blue]
Yast also has a problem. I think it has missing menu.
[image: https://s14.postimg.org/vzr4jqwht/image.jpg][/color]
Depending on what was there before, you may be missing a lot of things,
like the ‘Boot Loader’ option. Do you know what was there before? What
exactly did the upgrade prompt in Yast show you it was going to do? How
are you on disk space?
Perhaps post the output from the following commands:
yast -l
df -h
mount
cat /etc/SuSE-release–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…
Hi, thanks for the response. Here’s my answer:
[CODE]SBO:~ # yast -l
Available modules:
add-on-creator
apparmor
audit-laf
disk
dsl
host
isdn
keyboard
lan
language
modem
mouse
power-management
proxy
remote
sshd
timezone
x11
[/CODE]
SBO:~ # [B]df -h[/B]
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/root-root 99G 40G 54G 43% /
udev 32G 132K 32G 1% /dev
tmpfs 32G 68K 32G 1% /dev/shm
/dev/sda1 288M 42M 232M 16% /boot
/dev/mapper/root-home 5.7G 140M 5.2G 3% /home
/dev/mapper/root-opt 3.0G 69M 2.8G 3% /opt
/dev/mapper/root-tmp 25G 143M 24G 1% /tmp
/dev/mapper/root-var 3.0G 261M 2.6G 10% /var
/dev/mapper/root-var--log 4.0G 169M 3.6G 5% /var/log
/dev/mapper/root-shdm 197G 188M 187G 1% /shdm
/dev/mapper/root-shlm 74G 180M 70G 1% /shlm
/dev/mapper/root-shsb 79G 184M 75G 1% /shsb
SBO:~ # [B]mount[/B]
/dev/mapper/root-root on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,mode=1777)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sda1 on /boot type ext3 (rw,acl,user_xattr)
/dev/mapper/root-home on /home type ext3 (rw,acl,user_xattr)
/dev/mapper/root-opt on /opt type ext3 (rw,acl,user_xattr)
/dev/mapper/root-tmp on /tmp type ext3 (rw,acl,user_xattr)
/dev/mapper/root-var on /var type ext3 (rw,acl,user_xattr)
/dev/mapper/root-var--log on /var/log type ext3 (rw,acl,user_xattr)
/dev/mapper/root-shdm on /shdm type ext3 (rw,acl,user_xattr)
/dev/mapper/root-shlm on /shlm type ext3 (rw,acl,user_xattr)
/dev/mapper/root-shsb on /shsb type ext3 (rw)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
SBO:~ # [B]cat /etc/SuSE-release[/B]
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 4
[QUOTE=ab;34714]On 10/14/2016 03:04 AM, bryan1207 wrote:[color=blue]
I just rebooted our SLES server and the login interface became the image
below:
[image: https://s18.postimg.org/nvjtub51l/image.jpg][/color]
This looks like Gnome or KDE is not starting, but that’s not exactly a bad
thing unless you think it should start.
[color=blue]
This happen when I update the operating system using Yast. But now, the[/color]
Which version of SLES, with which SPs? How exactly did you update in
Yast, and from what version, or just simple intra-SP patches?
[color=blue]
Yast also has a problem. I think it has missing menu.
[image: https://s14.postimg.org/vzr4jqwht/image.jpg][/color]
Depending on what was there before, you may be missing a lot of things,
like the ‘Boot Loader’ option. Do you know what was there before? What
exactly did the upgrade prompt in Yast show you it was going to do? How
are you on disk space?
Perhaps post the output from the following commands:
yast -l
df -h
mount
cat /etc/SuSE-release–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…[/QUOTE]
On 10/17/2016 04:04 AM, bryan1207 wrote:[color=blue]
Hi, thanks for the response. Here’s my answer:
Code:
SBO:~ # *yast -l*Available modules:
add-on-creator
apparmor
audit-laf
disk
dsl
host
isdn
keyboard
lan
language
modem
mouse
power-management
proxy
remote
sshd
timezone
x11--------------------[/color]
That seems like a pretty small list. When you built this box, did you do
a minimal install, or a GUI install, or JeOS install, or anything like
that? My non-GUI install of SLES 11 SP-something has seventy-eight items
listed. I have no idea why you would have lost something other than by
doing an upgrade or other package change incorrectly. Maybe a clue will
be in the zypper logs at /var/log/zypper.log though it’s a pretty verbose
log. The y2logs may also be useful at /var/log/YaST2/y2log though it,
too, is very verbose and I have little experience pulling out details from
there.
I suppose you could try to add things back into Yast with zypper, assuming
that works properly; my current list o packages starting with ‘yast2’ from
my box follows, though you would not need all of these:
yast2
yast2-add-on
yast2-add-on-creator
yast2-apparmor
yast2-audit-laf
yast2-autofs
yast2-backup
yast2-boot-server
yast2-bootloader
yast2-branding-SLES
yast2-ca-management
yast2-core
yast2-country
yast2-country-data
yast2-dbus-client
yast2-dbus-server
yast2-dhcp-server
yast2-dirinstall
yast2-dns-server
yast2-fingerprint-reader
yast2-firewall
yast2-ftp-server
yast2-hardware-detection
yast2-http-server
yast2-inetd
yast2-installation
yast2-instserver
yast2-irda
yast2-iscsi-client
yast2-iscsi-server
yast2-isns
yast2-kdump
yast2-kerberos-client
yast2-kerberos-server
yast2-ldap
yast2-ldap-client
yast2-ldap-server
yast2-libyui
yast2-mail
yast2-mail-plugins
yast2-metapackage-handler
yast2-mouse
yast2-ncurses
yast2-ncurses-pkg
yast2-network
yast2-nfs-client
yast2-nfs-common
yast2-nfs-server
yast2-nis-client
yast2-nis-server
yast2-ntp-client
yast2-online-update
yast2-online-update-frontend
yast2-packager
yast2-pam
yast2-perl-bindings
yast2-pkg-bindings
yast2-power-management
yast2-printer
yast2-profile-manager
yast2-python-bindings
yast2-registration
yast2-registration-branding-SLE
yast2-repair
yast2-restore
yast2-runlevel
yast2-samba-client
yast2-samba-server
yast2-schema
yast2-security
yast2-slp
yast2-slp-server
yast2-squid
yast2-sshd
yast2-storage
yast2-storage-lib
yast2-sudo
yast2-support
yast2-sysconfig
yast2-tftp-server
yast2-theme-SLE
yast2-trans-en_US
yast2-trans-stats
yast2-transfer
yast2-tune
yast2-update
yast2-users
yast2-vm
yast2-wagon
yast2-xml
yast2-ycp-ui-bindings–
Good luck.
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below…