cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Veritas.com
Support

Upgrade of Veritas Foundation 5.0 to 5.1 system will not boot

rr3320
Not applicable

‎03-09-2012 07:18 AM

All, I upgraded a Solaris 9 SPARC system from 5.0 to 5.1 using the recommended option inside the installer.  it stated that it completed and to reboot the system.  On reboot, the system could not mount /var as there is no such device or address  vxprint -ht shows the  var  volume started but i cannot fsck them which is confusing,  i cannot fsck it as there is no such device or address but it shows in vxprint..

v  var          -            ENABLED  ACTIVE   4202688  ROUND     -        fsgen
pl var-01       var          ENABLED  ACTIVE   4202688  CONCAT    -        RW
sd rootdisk-04  var-01       rootdisk 18886655 4202688  0         disk_2   ENA
pl var-02       var          ENABLED  ACTIVE   4202688  CONCAT    -        RW
sd altroot-03   var-02       altroot  18886656 4202688  0         disk_0   ENA

VxVM sysboot INFO V-5-2-3390 Starting restore daemon...
configuring IPv4 interfaces: bge0 bge3.
Hostname: mdsuawo0j
VxVM  INFO V-5-2-3247 starting special volumes ( swapvol rootvol var opt home )...
/dev/vx/dsk/bootdg/swapvol: No such device or address
The /var file system (/dev/vx/rdsk/bootdg/var) is being checked.
Can't open /dev/vx/rdsk/bootdg/var: No such device or address
/dev/vx/rdsk/bootdg/var: CAN'T CHECK FILE SYSTEM.
/dev/vx/rdsk/bootdg/var: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

WARNING - Unable to repair the /var filesystem. Run fsck
manually (fsck -F ufs /dev/vx/rdsk/bootdg/var). Exit the shell when
done to continue the boot process.
 

0 Kudos
2 REPLIES 2

Yasuhisa_Ishika
Level 6
Partner Accredited Certified

‎03-11-2012 06:04 PM

Can you gather and post following information?

  • complete output of "vxprint -htr"
  • /etc/system
  • /etc/vx/volboot
  • /etc/vfstab

If you need to boot this system immediately, try to un-encapsulate as below.

  • Comment out the 2 lines in the /etc/system file
    rootdev:/pseudo/vxio@0:0
    set vxio:vol_rootdev_is_volume=1
  • Edit /etc/vfstab to change each disk devices to native slice form.(/dev/dsk/cXtXdXsX, /dev/rdsk/cXtXdXsX)
0 Kudos

Gaurav_S
Moderator
Moderator
   VIP    Certified

‎03-30-2012 09:55 PM

Question:

How did you ran upgrade ? Did you detach the mirror (Safe copy) , unencapsulate & then upgrade on one disk, then re-encapsulate ?

Have you followed the upgradge procedure from guide ?

https://sort.symantec.com/public/documents/sf/5.1/solaris/html/sf_install/ch11.htm

Secondly, on the basic, are your physical disks OK ? do they have any hard errors/ transport errors displayed in OS ?

Also, one more point, was upgrade executed from single user more or multiuser mode ?

 

Gaurav

0 Kudos