01-23-2013
You say the disk is visible in format. Please post the output of format.
@DukeNuke2......Do you recognise these device names? I'm very familiar with c0t0d0s0 and c0d0p1 but not c0d0s7. (on Solaris)
What hardware is this?
Last edited by hicksd8; 01-23-2013 at 11:06 AM..
This User Gave Thanks to hicksd8 For This Post:
9 More Discussions You Might Find Interesting
1. Solaris
Hi Guys,
Need to add 2 disks into a JBOD array (3310).
Does anyone see anything wrong with my Procedure / Doco below?
1> Logon to system, check system logs for abnormal entries.
2> Make backups of related system files:
A>cp -p /etc/system /etc/system.backup.081505
B>cp -p /etc/vfstab... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
2. Solaris
Hi there,
My task is to replace the two 73 G disks with two 143 G disks , which has vxvm 4.1 running on it. I would like to know whether the steps iam following are correct.
1. Break the sub-disks, plexes of the root mirror.
2. Remove the sub-disks,plexes of the root mirror.
3. Remove one of... (10 Replies)
Discussion started by: Jartan
10 Replies
3. Solaris
Hi all,
we have an existing system that was configured using just one of the (two) internal disks. I want to mirror the disk using SVM, but have realised there is no free slice for creating the metadb's. Is there a workaround I can use for this?
In the past we have always kept slice 7 free -... (8 Replies)
Discussion started by: badoshi
8 Replies
4. Solaris
Really sorry for the long posting. But i would really want to clear all the doubts.
I have 2 disk c0t0d0 & c0t1d0, i wanted to mirror c0t1d0 (mirror) to c0t0d0 (main).
Creating state database replica:
metadb -a -c3 -f c0t0d0s7
... (3 Replies)
Discussion started by: beginningDBA
3 Replies
5. Solaris
Dear All,
Please help me to configure root mirroring using SVM in Solaris 9.
Thanks and Regards,
Lakkireddy BR (3 Replies)
Discussion started by: lbreddy
3 Replies
6. Solaris
Hello All,
I am trying to mirror two non-root hard drives using zfs. But "fmthard" fails when I try to copy the vtoc due to disk mismatch. Please help me.
--- iostat command shows the disk to be similiar
--- format command shows disk to be different :confused:
--- c1t2d0 is the active... (8 Replies)
Discussion started by: pingmeback
8 Replies
7. Solaris
Need a procedure document to do "root disk mirroring in solaris volume manager for solaris 10". I hope some one will help me asap. I need to do it production environment.
Let me know if you need any deatils on this.
Thanks,
Rama (1 Reply)
Discussion started by: ramareddi16
1 Replies
8. Solaris
I would like to perform root disk mirroring task. Can someone please help me out on this.
Thanks !!
Regards,
Rama (2 Replies)
Discussion started by: ramagore85
2 Replies
9. UNIX for Advanced & Expert Users
We have two node cluster with OS disk mirrored under SVM. There is slight disk problem on one of the mirror disk causing cluster to panic.
Failure of one mirror disk causing VCS to panic the node. Why VCS is not able to write /var filesystem, as one of the disk is healthy.
... (1 Reply)
Discussion started by: amlanroy
1 Replies
LEARN ABOUT CENTOS
addbadsec
addbadsec(1M) System Administration Commands addbadsec(1M)
NAME
addbadsec - map out defective disk blocks
SYNOPSIS
addbadsec [-p] [ -a blkno [blkno...]] [-f filename] raw_device
DESCRIPTION
addbadsec is used by the system administrator to map out bad disk blocks. Normally, these blocks are identified during surface analysis,
but occasionally the disk subsystem reports unrecoverable data errors indicating a bad block. A block number reported in this way can be
fed directly into addbadsec, and the block will be remapped. addbadsec will first attempt hardware remapping. This is supported on SCSI
drives and takes place at the disk hardware level. If the target is an IDE drive, then software remapping is used. In order for software
remapping to succeed, the partition must contain an alternate slice and there must be room in this slice to perform the mapping.
It should be understood that bad blocks lead to data loss. Remapping a defective block does not repair a damaged file. If a bad block
occurs to a disk-resident file system structure such as a superblock, the entire slice might have to be recovered from a backup.
OPTIONS
The following options are supported:
-a Adds the specified blocks to the hardware or software map. If more than one block number is specified, the entire list should be
quoted and block numbers should be separated by white space.
-f Adds the specified blocks to the hardware or software map. The bad blocks are listed, one per line, in the specified file.
-p Causes addbadsec to print the current software map. The output shows the defective block and the assigned alternate. This option
cannot be used to print the hardware map.
OPERANDS
The following operand is supported:
raw_device The address of the disk drive (see FILES).
FILES
The raw device should be /dev/rdsk/c?[t?]d?p0. See disks(1M) for an explanation of SCSI and IDE device naming conventions.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Architecture |x86 |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
SEE ALSO
disks(1M), diskscan(1M), fdisk(1M), fmthard(1M), format(1M), attributes(5)
NOTES
The format(1M) utility is available to format, label, analyze, and repair SCSI disks. This utility is included with the addbadsec,
diskscan(1M), fdisk(1M), and fmthard(1M) commands available for x86. To format an IDE disk, use the DOS "format" utility; however, to
label, analyze, or repair IDE disks on x86 systems, use the Solaris format(1M) utility.
SunOS 5.10 24 Feb 1998 addbadsec(1M)