This content has been marked as final. Show 17 replies
I booted the OS from Linux installation DVD ans started in resuce mode.
Now when i run fsck, it says /etc/fstab is not found
no such file or directory.
i have /sbin/init file, /etc/passwd
The worst thing is we do not have back up for this OS.
Edited by: EBSDBA on Mar 21, 2012 3:36 PM
try the following:
Boot the system from DVD. At the boot prompt type "linux rescue"
It will prompt for language, keyboard, network.
When it prompts you to find your Linux installation, select "skip".
At shell prompt type:
Find the boot and root partition of your system.
<pre>fsck -fy /dev/sda1</pre>
If you installed your system with LVM you need to load it first and locate your volume:
Notice the output of volume groups found
<pre>lvm lvchange -ay VolGroup00</pre>
<pre>fsck -fy /dev/VolGroup00/LogVol00</pre>
Don't wory about /etc/fstab. The fsck command will check the filesystem inodes, etc.
Then reboot again into rescue mode, this time let it find your Linux installation and select "continue"
If you cd to /mnt/sysimage you should see the content of your root volume. Check it and see what's missing and report back.
Thanks for the reply and sorry for late reply as i was preparing the other server.
I had real bad experience with fsck in the past.
Kindly please let me know if this fsck with -fy going to corrupt in extreme cases.
We do not have VLM.
So i have to execute
#fsck -fy /dev/sda1
I just typed the Device and Boot (the one with *). I could type the rest info.
And so on.
Device Boot start end blocks id system /dev/cciss/c0d0p1 * 1 2611 20972826 83 linux /dev/cciss/c0d0p2 2612 6788 xxxxx 82 linux swap/solaris /dev/cciss/c0d0p3 6788 8746 xxxxx 83 linux /dev/cciss/c0d0p4 xxxxx xxxxx xxxxx 5 Extended /dev/cciss/c0d0p5
Edited by: EBSDBA on Mar 21, 2012 7:42 PM
exec of /sbin/init failed: No such file or directoryThis usually means the kernel cannot find its root file system (/). Probably the initial ramdisk (initrd) does not have the device drivers for your root file system.
kernel panic, Not syncing :Attempting to kill init!
Where do you keep your (/)? A local disk? Multipathed SAN?
I suspect your multipath setup is not right, so the stuff in the initrd does not recognize your multipaths, so it doesn't see your root file system.
Boot into rescue mode, and notice how it locates your root partition. Then you'll likely need to edit "/etc/multipath.conf" or "/etc/lvm/lvm.conf", then rebuild the initrd file.
Since your boot and root volume are supposedly on the same disk I would not suspect a driver problem with your initrd image, unless I guess your underlying file system configuration was changed. I suggest to mount the file system and check the /sbin /bin, etc. directories and verify they contain the necessary files. Also check file and directory permissions. If any files are missing you can copy them from the rescue DVD.
I did mount the file system and i can access everything in all the mountpoints, like
I suggest to mount the file system and check the /sbin /bin, etc. directories and verify they contain the necessary files. Also check file and directory permissions.
verify they contain the necessary files.How do i verify it contains all necessary files
The system was working fine. All of a sudden it got crashed.
When i run
It thows /bin/sh no such file or directory.
Also i cannot find boot folder in /