Hi All,
Anyone knows to back normal boot?
configuring IPv4 interfaces: ce0.
Hostname: jkt-db01
VxVM INFO V-5-2-3247 starting special volumes ( exportvol )...
mount: /dev/dsk/c1t0d0s0 is not this fstype.
/sbin/rcS: /etc/dfs/sharetab: cannot create
failed to open /etc/coreadm.conf: Read-only file system
Configuring /dev and /devices
devfsadm: mkdir failed for /dev 0x1ed: Read-only file system
devfsadm: open failed for /dev/.devfsadm_dev.lock: Read-only file system
Configuring the /dev directory (compatibility devices)
VxVM vxvm-startup2 INFO V-5-2-503 VxVM general startup...
Nov 7 22:32:53 vxvm:vxconfigd: V-5-1-7601 vxvm:vxconfigd: ERROR: Could not open file /etc/vx/array.info for writing
Nov 7 22:32:53 vxvm:vxconfigd:
rm: Unable to remove directory /var/vxvm/tempdb: Read-only file system
Nov 7 22:32:55 vxvm:vxconfigd: V-5-1-1589 enable failed: Error in disk group configuration copies
Nov 7 22:32:55 vxvm:vxconfigd: System error in configuration copy; transactions are disabled.
/etc/rcS.d/S85vxvm-startup2: /etc/vx/.vxesd.lock: cannot create
VxVM vxesd ERROR V-5-1-8405 Duplicate daemon check failed
dumpadm: failed to open /etc/dumpadm.conf: Read-only file system
VxVM vxvm-startup2 ERROR V-5-2-3656 Vold is not enabled for transactions
No volumes started
UX:vxfs qlogrec: ERROR: V-3-22653: Cannot open file /etc/qlog/config.lock
UX:vxfs qlogrec: ERROR: V-3-22695: Problem writing file /etc/qlog/config.lock: Bad file number
UX:vxfs qlogck: ERROR: V-3-22653: Cannot open file /etc/qlog/config.lock
UX:vxfs qlogck: ERROR: V-3-22695: Problem writing file /etc/qlog/config.lock: Bad file number
UX:vxfs qlogck: TO FIX: V-3-22842: Command qlogck was not successful
UX:vxfs qlogck: WARNING: V-3-25613: Fix whatever problem was encountered and rerun
the command qlogck
Running the command qlogck with the -f option
will fix most of the problem(s) but will force
a full consistency check (full fsck)
on the VxFS volume(s) which cannot be fixed.
The QuickLog routine 'qlogck' encountered the errors mentioned above. It is
recommended that you enter the maintenance shell and attempt to correct
these problems. Once all possible corrections have been made, enter
Control-d to exit the maintenance shell, and initialization will resume.
See qlogck(1M) for assistance.
Type control-d to proceed with normal startup,
(or give root password for system maintenance):
Resuming initialization
UX:vxfs qlogck: ERROR: V-3-22653: Cannot open file /etc/qlog/config.lock
UX:vxfs qlogck: ERROR: V-3-22695: Problem writing file /etc/qlog/config.lock: Bad file number
UX:vxfs qlogck: TO FIX: V-3-22842: Command qlogck was not successful
UX:vxfs qlogck: WARNING: V-3-25613: Fix whatever problem was encountered and rerun the command qlogck
Running the command qlogck with the -f option
will fix most of the problem(s) but will force
a full consistency check (f-22653: Cannot open file /etc/qlog/config.lock
UX:vxfs qlogattach: ERROR: V-3-22695: Problem writing file /etc/qlog/config.lock: Bad file number
INIT: Cannot create /var/adm/utmpx
INIT: failed write of utmpx entry:" "
INIT: failed write of utmpx entry:" "
INIT: SINGLE USER MODE
Thank you
Zainal
