ERROR : dimm-x

Post kali ini kita membahas tentang bagaimana menangani masalah memory’

Tampilan memory error di display biasanya akan seperti dibawah ini :

———————————————————-

ERROR: The following devices are disabled:
dimm1

Aborting auto-boot sequence.

[1] ok

———————————————————

Proses loading OS pada mesin anda akan berhenti di OBP (OpenBoot PROM) prompt dimana OBP ini juga digunakan untuk instalasi software maupun OS solaris yang ada di posting sebelumnya (categories : Instalasi) atau ada di buku SMM.

Kembali ke permasalahan, error semacam ini terjadi kemungkinan besar karena adanya bad-c0ntact , kerusakan di board ddr ataupun di slot ddr tersebut. Untuk selanjutnya, kita dapat mencoba untuk membersihkan contact connector di ddr memory maupun di slot connector ddr memory yang ada di motherboard mesin kita. Hal ini dapat terjadi karena pengaruh kelembab-an tinggi ruangan maupun karena korosi.

Apabila sudah dilakukan pembersihan contact/konektor dan mesin dijalankan seperti biasa, kemungkinan besar system masih akan memunculkan pesan error yang sama seperti diatas. Hal ini disebabkan karena system masih memutuskan koneksi ke device tersebut (dimmx), dimana kita harus me-reset device tersebut dengan menggunakan perintah ASR (Automatic System Recovery).

———————————————————-

ERROR: The following devices are disabled:
dimm1

[1] ok .asr

dimm1                        Disabled by FWDIAGS 
                                      POST  detected failure 

[1] ok  asr-clear

[1] ok  reset-all

———————————————————

setelah itu systen akan melakukan reboot dan loading ke OS dan aplikasi Skykeeper dengan normal.

Selamat mencoba 🙂

.

.

Restore Repository

Permasalahan Restore Repository biasanya disebabkan oleh kegagalan loading database atau juga dikarenakan system crash yang mengharuskan kita untuk me-load kembali working database yang telah tersimpan di backup repository system. Tulisan pada kotak di bawah ini adalah tampilan yang ada di monitor komputer SUN (WPO/WPT/ADP) walaupun tidak persis sama. Tulisan yang tercetak tebal adalah “command” yang harus dimasukkan.

SunOS Release 5.10 Version Generic_120011-14 64-bit Copyright 1983-2007 Sun Microsystem, Inc. All rights reserved. Use is subject to license terms. / svc.configd: smf(5) database integrity check of: /etc/svc/repository.db failed. The database might be damaged or a media error might have prevented it from being verified. Additional information useful to your service provider is in: /etc/svc/volatile/db_errors The system will not be able to boot until you have restored a working database. svc.startd(1M) will provide a sulogin(1M) prompt for recovery purposes. The command: /lib/svc/bin/restore_repository can be run to restore a backup version of your repository. See http://sun.com/msg/SMF-8000-MY for more information. Requesting System Maintenance Mode (See /lib/svc/share/README  for more information.) Svc.configd  exited  with status  102 (database initialization failure) Root password for system maintenance  (control-d to bypass) :

Masukkan Root password “operator” (password tdk tertampil di layar) dan tekan enter :

Lalu ikuti perintah berikut ini yang tercetak tebal secara ber-urut-an (perhatikan huruf besar/kecilnya) :

Root password for system maintenance  (control-d to bypass) : single-user privilege assigned to /dev/console. Entering System Maintenance Mode Oct 26 10:46:23 su: ‘su root’ succeeded for root on /dev/console Sun Microsystems Inc. SunOS 5.10 Generic January 2005 .profile run Shell is bash root@#  cd /lib/svc/method/ root@#  ./fs-root root@#  ./fs-usr The  /  file system (/dev/rdsk/c1t0d0s0) is being checked. The  /  file system (/dev/rdsk/c1t0d0s0) is being checked. CORRECTING BAD…………….. CORRECTING BAD CG SUMMARIES CORRECTED SUMMARY FOR CG 0 FRAG BITMAP WRONG (CORRECTED) /dev/rdsk/c1t0d0s0 : CORRECT GLOBAL SUMMARY ………………………….. ………………………. *****  FILE SYSTEM WAS MODIFIED  ***** root@#  cd /lib/svc/bin/ root@#  ./restore_repository See http://sun.com/msg/SMF-8000-MY for more information on the use of this script to restore backup copies of the smf(5) repository. If there are any problems which need human intervention, this script will give instructions and then exit back to your shell. Note that upon full completion of this script, the zone will be rebooted using reboot(1M), which will interrupt any active services. The following backups of /etc/svc/repository.db exist, from oldest to newest: manifest_import-20071210_112348 boot-20101207_232407 boot-20110118_084130 boot-20110118_105848 The backups are named based on their type and the time what they were taken. Backups beginning with “boot” are made before the first change is made to the repository after system boot.  Backups beginning with “manifest_import” are made after svc:/system/manifest-import:default finishes its processing. The time of backup is given in YYYYMMDD_HHMMSS format. Please enter either a specific backup repository from the above list to restore it, or one of the following choices : CHOICE                      ACTION —————————  ——————————————————— boot                             restore the most recent post-boot backup manifest_import          restore the most recent manifest_import backup -seed-                           restore the initial starting repository  (All customizations will be lost, including those made by the install/upgrade process. ) -quit-                            cancel script and quit Enter response [boot] :

Masukkan pilihan berdasarkan waktu terakhir kali sebelum terjadinya error. Contoh, apabila error terjadi pada sekitar pertengahan Desember 2010, maka pilihan yang bisa digunakan adalah :

boot-20101207_232407 , (ambil file berdasarkan tanggal sblm pertama kali error terjadi) lalu tekan enter.

Enter response [boot] : boot-20101207_232407 After confirmation, the following steps will be taken : svc.startd(1M) and svc.configd(1M) will be quiesced, if running. ………………………… ……………………………… …………………………………….. …………………………………………….. And the system will be rebooted with reboot(1M). Proceed [yes/no]?  yes   Quescing repository……… …………………….. …………………. …………… — copied –> /etc/svc/repository.db The backup repository has been successfully restored. Rebooting in 5 seconds.

Setelah proses reboot, silahkan jalankan computer seperti biasa.

Semoga berhasil 🙂

.

.