Home > Read Error > Read Error On /dev/dsk/c1t1d0s0

Read Error On /dev/dsk/c1t1d0s0

Contents

If so then yes, your drive has failed you. File systems that are mounted directly on disk slices do not have the protection of Solaris Volume Manager error handling. Table 25–1 Common Boot Problems With Solaris Volume Manager Reason for the Boot Problem For Instructions The /etc/vfstab file contains incorrect information. Leaving such file systems mounted can leave you vulnerable to crashing the system and losing data. http://peakappcare.com/read-error/read-error-in-data-read-ansys.php

Disk Movement and Device ID Overview Solaris Volume Manager uses device IDs, which are associated with a specific disk, to track all disks that are used in a Solaris Volume Manager The new format displays the device ID as an ASCII string. Please allow configuation to continue until you see " Welcome to the Solaris Management Console." Can someone tell me what these errors mean? However, if the metarecover command reports an inconsistency, you must examine its output carefully to determine whether the disk or the state database is corrupt.

Solaris Svm Cheat Sheet

Then, follow these steps: Steps Boot from another root (/) submirror. If you have the prtvtoc output from the failed disk, you can format the replacement disk with the fmthard -s /tmp/failed-disk-prtvtoc-output command. General Troubleshooting Approach Although no single procedure enables you to evaluate all problems with Solaris Volume Manager, the following process provides one general approach that might help. Search Forums Show Threads Show Posts Tag Search Advanced Search Unanswered Threads Find All Thanked Posts Go to Page... unix and linux operating commands How can we confirm that,

Use the format command or the fmthard command to partition the disk as it was configured before the failure. Use metadb to delete databases which are broken. Apr 16 13:35:07 TestHost scsi: WARNING: /[email protected],600000/[email protected]/[email protected],0 (sd1): Apr 16 13:35:07 TestHost disk not responding to selection Apr 16 13:35:09 TestHost scsi: WARNING: /[email protected],600000/[email protected]/[email protected],0 (sd1): Apr 16 13:35:09 TestHost disk not Metastat Needs Maintenance Please ensure that no filesystems are mounted on these device(s).

OCP, Oracle Solaris 11 SA . Warning: Stale State Database Replicas. Metastat Output May Be Inaccurate Verify that the /etc/vfstab file contains the correct volume entries. Conversely, Solaris Volume Manager displays either the old or the new format. Locate and delete any hot spares on the failed disk.

PBE configuration successful: PBE name PBE Boot Device . Mount: /dev/md/dsk/d0 Is Not This Fstype. of course its terrible that you have hard errors, but anyway try first repair deice in SVM, i mean force it for resync to the same device. Use the format command or the fmthard command to partition the disk with the same slice information as the failed disk. If the directory /var is in question with access problem, VCS GAB would trigger system panic due to client process failure as VCS daemon 'had' can't access the /var directory.

Warning: Stale State Database Replicas. Metastat Output May Be Inaccurate

In this example, /dev/dsk/c0t1d0s4 and mirror d10 are used. # metareplace -e d10 c0t1d0s4 If any RAID-0 volumes have soft partitions built on them, run the metarecover command for each RAID-0 Three replicas on the c0t0d0s4 slice are still good. Solaris Svm Cheat Sheet Use pwd to print the current working directory: Use ls to list a directory's contents: Use cd to change to a new directory: Use wildcards instead of typing out long directory Set Md:mirrored_root_flag=1 Another possible reason is that an old copy of the/etc/vfstab file was copied back into the current /etc/vfstab file.

Because Solaris Volume Manager is part of the Solaris OS, mounting the Solaris Volume Manager volumes ensures that any changes are reflected on both sides of the mirror. weblink How to Recover From Insufficient State Database Replicas Steps Boot the system. Source boot environment is . Mounting file systems for boot environment . Metastat: There Are No Existing Databases

Thanks Mada 0 Message Author Comment by:dee432003-08-27 Why can't I open the Solaris Management console? 0 LVL 16 Overall: Level 16 Unix OS 14 Message Active today Expert Comment devfsadm: mkdir fialed for /dev 0xled: Read-only file system devfsadm: inst_sync failed for /etc/path_to_inst.1359: Read-only file system devfsadm: WARNING: failed to update /etc/path_to_inst # metainit -r # metasync d0 # mount Output from the metastat command shows some of the cntndn names that were previously used. navigate here Creating compare database for file system .

Forcing update of md.conf. Metaclear Metadevice In Use Once you have a replacement disk, halt the system, replace the failed disk, and once again, reboot the system. If I clone it...

This situation could follow a panic when Solaris Volume Manager discovers that fewer than half of the state database replicas are available.

Populating contents of mount point . If you have a system failure, you can physically move the disk pack to a new system and enable the new system to recognize the configuration. Set the read policy on the mirror to “first.” # metaparam -r first d40 # metastat d40 d40: Mirror Submirror 0: d41 State: Okay Submirror 1: d42 State: Okay Pass: 1 Metareplace d0 -m d1 d2 d1 1 1 c0t0d0s0 d2 1 1 c0t1d0s0 When u run metastat d0 ..

Ignore any warning messages printed by the update_drv command. # update_drv -f md Configure the system volumes. # metainit -r If you have RAID-1 volumes in the Solaris Volume Manager configuration, Locate any state database replicas that might have been placed on the failed disk. Then, the system fails. his comment is here How to Print a Report on Disk Sets Available for Import Steps Become superuser.

c1t0d0 /[email protected],700000/[email protected]/[email protected],0 1. Note – This procedure only works to recover soft partition information. Obtain a report on disk sets available for import. # metaimport -r -v -r Provides a report of the unconfigured disk sets available for import on the system. -v Provides detailed In this example, RAID-0 volume, d17, has soft partitions built on it. # metarecover d17 -m -p Replace hot spares that were deleted, and add them to the appropriate hot spare

Run the metastat command to make sure the mirror is in the “Okay” state. # metastat d40 d40: Mirror Submirror 0: d41 State: Okay Submirror 1: d42 State: Okay Pass: 1 The system returns to normal operation. The W in the flags field of the c0t1d0s4 slice indicates that the device has write errors. Recovering Storage From a Different System You can recover a Solaris Volume Manager configuration, even onto a different system from the original system.

For more information on the metaimport command, see the metaimport(1M) man page. d12: Submirror of d2 State: Needs maintenance Invoke: "metareplace d2 /dev/dsk/c0t3d0s6 " Size: 286740 blocks Stripe 0: Device Start Block Dbase State Hot Spare /dev/dsk/c0t3d0s6 0 No Maintenance d22: Submirror Reboot the Server if required. In the following example, the metastat command output displays a different, but equivalent, form of the device ID for c1t6d0 from the prtconf -v command output for the same disk. #

Creating compare databases for boot environment .