System Administration
cancel
Showing results for 
Search instead for 
Did you mean: 

enable san device on console

irt_1
Frequent Advisor

enable san device on console

Hi All,

I have one ES40 server runing Tru64 ver. 4.0F. and connecting to the storage on SAN.

Last week there is a power outage (planned) so I shutdown the system and turn the power off.

The problem is after I reboot, the OS can not see the disk anymore.

I shutdown again and try to see the console. I read somewhere that I need to make the disk appear from the console.

How I do that?

Thank you in advance!

Iwan Tamimi

5 REPLIES
irt_1
Frequent Advisor

Re: enable san device on console

I just realized actually wwid from the console is just for if I set up the boot disk from SAN. Actually I dont really need that, as long as the OS can see again my disks.

Any command to diagnose? Or any command to enable the SAN disks?

Regards,

Iwan Tamimi
Ivan Ferreira
Honored Contributor

Re: enable san device on console

Aren't dga devices your SAN disks?

Also, one of your FCA (db0) shows link down. Is this ok?

To be able to boot disks from san you have to run:

wwidmgr -quickset -udid

And then set your bootdef_dev console variable correctly.
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Vladimir Fabecic
Honored Contributor

Re: enable san device on console

First, TRU64 V4.0F does not support multipathing. Are you sure that pgb0 link down is OK?
Second, what is the output of:
>>> wwidmgr -show reachability
>>> wwidmgr -show wwid -full
Third, if you boot from local disk, nothing have to set with wwidmgr in console. OS should recognize them.
Also post output of:
# scu show edt (form OS)
In vino veritas, in VMS cluster
Johan Brusche
Honored Contributor

Re: enable san device on console

Some other ways to look a storage via OS:

hwmgr view dev -category disk
hwmgr show fibre -topology

Rgds,
__ Johan.

_JB_
irt_1
Frequent Advisor

Re: enable san device on console

Sorry For the late reply,

Yes the boot disk is a local disks
The other path is not in use
The system booted OK just the other device were not there
I just found out it hapenned that this system use LVM/LSM (Tru64 v. 4.0. F)

The hardware manager showed:

:root>scu show edt

CAM Equipment Device Table (EDT) Information:

Device: DF600F Bus: 0, Target: 5, Lun: 0, Type: Direct Access
Device: DF600F Bus: 0, Target: 5, Lun: 1, Type: Direct Access
Device: DF600F Bus: 0, Target: 5, Lun: 2, Type: Direct Access
Device: DF600F Bus: 0, Target: 5, Lun: 3, Type: Direct Access
Device: DF600F Bus: 0, Target: 6, Lun: 0, Type: Direct Access
Device: DF600F Bus: 0, Target: 6, Lun: 1, Type: Direct Access
Device: DF600F Bus: 0, Target: 6, Lun: 2, Type: Direct Access
Device: DF600F Bus: 0, Target: 6, Lun: 3, Type: Direct Access
Device: BB018122B7 Bus: 2, Target: 0, Lun: 0, Type: Direct Access
Device: TZ89 Bus: 2, Target: 3, Lun: 0, Type: Sequential Access
Device: RZ1EF-CB Bus: 2, Target: 5, Lun: 0, Type: Direct Access
Device: CD-ROM XM-6302B Bus: 3, Target: 0, Lun: 0, Type: Read-Only Direct Ac
cess

Looks like the problem more to LVM. I dont really familiar with it.

I tried to bring up the lvm but this one I got:

root>/sbin/volstartup
vold appears to be running in disabled mode. Kill:


Start vold:


Fatal errors prevent /sbin/volstartup from continuing.

Any clue?

Thank you again for you all for the answers.

Best Regards,

Iwan Tamimi