Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
Distribution: Anything NOT SystemD (ie. M$) related.
Posts: 918
Rep:
Have you changed any kernel or initrds lately.. although not being able to chroot should partly cast aside this assumption.
This sounds like a fs error possibly.. how about that.. what fs is it.. ext3/4?
Have you fsck -VC it?
Was it working before.. because it sounds like something got trashed (or deleted).. but since you can't even chroot.. I suspect a fs error.. but I could be wrong.
/mnt/sysimage is mainly used for installs, unless you have set it up that way.
/ is not where you think it is. So your line
kernel somekernel root=somedrive is wrong,
When the kernel is loaded, the system mounts / and then runs /sbin/init. Now it is finding what you call / but it is not /, because /sbin/init or /bin/sh cannot be found. Post your grub.conf and we can get you out of this.
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux AS (2.6.9-42.ELsmp)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.ELsmp ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.9-42.ELsmp.img
title Red Hat Enterprise Linux AS-up (2.6.9-42.EL)
root (hd0,0)
kernel /vmlinuz-2.6.9-42.EL ro root=LABEL=/1 rhgb quiet
initrd /initrd-2.6.9-42.EL.img
I dont think there is something wrong in grub.conf because I've already matched with other servers.
I've had trouble with those label things before. Do you know what partition / is on? Edit that line; when grub comes up hit e twice, and you should get an editor of sorts. change that to root=/dev/sdax where x is the number of your / partition. Return to finish, and b to boot it.
checked with root=/dev/sda3 (my / drive) in grub.conf .. but still giving same error ..
I tried with making new initrd file but it says /lib/module .. no such file or dir.
I tried copying bash also (may be the bash giving the error ) ..
cp /usr/bin/bash /mnt/sysimage/bin/bash .. but was not useful.
while booting it gives
exec of init (/sbin/init) failed!!!: 2
umount /inited/dev failed: 2
kernel panic - not syncing: Attemped to kill init!
That's your latest post. "umount /inited/dev failed" looks like a typo has got in - inited??
In post #3, I pointed out
Quote:
/ is not where you think it is. So your line
kernel somekernel root=somedrive is wrong,
Because of this, it can't find /bin/sh or /sbin/init. get rid of that label= thing in grub.conf, because you can have 2 partitions called label=/1 and then the fun really starts. Believe me, I've had it!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.