Sponsored Content
Full Discussion: failing drive
Operating Systems AIX failing drive Post 302216787 by bakunin on Monday 21st of July 2008 06:58:05 AM
Old 07-21-2008
How this is exactly done is depending on the RAID adapter (more precisely: the adapters driver software), so i can give you only general directions.

If the failing disk is part of a RAID you will probably not be able to manage the disk device itself. A RAID works like this: there are several disks connected to an adapter. The driver software of the adapter makes one big virtual disk out of the several physical ones and presents this virtual construct as a physical disk to the machine. (This is what is done during the "RAID initialization" or however it is called with your software. The driver/adapter writes some bookkeeping information onto the physical disk to be able to use them the described way.)

Only this virtual disk is added to a VG as a "Physical Volume" and from there on normal LVM procedures apply.

Your first task is to make the PV free from OS access. You can do this by either breaking the mirror (if the VG is mirrored) or by varying off the VG as zaxxon suggested. Since the "disk" in the VG is only a virtual construct there is no strict relationship between disks and logical volumes. All the logical volumes on the virtual RAID disk are "smudged across" the physical disks comprising the RAID.

After this you need to use the adapters driver software (in case of the IBM SCSI RAID adapter this is plugged into SMITty and the diag utility) to remove the disk from the RAID, after which the RAID is in status "reduced". then physically change the disks and add the new disk to the RAID. This will probably take some time as the new disk has to be written with the data first to be useful in the RAID. Only then varyon again and start using the VG again.

Do you need to backup? In principle you don't, because in a RAID all the disks hold all the information with redundancy. The classical case is 5 disks holding the capacity of 4 - for this penalty it is possible to replace every single disk without losing data, because the data it holds is also available on the other 4. This does NOT mean that a backup would be a bad idea: not at all! It is better to have a backup you don't need than to need a backup you don't have.

I hope this helps.

bakunin
 

8 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

The best partitioning schem for a 250GB Sata hard drive & a 75GB SCSI hard drive

Hi I have 2 75GB SCSI hard drives and 2 250GB SATA hard drives which are using RAID Level 1 respectively. I wana have both FTP and Apache installed on them as services. I'm wondering what's the best partitioning schem? I wana use FC3 as my OS, so, I thought I can use the 75GB hard drive as the /... (0 Replies)
Discussion started by: sirbijan
0 Replies

2. UNIX for Dummies Questions & Answers

Map Drive From Windows To Apache Shared Drive?

Anyone know how I can map a windows drive to an apache shared drive? In my httpd.conf file, I have: Alias /merc_rpts/ "/u/merc_rpts/" <Directory "/u/merc_rpts"> Options Indexes </Directory> I'm able to bring up a browser and see the contents of this folder. In... (0 Replies)
Discussion started by: gseyforth
0 Replies

3. SCO

mounting USB floppy drive /Flash drive in OSR 6.0

Can anybody help me out to mount USB flash /floppy drive in sco openserver 6.0 . (5 Replies)
Discussion started by: sureshdrajan
5 Replies

4. Shell Programming and Scripting

ps -ef failing sometimes

Hi Everyone, we have a shell script "DLP_recv.sh" that has below command which is supposed to return the number of active instances of itself, which means of there is no other instance then commad would return 1 (for the current instance). The problem is that it sometimes it returns 0 which is... (3 Replies)
Discussion started by: guycool
3 Replies

5. Hardware

How to Clone a Drive with 512 byte Sectors to a Drive with 4096 bytes/sector (AF)?

I have a 320 GB drive which dual boots Windows and Debian: Disk /dev/sda: 320.1 GB, 320072933376 bytes 255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal):... (0 Replies)
Discussion started by: phillipsoasis
0 Replies

6. HP-UX

DLT 7000 tape drive failing with "write error on a record in the index"

