Re: ssa raid5 pdisk1 bad.
- From: Robert Binkley <leebinkley@xxxxxxxxx>
- Date: Thu, 20 Apr 2006 08:36:00 -0700
Here are some tips ::
Any time you are shutting down an IBM box for disk
replacement you ALWAYS want to run rmdev because
cfgmgr will assign a new alias to disk
when system reboots.
For example, because I didn't rmdel -l hdisk0
before we shut down the box & repl hdisk0
when the box came bk up after disk
was replaced the box displayed hdisk0 & hdisk96.
To Chk Device Driver Software Level On IBM:
lslpp -L | grep SSA
Check Adapters On IBM Boxes:
1. lsdev -Cc adapter
To Get FRU Number on IBM :
lscfg -vl hdisk0
lspv | grep hdisk0
chdev -l hdisk0 -apv=yes
lspv | grep hdisk0
lsdev -Cc disk | grep -i "scsi"
cfgmgr
rmdev -dl hdisk96
find out which process has cpu hung:
ps -ef -o user -o pid -o pcpu -o comm | more
ps -ef -o user -o pid -o pcpu -o comm | grep -v 0. |
more
--- "Leyden, Joseph" <LeydenJ@xxxxxxxxx> wrote:
This is my first time I had an ssaraid pdisk1 fail
and just want to verify the steps to replace.
No hot spare on my raid5 at this time.
-------------------
1. rmdev -dl pdisk1
2. IBM tech to replace pdisk1 after identifying it
with the blinking light.
3. run cfgmgr
4. make pdisk1 a hot spare disk.
Is this it?
Thanks,
Joe
Robert Lee Binkley leebinkley@xxxxxxxxx
IBM AIX Specialist Certified
HP-UX System Administration Certified
Work It's Nice To Be Important But It's More Important To Be Nice
- Follow-Ups:
- Re: ssa raid5 pdisk1 bad.
- From: Andrew . Townsend
- Re: ssa raid5 pdisk1 bad.
- References:
- Re: ssa raid5 pdisk1 bad.
- From: Leyden, Joseph
- Re: ssa raid5 pdisk1 bad.
- Prev by Date: Re: ssa raid5 pdisk1 bad.
- Next by Date: Re: ssa raid5 pdisk1 bad.
- Previous by thread: Re: ssa raid5 pdisk1 bad.
- Next by thread: Re: ssa raid5 pdisk1 bad.
- Index(es):
Relevant Pages
|
|