Tiba-tiba saja salah satu server Solaris di kantor mati mendadak, dan ketika dicoba dihidupkan power nya, dan tidak bisa masuk ke OS nya, padahal IP nya bisa di ping, namun tidak bisa di remote, akhirnya saya memutuskan untuk melakukan console ke server nya langsung dan ternyata benar saja OS nya seperti masuk ke single mode :
Type control-d to proceed with normal startup,
(or give root password for system maintenance):
Saya coba tekan control-d untuk boot normal dan mucul error seperti ini :
resuming system initialization
mount: the state of /dev/vx/dsk/bootdg/rootvol is not okay
and it was attempted to be mounted read/write
mount: Please run fsck and try again
/sbin/rcS: /etc/dfs/sharetab: cannot create
failed to open /etc/coreadm.conf: Read-only file system
chmod: WARNING: can't change /kernel/drv/rdriver.conf
chown: /kernel/drv/rdriver.conf: Read-only file system
chgrp: /kernel/drv/rdriver.conf: Read-only file system
VxVM vxvm-startup2 INFO V-5-2-503 VxVM general startup...
May 2 11:01:47 vxvm:vxconfigd: V-5-1-7601 vxvm:vxconfigd: ERROR: Could not open file /etc/vx/array.info for writing
May 2 11:01:47 vxvm:vxconfigd: V-5-1-11219 vxvm:vxconfigd: ERROR: Failed to open file /etc/vx/disk.info.new
May 2 11:01:48 vxvm:vxconfigd: V-5-1-1589 enable failed: Error in disk group configuration copies
May 2 11:01:48 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
May 2 11:02:15 vxvm:vxconfigd: V-5-1-7601 vxvm:vxconfigd: ERROR: Could not open file /etc/vx/array.info for writing
May 2 11:02:17 vxvm:vxconfigd: V-5-1-1589 enable failed: Error in disk group configuration copies
May 2 11:02:17 vxvm:vxconfigd: System error in configuration copy; transactions are disabled.
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):
Akhirnya saya masukan password root OS nya dan kemudian pertama kali saya coba cek dulu mount disk di file etc/vstab nya :
bash-2.05# more /etc/vstab
/etc/vstab: No such file or directory
bash-2.05# more /etc/vfstab
#device device mount FS fsck mount mount
#to mount to fsck point type pass at boot options
#
fd - /dev/fd fd - no -
/proc - /proc proc - no -
/dev/vx/dsk/bootdg/swapvol - - swap - no nologging
/dev/vx/dsk/bootdg/rootvol /dev/vx/rdsk/bootdg/rootvol / ufs 1 no nologging
/dev/vx/dsk/bootdg/home /dev/vx/rdsk/bootdg/home /export/home ufs 2 yes nologging
swap - /tmp tmpfs - yes -
#NOTE: volume rootvol () encapsulated partition c0t0d0s0
#NOTE: volume swapvol () encapsulated partition c0t0d0s1
#NOTE: volume home () encapsulated partition c0t0d0s6
Kemudian saya coba jalankan fsck :
bash-2.05# fsck -y /dev/vx/dsk/bootdg/rootvol
** /dev/vx/rdsk/bootdg/rootvol
** Last Mounted on /
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3a - Check Connectivity
** Phase 3b - Verify Shadows/ACLs
** Phase 4 - Check Reference Counts
UNREF FILE I=224826 OWNER=root MODE=100664
SIZE=41147 MTIME=Jun 14 17:09 2013
RECONNECT? yes
LINK COUNT FILE I=224826 OWNER=root MODE=100664
SIZE=41147 MTIME=Jun 14 17:09 2013 COUNT 0 SHOULD BE 1
ADJUST? yes
UNREF FILE I=226829 OWNER=root MODE=100664
SIZE=5242850 MTIME=Jun 15 10:30 2013
RECONNECT? yes
LINK COUNT FILE I=226829 OWNER=root MODE=100664
SIZE=5242850 MTIME=Jun 15 10:30 2013 COUNT 0 SHOULD BE 1
ADJUST? yes
UNREF FILE I=226830 OWNER=root MODE=100664
SIZE=1682730 MTIME=Jun 14 17:09 2013
RECONNECT? yes
LINK COUNT FILE I=226830 OWNER=root MODE=100664
SIZE=1682730 MTIME=Jun 14 17:09 2013 COUNT 0 SHOULD BE 1
ADJUST? yes
** Phase 5 - Check Cylinder Groups
197574 files, 16418504 used, 14562566 free (142830 frags, 1802467 blocks, 0.5% fragmentation)
***** FILE SYSTEM WAS MODIFIED *****
Setelah selesai fsck, maka tinggal di restart saja OS nya :
bash-2.05# reboot
syncing file systems... done
rebooting...
Resetting ...
Setelah restart, maka saat ini sudah bisa masuk ke OS Solaris dengan normal.
Semoga bermanfaat untuk pembaca semua.
Dony Ramansyah
site : http://donyramansyah.net
blog : dony-ramansyah.blogspot.com
email : dony.ramansyah[at]gmail.com
Registered linux user : ID 40017
