device files renamed

[Unix Administrator_5]

6 weeks ago we installed 6 additional fc addapters to our v2500. (we already had 4 that were connected to a old disk array).

Everything seemed to be fine.
However, on sunday when we attached a new array to these 6 new cards and rebooted, we got got some errors during the reboot (scrolled by to fast to determine what the were) and the system aborted the reboot early on. We rebooted again, and the system came up; however, most of our disk device files were renamed, we had some lan cards renamed, and our telnet device file apparently changed as telnet stopped working.


It was a mess to clean up. We had used this procedure many times before without incident.

We are trying to figure out why it happened and how to avoid this problem.

We had to disconnect the "new" array and vgexport/vgimport all 27 of the volumegroups on the old array.

Any help would be appreciated.

[James R. Ferguson]

Hi:

If one or more I/O cards were reshuffled in the backplane, then this would be a logical outgrowth.

Regards!

...JRF...

[Unix Administrator_5]

nothing was "reshuffled" - we just connected 6 fibre channel cables.

[Frank Slootweg]

It looks like that, for some reason, you lost your ioconfig files. The ioconfig files are the (on disk) 'memory' for your I/O configuration. For details, see ioinit(1M) and ioconfig(4). Note: Do *NOT* mess with ioinit, ioconfig, etc., unless there is a need *and* you know what you are doing.

[Unix Administrator_5]

I spoke with support and they gave me a way of "fixing this". They also said they didnt know why that this sometimes caused a remapping of the device files and sometimes it didnt. This was the first time in 8 years that its happened to me.