Upgradinin to OES 11 sp1 ,Mount options of root

Question

Hi
Got a Ques about
"Changing the Mount Options Before an Upgrade"
in "Preparing the Server You Are Upgrading"
I sazs
I should change to "mount by Device ID or PATH"
My partitions are
dev/sda = 200 MB boot ( = no problems to change to Device boot)
dev/sdb = 20 GB Linux LVM
made as a VG01
containing a swap volume on 1,5 GB + the rest as 18,5GB root volume
Here I cant Change anything ....in the SDB and volumes are the "device/path" options greyed out, Is this OK
It still warns me about "upgrading"
Please advice

Answer 1

Originally Posted by KBOYLE
Landersson wrote:
>
> Hi
> Got a Ques about
> "Changing the Mount Options Before an Upgrade"
> in "Preparing the Server You Are Upgrading"
If you only have one hard drive, I wouldn't worry about it. With two
hard drives, for example, sdb could appear as sda and vise versa.
With multiple hard drives or multiple paths to your storage device the
device name can change depending upon which one SLES encounters first.
By assigning permanent names (mount by Device ID or PATH) that won't
happen.
Kevin Boyle - Knowledge Partner
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
Thanks for Your anwser ,
I Doo got a serie of servers tha needs update,
all got SDA1 as boot =20 MB and the rest as LVM (SDB) Swap and root ,,, LVM just to be able to expand. all ext3
I still don't get how and where to "change"
Sorry for my extreme sluggish mind
Well My fstab looks like
/dev/VG00/swap swap swap defaults 0 0
/dev/VG00/root / ext3 acl,user_xattr 1 1
/dev/sda1 /boot ext3 acl,user_xattr 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
And
menu.lst
# Modified by YaST2. Last modification on Tue Jul 2 14:03:41 CEST 2013
default 0
timeout 8
##YaST - generic_mbr
gfxmenu (hd0,0)/message
##YaST - activate
###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Server 11 SP1 - 2.6.32.12-0.7
root (hd0,0)
kernel /vmlinuz-2.6.32.12-0.7-default root=/dev/VG00/root resume=/dev/VG00/swap
splash=silent crashkernel=128M-:64M showopts vga=0x317
initrd /initrd-2.6.32.12-0.7-default
###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE Linux Enterprise Server 11 SP1 - 2.6.32.12-0.7
root (hd0,0)
kernel /vmlinuz-2.6.32.12-0.7-default root=/dev/VG00/root showopts ide=nodma apm=off
noresume edd=off powersaved=off nohz=off highres=off processor.max_cstate=1 nomodeset
x11failsafe vga=0x317
initrd /initrd-2.6.32.12-0.7-default
###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
rootnoverify (fd0)
chainloader +1
devpts /dev/pts devpts mode=0620,gid=5 0 0
And bootloader
## Path: System/Bootloader
## Description: Bootloader configuration
## Type: list(grub,lilo,none)
## Default: grub
LOADER_TYPE="grub"
DEFAULT_NAME="SUSE Linux Enterprise Server 11 SP1 - 2.6.32.12-0.7"
DEFAULT_APPEND="resume=/dev/VG00/swap splash=silent crashkernel=128M-:64M showopts"
DEFAULT_VGA="0x317"
FAILSAFE_APPEND="showopts ide=nodma apm=off noresume edd=off powersaved=off nohz=off
highres=off processor.max_cstate=1 nomodeset x11failsafe"
FAILSAFE_VGA="0x317"
XEN_KERNEL_APPEND="resume=/dev/VG00/swap splash=silent showopts"
XEN_APPEND=""
XEN_VGA="0x317"
## Path: System/Bootloader
## Description: Bootloader configuration
## Type: yesno
## Default: no
# Should the boot cycle detection be used to
# avoid unconditional reboot cycles of not
# supervised system.
CYCLE_DETECTION="no"
## Type: integer(0:)
## Default: 1
# The number of the entry in grub's menu.lst
# which should be used on the next reboot cycle.
# Note that the first entry has the number 0.
CYCLE_NEXT_ENTRY="1"
## Path: System/Bootloader
## Description: Bootloader configuration
## Type: list(floppy,mbr,root,boot,custom,none)
## Default: mbr
# Location of boot loader.
# For making the change effect run bootloader configuration tool
LOADER_LOCATION=""
'xxxxxxxxxxxxxxxxxxxxx
And https://www.novell.com/documentation...a/bv6uejh.html section 5.4.1 doesnt make any sense for mee