From: Arthur Nascimento <tureba@gmail.com>
To: vrodriguez@municipiodeloja.gov.ec, linux-newbie@vger.kernel.org
Subject: Re: lilo boot problems with SATA and mandrake 10.1
Date: Fri, 17 Dec 2004 14:31:12 -0200 [thread overview]
Message-ID: <bb529e4041217083118a229d3@mail.gmail.com> (raw)
In-Reply-To: <1103190044.7183.12.camel@itanium>
I had that problem too a long time ago - it would show only a L but no
error code. (I didn't try with GRUB.) I have no idea whatsoever of
what machine it was, but I do know it had winxp on a dual boot too. I
was a mere mortal back then (win user) and believed that on a crash
the best thing was to reinstall everything all over again (as all win
users believe), so I don't know how to fix it since I used to just
blindly overwrite it. I tryed other distributions at the time (as well
as different versions of the same one) and this failure occured only
on some of them (don't remember which of them).
You could try updating your boot loader and bios to newer versions,
but i doubt it will make a difference.
I would imagine that this error happens when we install win on a
partition and it's loader on MBR and after try to put LILO/GRUB over
win's loader on MBR. Win must have some sort of self-healing mechanism
to repair the MBR when it is damaged (or in this case, fully altered).
That would explain why no error code is being shown - our boot loader
has been partially overwritten by win's loader, and I doubt a damaged
LILO/GRUB can do anything at all (such as shout an error).
You should try to reinstall win on a partition and tell it to put it's
loader on the begining of the same partition instead of on the MBR.
After that you can reinstall LILO/GRUB on the MBR (or perhaps
reinstall your distro - your call) and you should be all set. I'm sure
I sound like a win user, telling you to reinstall everything, but if I
am right, this will be the last time you will have to do that.
Good luck!
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-12-17 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-16 9:40 lilo boot problems with SATA and mandrake 10.1 Vladimir E. Rodriguez
2004-12-16 22:08 ` Simon Valiquette
2004-12-18 18:56 ` Hal MacArgle
2004-12-19 14:27 ` SOTL
2004-12-17 6:35 ` Richard Adams
2004-12-17 16:31 ` Arthur Nascimento [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bb529e4041217083118a229d3@mail.gmail.com \
--to=tureba@gmail.com \
--cc=linux-newbie@vger.kernel.org \
--cc=vrodriguez@municipiodeloja.gov.ec \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox