Opened 17 years ago

Closed 16 years ago

#117 closed defect (fixed)

Mondo does not support boot loader not in MBR

Reported by: bcomber Owned by: Bruno Cornec
Priority: normal Milestone: 2.2.4
Component: mondo Version: 2.2.1
Severity: major Keywords:
Cc:

Description

When running the command "mondoarchive -Oc 16 -d /dev/hdd -F " Mondo doesn't automatically find the boot loader. The default is grub on opensuse, and when viewing the log it shows that it searches for both lilo and grub and can't find it.

Strangely enough if I simply add -l GRUB without a drive behind it, it works fine. Or at least appears to in that the backup continues. the log shows that it still doesn't find it, but that the bootloader is grub and it is located on /dev/hda which is correct.

Attachments (2)

MA.log (17.2 KB ) - added by bcomber 17 years ago.
strings (446 bytes ) - added by bcomber 17 years ago.

Download all attachments as: .zip

Change History (18)

by bcomber, 17 years ago

Attachment: MA.log added

comment:1 by Bruno Cornec, 17 years ago

Milestone: 2.2.12.2.2
Status: newassigned

comment:2 by Bruno Cornec, 17 years ago

Could you run the following command on your system and attach the result back please ?

dd if=/dev/hda bs=446 count=1 | strings

comment:3 by Bruno Cornec, 17 years ago

On my SuSE 10.2 Qemu machine it seems that grub is installed by default on the partition and not on the MBR.

Thus the problem it seems.

comment:4 by RickFriedman, 17 years ago

Just a note to let you know that I am running opensuse 10.2 with grub on the MBR and Mondo seems to have no problem recognizing and finding it. The backup runs with no problem.

The restore is another matter... :)

by bcomber, 17 years ago

Attachment: strings added

comment:5 by bcomber, 17 years ago

Your file strings is attached. Rick says that his works fine. Just to clarify, this is a dual boot system. What I'll do this weekend, is another install on a spare drive and see if I get the same result.

comment:6 by bcomber, 17 years ago

I tried the same thing on a drive with only opensuse 10.2 installed. No dual boot. I got the same result. It will not recognize the boot sector unless I specifically tell it that I'm using grub. Once I tell it -l GRUB it's fine and finds everything.

comment:7 by RickFriedman, 17 years ago

As I said, Mondo has no problem finding the bootloader on my system. My system is also a dual boot system. Grub is in the MBR. Maybe seeing my partition table will help:

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1         701     5630751    7  HPFS/NTFS
/dev/hda2             702        4865    33447330    f  W95 Ext'd (LBA)
/dev/hda5             702         767      530113+   7  HPFS/NTFS
/dev/hda6             768        1825     8498353+   7  HPFS/NTFS
/dev/hda7            1850        3515    13382113+  83  Linux
/dev/hda8            3516        4731     9767488+  83  Linux
/dev/hda9            4732        4865     1076323+  82  Linux swap / Solaris

comment:8 by Bruno Cornec, 17 years ago

Summary: Mondo does not recognize boot loader automatically Opensuse 10.2Mondo does not support boot loader not in MBR

comment:9 by bcomber, 17 years ago

That's fine on your system. My system is about the same with the exception of using 4 primarys with the 4th being the extended partition. Been that way for ages. Worked fine with 10.0 so I don't know what the difference is. And to clarify, my bootloader IS in the MBR, so the change to boot loader not in the MBR that it was changed to is wrong.

comment:10 by bcomber, 17 years ago

I found the problem. When I did the install, I didn't check where the bootloader was going to be installed. I just checked, and it was on the root partition, not the MBR. I started YAST, and this confirmed it. I selected MBR, and it no longer has the problem. So I guess the change is correct. I didn't notice that when I simply told it -l GRUB it would find it without problems and tell me it was located on /dev/hda. That is what was so confusing.

comment:11 by Bruno Cornec, 17 years ago

Milestone: 2.2.22.2.3

comment:12 by Bruno Cornec, 17 years ago

Milestone: 2.2.32.2.4

comment:13 by Bruno Cornec, 17 years ago

Should be fixed in rev [1451]. Will be in 2.2.4

comment:14 by (none), 17 years ago

Milestone: 2.2.4

Milestone 2.2.4 deleted

comment:15 by Bruno Cornec, 17 years ago

Milestone: 2.2.4

Could you check this is indeed fixed in 2.2.4 ? TIA.

comment:16 by Bruno Cornec, 16 years ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.