Hello i am getting this error in the picture and need help . Can anybody see the attach and help me?

ext3-fs: error loading journal.
mount: error 22 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed: 2
umount /initrd/proc failed: 2
Freeing unused kernel memory: 132k freed
Kernel panic: No init found. Try passing init= option to kernel

You didn't attach anything, so no, we can't see it and help you. And when asking a question, you need to provide details...things like version/distro of Linux, if this EVER worked or not, what you were doing before it failed, what kind of server/system this is, etc.

Wild guess: your hard drive has errors on it, or your fstab file had errors in it.

the error is copy pasted in the post but i will send a jpeg.
this is red hat withkernel 2,4 or 2,3.
I have a ghost file and when i put it in any ide disk with 40 gb or more i install the image and do the configuration and i have no problem.
When i install it in a ide disk with 20 gb it install the ghost image ok but then when it restarts it gives this error.

Attached Thumbnails

 

...which STILL tells us nothing...and which is it, 2.4 or 2.3? What VERSION is it???
Anything with a 2.4 or 2.3 kernel is very, VERY old. What is the reason/purpose for this system, and why can't you upgrade it to something current? Why use a ghost image at all? And if it works on a larger disk, then chances are you're getting error(s) because you're out of space...sort of. From what I remember, Ghost tries to restore the partition tables, so if you have a 20 GB /home partition defined, it will work fine on the larger drive, but the image fails on the smaller.

So:

• Don't use Ghost, when there are better/free alternatives for Linux
• Use a larger hard drive for restore
• Use a CURRENT distribution of Linux

He very likely has a corrupted journal file and needs to run fsck on the filesystem.

...except he doesn't get the maintenance screen, any fsck warnings, and says the system won't boot.

He has to boot a rescue disk, or try the single user mode. Sometimes the fsck utility is on the initrd and can be used from there.

The fsck warnings only occur when fsck runs... it isn't being run. Instead, he got the error "ext3-fs: error loading journal.", which only happens when it is corrupted, thus needing to run fsck. If necessary, it is possible to mount the filesystem "ro,noload" which prevents mount from replaying the journal (which causes the failure), and then running fsck from the disk. Once the fsck completes (assuming no errors - sometimes it is useful for confidence by just running fsck again) a reboot should work normally.