07-28-2008 09:43 PM
I'm trying to build a test box (in VMWare Server) which will run Storage Foundation. The VM has RHEL 4 Update 1 (also tried Update 7 to no avail) and I'm running into an error during SF's installation which doesn't seem to make any sense. The error message seen during installation is below:
Installing VRTSvxvmcommon 4.1.00.10 on rhel4-1 .... ERROR 4 of 41 steps
error: %pre(VRTSvxvm-common-4.1.00.10-GA_RHEL4.i686) scriptlet failed, exit
status 1
error: install: %pre scriptlet failed (2), skipping
VRTSvxvm-common-4.1.00.10-GA_RHEL4
error: %pre(VRTSvxvm-common-4.1.00.10-GA_RHEL4.i686) scriptlet failed, exit
status 1
error: install: %pre scriptlet failed (2), skipping
VRTSvxvm-common-4.1.00.10-GA_RHEL4
error: %pre(VRTSvxvm-common-4.1.00.10-GA_RHEL4.i686) scriptlet failed, exit
status 1
error: install: %pre scriptlet failed (2), skipping
VRTSvxvm-common-4.1.00.10-GA_RHEL4
CPI WARNING V-9-0-0 Could not add
VRTSvxvm-common-4.1.00.10-GA_RHEL4.i686.rpm rpm to rhel4-1
When I tried to manually add the rpm this happens:
# rpm -i VRTSvxvm-common-4.1.00.10-GA_RHEL4.i686.rpm
This package is not built for athlon processors. Exiting.
error: %pre(VRTSvxvm-common-4.1.00.10-GA_RHEL4.i686) scriptlet failed, exit status 1
error: install: %pre scriptlet failed (2), skipping VRTSvxvm-common-4.1.00.10-GA_RHEL4
Running rpm with the vv option gives me a little insight into what is happenning:
# rpm -ivv VRTSvxvm-common-4.1.00.10-GA_RHEL4.i686.rpm
D: ============== VRTSvxvm-common-4.1.00.10-GA_RHEL4.i686.rpm
D: Expected size: 11911116 = lead(96)+sigs(180)+pad(4)+data(11910836)
D: Actual size: 11911116
D: VRTSvxvm-common-4.1.00.10-GA_RHEL4.i686.rpm: MD5 digest: OK (b9d250b3891680d625d94dc62b169b13)
D: added binary package [0]
---------------------------------------------------
------truncated to show the interesting part-------
---------------------------------------------------
++ uname -m
+ machine=i686
++ uname -p
+ processor=athlon
++ uname -r
+ kern_version=2.6.9-11.EL
++ echo 2.6.9-11.EL
++ cut -d - -f 1
+ short_kern_version=2.6.9
+ '[' i686 '!=' i686 -a i686 '!=' ia64 -a i686 '!=' x86_64 ']'
+ '[' athlon '!=' i686 -a athlon '!=' ia64 -a athlon '!=' x86_64 ']'
+ BADPROC=1
+ '[' athlon = athlon ']'
+ cat /proc/cpuinfo
+ grep Opteron
+ '[' 1 -eq 0 ']'
+ '[' 1 -ne 0 ']'
+ echo 'This package is not built for athlon processors. Exiting.'
+ /usr/bin/tee -a /etc/vx/.cpi_vm_rpm_msg
This package is not built for athlon processors. Exiting.
+ exit 1
--------------end of the interesting part------------
Following is the uname -a output:
# uname -a
Now the installation guide says the following:
Supported Linux Operating Systems
The VERITAS 4.1 release operates on the following operating systems and hardware:
◆ Red Hat Enterprise Linux 4 (RHEL 4) Update 1 (2.6.9-11 kernels) x86 (32-bit), Xeon (32-bit, 64-bit), Opteron (32-bit, 64-bit), IA64
◆ SUSE Linux Enterprise Server 9 (SLES 9) with SP1 (2.6.5-7.139 and 2.6.5-7.145 kernels) x86, x86-64 (32-bit and 64-bit modes), IA64
Now my questions are:
-What is so different between Athlon and Opteron that Veritas/Symantec decided to hardcode the installation on Opteron?
- How do I bypass this since running on Athlon or Opteron shouldn't in all essence make any difference to SF?
Solved! Go to Solution.
01-08-2010 08:28 AM
07-29-2008 03:05 AM
08-11-2008 11:10 AM
01-08-2010 07:06 AM
01-08-2010 08:28 AM