Inzu ajaveeb

This series of articles will show how to set up software RAID on a Windows Server 2003 system. Before you do anything with your disks, make sure you have a good backup. Please read our terms of use. We will start with one Basic drive, create a RAID1 set on a new drive we install, remove the first drive, and recover from the second. We wrote up an article over seven years ago here about Windows Server software RAID, and it is definately time to provide an update. First off, we have a single 12 gig drive running in Basic mode:

To run Software RAID, you need to convert this drive to a Dynamic Disk. Note that on Windows Server 2003 this is possible after installing the disk as Basic. To convert to a Dynamic Disk, simply right-click on the drive and select Convert to Dynamic Disk:

Check the disk you wish to convert:

Confirm which disks you want to convert to Dynamic:

You will be warned that converting this disk drive will limit the ability of other operating systmes to start for any volumes on the disk.

We are warned that filesystems on the disks to be converted need to be dismounted:

The system will need to reboot:

Confirm reboot:

At this point, add a drive. After the system reboot, go back in to computer management/disk management. There will be a Initialize and Convert Disk Wizard notification that the new drive will be set to a dynamic disk:

Select the disk to initialize:

At the Initialize and Convert Disk Wizard dialog, check the disk you want to convert, and click next:

Click finish to complete the Initialize and Convert Disk Wizard:

There is now one healthy dynamic disk, and one unallocated disk, both of the same size:

Right click on Disk 0, and select Add Mirror:

Select the disk and click Add Mirror:

An error may pop up that says “Logical Disk Manager could not update the boot file for any boot partitions on the target disk. Verify your arcpath listings in file boot.ini or through the bootcfg.exe utility.” Well, we are mirroring the first drive to the second, and the first drive doesn’t even have a filesystem, so it makes sense that we can’t update the boot file. We chose to ignore this error:

The RAID1 array is building:

The RAID1 array is done and healthy:

Let’s reboot and remove the original drive, putting the mirrored drive in its place. After the boot, this shows up in the system event logs:

We have a missing drive in computer management/disk. Remove the mirror:

Select the Disk to remove:

Confirm:

We now have a healthy Disk 0:

Remove the missing drive:

All is as it should be:

This is a summary of the mailman commands available via the console in ~mailman/bin/..

These commands are essential for building mailing lists and for backing up list information (users, user options, list configuration). The commands also greatly extend the functionality of Mailman.

For more information about a specific command, give the command with the ‘–help’ option.

---

add_members: add regular or digested users to a list.

arch: rebuild a mailing list’s archives.

change_pw: change a list’s password.

check_db: check a mailing list database for corruption.

check_perms: check the permissions on the Mailman installation.

cleanarch: clean up an .mbox archive file before importing with bin/arch.

clone_member: add a list member with identical settings as an existing list member (including password).

config_list: examine or change list configuration from the command line.

convert.py: a withlist script to convert a list’s interpolation strings from %-strings to $-strings.

discard: discard held messages.

dumpdb: dump the contents of a Mailman .db file.

find_member: find all lists that a specified user is on.

fix_url.py: a withlist script to reset a list’s web_page_url and host_name attributes.

genaliases: regenerate Mailman specific aliases from scratch.

inject: inject a message from a file into a Mailman queue.

list_admins: list all the owners of a mailing list.

list_lists: list all the Mailman mailing lists.

list_members: list members of a mailing list.

list_owners: list the owners of a mailing list, or all mailing lists.

mailmanctl: primary start-up and shutdown script for Mailman’s qrunner daemon.

mmsitepass: set the site password, good for admin-ing any list.

newlist: create a new mailing list.

qrunner: run one or more qrunners, once or repeatedly – usually only used by mailmanctl.

rb-archfix: reduce disk space usage for Pipermail archives.

remove_members: remove specified members from a list.

reset_pw.py: a withlist script to reset the passwords for members of a mailing list.

rmlist: remove an old mailing list – does not remove the archives unless you specify -a.

show_qfiles: show the contents of one or more Mailman queue files.

sync_members: synchronizes mailing list membership with a flat text file.

transcheck: check a given Mailman translation (i18n).

unshunt: move messages from the shunt queue to the original queue.

update: upgrade from previous version of Mailman to current version.

version: print out the version of Mailman you are using.

withlist: advanced interactions with mailing list objects.

---

Other notable files:

msgfmt.py: generate binary message catalog from textual translation description – a simple reimplementation of GNU msgfmt used during Mailman’s installation.

paths.py: module used by many Mailman scripts to tell it where its files are stored.

pygettext.py: module used to generate the master message strings catalog for internationalization.

mailman/Mailman/Defaults.py: The default values for configuring Mailing lists. Also controls how Mailman interacts with your MTA (sendmail, postfix, qmail…), and how it interacts with your web server. Note: NEVER change this file – copy any section you want to change into the file below and make the changes there.

mailman/Mailman/mm_cfg.py: Your sites customized settings. Used to set the defaults for any new mailing lists. It is highly recommended that you read through Defaults.py before making any changes, but that you make any desired changes in this file.

Converted from the Mailman FAQ Wizard