HP rp5450 (L2000) running HP-UX 11.11B Using DLT 7000 and DLT 4000 tape drives for nightly full backups Backup jobs created by SAM DLT 7000 cron entry is as follows: 00 2 * * 1-6 /usr/sam/lbin/br_backup DLT FULL Y /dev/rmt/0m /var/sam/graphLCAa17036 root Y 1 N > /var/sam/SAM_br_msgs 2>&1... (1 Reply)
Discussion started by: dreh99
1 Replies

7. UNIX for Dummies Questions & Answers

Need help to move .csv file from UNIX path to windows shared drive or c:\ drive

Hi Guys, Can any one help me on this. I need help to move .csv/.xls file from unix path to windows shared drive or c:\ drive? Regards, LKR (1 Reply)
Discussion started by: lakshmanraok117
1 Replies

8. Solaris

Drive is showing offline in the /var/adm/messages and shows "drive type unknown" in the format outpu

Hi, I am facing issue with one of the drive is solaris 10. it is showing offline in the messages file scsi: WARNING: /pci@2,600000/QLGC,qlc@0/fp@0,0/ssd@w5006016746e00b1b,0 (ssd0): drive offline genunix: WARNING: Page83 data not standards compliant DGC LUNZ 0430 ... (1 Reply)
Discussion started by: Prasanth T K
1 Replies
BIO(4)							   BSD Kernel Interfaces Manual 						    BIO(4)

NAME
bio -- Block IO ioctl tunnel pseudo-device SYNOPSIS
pseudo-device bio DESCRIPTION
The bio driver provides userland applications ioctl(2) access to devices otherwise not found as /dev nodes. The /dev/bio device node oper- ates by delegating ioctl calls to a requested device driver. Only drivers which have registered with the bio device can be accessed via this interface. The following device drivers register with bio for volume management: arcmsr(4) Areca Technology Corporation SATA RAID controller cac(4) Compaq RAID array controller ciss(4) Compaq Smart ARRAY 5/6 SAS/SATA/SCSI RAID controller mfi(4) LSI Logic & Dell MegaRAID SAS RAID controller The following ioctl calls apply to the bio device: BIOCLOCATE Locate a named device and give back a cookie to the application for subsequent ioctl calls. The cookie is used to tunnel further ioctls to the right device. BIOCINQ Retrieve number of volumes and physical disks for a specific device. BIOCDISK Retrieve detailed information for the specified physical disk. Information returned can include status, size, channel, target, lun, vendor name, serial number, and processor device (ses). BIOCDISK_NOVOL Is just the same as BIOCDISK but doesn't require the disks to be in volume sets, so this applies to any physical disk con- nected to the controller. Note: this ioctl might not be supported on all hardware. BIOCVOL Retrieve detailed information for the specified volume. Information returned can include status, size, RAID level, number of disks, device name association (sd?) and vendor name. BIOCALARM Control the alarm beeper on the device. Supported states are: disable alarm, enable alarm, silence alarm, status and test alarm. Note: These options might not be supported on all hardware. BIOCBLINK Blink an LED of the specified physical disk. Supported blink states are: blink LED, unblink LED and blink alarm LED. Note: This option is only supported if the disk is governed by ses(4) and the hardware supports hardware blinking. BIOCSETSTATE Alter the state of specified physical disk. Supported states are: create/remove hot-spare, create/remove pass through disk, start/stop consistency check in a volume, online disk and offline disk. Note: These options might not be supported on all hardware. BIOCVOLOPS For operations in volume sets. It's able to create and remove a volume set in a supported RAID controller. Note: this ioctl might not be supported on all hardware. FILES
/dev/bio ioctl tunnel device SEE ALSO
ioctl(2), bioctl(8) HISTORY
The bio driver first appeared in OpenBSD 3.2 and NetBSD 4.0. AUTHORS
The bio driver was written by Niklas Hallqvist <niklas@openbsd.org>. The API was written by Marco Peereboom <marco@openbsd.org> and was extended even more for NetBSD by Juan Romero Pardines <xtraeme@netbsd.org>. BSD
May 25, 2008 BSD
All times are GMT -4. The time now is 06:44 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy