Highlighted
Absent Member.
Absent Member.
1046 views

Getting wierd behaviour of SLES11 SP1 on XenCenter5.6 FP1

Hi,

I am trying to install SLES11 SP1 on XenCenter Virtual image and while Installation finding that it is showing 4 disks (hda, hdb, sda & sdb) instead of 2 disks.

Here is my observations:
1. Checked SLES11SP1 OS installation on Xen virtual image (5.6 FP1 -
build38895), seeing 4 disks (hda, hdb, sda, sdb) instead of 2 disks (either
hda, hdb, or sda, sdb).
2. On The same virtual instance, SLES11 GA shows proper 2 disks hda & hdb
3. When upgraded the SLES11GA instance with the SLES11SP1 OS, again during
installation it shows 4 disks and after OS installation completed also it shows
only 4 disks (hda, hdb, sda, sdb). That is, in SLES11 GA it was only 2 disks
and now after upgrde it shows 4 disks (hda, hdb, sda, sdb).
4. On the same instance, SLES10SP3 is installed successfully and shows only 2
disks hda & hdb
5. Even with the new virtual instance on XenCenter, I am getting the same behaviour.

here is the output after SLES11 SP1 installation:
*****************************************************************************
xensles11sp1: # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 17G 3.9G 13G 25% /
devtmpfs 939M 152K 939M 1% /dev
tmpfs 939M 24K 939M 1% /dev/shm
/dev/sda2 1004M 42M 912M 5% /boot
/dev/sr0 2.9G 2.9G 0 100% /media/SLES-11-SP1-DVD-x86_64.0432..001


xensles11sp1: #
You have new mail in /var/spool/mail/root
xensles11sp1: #
xensles11sp1: #
xensles11sp1: # cat /etc/*release
LSB_VERSION="core-2.0-noarch:core-3.2-noarch:core-4.0-noarch:core-2.0-x86_64:core-3.2-x86_64:core-4.0-x86_64"
SUSE Linux Enterprise Server 11 (x86_64)
VERSION = 11
PATCHLEVEL = 1
xensles11sp1:# fdisk -l

Disk /dev/hdb: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x86aa86aa

Disk /dev/hdb doesn't contain a valid partition table

Disk /dev/hda: 26.8 GB, 26843545600 bytes
255 heads, 63 sectors/track, 3263 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000b81a5

Device Boot Start End Blocks Id System
/dev/hda1 2 2220 17824117+ 83 Linux
/dev/hda2 * 2221 2350 1044225 83 Linux
/dev/hda3 2351 2872 4192965 82 Linux swap / Solaris

Disk /dev/sdb: 21.5 GB, 21474836480 bytes
255 heads, 63 sectors/track, 2610 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x86aa86aa

Disk /dev/sdb doesn't contain a valid partition table

Disk /dev/sda: 26.8 GB, 26843545600 bytes
255 heads, 63 sectors/track, 3263 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x000b81a5

Device Boot Start End Blocks Id System
/dev/sda1 2 2220 17824117+ 83 Linux
/dev/sda2 * 2221 2350 1044225 83 Linux
/dev/sda3 2351 2872 4192965 82 Linux swap / Solaris
xensles11sp1: # df -h
Filesystem Size Used Avail Use% Mounted on
/dev/sda1 17G 3.9G 12G 25% /
devtmpfs 939M 152K 939M 1% /dev
tmpfs 939M 24K 939M 1% /dev/shm
/dev/sda2 1004M 42M 912M 5% /boot
/dev/sr0 2.9G 2.9G 0 100% /media/SLES-11-SP1-DVD-x86_64.0432..001
Labels (2)
0 Likes
1 Reply
Highlighted
Absent Member.
Absent Member.

Re: Getting wierd behaviour of SLES11 SP1 on XenCenter5.6 FP1

Amrishparikh,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.