http://www.symantec.com/business/support/index?page=content&id=HOWTO58833
-
A kernel patch caused the machine to panic, leaving it in a confused state. I was able to boot from a CD and back out the patch, but it did not update the boot archive, even after issuing
/sbin/bootadm update-archive -R /ato fix:
Boot into the disk failsafe, then run:
/a/boot/solaris/bin/create_ramdisk -R /a
-
/usr/sbin/flarcreate -cSn “some comment” -a “some_email@somewhere.com” -R / -X /root/exclude_from_flar.txt /path/to/archive.flar
without the ‘-a’ the flar install will fail with the error: “ERROR: Could not find archive”
-
ksh -o vi
export TERM=vt100
/usr/openwin/bin/resize
or, If booted from CD or in failsafe:
/a/usr/openwin/bin/resize -
column
select inst_id,opname, totalwork, sofar, time_remaining from gv$session_longops where totalwork > sofar order by time_remaining; -
export DG=SOME-DG clear; for i in `vxprint -ht -g ${DG}|grep DISA| grep ^pl | awk '{print $2}'`; do echo "vxmend -g ${DG} fix stale $i" echo "vxmend -g ${DG} fix clean $i"; done vxvol -g ${DG} startall -
# add volume definition
hares -add SRVS-vol8 Volume SRVS-SG
hares -modify SRVS-vol8 Critical 0
hares -modify SRVS-vol8 DiskGroup cjprd
hares -modify SRVS-vol8 Volume cjprd-vol8
hares -modify SRVS-vol8 Enabled 1
hares -link SRVS-vol8 SRVS-dg 0 0# Add mount definition
hares -add SRVS-odbf4 Mount SRVS-SG
hares -modify SRVS-odbf4 Critical 1
hares -modify SRVS-odbf4 SnapUmount 0
hares -modify SRVS-odbf4 CkptUmount 1
hares -modify SRVS-odbf4 SecondLevelMonitor 0
hares -modify SRVS-odbf4 SecondLevelTimeout 30
hares -modify SRVS-odbf4 MountPoint /cjprd/odbf4
hares -modify SRVS-odbf4 BlockDevice /dev/vx/dsk/cjprd/cjprd-vol8
hares -modify SRVS-odbf4 FSType vxfs
hares -modify SRVS-odbf4 MountOpt
hares -modify SRVS-odbf4 FsckOpt -y
hares -modify SRVS-odbf4 Enabled 0
hares -modify SRVS-odbf4 Critical 0
hares -modify SRVS-odbf4 Enabled 1
hares -link SRVS-odbf4 SRVS-vol8 0 0hares -modify SRVS-odbf4 Critical 1
hares -link SRVS-odbf4 SRVS 0 0
hares -modify SRVS-vol8 Critical 1
haconf -dump -
Problem: not able to connect to the console
-> start /CH/BL1/SP/cli
Are you sure you want to start /CH/BL1/SP/cli (y/n)? y…just hangs indefinitely
Solution: We need to reset the serial port to the blade.
-> reset /CH/BL1/SP
Are you sure you want to reset /CH/BL1/SP (y/n)? y
Performing hard reset on /CH/BL1/SP-> start cli
Are you sure you want to start /CH/BL1/SP/cli (y/n)? y… connects successfully to the console now.
-
ETHTOOL_OPTS=”autoneg off speed 100 duplex full”
Category:
- Administration
- APPS
- Articles
- Backup & Recovery
- Certification
- Configuration
- DATABASE STRUCTURE
- DATAGUARD
- Documentation
- EBS
- Enterprise Manager
- FLASHBACK
- HACKING
- HEADS UP
- Installation
- JDeveloper
- Linux
- Monitoring
- MQ
- NFS
- NXclient/server
- Online Resources
- PERL
- python
- RMAN
- Routing & Switching
- SAN – NAS
- Scripts
- Serial-Parallel-Port-Testers
- SNMP
- Software
- Solaris
- Spiritual
- SQL & PL/SQL
- SQLPLUS
- Startup/Shutdown
- Streams
- Tuning
- Version Control
- Vertias
- VMWare
- VNC
- Windows XP
- ZFS





