https://bugzilla.novell.com/show_bug.cgi?id=398356
User rhg@marxmeier.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=398356#c8
Roland Genske changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rhg@marxmeier.com
--- Comment #8 from Roland Genske 2008-06-21 11:19:03 MDT ---
I think I can contribute. I get the same problem while trying a network
installation.
My partition scheme is (this is a VMware test installation before installing
the real thing [hosted root server in a remote data center]):
Disk /dev/sda: 5368 MB, 5368709120 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 9 72261 fd Linux raid autodetect
/dev/sda2 10 42 265072+ fd Linux raid autodetect
/dev/sda3 43 652 4899825 fd Linux raid autodetect
Disk /dev/sdb: 5368 MB, 5368709120 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 9 72261 fd Linux raid autodetect
/dev/sdb2 10 42 265072+ fd Linux raid autodetect
/dev/sdb3 43 652 4899825 fd Linux raid autodetect
Raid arrays:
/dev/md0 mounted as /boot consisting of /dev/sda1 and /dev/sdb1
/dev/md1 mounted as swap consisting of /dev/sda2 and /dev/sdb2
/dev/md2 mounted as / consisting of /dev/sda3 and /dev/sdb3
During installation the error message below appears on the shell where I did
the ssh login and started yast:
--- snip ---
*** Starting YaST2 ***
error: cannot open Packages index using db3 - No such file or directory (2)
Use of uninitialized value $extended_dev in string eq at
/usr/lib/perl5/vendor_perl/5.10.0/Bootloader/Core/GRUB.pm line 852 (#1)
(W uninitialized) An undefined value was used as if it were already
defined. It was interpreted as a "" or a 0, but maybe it was a mistake.
To suppress this warning assign a defined value to your variables.
To help you figure out what was undefined, perl will try to tell you the
name of the variable (if any) that was undefined. In some cases it cannot
do this, so it also tells you what operation you used the undefined value
in. Note, however, that perl optimizes your program and the operation
displayed in the warning may not necessarily appear literally in your
program. For example, "that $foo" is usually optimized into "that "
. $foo, and the warning will refer to the concatenation (.) operator,
even though there is no . in your program.
--- snap ---
The first reboot then fails with an "invalid boot sector" error message.
With the help of the Rescue System I found that /etc/grub.conf was setup
incorrectly:
setup --stage2=/boot/grub/stage2 (hd1,0) (hd0,0)
quit
This should have been:
setup --stage2=/boot/grub/stage2 (hd0,0) (hd0,0)
setup --stage2=/boot/grub/stage2 (hd1,0) (hd0,0)
quit
The problem can be fixed by correcting /etc/grub.conf and then invoking
grub-install. After that, the system successfully boots and the installation
can continue with /usr/lib/YaST2/startup/YaST2.ssh.
Good that I tried this in a test installation before using this on the remote
server :-)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.