Re: [SLE] Problems with initrd after mkinitrd

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


The Tuesday 2005-12-27 at 19:18 -0500, Carl Hartung wrote:

> More fodder to keep you up at nights ;-)
>
> On Tuesday 27 December 2005 13:16, Patrick Freeman wrote:
> <snip>
> > (BTW, thanks for the input, Terry) Well, interestingly, all of the
> > machines were booting at cylinder 2082 prior to the mkinitrd problem --
>
> Each cloned drive should theoretically have /boot and initrd "land" in the
> same physical location when the image is written, correct? Yet, sometimes and
> for unknown reasons, the clone doesn't completely "take" and you have to
> reinstall Grub to make the system bootable. Hmm... interesting clue...
>
> Please tell me you meant "sector" as in LBA and *not* "cylinder" as in CHS
> addressing? <shiver!><Ugh!> (Pardon my flashbacks...!)

No, it is track, ie, cylinder. That doesn't imply that the disk are using
CHS addressing, but only that he is partitioning using track numbers, as
is usual in fdisk.

Also, I gather he is talking of mkinitrd images, ie, ramdisk images, not
the disk cloning images. It is something different. The systems crash
sometimes after changing the initrd image.

I suggested that there could be a problem, in his case, when the image was
placed above some track number, perhaps 1024, and he is testing if that
hypothesis is correct by creating separate /boot partitions at low track
numbers.

The base for my idea is that grub and lilo have to use bios calls at first
to read the disk, and the bios might have problems with those disks. Its a
wild, educated guess ;-)

Let's wait and see! I'm curious :-)

- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76

iD8DBQFDseratTMYHG2NR9URAgFEAJ0Sfkiq3BWjKZS2lvekpZ2KV1l7EgCgg+s5
cWwWDPGpe5p7JuiPyeGShzg=
=5X4x
-----END PGP SIGNATURE-----


--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Relevant Pages

  • Re: Write-protect sctors?
    ... Remember that partitioning does modify the existing data on the disk, just the partition table, unless you chose to do a full format that data is still there. ... I imagine it would be possible for someone to modify the CMOS and protect any sectors they wish, but the attacker would undoubtedly need to have advanced knowledge of your system, BIOS, hard disk and geometry to make this attack possible. ... As the install progresses to the partitioning of the disc,I opt for the erase whole disc option.It progresses to a certain point and then quits with an error..repeatedly. ...
    (Focus-Linux)
  • Re: Old PC - ASUS P5A-B - Will not boot Linux (Ubuntu)
    ... > corresponds to the physical layout of the HDD) ... > The above is a summary of the info Ubuntu partitioning utility gives me. ... > I altered the BIOS boot sequence to boot C, A [but the original CDROM, ... chipset hard disk contoller with a 40G disk. ...
    (comp.os.linux.setup)
  • Re: How to use a corrupted hard drive as an external hard drive
    ... Do I just attach it and boot the computer like normal? ... Thank you in advance for any guidance you can give me as I am technically challenged and attaching all the cables correctly is a challenge. ... should see the identity string in the BIOS screen. ... as they exist on the disk). ...
    (microsoft.public.windowsxp.hardware)
  • Re: Grub hangs - two hard drives and a CD
    ... > What you wrote is all based on a wrong assumption that grub numbers drives ... > that the BIOS will call to boot an OS. ... The Bios calls to read disk require the register DL to ...
    (comp.os.linux.setup)
  • Re: maximum hard drive size in Latitude cpi
    ... > actually written a boot loader they won't be so adamant about how "Windows ... > of the disk, and while it is being read off of the disk the machine is ... > limitatoins of that BIOS. ... After that the kernel takes over. ...
    (comp.sys.laptops)