Upgrade VxVM 5.0 to VxVM 5.1
Hi
I have successfuly upgraded the VxVM from 5.0 to VxVM 5.1 ..
But during reboot I am getting given below error .
VxVM sysboot NOTICE V-5-2-3410 upgrade was not completed
configuring IPv4 interfaces: eri0 qfe0.
Hostname: sundev1
VxVM NOTICE V-5-2-3369 VxVM upgrade was not completed
WARNING: /pci@9,600000/lpfc@1/fp@0,0/ssd@w50060482cc19c1ec,0 (ssd131):
Corrupt label; wrong magic number
WARNING: /pci@9,600000/lpfc@1/fp@0,0/ssd@w50060482d52de668,0 (ssd141):
Corrupt label; wrong magic number
WARNING: /pci@9,600000/lpfc@2/fp@0,0/ssd@w50060482d52de647,0 (ssd277):
Corrupt label; wrong magic number
WARNING: /pci@9,600000/lpfc@2/fp@0,0/ssd@w5006048acc19c1d3,0 (ssd267):
Corrupt label; wrong magic number
VxVM NOTICE V-5-2-3369 VxVM upgrade was not completed
The system is coming up. Please wait.
checking vxfs filesystems
Running parallel replay fsck ...
UX:vxfs fsck: ERROR: V-3-20003: /dev/vx/rdsk/fsdg01/localvol:Cannot open /dev/vx/rdsk/fsdg01/localvol: No such device or address
UX:vxfs fsck: ERROR: V-3-20003: /dev/vx/rdsk/flashdg/flash01:Cannot open /dev/vx/rdsk/flashdg/flash01: No such device or address
UX:vxfs fsck: ERROR: V-3-20003: /dev/vx/rdsk/orafsdg03/db03:Cannot open /dev/vx/rdsk/orafsdg03/db03: No such device or address
I am starting vxconfigd daemon manually and starting all the volumes and mounting file system manually.
Any idea what could be the reason ...
Thansk
Sukrut S
Comments
See if you can find the
See if you can find the reason for:
VxVM NOTICE V-5-2-3369 VxVM upgrade was not completed
in the installation log: /opt/VRTS/install/logs/installer#######.log
This (old) TN http://www.symantec.com/business/support/index?pag... describes a situation where upgrade _finish did not complete successfully, leaving behind .start_runed.
Supporting Storage Foundation and VCS on Unix and Windows as well as NetBackup on Unix and Windows.
Handy NBU links
How was the product upgraded?
Hi Sukrut,
Can you share with us how you've performed the upgrade?
As Marianne explained, the message is reported because upgrade_finish was not run after upgrade_start.
Check for directory /VxVM## directory, if present rename it. If you haven't configured the product yet,
try # vxinstall to configure VxVM.
Regards
Srini
Would you like to reply?
Login or Register to post your comment.