07 July, 2006


New mondo package: Fixes for some (longstanding) bugs & Ubuntu

mondo-2.08-2-2 fixes three bugs, namely #369321, #222052 and #292782.

I am particularly happy with the two latter ones even though they were only minor and wishlist, respectively. But they were fairly longstanding, and it makes me feel good that I finally got around to fixing them.

I've also gone through all the remaining bugs again, nagged the submitters where appropriate and closed some (with submitter agreement), especially the ones about LVM and RAID because I feel they have been fully addressed now. The result is that mindi has currently no open bugs and mondo is down to nine. Certainly not as cool as what Steinar H. Gunderson is doing to the RC bug count, but still not bad. ;-) Hopefully, I'll be able to get the bug count down even further.

I've also worked on Ubuntu support with the result that things should function out of the box on Dapper now, i.e. the package should build and run fine.

mondo-2.08-2-2 was tested on:
Enjoy. ;-)

I am in a position where I will not build packages from source on severall VERY small servers using software RAID arrays.

For some reason, Mindi support is limited to 1.06-r266 in Ubuntu Dapper (6.06 LTS) and Edgy (6.10) and Mondo 2.08-2 will not install from packages in these conditions. This will likely be fixed at a later date but, for now, Ubuntu support for Mondo is suffering from jet lag on machines with RAID arrays :-).

There is a recent article (http://www.debian-administration.org/articles/393) (May 2, 2006) outlining a simple change to /etc/mindi/deplist (add mdadm and cfdisk) so that images produced by mondoarchive can be restored in "expert" mode.

In Ubuntu, Mondo (mondo_2.06-1_i386.deb) saves module dm-mod.ko instead of md-mod.ko. Adding the entry /lib/modules/2.6.15-23-server/kernel/drivers/md/md-mod.ko in /etc/mindi/deplist will force copy the module.

To restore/compare files in a configuration using a RAID array, boot in "expert" mode and manually install the modules (eg

insmod md-mod
insmod raid1
insmod raid5

and the like) before starting the RAID array(s) and mondorestore:

mdadm -As

This solution is release specific (tied to the kernel name). Is there a simple edit that can be done to mondoarchive so that md-mod is selected instead of dm-mod?

Thank you for your support.
Silly me!

/usr/sbin/mindi is a script and I only had to add md-mod to EXTRA_MODS. Now the Ubuntu server kernel loads md support just fine and Mondo Rescue can be used as packaged with 6.06 LTS. The joys of mixing a recipe for one distro onto another distro!

There are two cases of interest:

1) recovery from a complete crash: this was simulated by running DBAN on the local hard disks and nuking everything.

2) partial recovery, with or without the original md arrays: this is represented by a change in UUID of the RAID partitions.

The sample configuration for this test has 3 disks with 3 raid arrays. MD0 is RAID1 (2 disks and 1 spare, devices /dev/hda1, /dev/hdc1 /dev/hdd1) and is mounted on /boot. MD1 is RAID5 (3 disks, devices /dev/hda2, /dev/hdc2 /dev/hdd2) and is mounted on /. MD2 is RAID1 (2 disks and 1 spare, devices /dev/hda3, /dev/hdc3 /dev/hdd3) and is the swap file.

In the case of the complete recovery, the 9 partitions are first created with cfdisk and are all type 0xfd, Linux RAID Autodetect and of appropriate size (Yes Yoda, size does not matter). The arrays themselves are created using

mdadm --create /dev/md0 --level=1 --raid-devices=2 --spare-devices=1 /dev/hda1 /dev/hdc1 /dev/hdd1
mdadm --create /dev/md1 --level=5 --raid-devices=3 /dev/hda2 /dev/hdc2 /dev/hdd2
mdadm --create /dev/md2 --level=1 --raid-devices=2 --spare-devices=1 /dev/hda3 /dev/hdc3 /dev/hdd3

Caution should be taken to let the arrays sync before continuing.

In the case of partial recovery from a different set of arrays, the arrays need to be started with:

mdadm --assemble /dev/md0 /dev/hda1 /dev/hdc1 /dev/hdd1
mdadm --assemble /dev/md1 /dev/hda2 /dev/hdc2 /dev/hdd2
mdadm --assemble /dev/md2 /dev/hda3 /dev/hdc3 /dev/hdd3

In either case, you need to rebuild the mdadm.conf configuration file with:

echo "DEVICE partitions" > /etc/mdadm/mdadm.conf
mdadm --detail --scan >> /etc/mdadm/mdadm.conf

You can now proceed with mondorestore (restore everything, compare, whatever your fancy).

Give your mdadm configuration file some consideration before rebooting. You can copy your running configuration to the newly recovered system with:

mount /dev/md1 /mnt
cp /etc/mdadm/mdadm.conf /mnt/etc/mdadm/mdadm.conf
umount /mnt

and give your system the three finger salute!

If you want to boot any drive in the /boot array, reboot your newly recovered system and add GRUB support for the /boot partition on /dev/hdc1 with

device (hd0) /hdc
root (hd0,0)
setup (hd0)

You can do the same to the spare drive with:

mdadm --manage /dev/md0 --fail /dev/hdc1

Wait for the drives to sync (cat /proc/mdstat) and add GRUB support for the /boot partition on /dev/hdd1 with

device (hd0) /hdd
root (hd0,0)
setup (hd0)

Add back /dev/hdc1 as spare since it is not really faulty :-)

mdadm --manage /dev/md0 --remove /dev/hdc1
mdadm --manage /dev/md0 --add /dev/hdc1

Keep in mind that updating /boot does not always upgrade the spare disk, so you may need to resort to this trickery whenever the boot configuration changes.

NEVERTHELESS, THE CIVIL LAW is and must be neutral about who has a more noble or rewarding faith. The breakaway parishes ought to win every Office 2010facet of the lawsuit not becauseMicrosoft Office 2010 their beliefs or their politics are better, Microsoft wordbut because both lawOffice 2007and equity, along with common sense, are on Microsoft Officetheir side.Microsoft Office 2007 Not only does Virginia state law (the Division Statute)Office 2007 keyexplicitly apply to just such a Office 2007 downloadsituation as now exists, but the history Office 2007 Professionalespecially of The Falls Church argues against the claims of Outlook 2010the Virginia Diocese with which theyMicrosoft outlookhave disassociated.Microsoft outlook 2010First, The Falls Church wasWindows 7 founded, formed, and developed long before the diocese, or the national Episcopal Church, even existed.
Post a Comment

<< Home

This page is powered by Blogger. Isn't yours?