Ok, so this is what the scene is :

linux-g78h:~ # ls -al /dev/disk/by-id/
total 0
drwxr-xr-x 2 root root 220 Jan 7 12:44 .
drwxr-xr-x 5 root root 100 Jan 7 12:44 ..
lrwxrwxrwx 1 root root 9 Jan 7 12:44 edd-int13_dev80 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 7 12:44 edd-int13_dev80-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 7 12:44 edd-int13_dev80-part2 -> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 7 12:44 edd-int13_dev80-part3 -> ../../sda3
lrwxrwxrwx 1 root root 9 Jan 7 12:44 scsi-2221b000155f5d2d4 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jan 7 12:44 scsi-2221b000155f5d2d4-part1
-> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 7 12:44 scsi-2221b000155f5d2d4-part2
-> ../../sda2
lrwxrwxrwx 1 root root 10 Jan 7 12:44 scsi-2221b000155f5d2d4-part3
-> ../../sda3
lrwxrwxrwx 1 root root 9 Jan 7 12:44 usb-ASUS_CB-5216A_DEF10A4090DF
-> ../../sr0
linux-g78h:~ #
linux-g78h:~ # uname -a
Linux linux-g78h 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC
2007 i686 i686 i386 GNU/Linux
linux-g78h:~ #
linux-g78h:~ # cat /etc/grub.conf
setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0)
quit
linux-g78h:~ #
linux-g78h:~ # cat /boot/grub/menu.lst
# Modified by YaST2. Last modification on Mon Jan 7 19:40:30 UTC 2008
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 10 SP1
root (hd0,0)
kernel /vmlinuz-2.6.16.46-0.12-smp root=/dev/sda2 vga=0x31a
resume=/dev/sda3 showopts
initrd /initrd-2.6.16.46-0.12-smp

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- SUSE Linux Enterprise Server 10 SP1
root (hd0,0)
kernel /vmlinuz-2.6.16.46-0.12-smp root=/dev/sda2 vga=normal
showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0
edd=off 3
initrd /initrd-2.6.16.46-0.12-smp

###Don't change this comment - YaST2 identifier: Original name: linux###
title SUSE Linux Enterprise Server 10 SP1 ORG
root (hd0,0)
kernel /vmlinuz-2.6.16.46-0.12-smp root=/dev/sda2 vga=0x31a
resume=/dev/sda3 showopts
initrd /initrd-2.6.16.46-0.org.12-smp


So, I modified the fstab and menu.lst to replace all /dev/sdaX with
/dev/scsi-2221b000155f5d2d4-partX. It won't boot.

Any comments?

Thanks and Regards,
Pradipmaya.

