How to by pass Veritas Volume Manager drivers and daemons during system startup to troubleshoot system boot issues on Solaris 10

book

Article ID: 100038004

calendar_today

Updated On:

Description

Description

1. Boot system using following option

ok boot -m milestone=none

Probing system devices
Probing memory
Probing I/O buses

 

Rebooting with command: boot -m milestone=none
Boot device: /pci@1c,600000/scsi@2/disk@1,0  File and args: -m milestone=none
SunOS Release 5.10 Version Generic_147440-06 64-bit
Copyright (c) 1983, 2011, Oracle and/or its affiliates. All rights reserved.
Hardware watchdog enabled
Booting to milestone "none".
Requesting System Maintenance Mode
(See /lib/svc/share/README for more information.)
Console login service(s) cannot run  

2. Login as root user

Root password for system maintenance (control-d to bypass):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode Jan 16 09:59:33 su: 'su root' succeeded for root on /dev/console
Oracle Corporation      SunOS 5.10      Generic Patch   January 2005

3. Check currently mounted file systems

  # df -k
Filesystem            kbytes    used   avail capacity  Mounted on
/pci@1c,600000/scsi@2/disk@1,0:a
                     10326652 6330612 3892774    62%    /
/devices                   0       0       0     0%    /devices
ctfs                       0       0       0     0%    /system/contract
proc                       0       0       0     0%    /proc
mnttab                     0       0       0     0%    /etc/mnttab
swap                 4193920    1792 4192128     1%    /etc/svc/volatile
objfs                      0       0       0     0%    /system/object
sharefs                    0       0       0     0%    /etc/dfs/sharetab

4. By default, "boot -m milestone=none" command will mount root file system in read-only mode

 

5. Mount root file system in read-write mode as follow

  # mount -o remount,rw /

6. Mount other file system on rootdisk as follows

e.g.

  # mount /var

7. Check mounted file systems again

# df -k |grep dsk
/dev/dsk/c1t1d0s0    10326652 6330612 3892774    62%    /
/dev/dsk/c1t1d0s3    3316290 1211942 2071186    37%    /var

8. After this troubleshoot VxVM boot issue depending on nature of failure

e.g.
a) Disable VxVM during startup by touching following file

  #touch /etc/vx/reconfig.d/state.d/install-db

b) Un-encapsulate rootdisk

c) Remove VRTSvxvm package etc ...

Issue/Introduction

How to by pass Veritas Volume Manager drivers and daemons during system startup to troubleshoot system boot issues on Solaris 10
Powered by Wolken Software