Sponsored Content
Top Forums UNIX for Advanced & Expert Users WARNING: VxVM vxio V-5-0-2 Subdisk disk04-28 block 6654400: Uncorrectable read error Post 302273203 by 2k7.vipin on Saturday 3rd of January 2009 03:23:38 AM
Old 01-03-2009
Looks like your disk c2t4do is dying, Better to go for a disk replacement at the earliest,Disk replacement can me done through vxdiskadm using options 4 and 5, and this being fcal disk you need used luxadm to remove and insert disk..Detailed procedure will be available in net.

U can set off the failing flags in the disk using command vxedit set failing=off disk04 .But in this case it wont help u as there is bad blocks in disk..better to go for a replacement..
 

9 More Discussions You Might Find Interesting

1. IP Networking

WARNING: correctable error from pci0 (upa mid 0) during dvma read transaction.

I am getting the following message in /var/adm/messages Its harm to the system ?? in solaries 5.5.1 unix: WARNING: correctable error from pci0 (upa mid 0) during dvma read transaction. unix: unix: AFSR=40a200ff.80800000 AFAR=00000000.0132bee0, unix: double word offset=4, SIMM DIMM1 id 31.... (1 Reply)
Discussion started by: visveswaran
1 Replies

2. Solaris

Uncorrectable data Error

Hi all, I'm getting an error "Unocrrectable data Error: Block 77e9270" followed by "disk not responding to selection" and then "disk OK". At a guess I'd assume a corrupt sector. Anyone know how I can somehow mark that sector to tell the OS to leave it alone? (1 Reply)
Discussion started by: David North
1 Replies

3. Solaris

Failed To Read Super Block

Greetings: I am trying to re-install my system with the Solaris 9 CD. I typed boot cdrom from the OBP, the system restarted and started saying Failed To Read Super Block, and then proceeds to the screen where I was initially before I decided to re-install the OS. My system was working... (4 Replies)
Discussion started by: ogfunsho
4 Replies

4. UNIX for Dummies Questions & Answers

Failed To Read Super Block With Solaris 9

Greetings: I am trying to re-install my system with the Solaris 9 CD. I typed boot cdrom from the OBP, the system restarted and started saying Failed To Read Super Block, and then proceeds to the screen where I was initially before I decided to re-install the OS. My system was working... (0 Replies)
Discussion started by: ogfunsho
0 Replies

5. Solaris

WARNING: filename <not present on Read Only file system>+pkgadd error

Hi when trying to install the package initially that i have created on to the target host, i am getting error as below for all the files/directories during pkgadd. WARNING: filename <not present on Read Only file system> ........... ........... and so on. When i do the second attempt to... (1 Reply)
Discussion started by: kiran.zamre
1 Replies

6. Shell Programming and Scripting

Read block of lines from xml file

Hi I am new to this forum. I have few XML files and from each xml file I want to copy some specific 50 no of lines and copy them to some other file. how to do that? pls help.. (5 Replies)
Discussion started by: pritam1980
5 Replies

7. Shell Programming and Scripting

URGENT: Script/Function needed to read text property files in block wise

Hi, Iam in a need for a script/function in KSH where I want to read a text file (property file) in block by block. Here is the example: Heading Name Descripton Block Block1 Value1 Description Property Name Value Property Name Value Property Name Value Property Name Value Property Name... (7 Replies)
Discussion started by: ysreenivas
7 Replies

8. Solaris

Veritas VxVm 3.2 - Cannot unrelocate subdisk due to overlap with existing subdisks

Hi all, New to this forum as well as the world of Veritas Volume Manager. My client is using VxVM 3.2. We just changed one of the disk which is under veritas control. I used the appropriate options in vxdiskadm to replace this failed disk. Now when I am trying to unrelocate subdisks back to the... (0 Replies)
Discussion started by: rajan_g4
0 Replies

9. Solaris

Symantec/Veritas Volume Manager - subdisk * not in configuration

Hello, There once was a disk. Veritas thought it wasn't happy, but it really was. The disk was all alone on a plex. There was another plex, in the same volume, that was fine and happy with its own single disk. I removed the plex with the unhappy disk. Then I went into vxdiskadm, removed... (2 Replies)
Discussion started by: kity1kity
2 Replies
volreattach(8)						      System Manager's Manual						    volreattach(8)

NAME
volreattach - Reattaches disk drives that have once again become accessible SYNOPSIS
/usr/sbin/volreattach [-rb] [accessname...] /usr/sbin/volreattach -c accessname OPTIONS
The volreattach utility has the following options: Calls the volrecover utility to attempt to recover stale plexes of any volumes on the failed disk. Performs the reattach operation in the background. Checks whether a reattach is possible. No operation is performed, but the name of the disk group and disk media name at which the disk can be reattached is displayed. DESCRIPTION
The volreattach utility attempts to reattach disks using the same disk group and media names they had before detachment. This operation may be necessary if a disk has a transient failure, or if some disk drivers are unloaded or unloadable when the Logical Storage Manager is started, causing disks to enter the failed state. If the problem is fixed, the volreattach command can be used to reattach the disks without plexes being flagged as stale, as long as the reattach happens before any volumes on the disk are started. The volreattach command is called from the voldiskadm menus as part of disk recovery. The volreattach utility tries to find a disk with a disk group and disk ID matching that of the disk(s) being reattached. If the matching disk is found, the reattach operation may still fail if the original cause (or some other cause) for the disk failure still exists. EXIT CODES
A zero exit status is returned if it is possible to perform a reattach. Otherwise, non-zero is returned. SEE ALSO
volintro(8), voldiskadm(8), volrecover(8) volreattach(8)
All times are GMT -4. The time now is 10:04 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy