Release Notes
<InventoryError lang="en">
<SPStatus result="false" module="MaserIE -i">
<Message> Inventory Failure: Partition Failure - Attach partition has failed</Message>
</SPStatus><SPStatus result="false" module="MaserIE -i">
<Message>Invalid inventory results.</Message>
</SPStatus><SPStatus result="false">
To fix the issue, stop the USB arbitration service and run the DUPs,
or Inventory Collector.
Do the following to stop the USB arbitration service:
1. Use ps aux | grep usb to find out if the USB arbitration service
is running.
2. To stop the USB arbitration service from starting up at bootup,
use chkconfig usbarbitrator off.
3. Reboot the server after stopping the usbarbitrator to allow the
DUPs and/or the Inventory collector to run.
If you require the usbarbitor, enable it manually. To enable the
usbarbitrator, run the command - chkconfig usbarbitrator on.
(373924)
=====================================================================
USER NOTES FOR UPGRADE ON SUPPORTED RED HAT ENTERPRISE LINUX,SUSE LINUX
ENTERPRISE SERVER AND VMWARE ESX OPERATING SYSTEMS
=====================================================================
* Under some conditions with DKMS versions prior to version 2.0.9,
device driver build may fail. This may prevent Server
Administrator from installing. You may see the following
error message:
"Building module:
cleaning build area....(bad exit status: 2)
make KERNELRELEASE=2.6.5-7.232-smp -C src KSP=/lib/modules/
2.6.5-7.232-smp/build MANDIR=%{_mandir}....(bad exit status: 2)
Error! Bad return status for module build on kernel:
2.6.5-7.232-smp (x86_64)
Consult the make.log in the build directory
/var/lib/dkms/e1000/6.2.11/build/ for more information."
To resolve the device driver build problems:
1. Update the DKMS version to 2.0.9 or later.
2. Uninstall the kernel source on your system.
3. Reinstall the kernel source on your system.
4. Build and install the device driver that was failing to
build.
5. If Server Administrator has failed to install, either
install Server Administrator using the following script,
"./srvadmin-install.sh"
OR
install the appropriate Server Administrator RPMs.
(31564) (31829) (42077)