Sponsored Content
Full Discussion: Controller target disk?
Operating Systems Solaris Controller target disk? Post 302159965 by 1jnike on Saturday 19th of January 2008 05:24:29 PM
Old 01-19-2008
Java

Hi sudhir_shet,

I think you already have the control ids listed, the LiD & Port WWN you'll find are unique.

Before running any commands always check your man pages for backround & detailed information;

<snip start>
bash-2.05$ man format
Reformatting page. Please Wait... done

System Administration Commands

NAME
format - disk partitioning and maintenance utility
<snip end>


I believe the system is using FC-AL fibre disks, if you can boot the system to run solaris;

run the command

(As root or with root permission)

# format

(This will provide you with a list of attached disks & solaris control ids)

I hope this is of help

Jnike
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

The hard disk at channel 2, target 1 had a soft error.

Hi there! I received the following error message The hard disk at channel 2, target 1 had a soft error. The output of a system check reveiled the following (see entry <2,1> ): SWXCR xcr0 error counters: RAID Array 200 Controller Family Information Utility V1.03... (1 Reply)
Discussion started by: Ivo
1 Replies

2. SCO

Warning HD: no root disk controller was found

hi... i hav a problem to install sco unix while installing sco unix 5.0.5 in acer altos with hardware raid am getting error "Warning HD: no root disk controller was found system error 5: while getting fs type flushing controller: DAC960PRL cache done." i hav use the following... (18 Replies)
Discussion started by: mselvaprakash
18 Replies

3. HP-UX

[Joy Share] - Replace an unknown status controller on HP FC60 disk array

Replace an unknown status controller on HP FC60 disk array Author:JoyOnline JoyChangLu@gmail.com Trouble description: The users detected that the status of controller at A is unknown. Analysis and diagnostic: Physical observed all leds on enclosure of disk array is normal. The... (4 Replies)
Discussion started by: JoyOnLine
4 Replies

4. SCO

SCO 5.0.7 no root disk controller found error during install

I'm "attempting" to install SCO 5.0.7 on an HP ML370 G4 server and am ready to bash the keyboard with head now. I keep getting the error message "WARNING hd: no root disk controller found" when running the bootable install cd. I have a raid 5 array with an online spare created using 4 36.3 GB... (2 Replies)
Discussion started by: FrictionBurn
2 Replies

5. Solaris

Help needed to find out the disk controller for veritas disks

hi all i am using vxvm 5.1 on my sun blade 150 which is running with solaris 5.10. When i give the command "vxdisk list" it gives the following output # vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online... (2 Replies)
Discussion started by: kingston
2 Replies

6. SCO

Change Disk controller in SCO 6.0.0

So today I tried to upgrade a customer from a Proliant with an HPSAS controller to an Intel server with a MEGASAS controller. First, I downloaded the megasas driver from SCO and installed it on the old system. Then I created a new Microlite Edge emergency boot cd with the new driver on it. I... (2 Replies)
Discussion started by: jgt
2 Replies

7. Solaris

Changed disk controller -> drops into GRUB?!

I changed disk controller. Unplugged every disk, inserted another controller card, an IBM M1015. The disks are recognized in BIOS, and the controller card's BIOS shows up. But after that, I drop into GRUB and a prompt. That is all. How shall I solve this problem? I am thinking of booting from... (2 Replies)
Discussion started by: kebabbert
2 Replies

8. Solaris

Disk controller reassignment

Hi The scenario in the oracle t4-1 hardware with solaris 10 is as follows: 1. The initial install on the server was performed with an incorrect disk layout. 2. New disks were ordered and slot into the server. 3. The disks are allocated a controller and a disk number based on the disk or... (13 Replies)
Discussion started by: kerrygold
13 Replies

9. Solaris

Use 'dd' to copy boot disk to larger target disk

Hi, I'm looking to copy a boot disk on an old Solaris 8 system using dd. I'll bring the system down to single user mode and begin from there. I'm copying my source disk to a larger target disk. Do I need to do anything other than the 'dd' command below because the target disk is bigger? ... (2 Replies)
Discussion started by: sparcman
2 Replies
raidctl(1M)						  System Administration Commands					       raidctl(1M)

NAME
raidctl - RAID hardware utility SYNOPSIS
raidctl -c disk1 disk2 raidctl -d disk1 raidctl [-f] -F filename controller... raidctl -l [controller...] DESCRIPTION
The raidctl utility creates, deletes, or displays RAID volumes of the LSI1030 HW Raid controllers that include RAID support. The utility also updates firmware/fcode/BIOS for both RAID and non-RAID controllers. The raidctl utility requires privileges that are controlled by the underlying file-system permissions. Only privileged users can manipulate the RAID system configuration. If a non-privileged user attempts to create or delete a RAID volume, the command fails with EPERM. Without options, raidctl displays the current RAID configuration on all exisiting controllers. OPTIONS
The following options are supported: -c disk1 disk2 (for on board) Create a mirror using disk1 and disk2. Replace the contents of disk2 with the contents of disk1. Specify disk1 and disk2 in canonical form, for example, c0t0d0. When you create a a RAID volume, the RAID volume assumes the identity of the first target in the disk pair (disk1). The second target (disk2) disappears from the system. Therefore, the RAID volume appears as one disk. To have a successful RAID creation, there must not already be a RAID configuration present on the specified controller. Additionally, the secondary disk must not be mounted, as it has all its data erased and replaced with the primary disk's data. -d disk1 (for on board) Delete the RAID volume specified as disk1. Specify disk1 in canonical form, for example, c0t0d0. -f (for HBA) Force an update. Do not prompt. -F filename controller (for HBA) Update the firmware running on the specified controller (controller). -l [controller ...] (for on board) List the system's RAID configuration. If controller is specified, list RAID configurations for controller. Output from the -l lists the following information: RAID Volume Displays logical RAID volume name. RAID Status Displays RAID status as either RESYNCING (disks are syncing), DEGRADED RAID is operating with reduced functionality), OK (operating optimally), or FAILED (non-functional). RAID Disk Displays RAID disk name. Disk Status Displays disk status as either OK or FAILED. EXAMPLES
Example 1: Creating the RAID Configuration The following command creates the RAID configuration: # raidctl -c c0t0d0 c0t1d0 RAID Volume 'c0t0d0' created Example 2: Displaying the RAID Configuration The following command displays the RAID configuration: # raidctl RAID RAID RAID Disk Volume Status Disk Status ---------------------------------------- c0t0d0 RESYNCING c0t0d0 OK c0t1d0 OK Example 3: Deleting the RAID Configuration The following command deletes the RAID configuration: # raidctl -d c0t0d0 RAID Volume 'c0t0d0' deleted Example 4: Updating Flash Images on the Controller The following command updates flash images on the controller: # raidctl -F lsi1030.fw 0 Update flash image on controller 0? (y/N): y Flash updated successfully EXIT STATUS
The following exit values are returned: 0 Successful completion. 1 Invalid command line input. 2 Request operation failed. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5) System Administration Guide: Basic Administration SunOS 5.10 17 Aug 2004 raidctl(1M)
All times are GMT -4. The time now is 02:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy