Operating System - HP-UX
1752458 Members
6114 Online
108788 Solutions
New Discussion юеВ

Strange entry in make_net_recovery logs

 
Albert_31
Trusted Contributor

Strange entry in make_net_recovery logs

Hello All,

Can you help me diagonise what the error is all about and how to resolve it..

* lssf: /dev/dsk/c11t: No such file or directory

I did check up the /dev/dsk directory and dont find anything suspicious..there are other device files as well..ex c5, c10 but it always complains of c11t..any hints on what the issue can be.

Regards

Albert
17 REPLIES 17
VK2COT
Honored Contributor

Re: Strange entry in make_net_recovery logs

Hello,

The physical volume name is incomplete:

/dev/dsk/c11t

One would expect name like:

/dev/dsk/c11t2d3 (or similar)

If we assume that someone did not
create a volume group with incorrect
physical volume, then a faulty physical volume is likely cause of your problems.

Can you run these tests:

lvlnboot -v

vgdisplay -v /dev/vg00

ioscan -fn (and look for NO_HW)

cat /stand/bootconf

If /dev/dsk/c11t... is part of the volume group, then you must attend to it
firstly.

There are some nice references in ITRC
how to attend to a faulty PV in
vg00...

Finally, if you wat to run a comprehensive testing of your server (that includes
many exotic and hard-core tests that I
found extremely useful in my 20 years
of Unix support), here is a Perl script.

Regards,

VK2COT
VK2COT - Dusan Baljevic
rariasn
Honored Contributor

Re: Strange entry in make_net_recovery logs

Hi Albert,

The message seems to be incomplete. He verifie in the server of ignite the log of the client,

/var/opt/ignite/clients/$HOST_CLIENT/recovery/latest/recovery.log

rgs,

ran
Albert_31
Trusted Contributor

Re: Strange entry in make_net_recovery logs

Thank you for your replies.. i guess I was not clear enough..my apologies..

a) we run a make_net_recovery on the server and in the recovery.log file, we find the error reported above..There is no message before or after it..i mean a warning which can be linked to the above error..

To troubleshoot..
1)i have run a lssf on all the devices on the /dev/dsk directory and there is no error reported. 2) All the major and minor numbers are in order..
3) There is no device file with "c11t" in the /dev/dsk directory.
4) There are 310 device files in the /dev/dsk directory..c11 is the alternate path to c10 devices..however we dont get any warnings on c10..

Hope it helps in narrowing down the issue..Thank you all for helping me..out of this issue..

regards

albert
Albert_31
Trusted Contributor

Re: Strange entry in make_net_recovery logs

Hello Everyone,

Guess was not clear enough regarding the issue..

We are getting the above error in the recovery.log file.. to troubleshoot i have done the following and not able to see get anywhere near the issue..

a) lssf on all the device files in the /dev/dsk directory is going fine..no errors at all

b) c10 is teh alternate path of c11..however are getting errors on c11 only.

c) major ,minor, dates , permissions of the device files are in order..

d) There are no other errors in the recovery.log file which we hints of any other issues

e) all VGs are configured properly and all in good order.. have checked (double checked) the same.

any more hints..

regards

Albert
Steven E. Protter
Exalted Contributor

Re: Strange entry in make_net_recovery logs

Shalom Albert,

Find the device in question.

rmsf it.

insf -C disk

See if it goes away.

This problem needs to be resolved to avoid trouble using the Ignite archive.

ioscan -fnCdisk

Match this against the list Ignite is reporting.

It would appear a disk has been removed or perhaps failed in the system. If it went unnoticed long enough, you might have missed the lbolt in syslog.log

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Ninad_1
Honored Contributor

Re: Strange entry in make_net_recovery logs

Albert you have said
"3) There is no device file with "c11t" in the /dev/dsk directory.
"
Also you say "c11 is the alternate path to c10 devices.."

So do you mean to say that c11 are alternate paths to c10 devices but there are no entries for the c11 disk devices in /dev/dsk or /dev/rdsk ?
Then one clarification required - how do you determine that c11 is alternate links to c10 ?
Does your ioscan show the c11 entries and show CLAIMED ?
run insf -e to create the missing device entries and then try again.

Regards,
Ninad
Albert_31
Trusted Contributor

Re: Strange entry in make_net_recovery logs

Sincerely Apologize for the confusion..

a) The device files for /dev/dsk/c11t* are present in the /dev/dsk directory.

b) lssf /dev/dsk/c11t* works out fine.

c) c10txdy is the alternate path of c11txdy, this I have confirmed with the ioscan, pvdisplay output.


/root# pvdisplay /dev/dsk/c11t9d7
--- Physical volumes ---
PV Name /dev/dsk/c11t9d7
PV Name /dev/dsk/c10t9d7 Alternate Link
VG Name /dev/vg02
PV Status available
Allocatable yes
VGDA 2
Cur LV 73
PE Size (Mbytes) 16
Total PE 539
Free PE 0
Allocated PE 539
Stale PE 0
IO Timeout (Seconds) 180
Autoswitch On

The issue is with make_net_recovery.. I dont know which command actually runs this lssf and which file it is referring to so as to give the error

"lssf: /dev/dsk/c11t: No such file or directory"

If I run the command manually (the same error is reported)

/root# lssf /dev/dsk/c11t
lssf: /dev/dsk/c11t: No such file or directory

The issue is I am not able to determine where is this file or device "/dev/dsk/c11t" is...
Albert_31
Trusted Contributor

Re: Strange entry in make_net_recovery logs

Hello Everyone..

Tried out the following as well..ie ran the scripts the net_recovery would actually run during the configuratioin collection..

a)save_config --> no error..
b)list_expander --> no error..

does anyone know which command actually runs the lssf command during the net_recovery..??

Enrico P.
Honored Contributor

Re: Strange entry in make_net_recovery logs

Hi,
should be make_sys_image

Have you check the lvmtab for error?

ENrico