On Jan 7, 2008 1:57 PM, <malahal@us.ibm.com> wrote:
> Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> > I did exactly what you said for SLES 10.1,
> > - Create custom partition
> > - Created partitions for /boot, / and swap of 100MB, 5GB and 1024MB
> > respectively on /dev/sda. So /dev/sda1 is for "/boot", /dev/sda2 for
> > "/" and /dev/sda3 for "swap"
> > - Under fstab option, selected Mount by device-id for each of the partition
> > - Reboot is fine
> > - But as I said earlier, mount, fstab, everything shows devcie names, not id
> >
> > Any way to mount it by device-id?
> > Is there a way that it can be chaned after installation? Or re-install
> > is the only way.
>
> I would just replace sd* names by their equivalent by-id names in fstab
> and grub.conf. Do 'ls -l /dev/disk/by-id/*' to get the by-id names
> corresponding to your named partitions'
>
> No need to re-install.
>
>
>
> -Malahal.
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> Ok, so this is what the scene is :
>
> linux-g78h:~ # ls -al /dev/disk/by-id/
> total 0
> drwxr-xr-x 2 root root 220 Jan 7 12:44 .
> drwxr-xr-x 5 root root 100 Jan 7 12:44 ..
> lrwxrwxrwx 1 root root 9 Jan 7 12:44 edd-int13_dev80 -> ../../sda
> lrwxrwxrwx 1 root root 10 Jan 7 12:44 edd-int13_dev80-part1 -> ../../sda1
> lrwxrwxrwx 1 root root 10 Jan 7 12:44 edd-int13_dev80-part2 -> ../../sda2
> lrwxrwxrwx 1 root root 10 Jan 7 12:44 edd-int13_dev80-part3 -> ../../sda3
> lrwxrwxrwx 1 root root 9 Jan 7 12:44 scsi-2221b000155f5d2d4 -> ../../sdb
> lrwxrwxrwx 1 root root 10 Jan 7 12:44 scsi-2221b000155f5d2d4-part1
> -> ../../sda1
> lrwxrwxrwx 1 root root 10 Jan 7 12:44 scsi-2221b000155f5d2d4-part2
> -> ../../sda2
> lrwxrwxrwx 1 root root 10 Jan 7 12:44 scsi-2221b000155f5d2d4-part3
> -> ../../sda3
> lrwxrwxrwx 1 root root 9 Jan 7 12:44 usb-ASUS_CB-5216A_DEF10A4090DF
> -> ../../sr0
> linux-g78h:~ #
> linux-g78h:~ # uname -a
> Linux linux-g78h 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC
> 2007 i686 i686 i386 GNU/Linux
> linux-g78h:~ #
> linux-g78h:~ # cat /etc/grub.conf
> setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0)
> quit
> linux-g78h:~ #
> linux-g78h:~ # cat /boot/grub/menu.lst
> # Modified by YaST2. Last modification on Mon Jan 7 19:40:30 UTC 2008
> 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 10 SP1
> root (hd0,0)
> kernel /vmlinuz-2.6.16.46-0.12-smp root=/dev/sda2 vga=0x31a
> resume=/dev/sda3 showopts
> initrd /initrd-2.6.16.46-0.12-smp
>
> ###Don't change this comment - YaST2 identifier: Original name: failsafe###
> title Failsafe -- SUSE Linux Enterprise Server 10 SP1
> root (hd0,0)
> kernel /vmlinuz-2.6.16.46-0.12-smp root=/dev/sda2 vga=normal
> showopts ide=nodma apm=off acpi=off noresume nosmp noapic maxcpus=0
> edd=off 3
> initrd /initrd-2.6.16.46-0.12-smp
>
> ###Don't change this comment - YaST2 identifier: Original name: linux###
> title SUSE Linux Enterprise Server 10 SP1 ORG
> root (hd0,0)
> kernel /vmlinuz-2.6.16.46-0.12-smp root=/dev/sda2 vga=0x31a
> resume=/dev/sda3 showopts
> initrd /initrd-2.6.16.46-0.org.12-smp
>
>
> So, I modified the fstab and menu.lst to replace all /dev/sdaX with
> /dev/scsi-2221b000155f5d2d4-partX. It won't boot.

/dev/scsi-2221b000155f5d2d4-partX is bogus! Your root device /dev/sda2
actually is edd-int13_dev80-part2, specifically it is
/dev/disk/by-id/edd-int13_dev80-part2. You should replace /dev/sdaX
with /dev/disk/by-id/edd-int13_dev80-partX

Also, make sure that what ever you replace with is a valid name. For
example, /dev/scsi-2221b000155f5d2d4-partX will NOT exist on your
system where as /dev/disk/by-id/edd-int13_dev80-part2 should exist.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Pradipmaya Maharana wrote:
> RHEL Steps worked perfectly for me but i have a question for SLES installation.
>
> Question. While installing SLES on multipath devices, the second step says:
>
> " 2. Complete the installation. Let the system boot up in multiuser mode.
> Make sure the root device, swap device are all referenced by their by-id
> device node entries instead of /dev/sd* type names. If they are not, fix
> them first."
>
> How do you check that root device and swap device are referenced by their by-id?
> And if it is not referenced by the by-id, how do I fix it? Re-install?
>
Check /etc/fstab. Those devices should be listed as /dev/disk/by-id/XXX.
If not (ie if their names are /dev/sdXX) look for the appropriate symlink
in /dev/disk/by-id and edit /etc/fstab.

Cheers,

Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Hi All,

