lbolt value error message.

 
Aamir14
Regular Advisor

Re: RAID drive failed error message

Hi,

I want to delete raid disk (300gb)

Please see the command below:--

this is right command

 

saconfig /dev/ciss0 -D 2

 

after deleting what i will do ?

 

Torsten.
Acclaimed Contributor

Re: RAID drive failed error message

first you should delete the lvm structures from c0t0d2.

# strings /etc/lvmtab

# vgdisplay -v ...

# lvremove ...

# vgremove ...

then delete the logical drive, then pull the disk.


You will waste the space, better to ue a disk with same size.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Aamir14
Regular Advisor

Re: RAID drive failed error message

I have another server

disk details are:--

 

appsdev2.mpmkvvcl.com#
appsdev2.mpmkvvcl.com#sautil /dev/ciss0 |more

sautil: Unrecognized device file specified: "/dev/ciss0"

sautil: Error - File open failed
sautil: No such file or directory, errno=2


******************************************************************************
****                                                                      ****
****             S A U T I L   S u p p o r t   U t i l i t y              ****
****                                                                      ****
****             for the HP SmartArray RAID Controller Family             ****
****                                                                      ****
****                           version A.02.13                            ****
****                                                                      ****
****  (C) Copyright 2003-2007 Hewlett-Packard Development Company, L.P.   ****
******************************************************************************


  RAID SA device files (/dev/cissX) found using "/usr/sbin/ioscan -kfnd ciss":


  Run "sautil run_startup_script" if you suspect that the device file is missing or corrupted.
  Run "sautil" to view usage screen.

appsdev2.mpmkvvcl.com#ioscan -m dsf
Persistent DSF           Legacy DSF(s)
========================================
/dev/rdisk/disk9         /dev/rdsk/c0t2d0
/dev/rdisk/disk10        /dev/rdsk/c0t4d0
/dev/rdisk/disk11        /dev/rdsk/c0t1d0
/dev/rdisk/disk12        /dev/rdsk/c0t3d0
/dev/rdisk/disk14        /dev/rdsk/c0t5d0
/dev/rdisk/disk15        /dev/rdsk/c0t6d0
/dev/rdisk/disk15_p1     /dev/rdsk/c0t6d0s1
/dev/rdisk/disk15_p2     /dev/rdsk/c0t6d0s2
/dev/rdisk/disk15_p3     /dev/rdsk/c0t6d0s3
appsdev2.mpmkvvcl.com#
appsdev2.mpmkvvcl.com#
appsdev2.mpmkvvcl.com#diskinfo /dev/rdisk/disk10
SCSI describe of /dev/rdisk/disk10:
             vendor: HP
         product id: DG0300BALVP
               type: direct access
               size: 292968750 Kbytes
   bytes per sector: 512
appsdev2.mpmkvvcl.com#

 

 

disk 10 have a lot of space

Process to delete lvm----

 

# strings /etc/lvmtab

# vgdisplay -v ...

# lvremove ...

# vgremove ...

 

than i Think no p400 raid controller installed on the server

So,

only delete the LVM and pull the disk ?

 

thanks

aamir

 

Aamir14
Regular Advisor

Re: RAID drive failed error message

Hello Torsen,

 

I am awaiting of your precious reply.

 

 

 

Thanks

Aamir

Torsten.
Acclaimed Contributor

Re: RAID drive failed error message

It is a bit confusing - again a different server?


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Aamir14
Regular Advisor

Re: RAID drive failed error message

Hi,

 

Yes,on that server disk have three LVs .

my client told me don't delete the disk data.Its very important.

thats why i gave you different server disk details.

 

 

 

 

this server is rx3600 mention below:--

 

 

 

disk details are:--

 

appsdev2.mpmkvvcl.com#
appsdev2.mpmkvvcl.com#sautil /dev/ciss0 |more

sautil: Unrecognized device file specified: "/dev/ciss0"

sautil: Error - File open failed
sautil: No such file or directory, errno=2


******************************************************************************
****                                                                      ****
****             S A U T I L   S u p p o r t   U t i l i t y              ****
****                                                                      ****
****             for the HP SmartArray RAID Controller Family             ****
****                                                                      ****
****                           version A.02.13                            ****
****                                                                      ****
****  (C) Copyright 2003-2007 Hewlett-Packard Development Company, L.P.   ****
******************************************************************************


  RAID SA device files (/dev/cissX) found using "/usr/sbin/ioscan -kfnd ciss":


  Run "sautil run_startup_script" if you suspect that the device file is missing or corrupted.
  Run "sautil" to view usage screen.

appsdev2.mpmkvvcl.com#ioscan -m dsf
Persistent DSF           Legacy DSF(s)
========================================
/dev/rdisk/disk9         /dev/rdsk/c0t2d0
/dev/rdisk/disk10        /dev/rdsk/c0t4d0
/dev/rdisk/disk11        /dev/rdsk/c0t1d0
/dev/rdisk/disk12        /dev/rdsk/c0t3d0
/dev/rdisk/disk14        /dev/rdsk/c0t5d0
/dev/rdisk/disk15        /dev/rdsk/c0t6d0
/dev/rdisk/disk15_p1     /dev/rdsk/c0t6d0s1
/dev/rdisk/disk15_p2     /dev/rdsk/c0t6d0s2
/dev/rdisk/disk15_p3     /dev/rdsk/c0t6d0s3
appsdev2.mpmkvvcl.com#
appsdev2.mpmkvvcl.com#
appsdev2.mpmkvvcl.com#diskinfo /dev/rdisk/disk10
SCSI describe of /dev/rdisk/disk10:
             vendor: HP
         product id: DG0300BALVP
               type: direct access
               size: 292968750 Kbytes
   bytes per sector: 512
