Hi All,

I have taken the mondo backup of my linux server running with version Red Hat Linux Advanced Server release 2.1AS (Derry) .And when i am trying to boot it from the mondo image i am getting below error and system get hung.I tried all options like nuke, interactive,expert but getting same error with all options. Can some help me here to solve the issue.

Error
=========
kernel panic vfs unable to mount root fs on 01:00

Command i am using to create iso of mondo is below.

/usr/sbin/mondoarchive -NOi -7 -s 2g -p linux-1309061105 -T /dump/tmp -S /dump/scratch -d /dump/linux-1309061105 -E /u01


Thanks in advance!!!!!

From the Mondorescue FAQ:
http://trac.mondorescue.org/wiki/FAQ...yatarchivetime

And you're using a very, VERY old version of Red Hat Enterprise...since you're PAYING for RHEL, have you contacted them for assistance? This has been suggested to you MANY times now, in your other threads about RHEL. Asked what they would recommend for doing bare-metal recovery? RHEL2 has been end-of-life since 2009. At this point, you'd be much better served by NOT restoring such an old system, but updating instead, and moving forward.

1 members found this post helpful.

Hi TB0ne,

Thanks for your reply.

Redhat is not supporting this version of the redhat as it is very old version of redhat. We have some of the servers running with this version. So can you please suggest the solution to this problem.

I will be thankful to you if help me here.

Thanks

Did you read what was posted? Did you read the link to the Mondorescue page? Where it TELLS YOU how to fix such issues? Did you actually try/do anything suggested there??

And the best suggestion anyone can make for an old, unsupported operating system is UPGRADE IT to the latest version that IS supported.

Hi TBone,

Thanks for reply.

I tried all the option suggested in the link which you provided me and i am still getting the same error when i booting from the iso image.

Below are the changes i made in the first mindi.conf and after that it did not work then i made changes mindi binary as suggested in the link one by one but none of them works.

1) ADDITIONAL_BOOT_PARAMS="acpi=ht apm=off devfs=nomount noresume selinux=0 barrier=off"
2) ADDITIONAL_BOOT_PARAMS="apm=off devfs=nomount noresume selinux=0 barrier=off" .

Can you please suggest any other link or options which i can try without upgrading the OS.
Thanks

There was nothing, anywhere, telling you to change the 'mindi binary'...what are you talking about?? And the "acip=ht" was to be used stand-alone, not in conjunction with the other parameters. Try that
No, but you're free to do your own searching. There is a reason people pay for subscriptions to Red Hat Enterprise...addressing bugs/incompatibilities like this is one of them. Also, how did you install the package(s)? From source or from RPM? Were ALL of the dependencies satisfied?

Again, you're using an old, unsupported OS. PAY FOR RED HAT ENTERPRISE, or don't use it, and load CentOS instead. It's free, and will give you updates/patches as well.

1 members found this post helpful.

Hi Tbone,

I have installed the package via rpm.

Below are the dependent packages which are installed on the server.

[root@linux root]# rpm -qa|grep mondo
mondo-2.2.9.4-1.rhel2.1
[root@linux root]# rpm -qa|grep mindi
mindi-busybox-1.7.3-1.rhel2.1
mindi-2.0.7.5-1.rhel2.1
[root@linux root]# rpm -qa|grep afio
afio-2.4.7-1
[root@linux root]# rpm -qa|grep gzip
gzip-1.3-18.rhel2



I tried the acpi=ht option and that option also does not make any difference to the problem. Also redhat is not supporting mondo tool because it is not their tool . So can you please suggest the solution to this problem. Or suggest any other online tool to take the OS backup of the linux server where we need to bring the server down. It would be really helpful if the tool can create the iso image same as that of mondo.


Thanks

Which is not surprising. And you seem to have ignored my very first reply, which points out that RHEL2 is ANCIENT, unsupported, and insecure. If you ran a CURRENT VERSION OF RHEL, you probably wouldn't have this problem.
Nope, sorry...you didn't call Red Hat support, since there is NO WAY RHEL2 is still UNDER Red Hat support.
I already DID suggest a solution, but you ignored it. DO NOT reload the old RHEL...back up your data, and do a fresh install of the CURRENT version of RHEL if the system dies. Get up to date, and in support. That's your best solution.

Barring that, we can also suggest you look at Google, or use the search function on this site. This question has been asked and answered many, MANY times. Things like systemimager and mkcdrec are both available and similar to mondoarchive. But again, they will probably not work correctly, since your system is so old and unsupported.

1 members found this post helpful.

Another backup option is Clonezilla (cold backup I believe), but the ultimate problem is you are running a very old system that eg has many security holes that will never be fixed.
You really do need to get a current OS before the HW breaks, as that OS will not run on current HW, because the drivers are not available.

1 members found this post helpful.

Hi Tbone,

I tried the mkcdrec option but this also did not work . So can you please suggest any other such tool which i can use to take the live Linux os backup.

I am really thankful for your help which you did for me till now.

Thanks a lot!!!!!!!!

...and since you don't tell us what you mean by "did not work", there's not much we can tell you.
Please try to read/understand ALL of what people tell you, and go back and re-read my previous posts.

AGAIN, since you have missed/ignored it previously:

• This has been asked and answered MANY times on this site. Search for the topic.
• You were given two options, mkcdrec and systemimager were there, and you tried ONE. Did you try the other?
• You were given clonezilla as an option...did you try that?
• You have been REPEATEDLY TOLD that you're most likely having problems because your version of Linux is ANCIENT. DO NOT reload it...upgrade it. And PAY FOR SUPPORT if you're going to use RHEL.

Read EACH POINT carefully.