Thanks for all your comments, it worked for installaions on partitions.

Now the question is:
Is it supposed to work the same way if the SLES is installed on LVM?
On SLES, under fstab, I do not see any device, except for the boot
device; other entries does not have /dev/deisk mention. In such
scenario, how am I supposed to make the /root device multipath-aware?

I tried the same with RHEL, but with RHEL installed (with linux mpath)
on LVM, it seems to be working fine. Is there anything I am missing on
SLES?

Thanks and Regards,
Pradipmaya.



On Jan 7, 2008 11:17 PM, Hannes Reinecke <hare@suse.de> wrote:
> Pradipmaya Maharana wrote:
> > RHEL Steps worked perfectly for me but i have a question for SLES installation.
> >
> > Question. While installing SLES on multipath devices, the second step says:
> >
> > " 2. Complete the installation. Let the system boot up in multiuser mode.
> > Make sure the root device, swap device are all referenced by their by-id
> > device node entries instead of /dev/sd* type names. If they are not, fix
> > them first."
> >
> > How do you check that root device and swap device are referenced by their by-id?
> > And if it is not referenced by the by-id, how do I fix it? Re-install?
> >
> Check /etc/fstab. Those devices should be listed as /dev/disk/by-id/XXX.
> If not (ie if their names are /dev/sdXX) look for the appropriate symlink
> in /dev/disk/by-id and edit /etc/fstab.
>
> Cheers,
>
> Hannes
> --
> Dr. Hannes Reinecke zSeries & Storage
> hare@suse.de +49 911 74053 688
> SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
> GF: Markus Rex, HRB 16746 (AG Nürnberg)
>
> --
>
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

On Tue, 2008-01-15 at 18:25 -0800, Pradipmaya Maharana wrote:
> Hi All,
>
> Thanks for all your comments, it worked for installaions on partitions.

Cool.
>
> Now the question is:
> Is it supposed to work the same way if the SLES is installed on LVM?

Supposed to

> On SLES, under fstab, I do not see any device, except for the boot
> device; other entries does not have /dev/deisk mention. In such

I am not clear about what you are mentioning here. Can you annotate with
a cut-n-paste of /etc/fstab ?

> scenario, how am I supposed to make the /root device multipath-aware?
>
> I tried the same with RHEL, but with RHEL installed (with linux mpath)
> on LVM, it seems to be working fine. Is there anything I am missing on
> SLES?
>
> Thanks and Regards,
> Pradipmaya.
>
>
>
> On Jan 7, 2008 11:17 PM, Hannes Reinecke <hare@suse.de> wrote:
> > Pradipmaya Maharana wrote:
> > > RHEL Steps worked perfectly for me but i have a question for SLES installation.
> > >
> > > Question. While installing SLES on multipath devices, the second step says:
> > >
> > > " 2. Complete the installation. Let the system boot up in multiuser mode.
> > > Make sure the root device, swap device are all referenced by their by-id
> > > device node entries instead of /dev/sd* type names. If they are not, fix
> > > them first."
> > >
> > > How do you check that root device and swap device are referenced by their by-id?
> > > And if it is not referenced by the by-id, how do I fix it? Re-install?
> > >
> > Check /etc/fstab. Those devices should be listed as /dev/disk/by-id/XXX.
> > If not (ie if their names are /dev/sdXX) look for the appropriate symlink
> > in /dev/disk/by-id and edit /etc/fstab.
> >
> > Cheers,
> >
> > Hannes
> > --
> > Dr. Hannes Reinecke zSeries & Storage
> > hare@suse.de +49 911 74053 688
> > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
> > GF: Markus Rex, HRB 16746 (AG Nürnberg)
> >
> > --
> >
> > dm-devel mailing list
> > dm-devel@redhat.com
> > https://www.redhat.com/mailman/listinfo/dm-devel
> >
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
--

----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

I'm very new to sles 10; sounds like you want to do root-on-LVM-on-multipath
I don't know if sles10 supports that.

Maybe 2 things to try:
(1) if /dev/rootVG/rootLV has a /dev/disk/by-id/ link then use that persistent name along with putting dm-multipath in INITRD modules list; then run mkinitrd and zipl

