[opensuse] / as a LV - openSUSE Users - openSUSE Mailing Lists

newer
[opensuse] Disappeared Panel

[opensuse] / as a LV

older
[opensuse]...

LDB

17 Mar 2008 17 Mar '08

13:50

I hope this list can accommodate the SLES product, a well. Does anyone have any caveats about implementing "/" as a LV, especially with SuSE 10 SP1? Thanks, LDB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

Show replies by date

Ciro Iriarte

17 Mar 17 Mar

14:09

2008/3/17, LDB :

I hope this list can accommodate the SLES product, a well.

Does anyone have any caveats about implementing "/" as a LV, especially with SuSE 10 SP1?

Thanks,

LDB

It's fine, you'll have to leave /boot in a regular partition and everything will work. Regards, Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

LDB

14:33

Ciro Iriarte wrote:

2008/3/17, LDB :

...
I hope this list can accommodate the SLES product, a well.

Does anyone have any caveats about implementing "/" as a LV, especially with SuSE 10 SP1?

Thanks,

LDB

It's fine, you'll have to leave /boot in a regular partition and everything will work.

Regards, Ciro

That is what I thought, but I had an old server using an older MegaRAID and it would not activate the VG hence it would not mount the root volume. I had to resort to non-LVM for the root partition. When I booted it into rescue mode, it was fine. Thanks, LDB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

Ciro Iriarte

15:01

2008/3/17, LDB :

That is what I thought, but I had an old server using an older MegaRAID and it would not activate the VG hence it would not mount the root volume. I had to resort to non-LVM for the root partition.

When I booted it into rescue mode, it was fine.

Thanks,

LDB

What do you mean by "would not activate the VG"?, If it can boot from the same array using regular partitions, LVM should work. At home I have the root on top of LVM on top of MD raid1 running Opensuse 10.3@x86_64. At the office I have root on top of LVM on top of HP SmartArray (cciss driver) running SLES9SP3@{x86_64,i386} and everything works fine. Did you install with / on a LV or tried some kind of migration later? Regards, Ciro -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

LDB

18 Mar 18 Mar

13:56

Ciro Iriarte wrote:

2008/3/17, LDB :

...
That is what I thought, but I had an old server using an older MegaRAID and it would not activate the VG hence it would not mount the root volume. I had to resort to non-LVM for the root partition.

When I booted it into rescue mode, it was fine.

Thanks,

LDB

What do you mean by "would not activate the VG"?, If it can boot from the same array using regular partitions, LVM should work. At home I have the root on top of LVM on top of MD raid1 running Opensuse 10.3@x86_64. At the office I have root on top of LVM on top of HP SmartArray (cciss driver) running SLES9SP3@{x86_64,i386} and everything works fine. Did you install with / on a LV or tried some kind of migration later?

Regards, Ciro

Agreed, but after the autoyast installation process and during the 1st boot, it stops and spews the the following ... Attempting manual resume Waiting for device /dev/rootvg/root to appear: .................. not found -- exiting to /bin/sh $ but then when I boot into rescue mode it mounts just fine ... Any ideas?? LDB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

LDB

14:01

LDB wrote:

Ciro Iriarte wrote:

...
2008/3/17, LDB :

...
That is what I thought, but I had an old server using an older MegaRAID and it would not activate the VG hence it would not mount the root volume. I had to resort to non-LVM for the root partition.

When I booted it into rescue mode, it was fine.

Thanks,

LDB

What do you mean by "would not activate the VG"?, If it can boot from the same array using regular partitions, LVM should work. At home I have the root on top of LVM on top of MD raid1 running Opensuse 10.3@x86_64. At the office I have root on top of LVM on top of HP SmartArray (cciss driver) running SLES9SP3@{x86_64,i386} and everything works fine. Did you install with / on a LV or tried some kind of migration later?

Regards, Ciro

Agreed, but after the autoyast installation process and during the 1st boot, it stops and spews the the following ...

Attempting manual resume Waiting for device /dev/rootvg/root to appear: .................. not found -- exiting to /bin/sh $

but then when I boot into rescue mode it mounts just fine ...

Any ideas??

LDB

Scrutinizing even more I am discovering that it is seemingly not loading the cciss driver on the 1st reboot after the OS installation. Which does not make sense, since that is what was used to install the OS in the first place. LDB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

LDB

14:16

LDB wrote:

LDB wrote:

...
Ciro Iriarte wrote:

...
2008/3/17, LDB :

...
That is what I thought, but I had an old server using an older MegaRAID and it would not activate the VG hence it would not mount the root volume. I had to resort to non-LVM for the root partition.

When I booted it into rescue mode, it was fine.

Thanks,

LDB

What do you mean by "would not activate the VG"?, If it can boot from the same array using regular partitions, LVM should work. At home I have the root on top of LVM on top of MD raid1 running Opensuse 10.3@x86_64. At the office I have root on top of LVM on top of HP SmartArray (cciss driver) running SLES9SP3@{x86_64,i386} and everything works fine. Did you install with / on a LV or tried some kind of migration later?

Regards, Ciro

Agreed, but after the autoyast installation process and during the 1st boot, it stops and spews the the following ...

Attempting manual resume Waiting for device /dev/rootvg/root to appear: .................. not found -- exiting to /bin/sh $

but then when I boot into rescue mode it mounts just fine ...

Any ideas??

LDB

Scrutinizing even more I am discovering that it is seemingly not loading the cciss driver on the 1st reboot after the OS installation. Which does not make sense, since that is what was used to install the OS in the first place.

LDB

Scratch that last assessment it does load it ... LDB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

Pete Connolly

14:37

On Tuesday 18 March 2008 14:16:24 LDB wrote:

LDB wrote:

...
LDB wrote:

...
Ciro Iriarte wrote:

...
2008/3/17, LDB :

...
That is what I thought, but I had an old server using an older MegaRAID and it would not activate the VG hence it would not mount the root volume. I had to resort to non-LVM for the root partition.

When I booted it into rescue mode, it was fine.

Thanks,

LDB

What do you mean by "would not activate the VG"?, If it can boot from the same array using regular partitions, LVM should work. At home I have the root on top of LVM on top of MD raid1 running Opensuse 10.3@x86_64. At the office I have root on top of LVM on top of HP SmartArray (cciss driver) running SLES9SP3@{x86_64,i386} and everything works fine. Did you install with / on a LV or tried some kind of migration later?

Regards, Ciro

Agreed, but after the autoyast installation process and during the 1st boot, it stops and spews the the following ...

Attempting manual resume Waiting for device /dev/rootvg/root to appear: .................. not found -- exiting to /bin/sh $

but then when I boot into rescue mode it mounts just fine ...

Any ideas??

LDB

Scrutinizing even more I am discovering that it is seemingly not loading the cciss driver on the 1st reboot after the OS installation. Which does not make sense, since that is what was used to install the OS in the first place.

LDB

Scratch that last assessment it does load it ...

LDB

You might need to recreate your initrd using the mkinitrd command and using the 'feature' option (-f). From the help page... -f "feature list" Features to be enabled when generating initrd. Available features are: iscsi, md, mpath, lvm, lvm2, evms This is just to ensure that right lvm2 modules are included in the initial ram disk, plus the linuxrc has the required vgchange commands to activate the root lvm. I personally can't see a good reason to use lvms for root. The resizing ability is nice but I rarely resize root, just the seperate data lvms. Cheers Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

Moby

15:29

Pete Connolly wrote:

On Tuesday 18 March 2008 14:16:24 LDB wrote:

...
LDB wrote:

...
LDB wrote:

...
Ciro Iriarte wrote:

...
2008/3/17, LDB :

...
That is what I thought, but I had an old server using an older MegaRAID and it would not activate the VG hence it would not mount the root volume. I had to resort to non-LVM for the root partition.

When I booted it into rescue mode, it was fine.

Thanks,

LDB

What do you mean by "would not activate the VG"?, If it can boot from the same array using regular partitions, LVM should work. At home I have the root on top of LVM on top of MD raid1 running Opensuse 10.3@x86_64. At the office I have root on top of LVM on top of HP SmartArray (cciss driver) running SLES9SP3@{x86_64,i386} and everything works fine. Did you install with / on a LV or tried some kind of migration later?

Regards, Ciro

Agreed, but after the autoyast installation process and during the 1st boot, it stops and spews the the following ...

Attempting manual resume Waiting for device /dev/rootvg/root to appear: .................. not found -- exiting to /bin/sh $

but then when I boot into rescue mode it mounts just fine ...

Any ideas??

LDB

Scrutinizing even more I am discovering that it is seemingly not loading the cciss driver on the 1st reboot after the OS installation. Which does not make sense, since that is what was used to install the OS in the first place.

LDB

Scratch that last assessment it does load it ...

LDB

You might need to recreate your initrd using the mkinitrd command and using the 'feature' option (-f). From the help page...

-f "feature list" Features to be enabled when generating initrd. Available features are: iscsi, md, mpath, lvm, lvm2, evms

This is just to ensure that right lvm2 modules are included in the initial ram disk, plus the linuxrc has the required vgchange commands to activate the root lvm.

I personally can't see a good reason to use lvms for root. The resizing ability is nice but I rarely resize root, just the seperate data lvms.

Cheers

Pete

I had exactly the same problem - root cause was that Grub did not get installed to the MBR of /dev/cciss/c0d0. Fix was to boot into rescue mode, mount the root (/dev/system ... however your LVs are setup). Then mount /dev and /proc into the newly mounted root, chroot to the /dev/system/... root, and then re-run grub install to install into the MBR of /dev/cciss/c0d0. Worked like a charm here, hope it works for you as well. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

LDB

15:33

Moby wrote:

Pete Connolly wrote:

...
On Tuesday 18 March 2008 14:16:24 LDB wrote:

...
LDB wrote:

...
LDB wrote:

...
Ciro Iriarte wrote:

...
2008/3/17, LDB :

> That is what I thought, but I had an old server using an older > MegaRAID and it would not activate the VG hence it would not > mount the root volume. I had to resort to non-LVM for the root > partition. > > When I booted it into rescue mode, it was fine. > > Thanks, > > > LDB > What do you mean by "would not activate the VG"?, If it can boot from the same array using regular partitions, LVM should work. At home I have the root on top of LVM on top of MD raid1 running Opensuse 10.3@x86_64. At the office I have root on top of LVM on top of HP SmartArray (cciss driver) running SLES9SP3@{x86_64,i386} and everything works fine. Did you install with / on a LV or tried some kind of migration later?

Regards, Ciro

Agreed, but after the autoyast installation process and during the 1st boot, it stops and spews the the following ...

Attempting manual resume Waiting for device /dev/rootvg/root to appear: .................. not found -- exiting to /bin/sh $

but then when I boot into rescue mode it mounts just fine ...

Any ideas??

LDB

Scrutinizing even more I am discovering that it is seemingly not loading the cciss driver on the 1st reboot after the OS installation. Which does not make sense, since that is what was used to install the OS in the first place.

LDB

Scratch that last assessment it does load it ...

LDB

You might need to recreate your initrd using the mkinitrd command and using the 'feature' option (-f). From the help page...

-f "feature list" Features to be enabled when generating initrd. Available features are: iscsi, md, mpath, lvm, lvm2, evms

This is just to ensure that right lvm2 modules are included in the initial ram disk, plus the linuxrc has the required vgchange commands to activate the root lvm.

I personally can't see a good reason to use lvms for root. The resizing ability is nice but I rarely resize root, just the seperate data lvms.

Cheers

Pete

I had exactly the same problem - root cause was that Grub did not get installed to the MBR of /dev/cciss/c0d0. Fix was to boot into rescue mode, mount the root (/dev/system ... however your LVs are setup). Then mount /dev and /proc into the newly mounted root, chroot to the /dev/system/... root, and then re-run grub install to install into the MBR of /dev/cciss/c0d0. Worked like a charm here, hope it works for you as well.

Thank you Moby .. Great fix .. now I just have to figure out how to get it automated. :) Thanks, LDB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

Pete Connolly

22:43

Moby wrote:

...
Pete Connolly wrote:

...
On Tuesday 18 March 2008 14:16:24 LDB wrote:

...
LDB wrote:

...
LDB wrote:

...
> > Agreed, but after the autoyast installation process and during the 1st boot, it stops and spews the the following ...

Attempting manual resume Waiting for device /dev/rootvg/root to appear: .................. not found -- exiting to /bin/sh $

but then when I boot into rescue mode it mounts just fine ...

Any ideas??

LDB

Scrutinizing even more I am discovering that it is seemingly not loading the cciss driver on the 1st reboot after the OS installation. Which does not make sense, since that is what was used to install the OS in the first place.

LDB

Scratch that last assessment it does load it ...

LDB

You might need to recreate your initrd using the mkinitrd command and using the 'feature' option (-f). From the help page...

-f "feature list" Features to be enabled when generating initrd. Available features are: iscsi, md, mpath, lvm, lvm2, evms

This is just to ensure that right lvm2 modules are included in the initial ram disk, plus the linuxrc has the required vgchange commands to activate the root lvm.

I personally can't see a good reason to use lvms for root. The resizing ability is nice but I rarely resize root, just the seperate data lvms.

Cheers

Pete

I had exactly the same problem - root cause was that Grub did not get installed to the MBR of /dev/cciss/c0d0. Fix was to boot into rescue mode, mount the root (/dev/system ... however your LVs are setup). Then mount /dev and /proc into the newly mounted root, chroot to the /dev/system/... root, and then re-run grub install to install into the MBR of /dev/cciss/c0d0. Worked like a charm here, hope it works for you as well.

Thank you Moby .. Great fix .. now I just have to figure out how to get it automated. :)

Thanks,

LDB I'm going to have to try this in the morning on my P2V migrated system. I've got a double whammy of removing the cciss drivers from the initrd and replacing them with the lsilogic drivers required for VMware (mptscsih and mptbase) plus getting the initrd to actually activate the lvm2 volume group that contains the root partition. Under the rescue system, all is fine, but trying to force mkinitrd to use lvm commands (this is a SLES9 server being 'migrated' to a VM) to activate the root

LDB wrote: partition is still failing. I'll press on with it, but I still think that a root partition on an LVM is over engineering and it limits what you can do in the future, such as virtualising servers. I can understand LVM for /var, /opt/, /usr etc. but for /root? Too complex and not really required. I'm a dedicated believer in keeping things simple. :) Cheers Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

Sam Clemens

22:57

Pete Connolly wrote:

...
Moby wrote:

...
Pete Connolly wrote:

...
On Tuesday 18 March 2008 14:16:24 LDB wrote:

...
LDB wrote:

...
LDB wrote:

>> >> > Agreed, but after the autoyast installation process and during the > 1st boot, it stops and spews the the following ... > > > Attempting manual resume > Waiting for device /dev/rootvg/root to appear: > .................. > not found -- exiting to /bin/sh > $ > > > but then when I boot into rescue mode it mounts just fine ... > > Any ideas?? > > > LDB > Scrutinizing even more I am discovering that it is seemingly not loading the cciss driver on the 1st reboot after the OS installation. Which does not make sense, since that is what was used to install the OS in the first place.

LDB

Scratch that last assessment it does load it ...

LDB

You might need to recreate your initrd using the mkinitrd command and using the 'feature' option (-f). From the help page...

-f "feature list" Features to be enabled when generating initrd. Available features are: iscsi, md, mpath, lvm, lvm2, evms

This is just to ensure that right lvm2 modules are included in the initial ram disk, plus the linuxrc has the required vgchange commands to activate the root lvm.

I personally can't see a good reason to use lvms for root. The resizing ability is nice but I rarely resize root, just the seperate data lvms.

Cheers

Pete

I had exactly the same problem - root cause was that Grub did not get installed to the MBR of /dev/cciss/c0d0. Fix was to boot into rescue mode, mount the root (/dev/system ... however your LVs are setup). Then mount /dev and /proc into the newly mounted root, chroot to the /dev/system/... root, and then re-run grub install to install into the MBR of /dev/cciss/c0d0. Worked like a charm here, hope it works for you as well.

Thank you Moby .. Great fix .. now I just have to figure out how to get it automated. :)

Thanks,

LDB I'm going to have to try this in the morning on my P2V migrated system. I've got a double whammy of removing the cciss drivers from the initrd and replacing them with the lsilogic drivers required for VMware (mptscsih and mptbase) plus getting the initrd to actually activate the lvm2 volume group that contains the root partition. Under the rescue system, all is fine, but trying to force mkinitrd to use lvm commands (this is a SLES9 server being 'migrated' to a VM) to activate the root

LDB wrote: partition is still failing. I'll press on with it, but I still think that a root partition on an LVM is over engineering and it limits what you can do in the future, such as virtualising servers. I can understand LVM for /var, /opt/, /usr etc. but for /root? Too complex and not really required.

Worse... it's not /root (super-user's home directory) but /. And asking for real headache if the root volume crashes and the system needs to be restored from backup.

I'm a dedicated believer in keeping things simple. :)

Cheers

Pete

-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

LDB

19 Mar 19 Mar

12:41

Sam Clemens wrote:

And asking for real headache if the root volume crashes and the system needs to be restored from backup.

I agree with Sam, but I just like flexibility in all environments. I have abandoned the LV root, due to all the issues and and uncertainty. Let me know what your tests reveal though .. :) Thanks, LDB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

Lars Marowsky-Bree

30 Mar 30 Mar

16:34

On 2008-03-19T08:41:48, LDB wrote:

...
And asking for real headache if the root volume crashes and the system needs to be restored from backup. I agree with Sam, but I just like flexibility in all environments. I have abandoned the LV root, due to all the issues and and uncertainty.

All my systems run with root on LVM. I've never had a problem since 6.4, neither with swap on LVM as well. Yes, I keep /boot separate. Regards, Lars -- Teamlead Kernel, SuSE Labs, Research and Development SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

Moby

17:38

Lars Marowsky-Bree wrote:

On 2008-03-19T08:41:48, LDB wrote:

...
...
And asking for real headache if the root volume crashes and the system needs to be restored from backup.

I agree with Sam, but I just like flexibility in all environments. I have abandoned the LV root, due to all the issues and and uncertainty.

All my systems run with root on LVM. I've never had a problem since 6.4, neither with swap on LVM as well. Yes, I keep /boot separate.

Regards, Lars

Same here, multiple servers with / on LVM, no issues. -- --Moby They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. -- Benjamin Franklin -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

Anders Johansson

18 Mar 18 Mar

23:47

LDB wrote:

...
I had exactly the same problem - root cause was that Grub did not get installed to the MBR of /dev/cciss/c0d0. Fix was to boot into rescue mode, mount the root (/dev/system ... however your LVs are setup). Then mount /dev and /proc into the newly mounted root, chroot to the /dev/system/... root, and then re-run grub install to install into the MBR of /dev/cciss/c0d0. Worked like a charm here, hope it works for you as well.

Thank you Moby .. Great fix .. now I just have to figure out how to get it automated. :)

Are you saying you tested it and it worked? I don't see how it could possibly be the problem. Your machine booted, so grub must be there I think Pete Connolly's advise about using mkinitrd -f lvm2 is more likely to work. But you may have run into a bug in the SP1 mkinitrd. I suggest you boot the system using the installer's "boot installed system" and run an online update to get the latest fixes You might also consider opening a call with novell support, so it can be properly investigated, if none of the ideas in this thread work Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

LDB

19 Mar 19 Mar

01:35

Anders Johansson wrote:

LDB wrote:

...
...
I had exactly the same problem - root cause was that Grub did not get installed to the MBR of /dev/cciss/c0d0. Fix was to boot into rescue mode, mount the root (/dev/system ... however your LVs are setup). Then mount /dev and /proc into the newly mounted root, chroot to the /dev/system/... root, and then re-run grub install to install into the MBR of /dev/cciss/c0d0. Worked like a charm here, hope it works for you as well.

Thank you Moby .. Great fix .. now I just have to figure out how to get it automated. :)

Are you saying you tested it and it worked?

I don't see how it could possibly be the problem. Your machine booted, so grub must be there

I think Pete Connolly's advise about using mkinitrd -f lvm2 is more likely to work.

But you may have run into a bug in the SP1 mkinitrd. I suggest you boot the system using the installer's "boot installed system" and run an online update to get the latest fixes

You might also consider opening a call with novell support, so it can be properly investigated, if none of the ideas in this thread work

Anders

No the grub-install did not work for the reasons you specified. Yep, I was told in the opensuse-autoinstall list that there is a bug with mkinitrd. Good suggestion Anders .. Thanks, LDB -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Reply

Sign in to reply online Use email software

5877

Age (days ago)

5890

Last active (days ago)

Download

16 comments

7 participants

tags

participants (7)

Anders Johansson
Ciro Iriarte
Lars Marowsky-Bree
LDB
Moby
Pete Connolly
Sam Clemens