Sponsored Content
Operating Systems Solaris Need assistance to replace root disk on Netra X4200 Post 302886044 by hicksd8 on Wednesday 29th of January 2014 12:35:19 PM
Old 01-29-2014
Firstly, the 0.5.0 will refer to the position in the SCSI chain; perhaps SCSI ID 5?

Don't worry about finding 0.0.0. It was how it was configured and which disks were selected by the sysadmin to go into the array.

So, your controller knows exactly what's going on; there are two RAID1 arrays and one of the disks has failed.

Do you know exactly which disk it is??? Pulling out the wrong disk will be fatal!!!!

Assuming you know EXACTLY which disk is in trouble, the first thing to try is to pull it out and simply push it back in. Then check the status again. If it says it's rebuilding then perhaps it was just a connection problem (poor contacts happen all the time). If it still says FAILED then replacement is needed.

Most disks show the number of LBA's on the label. LBA=logical blocks or sectors on the disk.

The replacement disk must be the same or greater number of LBA's for it to work. It stands to reason that you can't completely mirror a drive to one which is smaller. [Some disks which have exactly the same model number have different numbers of LBA's. Different versions of manufacture. So beware.]

If you do plug in a disk which is smaller then the RAID controller will refuse to do anything with it. It's not because the replacement is faulty.

If you plug in a disk that the controller is happy with then the status will go into REBUILD whilst the remirror is being done, followed by OPTIMAL when the remirror has finished.

These RAID controllers support hot-swap so no need to take the system down just make damned sure that you're pulling out the right disk.

Hope that helps.
 

10 More Discussions You Might Find Interesting

1. AIX

Replace a Failed Root Disk in AIX

My root disk is failed and how to replace the root disk in AIX. Can u give a detailed explanation in step wise. Pls give the answer taking different scenarios. Regards Praveen (1 Reply)
Discussion started by: chinnu_mulakala
1 Replies

2. Solaris

Netra 240 Hard disk are not detected

Hi All, I have new Netra 240 box which is not detecting its harddisk equiped with itse same har disk are detected when I swap with another machine. Same time If I swap hardisk of other machine to this Netra 240 box, also do not work. I have checked chassis, cabling etc and all looks fine. ... (1 Reply)
Discussion started by: xpwistler
1 Replies

3. Shell Programming and Scripting

sed search and replace word assistance...

Hi, I am trying to write a shell script designed to take input line by line by line from a file with a word on each line for editing with sed. Example file: 1.ejverything 2.bllown 3.maikling 4.manegement 5.existjing 6.systems My design currently takes input from the user, and... (2 Replies)
Discussion started by: mkfitzwilliams
2 Replies

4. Solaris

Netra V440 & Netra 1290 keyswitch

Hello, I wrote a script which monitor the keyswitch state repeatedly each 10 minutes. I'm extracting the keyswitch status by using prtdiag. The script works fine for Netra v440 , but I found that prtdiag under Netra 1290 don't give keyswitch status. unlike Netra 440 server , I found that... (2 Replies)
Discussion started by: Alalush
2 Replies

5. Solaris

x4200 solaris doesn't see new disk

I got two 2.5" disk for a x4200 and put it in. Just same these disk were, I remember doing this in the past, working.. Now when I put in the disk and run 'devfsadm' and also check with 'cfgadm -a', that disk doesn't seem to show up. When I pull out the disk I see this in the logs: Mar... (15 Replies)
Discussion started by: madvikas
15 Replies

6. UNIX for Advanced & Expert Users

Assistance Needed With Find/Replace in Vi

Hello All I have always had a question about find and replace in Vi. As this uses Vi, sed, and RegEx I never knew how or where to post the question but I thought I would give it a shot here. Say I have a text file filled with the following: Sue, your IP address is 192.168.1.10 which is... (4 Replies)
Discussion started by: NoSalt
4 Replies

7. Solaris

Mirror the root disk

Hi all I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =) At the last code, is the step i wish to do. Please help to check and correct me if got any wrong. root@leo # format </dev/null Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies

8. Solaris

Lost Root Password on VXVM Encapsulated Root Disk

Hi All Hope it's okay to post on this sub-forum, couldn't find a better place I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies

9. Hardware

Cable for SUN x4200 DC

Hello, I have a spare SUN server X4200 with a DC PSU (oracle part number 300-2186) The PSU is the one in the photo I was looking in the net about what cable i can order but i couldn't find anything that fit there :) Any idea? Thanks! (2 Replies)
Discussion started by: @dagio
2 Replies

10. Solaris

SUn Netra X4200 M2 Drivers

Hi Guys, Could someone please share the dvd/cd that came with server Netra x4200 M2 since it is not more available in Oracle site? Or do you know where I can get that? Thanks! (4 Replies)
Discussion started by: CristianS
4 Replies
voldiskadm(8)						      System Manager's Manual						     voldiskadm(8)

NAME
voldiskadm - Menu interface for LSM disk administration SYNOPSIS
/usr/sbin/voldiskadm DESCRIPTION
The voldiskadm script is an interactive tool that presents a menu of possible operations to the user. When an operation is selected, the script guides the user through the necessary steps, and prompts for data needed to complete the operation. The voldiskadm interface is intended mainly for beginning users and for those who prefer a simple method for doing common operations. The interface uses query-based prompts to gather input, with defaults supplied when possible. Context-sensitive help is available at every prompt by typing ?. Also, a list option can be used to get information on available target disks for an operation. For operations that require a device name, one or more names can be specified using a space-separated list. Names in the list can have the form dskn or rdskn (for an entire disk) or dsknp or rdsknp (for a specific disk partition). Disk names relate directly to device names in the /dev/disk and /dev/rdisk directories. The file, /etc/vol/disks.exclude, may be used to exclude disks from use by voldiskadm. Each line of the file specifies the name of a disk to exclude (for example, dsk5). The voldiskadm menu includes the following options: Add or initialize one or more disks This option prompts for one or more disk device addresses. The specified disks can be added to an existing disk group, added to a new disk group, added to a disk group as spares, or initialized but not added to a disk group (reserved for use as replacement disks). After specifying the disks, the user is prompted for a disk group (rootdg by default) and a disk name. If no name is specified, a default disk name is assigned (diskn for disks in the rootdg disk group and diskgroupn for disks in other disk groups). The disks are then checked to ensure that there is no information already on them. If there is, the user is given the option of encapsulating the disks. Encapsulate one or more disks This option prompts for one or more disk addresses. It then calls volencap to encapsulate the specified partitions. Remove a disk This option prompts for a disk, by disk media name. The disk is checked to ensure that no subdisks reside on the disk. If the disk is in use, the operation fails with a recommendation to first move all volumes off the disk. If this disk is the last disk in a disk group, the user is prompted for whether the disk group should be removed from the system, as well. The operation proceeds by calling voldg rmdisk to remove the disk from its disk group. If this is the last disk in its disk group, voldg deport is used, instead, to remove the disk group from use. Remove a disk for replacement This option prompts for a disk, by disk media name. The disk is checked for volumes that would lose all mirrors as a result of the operation. If such volumes exist, they are listed and the user is prompted to ensure that the operation should proceed. The operation proceeds by calling voldg -k rmdisk to dissociate the media record from the physical disk. If some formatted disks are under LSM control but not assigned to a disk group, the user is prompted for whether one of these disks should be used as a replacement. Replace a failed or removed disk This option prompts for a disk media name. The named media record must be dissociated from a disk. If the media record is not in the removed state, unused disks are scanned for matching disk IDs. If a disk with a matching disk ID is found, the user is prompted for whether that disk should be reattached. If a matching disk is not used, the user is prompted for a new disk, by device name. If the named replacement disk has a valid disk header, but is not allocated to a disk group, the user is prompted for whether the disk should be reinitialized. If the named replacement disk is listed as allocated to a disk group or to another host, the user is prompted to ensure that the operation should proceed. If the device is to be initialized, a new disk label is written to the disk to reflect its private and public regions. Given an initialized disk, the operation proceeds by replacing the disk in a disk group with voldg -k adddisk. Mirror volumes on a disk This option prompts for a disk, by disk media name. It then prompts for a destination disk within the same disk group, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volmirror to mirror the volumes. Mirroring volumes from the boot disk will produce a disk that can be used as an alternate boot disk. This is done by calling the volrootmir command. Move volumes from a disk This option prompts for a disk, by disk media name. It then prompts for a possible list of destination disks, also by disk media name. Specifying no destination disks indicates that any disk is suitable. The operation proceeds by calling volevac to move sub- disks off the disk. Enable access to (import) a disk group This option prompts for a disk, by device address. The operation proceeds by calling voldg import to import the disk group stored on that disk. Disable access to (deport) a disk group This option prompts for a disk group name. The prompt display lists alternate disk groups and the disks (media name and access name) that they contain. The operation proceeds by calling voldg deport. Enable (online) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an offline state. It then proceeds to make the disk accessible. Disable (offline) a disk device This option prompts for a disk device. The prompt display allows for a display of disks on the system. The operation only func- tions for disks currently in an online state but not part of any disk group. It then proceeds to mark the disk as offline such that the Logical Storage Manager makes no further attempt at accessing the disk. Mark a disk as a spare for a disk group This option sets up a disk to be used as a spare device for its disk group. A spare disk can be used to automatically replace a disk that has failed. No space can be used on a disk that is marked as a spare. Turn off the spare flag for a disk This option removes a disk from those that can be used as a spare and returns its space to the general pool of available space. Recover plexes and volumes after replacement This operation performs plex attachment, RAID-5 subdisk recovery, and resynchronize operations for the named volumes, or for volumes residing on the named disks (media name). If no media name or volume operands are specified, the operation applies to all volumes (or to all volumes in the specified disk group). ERRORS
See the voldiskadd(8) reference page for a description of errors related to the initialization operation. FILES
A list of disks to exclude from use by voldiskadm. SEE ALSO
disklabel(8), volintro(8), voldg(8), voldisk(8), voldiskadd(8), voldisksetup(8), volrootmir(8) voldiskadm(8)
All times are GMT -4. The time now is 09:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy