cancel
Showing results for 
Search instead for 
Did you mean: 

Baremetal on RedHat EL5 x86_64

AndreaBolongaro
Level 5
Certified
Hello, 

we'd like to have BMR working for Red hat Enterprise Linux 5 (update 4) x86_64.

We have a BMR boot server on RHEL5 and we created SRT for RHEL5 U4. 
We ran a backup job with BMR option selected  on a test server and now we'd like to restore it from scratch. 

We tried the BMR boot both via network (BMR boot server) and via iso created from SRT with same results:
the BMR screenshot started up but shortly after we have these errors

"mount: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory"

and

"/etc/rc: 23: cannot create /proc/sys/kernel/ctrl-alt-del: Directory nonexistent"

Did anybody have this issue?
Did someone complete a  bmr recovery successfully on RHEL5 x86_64?


Any help is appreciated.

Thank you

Andrea
8 REPLIES 8

AmolV
Level 5
This is a known issue with RHEL5.4 SRTs.
Options for you:
1. If you have RHEL5.0 or .1 or .2 OS media available, create and use those SRTs. (These should work unless your original system had some devices whose drivers are not a part of RHEL5 pre 5.4 kernel.)
2. OR edit the RHEL5 x64 section of /usr/openv/var/global/createsrt.conf to change the glibc and glibc64 parts to ALL.

HTH,
AmolV

AndreaBolongaro
Level 5
Certified
Thank you AmolV, 
I'm going to try it.

There's a public technote for this issue, as far as you know?
I could not find anything so I posted netbackup forum.

Thanks

Andrea

AndreaBolongaro
Level 5
Certified

I edited createsrt.conf  and in SECTION x86_64-RHEL-5.0 (both [CONTENTS-BOOT] 
and [CONTENTS-SRT]) replace the glibc and glibc64 part

from 

glibc       /lib/ld-2.*.so /lib/ld-linux.so.2 /lib/libc-2.*.so \
               /lib/libc.so.6 /lib/libm-2.*.so /lib/libm.so.6 \
              /lib/libdl*
 
glibc64   /lib64/ld-2.*.so /lib64/ld-linux-x86-64.so.2 /lib64/libc-2.*.so \
               /lib64/libc.so.6 /lib64/libm-2.*.so /lib64/libm.so.6 \
               /lib64/libdl*

to 
glibc     ALL
glibc64   ALL

Then, I run SRT creation but job stopped as follow:

 The media repository is now complete.
Working ....................V-125-50 cannot extract file "ALL" from RPM "/usr/openv/netbackup/baremetal/server/data/media/x86_64-RHEL-5.04865/glibc.rpm"
V-125-39 caught exception: runtime error in srtPlat.cpp:ExtractRpmFiles()
[Error] V-125-105 Cannot install operating system onto this SRT.


 

AmolV
Level 5
Thats strange, coz if you note, there are other packages, for which bmrsrtadm extracts "ALL" from them and that has been working just fine.
just on a hunch, did you modify the file, say on windows, and them copy the file to the linux machine? if yes, could you try doing a dos2unix for the file and give it a shot again?

AndreaBolongaro
Level 5
Certified
I edited createsrt.conf file on linux, checked with vi -b for ^M, and dosunixed, but have same issue.

I also tried to change all occurrences under x86_64-RHEL-5.0 in section [CONTENTS-SRT], .i.e.

# essential libraries, also found in the boot image
# these are repeated here to ensure the SRT is a usable chroot filesystem

and

# shared libraries

and

# NSS dynamically loaded shared libraries

without any changes in results. 

I created SRT from RHEL5 x8664 following this technote
http://support.veritas.com/docs/336391
Creation of RedHat Enterprise Linux Shared Resource Tree (SRT) using DVD media.
don't know if this could be the problem. 

Viewing vx log file I have 

01/25/2010 16:28:37.926 [srtPlat.cpp:ExtractedFileExists()] Entering, line=2353, filePathname=/export/srt/EL5U4_x8664/ALL
01/25/2010 16:28:37.926 [fileAttribsCommon.cpp:FileExistsCommon()] Entering, line=41, fileName=/export/srt/EL5U4_x8664/ALL
01/25/2010 16:28:37.926 [fileAttribsCommon.cpp:FileExistsCommon()] Could not do stat on file /export/srt/EL5U4_x8664/ALL
01/25/2010 16:28:37.926 [fileAttribsCommon.cpp:FileExistsCommon()] Exiting, line=60, rc=0
01/25/2010 16:28:37.926 [srtPlat.cpp:ExtractedFileExists()] Exiting, line=2378, return ok=0
01/25/2010 16:28:37.926 V-125-50 [srtPlat.cpp:ExtractRpmFiles()] cannot extract file "ALL" from RPM "/usr/openv/netbackup/baremetal/server/data/media/x86_64-RHEL-5.012811/glibc.rpm"
01/25/2010 16:28:37.949 [srtPlat.cpp:ExtractRpmFiles()] Exiting, line=2475, throwing exception SrtFuncsRunTimeError
01/25/2010 16:28:37.958 V-125-39 [srtPlat.cpp:SrtMkOsImgOk()] caught exception: runtime error in srtPlat.cpp:ExtractRpmFiles()
01/25/2010 16:28:37.959 [srtPlat.cpp:SrtMkOsImgOk()] Exiting, line=632, return BMR_ERROR
01/25/2010 16:28:37.959 [Error] V-125-105 Cannot install operating system onto this SRT.
 

thank you

 

AmolV
Level 5
could you please send me your createsrt.conf file as an attachment either here or via the messaging facility on this site?

AndreaBolongaro
Level 5
Certified
Thank you, AmoIV.
We opened a case with symantec and they told me that, due to changes in RHEL-5.4, 
we need to modify /usr/openv/var/global/createsrt.conf file.

In sections marked
i686-RHEL-5.0
x86_64-RHEL-5.0

in stanza [CONTENTS-BOOT],
the glibc paragraph should read:

# shared libraries used by boot image executables
glibc    /lib/ld-2.*.so /lib/ld-linux.so.2 /lib/libc-2.*.so \
        /lib/libc.so.6 /lib/libm-2.*.so /lib/libm.so.6 \
        /lib/libdl-2.*.so /lib/libdl.so.2 \
        /lib/libnsl-2.*.so /lib/libnsl.so.1 \
        /lib/libpthread-2.*.so /lib/libpthread.so.0 \
        /lib/libresolv-2.*.so /lib/libresolv.so.2 \
        /lib/libdl* /lib/librt*


For the x86_64 architecture, the additional 64 bit library paragraph should look like:

glibc64    /lib64/ld-2.*.so /lib64/ld-linux-x86-64.so.2 /lib64/libc-2.*.so \
          /lib64/libc.so.6 /lib64/libm-2.*.so /lib64/libm.so.6 \
          /lib64/libdl-2.*.so /lib64/libdl.so.2 \
          /lib64/libnsl-2.*.so /lib64/libnsl.so.1 \
          /lib64/libpthread-2.*.so /lib64/libpthread.so.0 \
          /lib64/libresolv-2.*.so /lib64/libresolv.so.2 \
          /lib64/libdl* /lib64/librt*

After making the file modifications to createsrt.conf, you will need to create a new SRT to use for client restores.


That's solved the issue.

Bye, 

Andrea


AmolV
Level 5
Ok, I have found what the problem with the "ALL" that you are using is.
So in the CONTENTS-BOOT section, glibc & glibc64 appears only once, so using ALL there is ok.
But in the next section, i.e. the CONTENTS-SRT section, it appears 2-3 times with different file selection.
So once you change one of them to ALL, you need to comment/delete the other occurrences.
I tried it on my setup and I was able to hit your problem.

And yes, the above approach suggested by support too would work and hopefully, RHEL wont change any dependencies in the next RHEL5 update, otherwise newer libraries would have to be extracted from the RPM. The benefit of using ALL is that such a problem is avoided, but yeah, on the negative side, the size of your SRT and the boot image increases a bit.