06-05-2008
pull out one of the disk and check if your system is still ok and accessible. check raidctl and it should tell that a controller device as "missing" plug back in the removed disk and synchronization takes place automatically
9 More Discussions You Might Find Interesting
1. Solaris
I don't understood why on SPARC-Platforms have not present RAID-Controller ? Sorry for my bad english, but it's crazy always setup software RAID !!! I whanna Hardware RAID and when i can find solution ? (7 Replies)
Discussion started by: jess_t03
7 Replies
2. Solaris
Hi,
I have a root with hardware RAID on c0t0d0 and c0t2d0. I would like to set the boot device sequence in OBP for both hdds.
I have checked in ls -l /dev/rdsk/ for the path of c0t2d0 but it does not exist. Can anyone shed some lights on this?
AVAILABLE DISK SELECTIONS:
0.... (12 Replies)
Discussion started by: honmin
12 Replies
3. Solaris
Hi,
I have problem creating hardware raid on T5120 with 4 disks. After the hardware raid 1 created, then I used the raidctl -l c1t0d0 and raidctl -l c1t2d0
the output of volume c1t0d0 contain disk 0.0.0 0.1.0, also the volume c1t2d0 contain disk 0.0.0 0.1.0 and should be 0.2.0 0.3.0
so I... (15 Replies)
Discussion started by: netlink
15 Replies
4. Solaris
Hi everyone
I've just purchased a Sun T5120 server with 2 internal disks. I've configured hardware RAID (mirror) and as a result the device tree in Solaris only contains 1 hard drive.
My question is, how would I know when one of the drives become faulty?
Thanks (2 Replies)
Discussion started by: soliberus
2 Replies
5. UNIX for Dummies Questions & Answers
Hi
Can someone tell me what are the differences between software and hardware raid ?
thx for help. (2 Replies)
Discussion started by: presul
2 Replies
6. Hardware
Hi all
I've just received my T3-1. It has 8 disks and I would like to configure RAID1 on the disks. The Sun documentation states that you can either use the OpenBoot PROMP utility called Fcode or you can use software via the Solaris OS.
The documentation doesn't make it clear if:
1. The... (6 Replies)
Discussion started by: soliberus
6 Replies
7. Solaris
Server Model: T5120 with 146G x4 disks.
OS: Solaris 10 - installed on c1t0d0.
Plan to use software raid (veritas volume mgr) on c1t2d0 disk.
After format and label the disk, still not able to detect using vxdiskadm.
Question:
Should I remove the hardware raid on c1t2d0 first?
My... (4 Replies)
Discussion started by: KhawHL
4 Replies
8. Solaris
Dear All ,
we have hardware raid 1 implemented on Solaris Disks.
We need to patch the Servers. Kindly let me know how to patch hardware raid implemented Servers.
Thanks...
Rj (7 Replies)
Discussion started by: jegaraman
7 Replies
9. Solaris
Dear All ,
Pl find the below command ,
# raidctl -l
Controller: 1
Volume:c1t0d0
Disk: 0.0.0
Disk: 0.1.0
Disk: 0.3.0
#
raidctl -l c1t0d0
Volume Size Stripe Status Cache RAID
Sub Size ... (10 Replies)
Discussion started by: jegaraman
10 Replies
LEARN ABOUT ULTRIX
creatediskbyname
creatediskbyname(3x) creatediskbyname(3x)
Name
creatediskbyname - get the disk description associated with a file name
Syntax
#include <disktab.h>
struct disktab *
creatediskbyname(name)
char *name;
Description
The subroutine takes the name of the character device special file representing a disk device (for example, and returns a structure pointer
describing its geometry information and the default disk partition tables. It obtains this information by polling the controlling disk
device driver. The subroutine returns information only for MSCP and SCSI disks.
The file has the following form:
#define DISKTAB "/etc/disktab"
struct disktab {
char *d_name; /* drive name */
char *d_type; /* drive type */
int d_secsize; /* sector size in bytes */
int d_ntracks; /* # tracks/cylinder */
int d_nsectors; /* # sectors/track */
int d_ncylinders; /* # cylinders */
int d_rpm; /* revolutions/minute */
struct partition {
int p_size; /* #sectors in partition */
short p_bsize; /* block size in bytes */
short p_fsize; /* frag size in bytes */
} d_partitions[8];
};
struct disktab *getdiskbyname();
struct disktab *creatediskbyname();
Diagnostics
Successful completion of the subroutine returns a pointer to a valid disktab structure. Failure of this subroutine returns a null pointer.
The subroutine fails if it cannot obtain the necessary information from the device driver or disktab file.
A check is done to ensure that the disktab file exists and is readable. This check ensures that the subroutine is not being called because
the disktab file was accidentally removed. If there is no disktab file, the subroutine fails.
The subroutine also fails if it cannot determine disk geometry attributes by polling the driver. This can occur if the disk is not an MSCP
or SCSI disk. In some cases where the disk consists of removable media and the media is not loaded, the driver will be unable to determine
disk attributes.
Restrictions
The subroutine returns information only for MSCP and SCSI disks.
See Also
getdiskbyname(3x), ra(4), rz(4), disktab(5)
creatediskbyname(3x)