appsdev2.mpmkvvcl.com#

 

 

disk 10 have a lot of space

Process to delete lvm----

 

# strings /etc/lvmtab

# vgdisplay -v ...

# lvremove ...

# vgremove ...

 

than i Think no p400 raid controller installed on the server

So,

only delete the LVM and pull the disk ?

 

 

Thanks

aamir

 

Torsten.
Acclaimed Contributor

Re: RAID drive failed error message

OK, you now want to remoce a disk from the third server and use this disk as a replacement in the first server, right?

 

I already told you, remove the LVM configuration from the disk and pull the drive.

 

Consider to use "rmsf -x" after this to get rid of the NO_HW device.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Aamir14
Regular Advisor

Re: RAID drive failed error message

Thanks.

after replacing a disk

Following error message are generated

 

prodata2#tail -1000000 /var/adm/syslog/syslog.log |grep CRITICAL
Aug  8 00:06:13 prodata2 EMS [2614]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/adapters/events/raid_adapter/0_6_0_0_0_0_4_0_0_0"     (Threshold:  >= " 3")    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 171311106 -r /adapters/events/raid_adapter/0_6_0_0_0_0_4_0_0_0 -n 171311105 -a
Aug  9 00:11:39 prodata2 EMS [2614]: ------ EMS Event Notification ------   Value: "CRITICAL (5)" for Resource: "/adapters/events/raid_adapter/0_6_0_0_0_0_4_0_0_0"     (Threshold:  >= " 3")    Execute the following command to obtain event details:   /opt/resmon/bin/resdata -R 171311106 -r /adapters/events/raid_adapter/0_6_0_0_0_0_4_0_0_0 -n 171311106 -a

 

more /var/mail/root

 

>---------- End Event Monitoring Service Event Notification ----------<

From root@prodata2.mpmkvvcl.com Thu Aug  9 00:11:39 IST 2012 Received: (from root@localhost)         by prodata2.mpmkvvcl.com (@(#)Sendmail version 8.13.3 - Revision 1.001:: HP-UX11.31 - 2nd April,2008/8.13.3) id q78If dDO018729;         Thu, 9 Aug 2012 00:11:39 +0530 (IST) Date: Thu, 9 Aug 2012 00:11:39 +0530 (IST) Message-Id: <201208081841.q78IfdDO018729@prodata2.mpmkvvcl.com> To: root@prodata2.mpmkvvcl.com From: root@prodata2.mpmkvvcl.com Subject: prodata2: Event Monitor Notification

>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Thu Aug  9 00:11:39 2012

prodata2 sent Event Monitor notification information:

/adapters/events/raid_adapter/0_6_0_0_0_0_4_0_0_0  is >= 3. Its current value is CRITICAL(5).

 

Event data from monitor:

Event Time..........: Thu Aug  9 00:11:39 2012 Severity............: CRITICAL Monitor.............: dm_raid_adapter Event #.............: 43 System..............: prodata2

Summary:      Adapter at hardware path 0/6/0/0/0/0/4/0/0/0 : CISS: Logical Drive      transitioned state.

 

Description of Error:

 lbolt value: 8724285

    CISS: Logical Drive Status:     CISS: Logical Drive 0 transitioned from INTERIM RECOVERY to READY FOR     RECOVERY     Drive Type : RAID 1+0 - Disk Mirroring

Probable Cause / Recommended Action:

Informational message.

Additional Event Data:      System IP Address...: 192.168.4.6      Event Id............: 0x5022b2e300000000      Monitor Version.....: B.01.00      Event Class.........: I/O      Client Configuration File...........:      /var/stm/config/tools/monitor/default_dm_raid_adapter.clcfg      Client Configuration File Version...: A.01.00           Qualification criteria met.                Number of events..: 1      Associated OS error log entry id(s):           0x5022b2e300000001      Additional System Data:           System Model Number.............: ia64 hp server rx6600           OS Version......................: B.11.31           EMS Version.....................: A.04.20.31.02           STM Version.....................: D.04.00      Latest information on this event:           http://docs.hp.com/hpux/content/hardware/ems/dm_raid_adapter.htm#43

v-v-v-v-v-v-v-v-v-v-v-v-v    D  E  T  A  I  L  S    v-v-v-v-v-v-v-v-v-v-v-v-v

 

I/O Log Event Data:

     Driver Status Code..................: 0x0000002B      Length of Logged Hardware Status....: 0 bytes.      Offset to Logged Manager Information: 0 bytes.      Length of Logged Manager Information: 184 bytes.

Manager-Specific Information:

Raw data from the SCSI RAID SA Controller CISS driver: 00000007 00851F3D 00000001 00000304 00000000 00000000 11165880 02000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 000016B1

 

 

>---------- End Event Monitoring Service Event Notification ----------<

prodata2#

Thanks

aamir 

Torsten.
Acclaimed Contributor

Re: RAID drive failed error message

Meanwhile the recovery should be finished. What is the status now?


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Torsten.
Acclaimed Contributor

Re: RAID drive failed error message

Sorry, can't read this.

 

Could you try again with better format?


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!