Red HatThis forum is for the discussion of Red Hat Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I got the error when i rebooted my redhat 5.5 server.
Mounting root filesystem.
EXT2-fs: sda5: couldn't mount because of unsupported optional features (4).
mount: error mounting /dev/root on /sysroot as ext2: Invalid argument
Setting up other filesystems.
Setting up new root fs
setuproot: moving /dev failed: No such file or directory
no fstab.sys, mounting internal defaults
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
Switching to new root and running unit.
unmounting old /dev
unmounting old /proc
unmounting old /sys
error /dev/console: no such file or folder
trying to use fd O in lead
exec of null failed: Bad address
kernel panic-not syncing:Attempted to kill init!
Distribution: RHEL, CentOS, Debian, Oracle Solaris 10
Posts: 1,420
Rep:
I doubt that you messed up with your /etc/fstab file. You need to correct the entries of fstab file, if such is the case. And remounting the / partition.
Before the problem happened, there is no installation/updation on the system.
Can you please tell me how can i correct the fstab entries. When I boot my system in rescue mode and continue with chroot /mnt/sysimages i get a following warning message.
"The partition table on device sdb was unreadable.
To create new partition on it must be initialized, causing the loss of all data on this data.
This operation will override any previous installation choices about which drives to ignore.
Would you like to initialize this drive, erasing all data. YES/NO"
As I have very valuable data please advise me on how you propose to resolve this situation as soon as possible.
Distribution: RHEL, CentOS, Debian, Oracle Solaris 10
Posts: 1,420
Rep:
As deepak said in his post first we have to take a look into your system's /etc/fstab file entries. So boot into rescuemode and post the entries of fstab file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.