help replacing the correct drive

[whiteSox]

hi ,

i am using the OS version
OSF1 V5.1 732 alpha

I have a bad disk and want to replace that I have added two used disk from an old system .Now I want to know how to find the bad disk and take that out also add the file system to the two used drive that I have added .Please I need step by step instructions as I am not familiar with the tru64 OS .your help is greatly appreciated..
Thanks

[Steven Schweda]

> OSF1 V5.1 732 alpha

Actual output from "sizer -v" might be
helpful.

> I have a bad disk [...]

> Now I want to know how to find the bad
> disk [...]

Huh? I don't see how you can know that you
have a bad disk, and still need help to find
the bad disk.

> [...] I need step by step instructions
> [...]

I need a clearer explanation of what you're
trying to do, and what you know and don't
know.

> [...] add the file system [...]

http://h30097.www3.hp.com/docs/pub_page/doc_list.html

Choose a version. Look for the "System
Administration" manual. Look for a chapter
on "Administering File Systems".

Some non-empty description of the hardware
involved might also be helpful.

[whiteSox]

I find out because there is an I/o error for one of the file system .But i am not sure how to tell on this OS ..on what disk that it resides on .
chown: migar.msb: I/O error
chown: migar.msg: I/O error
chown: migca.msb: I/O error
chown: migca.msg: I/O error
chown: migcs.msb: I/O error
chown: migcs.msg: I/O error
chown: migd.msb: I/O error

[Steven Schweda]

> I find out because there is an I/o error
> for one of the file system .

That might mean that the disk is bad, but I
wouldn't bet on it.

> chown: migar.msb: I/O error

Who or what is producing these messages?

Where are these files?

> But i am not sure how to tell on this OS
> ..on what disk that it resides on .

What would you do on some other OS?

You might start with:

mount

Around here, for example:

urtx# mount
root_domain_2#root on / type advfs (rw)
/proc on /proc type procfs (rw)
usr_domain_2#usr on /usr type advfs (rw)
usr_domain_2#var on /var type advfs (rw)

For AdvFS file systems ("advfs"), the
physical disk info can be obtained using
"showfdmn":

urtx# showfdmn -k usr_domain_2

Id Date Created LogPgs Version Domain Name
47151c4e.00091e98 Tue Oct 16 15:17:18 2007 512 4 usr_domain_2

Vol 1K-Blks Free % Used Cmode Rblks Wblks Vol Name
1L 14058600 1563896 89% on 256 256 /dev/disk/dsk6f


Also potentially helpful:

sysman


> Actual output from "sizer -v" might be
> helpful.

Still true.

[Kapil Jha]

OK i hope you are using LSM.
You can see the bad disk in
#volprint -thA

Or as suggested by Stevan.

then run the command
#hwmgr -flash light -dsf /dev/disk/dskX

it would turn on the light on the disk and u can remove it, make sure u remove it from LSM.

BR,
Kapil+

[Pieter 't Hart]

the initial eror message may be found in the system logfiles.

the message posted could just mean the filesystem is full?

look in /var/adm/syslog.dated directory tree for the logfile containing the first error.

or use sysman -> monitoring -> event_viewer that can give you even more information.

if it's confirmed it's a hardware error, we can proceed from there.
if it's an other error let's check that.