Reservation-Conflict

From pressy's brainbackup
Jump to: navigation, search

Reservation Conflict

Boot device: /pci@1f,700000/scsi@2/disk@0,0  File and args: -s -x
SunOS Release 5.10 Version Generic_125100-09 64-bit
Copyright 1983-2007 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Hardware watchdog enabled
Indicator SYS.ACT is now ON
Booting to milestone "milestone/single-user:default".
Failed to configure IPv4 interface(s): ce1
Hostname: server
Not booting as part of a cluster
Nov 25 12:50:50 svc.startd[7]: system/cluster/initdid:default transitioned to maintenance by request (see 'svcs -xv' for details)
Requesting System Maintenance Mode
SINGLE USER MODE

Root password for system maintenance (control-d to bypass):
single-user privilege assigned to /dev/console.
Entering System Maintenance Mode

Nov 25 12:50:54 su: 'su root' succeeded for root on /dev/console
Sun Microsystems Inc.   SunOS 5.10      Generic January 2005
Sourcing //.profile-EIS.....
# /usr/cluster/lib/sc/scsi -c scrub -d /dev/rdsk/c5t60060E8005435500000043550000063Bd0s2
Reservation keys currently on disk:
0x41e7951600000002
0x41e7951600000001
Attempting to remove all keys from the disk...
Scrubbing complete, use '/usr/cluster/lib/sc/scsi -c inkeys -d /dev/rdsk/c5t60060E8005435500000043550000063Bd0s2' to verify success
# reboot