Bad Hdisk

[johndrake]

Hi All,

How does one reformat a a bad hdisk? The person who
is my back up tried to create a logical volume using an
existing hdisk. He told me that their was some type of
corruption issue because he could not use that hdisk at
all. Unfortunately, I could not get more detail from him.
I need to logon tonight and try to fix it. I'd like to have an idea as to how to fix this problem before I log in. The
problem that I have is that I can only login in the evening
because the client site where I am at will not allow me to
pass through their firewall.

Thanks!

-Joe

 

[victorv]

hi,
I have mounted tens of disk, and never I need to format them. However you can find this service in diagnostic

diag
Task Sel.
Format Media
or
Certify Media

from the command line. In some cases, you need start
diagnostic, from a special CDrom, booting from it.

In my experience, I have found problems to configure
no-IBM-risc-certified devices, when setting jumpers
according to scsi-risc-specifies

If you see hdisk defined, use smitty devices, Fixed Disk,
Configure defined disk
or
mkdev -l hdiskX

Create a new VG or add disk to an exist. VG (I belive you
know how to do this)

When you do this step, you erase (for AIX) all disk content.

bye

 

[mkharris]

diag
then choose 'Task Selection'
then choose 'Certify Media'
select the suspect disk with enter, and then F7 to commit.

If you really want to format, then that option is also available from task selection.

 

[johndrake]

Hi All,

Thank you.

-Joe

 

[johndrake]

Hi All,

Tried both these but did not work. Here is the message I am getting---also tried to configure it:


Command: running stdout: yes stderr: no

Before command completion, additional instructions may appear below.

0516-024 mkvg: Unable to open physical volume.
Either PV was not configured or could not be opened. Run
diagnostics.
0516-862 mkvg: Unable to create volume group.
0516-1254 mkvg: Changing the PVID in the ODM.

-oe

 

[Yegolev]

an IBM DASD has 40+ levels of error checking on the disk itself, or so i am told, so generally when they start going bad you really should just get a replacement. if the Certify operation failed, definitely get a new DASD. i am assuming you have checked errpt for SCSI and DISK errors.

IBM Certified -- AIX 4.3 Obfuscation

 

[bonsky]

if you tried to certify the disk already and still got error messages, i believed their recommendation to change the disk is the best.. hehe..Check also wether you see unusual lights on the disk or failing lights there..