On 07/30/2007 09:19 PM, Steve Kleene wrote:
On Sun, Jul 29, 2007 at 11:00:30PM -0400:
[I wrote that my fresh Etch install calls grub and then stops.]
I've tried several of the solutions suggested and am still stuck. In the
BIOS, Virus Protection was already disabled, and I tried turning off Power
Management. I've tried the different Access Modes for the drive (Auto, LBA,
Large).
Then I tried rebooting the installer in rescue mode and reinstalling grub (I
think it did "grub-install /dev/hde1").
I am absolutely not a Grub expert, but maybe you want "grub-install
/dev/hde".
How do you get a /dev/hde anyway? Perhaps your BIOS prefers to boot from
/dev/hd[a-d].
Take a look at your old Lilo config file. You might have needed to use
Lilo's map-drive feature to trick the BIOS into thinking that /dev/hde
is a more traditionally-positioned IDE drive. Grub has something similar.
Then I tried doing a whole new install of just the base system, but set up
these partitions:
IDE5 master (hde) - 41.2 GB IC35L040AVER07-0
#1 primary 98.7 MB B f ext3 /boot
#3 primary 39.5 GB f ext3 /
#5 logical 1.5 GB F swap swap
IDE5 slave (hdf) - 41.2 GB IC35L040AVER07-0
#1 primary 41.2 GB ext2
which gave /boot its own partition at the start of the disk. I tried this a
few times and should mention that the `f' flags in the table sometimes showed
as `F' or `K'. I think `F' means "format this", but I haven't been able to
track down what `f' and `K' mean.
It's nice to have a Knoppix or Kanotix disk when these situations arise.
The 'rescue' feature of the Debian install disk might suffice to let you
see what is actually on those partitions.
I hope that you rebooted after changing the partition table. On every
i386 computer I've used, under every O/S I've used (Windows 3.1-XP,
multiple Linux distros) I've used, the computer must be rebooted after
the partition table has been changed, or the system will be messed up.
I've never been clear on the exact reasoning, but that's the case.
As I said, these all still crashed when the boot got to grub. I wouldn't
have guessed that there was any need to have the boot files near the start of
the disk anyway. Until two days ago, this same disk in the same box had a
9.8-GB Win98 partition (1252 cylinders), followed by Red Hat, as follows:
[...]
I'm convinced that the 1024th cylinder limit doesn't relate to your
problem; however, you might consider using the "--force-lba" option to
"grub-install" next time.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
