Not logged in - Login
< back

Linux Server Configuration

This page will be updated with configuration notes during the process of configuring the first new clone of viking.

Raid Configuration Notes

Raid array configuration is managed in a bios-like configuration system entered during the boot process. There is a notice to press (Ctrl+R) to enter the configuration utility. On Viking Ctrl+H accomplishes the same goal.

In order to create a new array a new configuration is made. By default the installed disks show up as JBOD. They must be made available, where the JBOD disks are listed there is a "Make good" action which frees a JBOD drive to be added to a new array.

After creating the configuration a new device will show up in the OS. There does not appear to be any control over what letter device is created (eg /dev/sda vs /dev/sdb). I accomplished partitioning and mounting the array as follows:

parted /dev/sda mklabel gpt
parted /dev/sda
....mkpart primary ext4 1 -1
....quit
mkfs.ext4 -L data /dev/sda
mount /dev/sda /mnt/data1

This process did not make a swap partition. something about the gpt label. Need to re-evaluate this to make sure it's appropriate.

Updated /etc/fstab as follows (per notes, need to check)

/dev/sda mnt/data1 ext4 noatime,defaults 1 1

TODO Try this https://www.centos.org/docs/5/html/Deployment_Guide-en-US/ch-disk-storage.html Use the process in this link. The raid array should be made at /dev/sda1

Hot Swapping Drives

Drives can be added/removed while the system is online. I have not tested this with raid array members. Inserting a SATA drive into one of the available bays causes the drive to appear as a new device. The new devices must be manually mounted. To avoid conflict with the boot drive or other drives this should be done while the system is online and any permanent mounts should use the UUID or device id as visible under /dev/disk/by-uuid/