(2) Or, use the LVM persistent name, /dev/rootVG/rootLV, instead of a /dev/disk/by-id/ name

good luck.


--------------------------------------------------------
This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.


-----Original Message-----

From: dm-devel-bounces@redhat.com on behalf of Chandra Seetharaman
Sent: Tue 1/15/2008 9:32 PM
To: device-mapper development
Subject: Re: [dm-devel] Configuring multipath for root device

On Tue, 2008-01-15 at 18:25 -0800, Pradipmaya Maharana wrote:
> Hi All,
>
> Thanks for all your comments, it worked for installaions on partitions.

Cool.
>
> Now the question is:
> Is it supposed to work the same way if the SLES is installed on LVM?

Supposed to

> On SLES, under fstab, I do not see any device, except for the boot
> device; other entries does not have /dev/deisk mention. In such

I am not clear about what you are mentioning here. Can you annotate with
a cut-n-paste of /etc/fstab ?

> scenario, how am I supposed to make the /root device multipath-aware?
>
> I tried the same with RHEL, but with RHEL installed (with linux mpath)
> on LVM, it seems to be working fine. Is there anything I am missing on
> SLES?
>
> Thanks and Regards,
> Pradipmaya.
>
>
>
> On Jan 7, 2008 11:17 PM, Hannes Reinecke <hare@suse.de> wrote:
> > Pradipmaya Maharana wrote:
> > > RHEL Steps worked perfectly for me but i have a question for SLES installation.
> > >
> > > Question. While installing SLES on multipath devices, the second step says:
> > >
> > > " 2. Complete the installation. Let the system boot up in multiuser mode.
> > > Make sure the root device, swap device are all referenced by their by-id
> > > device node entries instead of /dev/sd* type names. If they are not, fix
> > > them first."
> > >
> > > How do you check that root device and swap device are referenced by their by-id?
> > > And if it is not referenced by the by-id, how do I fix it? Re-install?
> > >
> > Check /etc/fstab. Those devices should be listed as /dev/disk/by-id/XXX.
> > If not (ie if their names are /dev/sdXX) look for the appropriate symlink
> > in /dev/disk/by-id and edit /etc/fstab.
> >
> > Cheers,
> >
> > Hannes
> > --
> > Dr. Hannes Reinecke zSeries & Storage
> > hare@suse.de +49 911 74053 688
> > SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
> > GF: Markus Rex, HRB 16746 (AG Nürnberg)
> >
> > --
> >
> > dm-devel mailing list
> > dm-devel@redhat.com
> > https://www.redhat.com/mailman/listinfo/dm-devel
> >
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
--

----------------------------------------------------------------------
Chandra Seetharaman | Be careful what you choose....
- sekharan@us.ibm.com | .......you may get it.
----------------------------------------------------------------------


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel


--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> Hi All,
>
> Thanks for all your comments, it worked for installaions on partitions.
>
> Now the question is:
> Is it supposed to work the same way if the SLES is installed on LVM?

Hmmm, I don't know if LVM devices have by-id names. I never installed
SLES on LVM with multipath. Label is your best friend with LVM and that
is what RHEL uses, I believe.

> On SLES, under fstab, I do not see any device, except for the boot
> device; other entries does not have /dev/deisk mention. In such
> scenario, how am I supposed to make the /root device multipath-aware?

They probably have labels???

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Here are some details:

