Problems reinstalling grub/lilo (they always hang at boot time ...)
Olaf
Everything worked fine until yesterday, but since I last shut down my linux
system I cannot boot any OS :(
Grub hangs after displaying the following messages:
Grub loading Stage1.5
Grub loading, please wait...
I've booted my system via the SystemRescueCD and
I've followed the instructions on the Grub wiki
http://grub.enbug.org/GrubLegacy in the troubleshooting section, but
unfortunately without any success. Using the described method via chroot
actually does not work since grub-install then cannot find "sort" and other
tools. But if I only mount the /boot partition I can then reinstall grub,
but the loader then still hangs ...
One possible problem I've noticed is, that I get a warning when I mount
the /boot partition. It is a ext3 partition, but is only mounted as ext2
(ext2_fill_super warning). Is there anything I need to (can) do about this?
Next I tried to install lilo:
I booted via SysRescCD and mounted /dev/hdb1 as /boot
and /dev/mapper/vg00-root as /mnt/sysimage. I then ran
lilo -C /mnt/sysimage/etc/lilo.conf -b /dev/hdb
Unfortunately this also results in lilo hanging as follows:
LIL
I would appreciate any help in order to get my linux system booted again :)
My setup is as follows:
/dev/hda - used for Windows XP (Windows actually also fails to boot)
/dev/hdb Ubuntu, with /root and /home dirs via LVM,
/boot on /dev/hdb1 (ext3)
I used to chainload grub via the XP bootloader.
Thanks,
Olaf
Douglas Mayne
> I suddenly cannot boot my ubuntu (5.04) linux system anymore (nor windows).
> Everything worked fine until yesterday, but since I last shut down my linux
> system I cannot boot any OS :(
Were you making changes to your system? Did you accidentally delete files
from /boot/grub?
>
> Grub hangs after displaying the following messages:
>
> Grub loading Stage1.5
> Grub loading, please wait...
>
> I've booted my system via the SystemRescueCD and
> I've followed the instructions on the Grub wiki
> http://grub.enbug.org/GrubLegacy in the troubleshooting section, but
> unfortunately without any success. Using the described method via chroot
> actually does not work since grub-install then cannot find "sort" and other
> tools. But if I only mount the /boot partition I can then reinstall grub,
> but the loader then still hangs ...
>
> One possible problem I've noticed is, that I get a warning when I mount
> the /boot partition. It is a ext3 partition, but is only mounted as ext2
> (ext2_fill_super warning). Is there anything I need to (can) do about this?
I don't use ext3, but I know an initial ramdisk may be required to load
the ext3 kernel module. Without the module, then it may be fall back to
use ext2 (since ext2 is backward compatible with ext3). You can use an
ext3 partition for strictly boot purposes, but when you start mounting
devices you need to have all of the necessary kernel modules loaded.
Also, your /etc/fstab file should specify the ext3 filesystem for the
partition in question.
>
> Next I tried to install lilo:
>
> I booted via SysRescCD and mounted /dev/hdb1 as /boot and
> /dev/mapper/vg00-root as /mnt/sysimage. I then ran
>
> lilo -C /mnt/sysimage/etc/lilo.conf -b /dev/hdb
>
> Unfortunately this also results in lilo hanging as follows:
>
> LIL
>
> I would appreciate any help in order to get my linux system booted again
> :)
>
> My setup is as follows:
> /dev/hda - used for Windows XP (Windows actually also fails to boot)
> /dev/hdb Ubuntu, with /root and /home dirs via LVM,
> /boot on /dev/hdb1 (ext3)
>
> I used to chainload grub via the XP bootloader.
Do you mean that you use grub to chainload XP, similar to this:
title Windows
rootnoverify (hd0,0)
makeactive
chainloader +1
>
> Thanks,
> Olaf
>
Decide which loader you want to use, then concentrate on fixing that
loader. I looked at the wiki you referenced, which says grub can hang at
this point if the grub files are damaged. Presumably, you would fix the
files at /boot/grub. Did you attempt to do that?
I don't use ubuntu. Perhaps, reinstalling the grub package will restore
your grub directory. I'll wait for your reply before posting more. I
don't use lilo.
--
Douglas Mayne
Olaf
I'm pretty sure I did not change anything in the /boot/grub directory. I
actually had backups of the bootsectors (first 512 byte of the harddisks)
and they were unaltered (or do these only contain the partition table?).
I did reinstall the files in the /boot/grub directory via grub-install but
the loader still hangs.
I used to load grub from the XP bootloader (and not the other way around as
you suggested), but for now I'm happy if I can directly boot from the disk
where the grub boot loader is located (/dev/hdb).
Thanks for your comments,
Olaf
Douglas Mayne
> Douglas,
>
> I'm pretty sure I did not change anything in the /boot/grub directory. I
> actually had backups of the bootsectors (first 512 byte of the harddisks)
Do you mean the bootsector of a partition or the MBR of the disc? The
first 512 bytes of the entire disk is the MBR (master boot record).
> and they were unaltered (or do these only contain the partition table?).
The _MBR_ of a disk contains id signatures, boot code, and space to define
four primary partitions.
The _bootsector of a partition_ contains id signatures, boot code, and
filesystem parameters.
Which of these did you compare and verify they had been unaltered?
>
> I did reinstall the files in the /boot/grub directory via grub-install
> but the loader still hangs.
Do the "stage" files exist at the /boot/grub directory? Does grub-install
report any errors? I looked closer at your first post, and you say that
/dev/hdb1 is a boot partition; therefore, look for the grub directory
relative to /dev/hdb1 (/grub, not /boot/grub). BTW, what environment is
available when you boot with the rescue CD? Are you working directly with
your setup, or is it using a "live CD" where you have to manually mount
your partitions, etc.
>
> I used to load grub from the XP bootloader (and not the other way around
> as you suggested),
OK, the fact you can't boot XP any more is a good clue to what is broken
on your system. Because XP's loader is set to control the bootup, is the
Windows menu displayed which offers choices to start XP or Ubuntu?
> but for now I'm happy if I can directly boot from the disk where the
> grub boot loader is located (/dev/hdb).
>
<snip>
>
Note: comments inline.
Also, please don't top post replies.
--
Ripley: And you let him in.
http://us.imdb.com/title/tt0078748/quotes
Olaf
> On Tue, 25 Apr 2006 08:55:41 +0200, Olaf wrote:
>
>> Douglas,
>>
>> I'm pretty sure I did not change anything in the /boot/grub directory. I
>> actually had backups of the bootsectors (first 512 byte of the harddisks)
>
> Do you mean the bootsector of a partition or the MBR of the disc? The
> first 512 bytes of the entire disk is the MBR (master boot record).
Yes this is what I am referring to.
>> and they were unaltered (or do these only contain the partition table?).
>
> The _MBR_ of a disk contains id signatures, boot code, and space to define
> four primary partitions.
>
> The _bootsector of a partition_ contains id signatures, boot code, and
> filesystem parameters.
>
> Which of these did you compare and verify they had been unaltered?
I only compared the MBRs of the disks with the backups that I had.
>> I did reinstall the files in the /boot/grub directory via grub-install
>> but the loader still hangs.
>
> Do the "stage" files exist at the /boot/grub directory? Does grub-install
> report any errors? I looked closer at your first post, and you say that
> /dev/hdb1 is a boot partition; therefore, look for the grub directory
> relative to /dev/hdb1 (/grub, not /boot/grub). BTW, what environment is
> available when you boot with the rescue CD? Are you working directly with
> your setup, or is it using a "live CD" where you have to manually mount
> your partitions, etc.
Yes the stage file exist in the /boot/grub (or /grub from /dev/hdb1 point of
view). Is there anyway I can verify that they are ok (e.g. calculating a
checksum or something similar).
I am using a live CD (SysRescCD) and I need to mount my partitions.
>>
>> I used to load grub from the XP bootloader (and not the other way around
>> as you suggested),
>
> OK, the fact you can't boot XP any more is a good clue to what is broken
> on your system. Because XP's loader is set to control the bootup, is the
> Windows menu displayed which offers choices to start XP or Ubuntu?
Yes I get the choice menu and I can select either OS, but as soon as I press
enter the computer hangs ...
>> but for now I'm happy if I can directly boot from the disk where the
>> grub boot loader is located (/dev/hdb).
>>
> <snip>
>>
> Note: comments inline.
>
> Also, please don't top post replies.
Some readers don't support inlining :( e.g. google groups UI ...
Douglas Mayne
The fact that the boot menu is displayed indicates that the Window's
boot drive bootsector is ok. However, the fact that neither Windows or
Linux will load (using the Windows loader) indicates something is
probably wrong with the windows partition's ability to read more files
beyond the bootsector and ntldr (these are not broken because the menu is
displayed.) Have you made any changes to your BIOS settings, or crashed
Windows recently? Because you have two discs, I think chances are good
that whatever has damaged your system, it is isolated to one disc or the
other. All clues point to your Windows partition being damaged. I am
assuming you haven't damaged your system by making a mistake in the
recovery process or by attempting to change something else just before the
failure.
You should also rule out hardware failure. There are some tests
which you can perform on your hard discs. Do you have the hard disc
manufacturer's diagnostic CD for your hard discs? Most diagnostic CDs have
read only tests which do simple checks to verify your hardware is working.
If you don't have that disc, you can use the GNU/Linux command dd.
I could post a grub bootable CD image if you think that would help.
--
Douglas Mayne
CBFalconer
> Douglas Mayne wrote:
>
>>
>> Also, please don't top post replies.
>
> Some readers don't support inlining :( e.g. google groups UI ...
Nonsense. Just edit your reply appropriately.
--
"If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers." - Keith Thompson
More details at: <http://cfaj.freeshell.org/google/>
Also see <http://www.safalra.com/special/googlegroupsreply/>
Grant
>The fact that the boot menu is displayed indicates that the Window's
>boot drive bootsector is ok. However, the fact that neither Windows or
>Linux will load (using the Windows loader) indicates something is
>probably wrong with the windows partition's ability to read more files
>beyond the bootsector and ntldr (these are not broken because the menu is
>displayed.)
I wonder if OP inserted a partition, moving the windoze one? (PQmagic
will do that) ntldr enumerates partitions on boot, for example this
box I type on uses C: for boot / temp / paging, and winxp is on first
primary (D:) partition on second drive.
boot.ini has: "default=multi(0)disk(0)rdisk(1)partition(1)\WINDOWS"
The partition number may need changing? I'd like to see if output
of fdisk -l matches bootloader's. Also check BIOS boot drive selection.
Grant.
--
Memory fault -- brain fried
iforone
Douglas Mayne wrote:
> I could post a grub bootable CD image if you think that would help.
>
This would most certainly help me in the future :-)
[ Concerning the OP's GRUB problem ]
*Considerations*;
I *have not* used XP in a dual-boot situation.
I *have not* run into this issue (yet, thankfully) using 2 physical
HDDs.
I *have* run into very similar issues with GRUB dual-booting win98 and
Debian.
I *have* always installed GRUB into the MBR.
Perhaps;
Just to get XP to boot again, and since the OP is booting through XP's
Boot.ini, Ntdetect.com and Ntldr (and whatever else gets placed on C:\
in this situation, such as in a LiLo config) - and chainloading through
Boot.ini (instead of GRUB);
I might suggest the OP boot into XP CDROM and run the commands;
CHKDSK C: /r
FIXMBR
FIXBOOT
BOOTCFG /rebuild
Then, perhaps reinstalling GRUB.
I only suggest above, because I'm unsure of how to directly clear up
the GRUB issues.
NOTE: ** Some of this info _below_ may be inaccurate or non-precise **
It appears either 1 or both HDDs xMBR is damaged...(allow me to try and
explain - and note; some of this *not* exact! ...nor precise).
Windows (atleast Fat32 on win98) uses an *xMBR* (e'X'tended MBR) which
is larger than the typical "standard" Boot sector size of 512Bytes.
This xMBR (Douglas refers to this xMBR as the
*partition_boot_sector(s)*) can/does span across atleast 6 more 512Byte
sectors (in a Ext'd win95 LBA partitioning scheme, this area on the HDD
is usually Logical sectors 63-69). IIRC - one of these sectors contains
the BPB(BIOS Parameter Block), which is hit along the way, during a
boot.
The MBR/MPT area of a physical HDD (512Bytes), as Douglas has
explained, is only large enough to contain the 4 Primary partition (or
3 Pri + 1 Ext'd) entries, some code, and other id info only.
One a single solitary HDD dual-boot installation using Debian Sarge - I
noticed GRUB, (_when_installed_to_the_MBR_), lives in the area(sectors)
*between* the MBR and the xMBR (especially the Stage 1.5 and Stage 2
aspects). I've confirmed this using the 'dd' utility. I can venture
into much further detail, but at the moment I will refrain.
Installing LiLo, IMHO, would likely only make things worse and more
confusing (though I'm unsure if it is actually _damaging_), in this
situation - yet unfortunately the OP has past the time for that
decision.
Windows also will place the MBR (and/or it's mirror copy) wherever it
likes on the HDD, including at the "end of the disk".
/NOTE: ** Some of this info _above_ may be inaccurate or non-precise **
Grant and Douglas have much more experience in this area than do I, so
please await their further replies, before acting upon the information
I have posted. Plus, I'm fairly new to GNU/Linux as well :-)
Regards
Olaf
> On Fri, 28 Apr 2006 00:10:55 +0200, Olaf wrote:
>
>> Douglas Mayne wrote:
>>
>> snip
>>
> The fact that the boot menu is displayed indicates that the Window's
> boot drive bootsector is ok. However, the fact that neither Windows or
> Linux will load (using the Windows loader) indicates something is
> probably wrong with the windows partition's ability to read more files
> beyond the bootsector and ntldr (these are not broken because the menu is
> displayed.) Have you made any changes to your BIOS settings, or crashed
> Windows recently? Because you have two discs, I think chances are good
> that whatever has damaged your system, it is isolated to one disc or the
> other. All clues point to your Windows partition being damaged. I am
> assuming you haven't damaged your system by making a mistake in the
> recovery process or by attempting to change something else just before the
> failure.
>
> You should also rule out hardware failure. There are some tests
> which you can perform on your hard discs. Do you have the hard disc
> manufacturer's diagnostic CD for your hard discs? Most diagnostic CDs have
> read only tests which do simple checks to verify your hardware is working.
> If you don't have that disc, you can use the GNU/Linux command dd.
>
>
> I could post a grub bootable CD image if you think that would help.
>
Douglas, yes if you can point me to a grub bootable CD image that would
provide some help. The first thing I'll do is reinstall XP since I have no
clue how to recover that, on the other hand I'm pretty sure I can recover
the Linux installation :)
Thanks for your help.
Olaf
Douglas Mayne
>
> Douglas Mayne wrote:
>
>> I could post a grub bootable CD image if you think that would help.
>>
>
>
> This would most certainly help me in the future :-)
>
<snip>
>
Thanks for giving me the opportunity to post this. I think a tool like
this would be useful. Obviously, there are rescue discs which can do some
of the same things. I have one of my own, for example (Doesn't everyone?):
http://www.xmission.com/~ddmayne2/10.2-live/index.html
But that is a bigger download, and if you are only in need of
fixing the loader, then perhaps this smaller tool will suffice. Here is
Grub version 0.97 written as an iso image. It is a small image for sure
(less that 1M expanded.) I tested it quickly with VMWare, and it appears
to work. Notice that there is no default menu, it will drop you directly
at the grub boot command line. From there you must enter commands
appropriate for your system. For example:
Example 1:
grub> rootnoverify (hd0,0)
grub> makeactive
grub> chainloader +1
grub> boot
Example 2:
grub> root (hd1,0)
grub> kernel /boot/vmlinuz ro root=/dev/hdb1
grub> boot
Example 3:
grub> rootnoverify (hd1)
grub> chainloader +1
grub> boot
Review the grub documentation here for more usage details:
http://www.gnu.org/software/grub/manual/html_node/index.html
-- NO WARRANTY (A DISCLAIMER) --
Use of this software is subject to the provisions of the GPL license:
http://www.xmission.com/~ddmayne2/grub/COPYING
The statement below emphasizes the "No Warranty" provisions of the GPL (see
Sections 11 and 12 of the above document.) This statement applies to this
software project, a bootable iso image which encapsulates the grub
loader, v0.97:
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED
TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Source Code: The source code for grub is widely available on the internet.
Here is one location:
ftp://alpha.gnu.org/gnu/grub/grub-0.97.tar.gz
I used the version compiled from the Slackware (r) Linux Project, version
10.2:
http://mirrors.xmission.com/slackware/slackware-10.2/extra/source/grub/grub-0.97.tar.gz
http://mirrors.xmission.com/slackware/slackware-10.2/extra/grub/grub-0.97-i486-1.tgz
Specific Instructions:
1. Obtain software (compressed image and checksum) here:
http://www.xmission.com/~ddmayne2/grub/v0.97/grub.iso.gz
http://www.xmission.com/~ddmayne2/grub/v0.97/md5sums
These are the correct values:
45a81605715e1a557317bfcfa3e99191 grub.iso
acb3abf4a252b605c8b54c46da6b428c grub.iso.gz
2. Expand image and verify MD5SUM checksum:
# cat grub.iso.gz | gzip -cd >grub.iso
# md5sum -c md5sums
3. Burn and verify the iso image file, grub.iso using the cd writing tool
of your choice. Remember: this is the cd _image_.
4. Test booting system with new cd. See examples above.
Here are some more points to consider when using grub, as I have
written earlier when testing grub:
http://groups.google.com/group/comp.os.linux.setup/msg/86f68934908589ba
Specifically, use extreme caution installing grub on the partition of
advanced filesystems, such as ReiserFS, XFS, JFS.
The grub project continues to do very good work, and I look forward to
grub, version 2.
(r) Slackware is a registered trademark of Patrick Volkerding and the
Slackware Linux Project.
--
Douglas Mayne
Douglas Mayne
See my last post here:
http://groups.google.com/group/comp.os.linux.setup/msg/602040b59e1eac50
These instructions are buried in there:
Specific Instructions:
1. Obtain software (compressed image and checksum) here:
http://www.xmission.com/~ddmayne2/grub/v0.97/grub.iso.gz
http://www.xmission.com/~ddmayne2/grub/v0.97/md5sums
--
Douglas Mayne
Olaf
This did the trick. CHKDSK actually found a problem with my XP boot drive.
After fixing it I can now boot in to both OSes again :)
Olaf
Douglas,
your suspicion was true, the XP bootdisk was defect! After I fixed it by
running CHKDSK from the XP boot disk I can now boot into both OSes again!
I've seen your post on the GRUB boot disk, and I'll also get that, since I'm
sure it will be useful in the future.
Thanks again for your support. Without your help I may have winded up
installing one or both OSes. That would have really been a waste of time.
I'm now trying to figure out, why my boot drive was corrupt, but this is not
a linux issue :) Strangely my mouse does not always work when booting into
XP ...
Olaf
Douglas Mayne
> Douglas Mayne wrote:
>
>> On Fri, 28 Apr 2006 00:10:55 +0200, Olaf wrote:
>>
>>> Douglas Mayne wrote:
>
<snip>
>
> Douglas,
>
> your suspicion was true, the XP bootdisk was defect! After I fixed it by
> running CHKDSK from the XP boot disk I can now boot into both OSes again!
>
> I've seen your post on the GRUB boot disk, and I'll also get that, since I'm
> sure it will be useful in the future.
>
> Thanks again for your support. Without your help I may have winded up
> installing one or both OSes. That would have really been a waste of time.
>
> I'm now trying to figure out, why my boot drive was corrupt, but this is not
> a linux issue :) Strangely my mouse does not always work when booting into
> XP ...
>
> Olaf
>
I'm glad you were able to track it down.
[OT] My daughter's boyfriend wasn't as lucky when his laptop suddenly
refused to boot last Sunday. I hope I am making progress telling
people that XP is not the only game in town. He might have been able to
use an XP setup CD in rescue mode like you did, except for the fact his
system was sold without one. The setup files were on the harddisk itself
only. He also had a restore CD, which could be used as the method of
last resort, to reset the system with the initial ghost image. He was
able to use Slax to get his files for school before sending it back for
repair under warranty. It's not unusual for GNU/Linux to come in and save
the day when pursuing viruses/rootkits/etc. Final word: make backups.
ntfsclone is a very good tool.
--
Douglas Mayne
iforone
Douglas Mayne wrote:
> On Fri, 28 Apr 2006 09:10:49 -0700, iforone wrote:
>
> >
> > Douglas Mayne wrote:
> >
> >> I could post a grub bootable CD image if you think that would help.
> >>
> >
> >
> > This would most certainly help me in the future :-)
> >
> <snip>
> >
> Thanks for giving me the opportunity to post this. I think a tool like
> this would be useful. Obviously, there are rescue discs which can do some
> of the same things. I have one of my own, for example (Doesn't everyone?):
> http://www.xmission.com/~ddmayne2/10.2-live/index.html
[ Very much more, wonderfully useful info, snipped for brevity ]
A very wholehearted Thank You to you Douglas;
Not only for specifically helping me with my issues months ago (the
link above recounts such an encounter :-)) - but also for your
continuing devotion and effort you put into your project, which helps
all in the FOSS community! As well as all the detailed helpful posts I
see you make across the varying *nix groups.
I have been s-l-o-w-l-y reviewing all the documentation you have posted
and am starting my way again through the GRUB manual. Time is short for
me though, and I will eventually post back with more updates on my
progress (as time allows).
I too, also hope that GRUB 2.0 will be a whole lot better than I have
experienced so far...I have yet to read all the changes that are to be
made, and decide whether or not I may like them (or not) ...Thanks again
iforone
Olaf wrote:
> iforone wrote:
> > I might suggest the OP boot into XP CDROM and run the commands;
> > CHKDSK C: /r
> > FIXMBR
> > FIXBOOT
> > BOOTCFG /rebuild
> >
> > Then, perhaps reinstalling GRUB.
> >
> > I only suggest above, because I'm unsure of how to directly clear up
> > the GRUB issues.
> >
>
> This did the trick. CHKDSK actually found a problem with my XP boot drive.
> After fixing it I can now boot in to both OSes again :)
>
> Thanks for your help.
>
> Olaf
You are most welcome - glad I could help :-)