** Reply to message from Felix Miata <mrmazda@ij.net> on Sat, 29 Dec 2007 14:58:58 -0500
On 2007/12/29 20:27 (GMT+0200) Stan Goodman apparently typed:
Today I installed a maintenance copy of v10.3 in a formerly unused 10GB of the
What exactly is a "maintenance copy"?
I'm sorry if the terminology is unconventional. I installed a small v10.3 for maintenance purposes; it was one of your suggestions.
HD. That installation seems to work properly, but I don't understand why the boot sequence is as it is:
The maintenance copy has but one partition in addition to SWAP. In setting up the installation, I was very careful to arrange that GRUB be installed in the root partition, rather than the MBR. After setting the configuration and before confirming actual installation, I verified that this was the case. I expected therefore that the boot sequence would be: OS/2 Boot Manager, followed by whatever line of BM is chosen. What actually happens is as follows:
1) openSuSE (maintenance partition) Welcome screen, with its list of choices 2) I choose "Boot from Hard Disk"
That choice usually only occurs when booting from installation or recovery media. Did you ever remove the DVD from the drive after installing 10.3? Do you see a syslinux message briefly on screen before the Welcome screen?
Ach!! I never removed the DVD from the drive -- even after the installation was complete. It's so obvious. Well, I've taken it out now, and am deeply embarrassed. I can only apologize for bothering you and Rajko unnecessarily. Of course now the boot sequence is exactly what it should be. Tomorrow or the next day I'll do the necessarily retrieval of data that was not backed up. Then I'll install v10.3 over the failed upgrade, but with some changes in partitioning. I will alloacate 20GB for /root and the same amount for /home, so that user apps and data will not be affected by any future upgrading disaster. All the partitions are EXT3 (no more XFS). Therefore no need for special partitions in which to put GRUB -- I eventually learn lessons; it just takes more time than it used to. If it is true that OS/2 supports a EXT3 driver, I might instead do away with the maintenance partition, and rely on OS/2 (actually eCS v1.1) for emergency manipulation; I have to think about that.
The easiest solution for you might be to boot into OS/2 and reinstall standard MBR code with DFSee or LVM.EXE, and at the same time verify that the 0Ah partition is marked as the only active/startable partition in the master partition table.
It is, of course. Many, many thanks .... and apologies. -- Stan Goodman Qiryat Tiv'on Israel "Windows - a hairball of software" -- Scott McNealy, Sun Microsystems -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org