linux-qeh4:~ # ls -al /dev/disk/by-id/
total 0
drwxr-xr-x 2 root root 180 Jan 16 10:39 .
drwxr-xr-x 5 root root 100 Jan 16 10:12 ..
lrwxrwxrwx 1 root root 9 Jan 16 10:12 edd-int13_dev80 -> ../../sda
lrwxrwxrwx 1 root root 10 Jan 16 10:12 edd-int13_dev80-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 16 10:12 edd-int13_dev80-part2 -> ../../sda2
lrwxrwxrwx 1 root root 9 Jan 16 10:12 scsi-222f2000155c11879 -> ../../sdb
lrwxrwxrwx 1 root root 10 Jan 16 10:12 scsi-222f2000155c11879-part1
-> ../../sda1
lrwxrwxrwx 1 root root 10 Jan 16 10:12 scsi-222f2000155c11879-part2
-> ../../sda2
linux-qeh4:~ #
linux-qeh4:~ #
linux-qeh4:~ # cat /etc/fstab
/dev/system/root / reiserfs acl,user_xattr 1 1
/dev/sda1 /boot ext2 acl,user_xattr 1 2
/dev/system/swap swap swap defaults 0 0
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
devpts /dev/pts devpts mode=0620,gid=5 0 0
linux-qeh4:~ #
linux-qeh4:~ #
linux-qeh4:~ # uname -a
Linux linux-qeh4 2.6.16.46-0.12-smp #1 SMP Thu May 17 14:00:09 UTC
2007 i686 i686 i386 GNU/Linux
linux-qeh4:~ #
linux-qeh4:~ # mount
/dev/mapper/system-root on / type reiserfs (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sda1 on /boot type ext2 (rw,acl,user_xattr)
securityfs on /sys/kernel/security type securityfs (rw)

Let me know if you need any other information.

Malahal, are you saying that I should mount the "/" and "swap" by
volume label and it should be able to boot fine?

Thanks and Regards,
Pradipmaya.



On Jan 16, 2008 9:36 AM, <malahal@us.ibm.com> wrote:
> Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> > Hi All,
> >
> > Thanks for all your comments, it worked for installaions on partitions.
> >
> > Now the question is:
> > Is it supposed to work the same way if the SLES is installed on LVM?
>
> Hmmm, I don't know if LVM devices have by-id names. I never installed
> SLES on LVM with multipath. Label is your best friend with LVM and that
> is what RHEL uses, I believe.
>
> > On SLES, under fstab, I do not see any device, except for the boot
> > device; other entries does not have /dev/deisk mention. In such
> > scenario, how am I supposed to make the /root device multipath-aware?
>
> They probably have labels???
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
>
> Let me know if you need any other information.
>
> Malahal, are you saying that I should mount the "/" and "swap" by
> volume label and it should be able to boot fine?

What are /dev/system/root and /dev/system/swap? Are they symlinks or do
they have same major/minor number of corresponding LVM LVs?
Yes, volume labels may work but I never booted SLES with LVM.

-Malahal.

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel

# ls -al /dev/system/
total 0
drwx------ 2 root root 80 Jan 16 17:44 .
drwxr-xr-x 11 root root 6660 Jan 16 17:46 ..
lrwxrwxrwx 1 root root 23 Jan 16 17:44 root -> /dev/mapper/system-root
lrwxrwxrwx 1 root root 23 Jan 16 17:44 swap -> /dev/mapper/system-swap

Yes, /dev/system/root and swap are links, as shown above.

About volume labels, I tried assigning label to mount /dev/system/root
to label-root but it would fail.
I tried doing it through YaST/partitioner and it failed with the
following error:

"Failure occurred during following action:
Setting label on /dev/system/root to label-root.

System error code was : -3024"

Is there any other way to change the label.


Further information:
when I try to run "multipath -v3", it would not create any map , with
following error
222f2000155c11879: set ACT_CREATE (map does not exist)
222f2000155c11879: domap (0) failure for create/reload map

Thanks and Regards,
Pradipmaya.

On Jan 17, 2008 12:21 PM, <malahal@us.ibm.com> wrote:
> Pradipmaya Maharana [pradipmaya@gmail.com] wrote:
> >
> > Let me know if you need any other information.
> >
> > Malahal, are you saying that I should mount the "/" and "swap" by
> > volume label and it should be able to boot fine?
>
> What are /dev/system/root and /dev/system/swap? Are they symlinks or do
> they have same major/minor number of corresponding LVM LVs?
> Yes, volume labels may work but I never booted SLES with LVM.
>
> -Malahal.
>
>
> --
> dm-devel mailing list
> dm-devel@redhat.com
> https://www.redhat.com/mailman/listinfo/dm-devel
>

--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel