From: matilda matilda (matilda_at_grandel.de)
Date: Thu May 24 2007 - 08:41:03 CEST
Message-Id: <46554F94.117B.0044.0@grandel.de> Date: Thu, 24 May 2007 08:41:03 +0200 From: "matilda matilda" <matilda@grandel.de> Subject: [suse-sles-e] Several Problems with EVMS and SLES10
Hi all,
after spending a half workday finding out what does not work,
I hope now to get the right hints here.
The story:
- Installed SLES10 as guest in VMWare-Server 1.0.3 and wanted
to use EVMS as it is stated to be THE Enterprise Volume Manager.
(EVMS given the control over all devices)
- Found the right manual 'SLES 10 Storage Administration Guide for
EVMS'
(http://www.novell.com/documentation/sles10/index.html) and did the
steps
described at 'Configuring the System Device at Install to Use EVMS'.
- Did a correct product registration at install time.
- Did no update while installing.
- After complete installation I did a reboot. System came up as
expected.
- Now I started Yast and within Yast 'Software->Online Update'.
- The first step was only the update of libzypp (backend blabla)
- The second update mirrored the internet ;-))
- As there was a kernel update I rebooted the machine after the update
NOW I have the following:
- Kernel comes up
- I get the following message:
--------------------8<-----------------------------------------------------
Loading dm-snapshot
Loading jbd
Loading ext3
resume device /dev/evms/lvm2/vgsystem/lvswap
Waitinf for device /dev/evms/lvm2/vgsystem/lvroot to appear: ......not
found
$
--------------------8<-----------------------------------------------------
No I'm stuck.
I did a second try: Yes, yes, I was pessimistic enough to make a
snapshot in
VMWare before the update.
Did all as above except the last booting step. Here I wrote a new
initrd-image
with mkinitrd (I saw it's also a part of the updated packages).
And I tried to write GRUB once again. BUT: Installing neither GRUB nor
LILO liked
to be installed out of Yast:
With GRUB there seems to be some parsing errors. The generated grub
command is not
valid in my opinion:
---------------------------8<-------------------------------------------------
grub> install --stage2=/boot/grub/stage2 /grub/stage1 d (hd0)
/grub/stage1 d (hd0) /grub/stage2 0x8000 (/dev/evms/sda1)/grub/menu.lst
---------------------------8<-------------------------------------------------
A simple 'grub-install /dev/sda' or 'grub-install /dev/evms/.nodes/sda'
does only
respond:
---------------------------8<-------------------------------------------------
/dev/evms/sda1 does not have any corresponding BIOS drive.
---------------------------8<-------------------------------------------------
Probably you all find it interesting enough to have a look at this
problem.
I have really bad experiences with EVMS under SLES9 and I hoped that it
is
mature enough to be used in a production environment now.
1) What do I have to do, when I get the first error message because no
filesystem
is found at first boot? (I don't have any tools in this stage.)
2) Why do I get the errors while installing GRUB or LILO? Is this
something special
with VMWare?
Best regards
Andreas Mock
---------------------------------------------------------------------
To unsubscribe, e-mail: suse-sles-e-unsubscribe@suse.com
For additional commands, e-mail: suse-sles-e-help@suse.com
This archive was generated by hypermail 2.1.7 : Thu May 24 2007 - 10:43:59 CEST