Environment
Novell Open Enterprise Server 2
(OES 2)
Novell Open Enterprise Server 2 (OES 2) Support Pack 1
Novell Open Enterprise Server 2 (OES 2) Support Pack 1
Situation
Symptoms
- After upgrading from OES 1
Linux to OES 2 Linux some pools can not be seen in NSSMU.
- As the system boots
device-mapper errors are reported.
- When going to NSSMU and
selecting Devices errors similar to the following are logged in/var/log/messages:
Dec 20 12:10:09 s13 kernel: device-mapper: dm-linear: Device lookup failed
Dec 20 12:10:09 s13 kernel: device-mapper: error adding target to table
Dec 20 12:10:09 s13 kernel: device-mapper: device 253:8 too small for target
Dec 20 12:10:09 s13 kernel: device-mapper: dm-linear: Device lookup failed
Dec 20 12:10:09 s13 kernel: device-mapper: error adding target to table
Dec 20 12:10:09 s13 kernel: device-mapper: device 253:9 too small for target
Dec 20 12:10:09 s13 kernel: device-mapper: dm-linear: Device lookup failed
Dec 20 12:10:09 s13 kernel: device-mapper: error adding target to table
Resolution
Contact Novell Technical
support for assistance.
Workaround
Prevent EVMS's dos segment manager from loading by moving the plugin aside:
Workaround
Prevent EVMS's dos segment manager from loading by moving the plugin aside:
mv $(find /lib*/evms -name
dos-*.so) /root
Additional Information
Root
cause
This issue is caused by an incorrect size being listed in the Master Boot Record for the pools. There is also an incorrect size on the free space at the end of the disk.
In OES1, the nwmgr plugin would be loaded before the dos plugin, whereas in OES2, the dos plugin is loaded first. The workaround prevents the dos plugin from being loaded when EVMS starts, thereby emulating OES1's behaviour.
This issue is caused by an incorrect size being listed in the Master Boot Record for the pools. There is also an incorrect size on the free space at the end of the disk.
In OES1, the nwmgr plugin would be loaded before the dos plugin, whereas in OES2, the dos plugin is loaded first. The workaround prevents the dos plugin from being loaded when EVMS starts, thereby emulating OES1's behaviour.