Module emx failed to load. status:22

[Osama Ahmed]

I have a GS1280 partioned into 2 hard partitions.
I have installed Tru64 5.1B and PK5 then connect the server to EMC storage. The server did not recognize the storage and gives the error:
Module emx failed to load. status:22

Please help

[Ivan Ferreira]

Have you configured the topology at console level with wwidmgr?

wwidmgr -set adapter -item 9999 -topo FABRIC

The command:

wwidmgr -show adapter
wwidmgr -show reachability

Displays the correct output?

You can also check the status of the adapter with the emxmgr command in the Tru64.

[Osama Ahmed]

Thanks Ivan for your reply.

The commands output is as follows :

P00>>>wwidmgr -show adapter
item adapter WWN Cur. Topo Next Topo
[ 0] pga0.0.0.1.1 2000-0000-c94a-ead0 FABRIC FABRIC
[ 1] pgb0.0.0.1.2 2000-0000-c94a-eefe FABRIC FABRIC
[9999] All of the above.
P00>>>wwidmgr -show reachability

Disk assignment and reachability after next initialization:

$ emxmgr
framework error: subsystem 'emx' not found
Unable to locate emx driver major number
Unable to configure for emx subsystem

It seems the emx driver is not included in the kernel. The question now is how to add emx subsystem in the kernel ?

Thanks

[Aaron Biver_2]

Try booting genvmunix (it should boot with no error) and rebuilding your kernel. Then, copy your new kernel to / and boot it.

[Osama Ahmed]

I have tried to do the genvmunix/doconfig steps but still no luck.

[Ivan Ferreira · Accepted solution]

Maybe you need to install New Hardware Delivery to allow the system recognize the HBA.

Also, the show reachability should show the disks that the system has access.

For example:

Disk assignment and reachability after next initialization:
6000-1fe1-0000-04a0-ffff-fffe-0005-0000
via adapter: via fc nport: connected:
dgb40.1001.0.8.6 kgpsab0.0.0.8.6 5000-1fe1-0000-04a3 Yes
dgb40.1002.0.8.6 kgpsab0.0.0.8.6 5000-1fe1-0000-04a2 No
dgb40.1003.0.8.6 kgpsab0.0.0.8.6 5000-1fe1-0000-04a1 No
dgb40.1004.0.8.6 kgpsab0.0.0.8.6 5000-1fe1-0000-04a4 Yes
dga40.1001.0.4.6 kgpsaa0.0.0.4.6 5000-1fe1-0000-04a3 Yes
dga40.1002.0.4.6 kgpsaa0.0.0.4.6 5000-1fe1-0000-04a2 No
dga40.1003.0.4.6 kgpsaa0.0.0.4.6 5000-1fe1-0000-04a1 No
dga40.1004.0.4.6 kgpsaa0.0.0.4.6 5000-1fe1-0000-04a4 Yes

[Aaron Biver_2]

Osama,

Your kernel config file most likely does not have an entry for the emx driver. The genvmunix/doconfig is your most likely solution.

You said:
> I have tried to do the genvmunix/doconfig
> steps but still no luck.

Please elaborate. What did you do and what went wrong?

1) When you booted genvmunix, did emx driver get configured correctly?
(you can tell that emx driver is loaded via "sysconfig -q emx"...if it succeeds at all, then the driver is loaded, also, look for this error in the boot messages)

2) When you then ran doconfig, did you choose to overwrite previous config file? You should, since it is obvious that the current config file lacks the emx driver...and you don't want to reuse that bad config file.
(I'm pretty sure this is where you went wrong, since its a common problem)

3) when you finish building the kernel, copy it to the boot partition. If you have a cluster remember that 'boot' and 'root' partitions are not the same (cluster boot partition is /var/.../

[Osama Ahmed]

Ivan,
I have installed NHD7 and the system recognize the HBAs. The HBA Revision was new(FCA-2684 : Driver Rev 2.17 ) and required the NHD7 CD.

I have assigned points to Ivan and also to Aaron for this help.

Thanks

[Osama Ahmed]

The solution is NHD7 CD.