Mailinglist Archive: opensuse (3336 mails)
| < Previous | Next > |
Re: [SLE] Problems with initrd after mkinitrd
- From: "Carlos E. R." <robin1.listas@xxxxxxxxxx>
- Date: Mon, 26 Dec 2005 20:48:31 +0100 (CET)
- Message-id: <Pine.LNX.4.61.0512262046150.3993@xxxxxxxxxxxxxxxx>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
The Monday 2005-12-26 at 12:16 -0500, Carl Hartung wrote:
> Maybe the boot failures are just a symptom of a problem being introduced at
> write time. If the process somehow pushes the drives and/or subsystems right
> up to their performance limit, could it be that some are drifting into the
> margin and writing flaky images?
I would think the image (some of them, at least) is written at a place of
the disk where the boot loader has difficulties in reading from. Remember
that at that point it has to use the bios services, the kernel is not
running yet.
- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFDsEkRtTMYHG2NR9URAqRDAJ9WIpGEV7m/i6zhRUJ9BB2JYYZRRwCgjpLj
0QUKgpY03pLBn3SlQDZvdSY=
=aJEl
-----END PGP SIGNATURE-----
Hash: SHA1
The Monday 2005-12-26 at 12:16 -0500, Carl Hartung wrote:
> Maybe the boot failures are just a symptom of a problem being introduced at
> write time. If the process somehow pushes the drives and/or subsystems right
> up to their performance limit, could it be that some are drifting into the
> margin and writing flaky images?
I would think the image (some of them, at least) is written at a place of
the disk where the boot loader has difficulties in reading from. Remember
that at that point it has to use the bios services, the kernel is not
running yet.
- --
Cheers,
Carlos Robinson
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFDsEkRtTMYHG2NR9URAqRDAJ9WIpGEV7m/i6zhRUJ9BB2JYYZRRwCgjpLj
0QUKgpY03pLBn3SlQDZvdSY=
=aJEl
-----END PGP SIGNATURE-----
| < Previous | Next > |