Re: [opensuse-autoinstall] "Invalid partition table" on SLES10SP2/3 with soft RAID
Thank you for responding.
On 6/17/2010 at 16:39, Uwe Gansert <ug@suse.de> wrote: on Thursday 17 June 2010 Andreas Taschner wrote:
I am trying to duplicate a problem at a customer that has a RAID1 setup with /boot, / and other partitions on md. For this I install SLES10SP2 as step one and upgrade to SLES10SP3 as step2. Doing this manually works fine, but when installing SP2 or upgrading to SP3 using AutoYaST, the
how do you upgrade with autoyast? you leave the partitioning as it is but format all system-relevant parts?
If we stick to the installation of SP2 for now, then I format md* and initialize both physical drives (added the initialize manually). Changing persistent_superblock from false to true has not changed the situation. What I find really strange about the upgrade profile (generated as the last step during the upgrade) also formats all partitions ??? So that one would probably never work anyway... I have attached an archive of the partition tag of both SP2 installation and SP2-->SP3 profiles.
/boot/grub/menu.lst refers to /dev/md? and I have tried configuring device.map to map to both /dev/sd? and /dev/disk/by-id/*. Another funny observation : Switching the bootable flag from sdb1 to sda1 changes the boot error from "Invalid partition able" to "No operating system"
So it looks like the RAID setup somehow does not make it to disk when using AutoYaST.
Any ideas ?
the only idea and bug that comes close to it is https://bugzilla.novell.com/show_bug.cgi?id=581523 it's about LVM but RAID was affected too. SP3 accidently pulls in multipath drivers into the ramdisk and those make trouble during the reboot. But actually your sympthons are a bit different, so I have doubts that you hit that problem.
Thank you for any inspiration. //Andreas
on Monday 21 June 2010 Andreas Taschner wrote:
What I find really strange about the upgrade profile (generated as the last step during the upgrade) also formats all partitions ??? So that one would probably never work anyway...
but that's normal. A cloned profile wants to format all partitions always. Autoyast does not know anymore what you decided to format/not format in the proposal screen. You have to change those format=true values to "false" by hand. No big deal I think. If you still have issues, maybe you want to create a bugzilla entry for that. It's easier to track then. -- ciao, Uwe Gansert Uwe Gansert SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) Business: http://www.suse.de/~ug listening to: "Falling" by Edge Of Dawn -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
On 6/28/2010 at 12:35, Uwe Gansert <ug@suse.de> wrote: on Monday 21 June 2010 Andreas Taschner wrote:
What I find really strange about the upgrade profile (generated as the last step during the upgrade) also formats all partitions ??? So that one would probably never work anyway...
but that's normal. A cloned profile wants to format all partitions always. Autoyast does not know anymore what you decided to format/not format in the proposal screen. You have to change those format=true values to "false" by hand. No big deal I think.
Ah - now I understand that. Thank you for explaining
If you still have issues, maybe you want to create a bugzilla entry for that. It's easier to track then.
I will do that when/if I get back to researching this again. //Andreas -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-autoinstall+help@opensuse.org
participants (2)
-
Andreas Taschner -
Uwe Gansert