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

Re: Discussion: Device special file changed for unknown reason.

 
Acclaimed Contributor

Re: Discussion: Device special file changed for unknown reason.

Look at this:

 

your new ioscan:

 

disk         9  0/1/1/0.0.0.0.0      sdisk          CLAIMED     DEVICE       HP      IR Volume
                               /dev/dsk/c9t0d0     /dev/dsk/c9t0d0s2   /dev/rdsk/c9t0d0    /dev/rdsk/c9t0d0s2
                               /dev/dsk/c9t0d0s1   /dev/dsk/c9t0d0s3   /dev/rdsk/c9t0d0s1  /dev/rdsk/c9t0d0s3

 

but your lvmtab:

 

/dev/vg00
/dev/dsk/c1t0d0s2

 

and because of this mismatch vgdisplay shows

 

 VG Name                     /dev/vg00
VG Write Access             read/write    
VG Status                   available                
Max LV                      255   
Cur LV                      8     
Open LV                     8     
Max PV                      16    
Cur PV                      1     
Act PV                      0     

 

 

But without current command outputs and logs it is impossible to help.


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Valued Contributor

Re: Discussion: Device special file changed for unknown reason.

Torsten,

From my aspect, the os show no difference whether with right dsf to form vg00 or not, only output of vgdisplay -v vg00 look terribly wrong. Of course I could not activate other vgs in the system. My opinion was that vmunix ignored mismatch of real dsf c9t0d1 and c1t0d0 in /etc/lvmtab, and just recognize hardware path set by setboot.

To hard for me to express myself  in English:)

 

regards

Stephen

Respected Contributor

Re: Discussion: Device special file changed for unknown reason.

Stephen,

 

Torsten is correct. Even though the OS was able to boot and activate vg00, it was operating in a state that would not be considered stable.  If you did rebuild lvmtab and now have the correct volume in vg00 the vgdisplay should now show the active volumes as 1 rather than 0.  If you haven't rebuilt it, then your probably still unstable.

Valued Contributor

Re: Discussion: Device special file changed for unknown reason.

Ken,
I did not realize that there was a problem with this box, until I checked vgdisplay -v vg00, before that checking, everybody assumed it alright. And I did correct it, simple vgexport and vgimport, as soon as I noticed that problem.

regards
Stephen
Respected Contributor

Re: Discussion: Device special file changed for unknown reason.

So then "strings /etc/lvmtab" shows the correct information now?  The procedure to rebuild lvmtab is to copy it to the side and run vgscan.

Valued Contributor

Re: Discussion: Device special file changed for unknown reason.

Ken,
In my opinion, one should boot to LVM maintenance mode and issue vgexport&vgimport to reconfigure vg00.

regards
Stephen
Respected Contributor

Re: Discussion: Device special file changed for unknown reason.

Is that what you did, and does lvmtab show the correct disk now?

Valued Contributor

Re: Discussion: Device special file changed for unknown reason.

of course it does.
Acclaimed Contributor

Re: Discussion: Device special file changed for unknown reason.

As said earlier, without all the related logs we will never really know what happens to the system.

However, you should also check the bootconf file if it contains the correct values now.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Valued Contributor

Re: Discussion: Device special file changed for unknown reason.

S**t! That was exactly what I forgot to do!