Hello team
i am running OpenSUSE on VMware environment
recently while rebooting the server I am getting the following error
waiting for device /dev/sda3 to appear
sda3 is my root partition
i tried different solutions found on the web by using a Rescue disk without no success
do you know how to fix this issue
thanks
What is the content of /etc/fstab and the kernel line in the default grub stanza (/boot/grub2/grub.cfg)?
Which version?
You choose for OTHER VERSION, which means that it is not one of the supported versions. And it means also that it is the more important that you explain which one… Most people here are not clairvoyant.
that is right, it is a old version 10.0
The server was running fine and no change or update was done on Linux side.
I only had a problem with he VMware tools and i reinstalled the VMware tools on the server without any issue
The content of the fstab is
/dev/sda3 / reiserfs noatime,acl,user_xattr 1 1
/dev/sda1 /boot ext2 noatime,acl,user_xattr 1 2
/dev/sda4 /backup ext3 noatime,acl,user_xattr 1 2
/dev/sda2 swap swap defaults 0 0
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
/dev/cdrom /cdrom iso9660 noauto 0 0
and the content of the /boot/grub/menu.lst is
color white/blue black/light-gray
default 0
timeout 8
###Don’t change this comment - YaST2 identifier: Original name: linux###
title SUSE LINUX 10.0
root (hd0,0)
kernel /vmlinuz root=/dev/sda3 vga=normal selinux=0 splash=silent showopts
initrd /initrd
###Don’t change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe – SUSE LINUX 10.0
root (hd0,0)
kernel /vmlinuz root=/dev/sda3 vga=normal showopts ide=nodma apm=off acpi=off noresume selinux=0 nosmp noapic maxcpus=0 edd=off 3
initrd /initrd
###Don’t change this comment - YaST2 identifier: Original name: memtest86###
But changes are done to the outside world ;). And I am afraid that many are now scratching the head: How was life in those years? And more important: how was openSUSE in those years? I see Reiserfs and Grub legacy. …
It’s that old, that it’s called SUSE Linux, where after 2005 it became openSUSE / SUSE Linux Enterprise. This means the biggest security risk is the admin of the server. IMNSHO.
The server was running fine and no change or update was done on Linux side.
I only had a problem with he VMware tools and i reinstalled the VMware tools on the server without any issue
These two lines contradict, i.e. ‘no change’ vs. ‘reinstalled the VMware tools’.
Once again: keeping a server running without maintenance for this long, is outright dangerous. And please, don’t expect support for versions that are not only out of support and maintenance, but could be considered archeological findings.
A couple of tips:
Is there any other way to fix it rather than to install it from scratch.
We have a lot of service running on this server and this may take a long time to complete it
did someone face such situation in the past?
Try conforming its configuration to match mine following:
# date
Mon Oct 29 14:10:49 EDT 2018
# hostname
gx260
# head -n1 /etc/SuSE-release
SUSE LINUX 10.0 (i586) OSS
# uname -a
Linux gx260 2.6.13-15.18-default #1 Tue Oct 2 17:36:20 UTC 2007 i686 i686 i386 GNU/Linux
# cat /proc/cmdline
root=LABEL=S16A-suse100 selinux=0 noresume
# blkid /dev/hda30
/dev/hda30: LABEL="S16A-suse100" UUID="d8e3f45a-...." SEC_TYPE="ext2" TYPE="ext3"
# grep suse100 /etc/fstab
LABEL=S16A-suse100 / ext3 noatime,noacl,user_xattr 1 1
# head /boot/grub/menu.lst | grep kernel
kernel /boot/vmlinuz showopts root=LABEL=S16A-suse100 selinux=0 noresume
# mount | grep suse
LABEL=S16A-suse100 on / type ext3 (rw,noatime,noacl,user_xattr)
IOW, replace device names with labels in menu.lst and fstab.