Opened 3 years ago

Closed 16 months ago

#757 closed defect (fixed)

Mondorescue 3.2.0 can't handle Linux software RAID

Reported by: AndyWas Owned by: bruno
Priority: normal Milestone: 3.2.2
Component: mondo Version: 3.0.2
Severity: major Keywords: Mondorescue RAID
Cc:

Description

I am testing out Bruno's new 3.2.0 Fedora 20 packages from the test repo.

My kernel is 3.16.3-200.fc20.x86_64. Fedora 20 is installed on 2 x 64GB SSD. /boot is on Linux md RAID 1, everything else is in LVM on another Linux md RAID 1 and Grub 2 is installed on both devices.

DVD verification at the end of Mondoarchive passes OK but on booting in “compare” mode Mondo is unable to mount the LVM-on-RAID volumes. If I do the same on another otherwise similar Fedora 20 install but on a single disk (i.e. root VG still in LVM but no RAID) the mount list still shows zero size for the LVM volumes but can mount them OK and "compare" is happy.

When I booted in "nuke" mode Mondo was also unable to mount the LVM-on-RAID volumes, and when I ran it a second time it tried (but failed) to reformat partitions, and on rebooting dropped into grub-rescue mode. This obliterated the RAID 1 volume for /boot - when I boot from a Fedora installation DVD it looks like everything in the LVM-on-RAID is still there (as well as presumably Grub 2) but I just see 2 blank partitions where /boot used to be.

The "nuke" was on a different machine from "compare", but the RAID setup and filesystem organisation, architecture and kernel version is the same on both. In each case, all partitions are MBR type.

Log files attached. I deleted to non-matching file listing from the "compare" log for privacy and to reduce file size.

Thanks, Andrew

Attachments (4)

mondorestore.log.nuke (231.4 KB) - added by AndyWas 3 years ago.
mondofdisk.log.nuke (5.8 KB) - added by AndyWas 3 years ago.
mondorestore.log.compare (372.3 KB) - added by AndyWas 3 years ago.
mondoarchive.log (923.4 KB) - added by AndyWas 3 years ago.

Download all attachments as: .zip

Change History (8)

Changed 3 years ago by AndyWas

Changed 3 years ago by AndyWas

Changed 3 years ago by AndyWas

Changed 3 years ago by AndyWas

comment:1 Changed 3 years ago by bruno

  • Milestone changed from 3.2.0 to 3.2.1

comment:2 Changed 2 years ago by bruno

  • Milestone changed from 3.2.1 to 3.2.2

comment:3 Changed 16 months ago by bruno

  • Status changed from new to assigned

Should be fixed with rev [3566]

comment:4 Changed 16 months ago by bruno

  • Resolution set to fixed
  • Status changed from assigned to closed

And also with rev [3572]

Note: See TracTickets for help on using tickets.