At my own eys I can see 4 disks inside of server. Previous admin told me that hardware mirror is done.
What I see with "format" is 2 disks - I suspect that these are 2 MIRRORS.
I just cant be sure because raidctl show this:
Im not sure how to read above. Correct me please, but what I understand is:
Volume c0t0d0 - is 1st MIRROR that contain 2 phisical disks and format display it as
Code:
0. c0t0d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
Volume c0t2d0 - is 2nd MIRROR that contain another 2 phisical disks and format display it as
Code:
1. c0t2d0 <LSILOGIC-LogicalVolume-3000 cyl 65533 alt 2 hd 16 sec 273>
So phisically 4 disks are used... am I right ?
BUT...
If Volume c0t0d0 is 1st MIRROR and it contain 2 phisical disks 0.3.0 and 0.2.0
then why the heck Volume c0t2d0 which is 2nd MIRROR contain exactelly this same disks ???
I have a live Sunfire v440 server with 4 drives and I want to mirror drive 0 & 1 to 2 & 3. The on-board raid controller only allows for 1 live mirror. I was thinking of disksuite, but unfortunately the second disk is just one large partition with no free slices.
I was thinking of using... (0 Replies)
I am using raidctl on a v440 disk and noticed it resyncs after every boot, which takes about 30 minutes because of the size of the partition. I am concerned with what happens during the resync if "writes" happen to the disk before it is complete?
Any info would be helpful.
Thanks (0 Replies)
I am mirroring a single partition drive with raidctl. The source partition was mounted when I created the mirror with raidctl -c c1t1d0 c1t3d0. The source disk was defined with s2 and s6 only.
I didn't think to umount it first.
Is there a problem with that? (2 Replies)
Setting up a T5240 with two disks c1t0d0 and c1t1d0.
I am trying to use raidctl but when I issue.
raidctl -l
I get
Controller 1
Disk: 0.0.0
Disk: 0.1.0
So I try
raidctl -c '0.0.0 0.1.0' -r 1 1
and I get "Array in use."
I try (4 Replies)
Hello World:
Recently I ran into an issue where a collegue had installed a Sun T5140 with twin 136GB disks in them. However, he forgot to execute the raidctl command first to mirror c1t0d0 to c1t1d0 boo hoo:) So along I come and try to mirror the disks by booting to sigle user... (1 Reply)
using the internal 2 drives mirror was created using raidctl on 100's of our servers . sometime when one drive fails we dont face any issue & we replace the drive with out any problem . but sometimes when one drive fails , system becomes unresponsive and doesnot allow us to login , the only way to... (1 Reply)
I have boot disk mirrored using hardware raid i.e raidctl command.
If I want to place an order for a spare drive and keep it at our location for spare, how do I find the disk specification since #format does not reveal this.
The server is T2000 running Solaris 10.
Any help please. (5 Replies)
I tried using raidctl earlier today to use my 2 disks in a RAID1 setup and I totally destroyed my OS install. I'm sure I did something funky and it freaked out. No big deal...right?
This is what I was seeing after a reboot.
I decided to just reinstall the OS. It let me go through all of... (3 Replies)
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)