Quick Reference Guide

Unable To Update Bootloader When SUSE Linux Enterprise Server 10 SP 2 Is Upgraded To

SUSE Linux Enterprise Server 10 SP 3

Description When you install the boot loader while upgrading from SUSE Linux Enterprise Server 10 SP 2 to SUSE

Linux Enterprise Server 10 SP 3, the boot loader fails to mount.

Workaround To work around the issue, edit the GRUB configuration file to point to the correct root path.

This issue will be fixed in a future service pack of SUSE Linux Enterprise Server 10.

Cause This issue occurs because the function responsible for getting all the mount points does not return all

the values correctly.

Unable To Install SUSE Linux Enterprise Server 10 SP 3 On An iSCSI LUN

Description When you try to install SUSE Linux Enterprise Server 10 SP 3 64-bit using iSCSI boot and the spanning

tree is enabled in the network switch, the iSCSI session is established but you may not be able to log in.

Workaround Disable the spanning tree protocol on the switch ports on which the iSCSI boot NIC is configured.

For information about disabling the spanning tree, see the documentation that shipped with the switch.

Issues Fixed In SUSE Linux Enterprise Server 10 SP 2

This section contains information about general issues, resolutions, and their workarounds when using SUSE Linux

Enterprise Server 10 SP 2 on your Dell system.

System With The Root Device On The Logical Volume Manager (LVM) Fails To Boot After

Upgrading To SUSE Linux Enterprise Server 10 Service Pack 1

Description After you have upgraded from SUSE Linux Enterprise Server 10 GA to SUSE Linux Enterprise Server 10

Service Pack 1, the second stage installation hangs while booting. The following error message is

displayed:

ERROR: Waiting for device /dev/<vg>/<lv> to appear:

............not found -- exiting to /bin/sh

Cause The issue is caused by a bug in mkinitrd that does not match the Enterprise Volume Management System

(EVMS)/LVM devices.

Call Trace Observed With Direct Input Output On Pre-Formatted Tape Media Using Tar

Commands

Description I/O operations with tape drives must occur in fixed block mode with buffer size that is a multiple of pre-

formatted block size.

This issue is not specific to any HBA and occurs frequently when you are using the following media:

• Pre-formatted new media.

• Media formatted with different block size using a backup software.