Mailinglist Archive: opensuse (3336 mails)

< Previous Next >
Re: [SLE] Problems with initrd after mkinitrd
  • From: Carl Hartung <suselinux@xxxxxxxxxxxxx>
  • Date: Tue, 27 Dec 2005 11:00:19 -0500
  • Message-id: <200512271100.20946.suselinux@xxxxxxxxxxxxx>
On Tuesday 27 December 2005 09:25, Terry Eck wrote:
> Ever since I started using Linux (RedHat 4, 1996) I've always placed
> /boot as /dev/hda1 using 10-20 Mb and have never had a problem. This
> relates back to to old problem with tracks above 1024 on older disks.

Hi Terry, Hi All...

I have to acknowledge this problem exist(s/ed) on older hardware, but it is
also important to point out that modern drives and BIOSes set to use LBA
(which Grub and Linux 'speak') cleanly eliminates this specific limitation.
AIUI, under LBA, the current "interesting" addressing barrier is 137GB.

And Patrick,

I've studied the entire thread again, top to bottom, to see if we have
overlooked something, and I'll share these thoughts:

1. We don't know the manufacturer or age of the machines we're discussing...
no mainboard or CPU models/numbers etc... the only 'clue' is that you've seen
this problem "to some degree" under SuSE 9.1. The ages and make/model of
these systems are important clues.

2. Is the 2.5" to 3.5" "adapter" just a mechanical carrier, or is it also
involved in the (data) cabling? This adapter (coupled with WD's specific
recommendation that you *not* use this drive in your application) *and* the
inclusion of the highpoint driver are big enough 'atypical' factors that they
deserve special attention. You need to be certain that these have been
properly ruled out and aren't involved/contributing/confusing matters.

3. We should not overlook this one important clue: "... requires re-installing
grub which sometimes produces a hang on loading stage1.5."

All things being equal, I think Carlos' hypothesis is likely correct. I'll be
looking forward to your "report", so have fun and good luck!

- Carl

< Previous Next >