2
edits
Changes
From SME Server
Jump to navigationJump to search
mLine 3:
Line 3: + + Line 10:
Line 12: + + + + + + + Line 148:
Line 157: − + + + Line 170:
Line 181: − + − # you don't need the pvresize or lvresize command+ − # the final line becomes ext2online -C0 /dev/md2 (or whatever / is mounted to)+ + Line 196:
Line 208: + + Line 211:
Line 225: − + − # you don't need the pvresize or lvresize command+ − # the final line becomes ext2online -C0 /dev/md2 (or whatever / is mounted to)+ + Line 228:
Line 243: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 233:
Line 328: + + + + + + + + + + + + + + + + + + Line 315:
Line 428: + + + − Your devices are likely to be different, and you may have more than two disks, including a hot standby, but will always be determined from the mdstat file. Once the raid resync has been started, the progress will be noted in mdstat. You can see this real time by:+ Line 349:
Line 465: + + + − + Line 376:
Line 495: − + Line 400:
Line 519: − +
typo: ecc to etc
===Hard Drives – Raid===
===Hard Drives – Raid===
From SME Server 8 a new feature was introduced - Automatic configuration of Software RAID 1, 5 or 6. RAID is a way of storing data on more than one hard drive at once, so that if one drive fails, the system will still function.
From SME Server 8 a new feature was introduced - Automatic configuration of Software RAID 1, 5 or 6. RAID is a way of storing data on more than one hard drive at once, so that if one drive fails, the system will still function.
{{Note box| As per the [http://lists.contribs.org/pipermail/updatesannounce/2014-June/000366.html '''release notes'''], SME Server 9 default install will only configure a Raid 1 configuration regardless of the number of Hard Drives, there are selectable install options for other Raid configurations available from the install menu}}
Your server will be automatically configured as follows:
Your server will be automatically configured as follows:
* 4-6 Drives - Software RAID 5 + 1 Hot-spare
* 4-6 Drives - Software RAID 5 + 1 Hot-spare
* 7+ Drives - Software RAID 6 + 1 Hot-spare
* 7+ Drives - Software RAID 6 + 1 Hot-spare
As per the above note, on SME Server 9.0, the RAID 1 configuration will add the 3rd drive as a member of the RAID and not as a spare.:
* 1 Drive - Software RAID 1 (degraded RAID1 mirror ready to accept a second drive).
* 2 Drives - Software RAID 1
* 3 Drives - Software RAID 1
If you use a true hardware raid controller to manage your hard drives and choose noraid during install, your system will still be configured with RAID1.
====Hard Drive Layout====
====Hard Drive Layout====
# Shut down and install one larger drive in system for one old HD. Unplug any USB-connected drives.
# Shut down and install one larger drive in system for one old HD. Unplug any USB-connected drives.
# Boot up and manage raid to add new (larger) drive to system.
# Boot up and login to the admin console and use option 5 to add the new (larger) drive to system.
# Wait for raid to fully sync.
# Wait for raid to fully sync.
# Repeat steps 1-3 until all drives in system are upgraded to larger capacity.
# Repeat steps 1-3 until all drives in system are upgraded to larger capacity.
# Ensure all drives have been replace with larger drives and array is in sync and redundant!
# Ensure all drives have been replace with larger drives and array is in sync and redundant!
# Issue the following commands:
# Issue the following commands:
{{Note box|SME9 uses /dev/md1 not /dev/md2.}}
mdadm --grow /dev/md2 --size=max
mdadm --grow /dev/md2 --size=max
* All of this can be done while the server is up and running with the exception of #1.
* All of this can be done while the server is up and running with the exception of #1.
* These instructions should work for any raid level you have as long as you have >= 2 drives
* These instructions should work for any raid level you have as long as you have >= 2 drives
* If you have disabled lvm
* If you have disabled lvm , you don't need the pvresize or lvresize command, therefore the final line becomes
ext2online -C0 /dev/md2 <nowiki>#</nowiki>(or whatever / is mounted to)
or If you receive an "command not found" error, try this:
resize2fs /dev/md2 &
====Replacing and Upgrading Hard Drive after HD fail====
====Replacing and Upgrading Hard Drive after HD fail====
# Reboot and ensure all drives have been replaced with larger drives and array is in sync and redundant!
# Reboot and ensure all drives have been replaced with larger drives and array is in sync and redundant!
# Issue the following commands:
# Issue the following commands:
{{Note box|SME9 uses /dev/md1 not /dev/md2.}}
mdadm --grow /dev/md2 --size=max
mdadm --grow /dev/md2 --size=max
Notes :
Notes :
* These instructions should work for any raid level you have as long as you have >= 2 drives
* These instructions should work for any raid level you have as long as you have >= 2 drives
* If you have disabled lvm
* If you have disabled lvm , you don't need the pvresize or lvresize command, therefore the final line becomes
ext2online -C0 /dev/md2 <nowiki>#</nowiki>(or whatever / is mounted to)
or If you receive an "command not found" error, try this:
resize2fs /dev/md2 &
====Raid Notes====
====Raid Notes====
Theses operations are logged, however, no emails will be sent to admin as of the release of packages associated with Bug #6160 or the release of the 8.1 ISO.
Theses operations are logged, however, no emails will be sent to admin as of the release of packages associated with Bug #6160 or the release of the 8.1 ISO.
==== Receive periodic check of Raid by email ====
There are routines in SME Server to check the raid and sent mail to the admin user, when the raid is degraded or when the raid is resynchronizing. But the admin user receive a lot of emails and some time messages can be forgotten.
So the purpose is to have a routine which sent email to the user of your choice each week.
nano /etc/cron.weekly/raid-status.sh
You have to change the variable '''DEST="stephane@your-domaine-name.org"''' to the email you decide to use.
#!/bin/sh
# cron.weekly/mdadm-status -- weekly status of the RAID
# 2013 Pierre-Alain Bandinelli
# distributed under the terms of the Artistic Licence 2.0
# Get status from the RAID array and send the details by email.
# Email will go to the address specified in the commandline.
set -eu
MDADM=/sbin/mdadm
[ -x $MDADM ] || exit 0 # package may be removed but not purged
'''DEST="stephane@your-domaine-name.org"'''
exec $MDADM --detail $(ls /dev/md*) | mail -s "RAID status SME Server" $DEST
save by ctrl+x
chmod +x /etc/cron.weekly/raid-status.sh
each sunday a 4h00 AM you will receive a mail which looks to this :
/dev/md1:
Version : 0.90
Creation Time : Sun Jan 6 20:50:41 2013
Raid Level : raid1
Array Size : 104320 (101.89 MiB 106.82 MB)
Used Dev Size : 104320 (101.89 MiB 106.82 MB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 1
Persistence : Superblock is persistent
Update Time : Sun Dec 22 04:22:42 2013
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : 28745adb:d9cff1f4:fcb31dd8:ff24cb0c
Events : 0.208
Number Major Minor RaidDevice State
0 8 1 0 active sync /dev/sda1
1 8 17 1 active sync /dev/sdb1
/dev/md2:
Version : 0.90
Creation Time : Sun Jan 6 20:50:42 2013
Raid Level : raid1
Array Size : 262036096 (249.90 GiB 268.32 GB)
Used Dev Size : 262036096 (249.90 GiB 268.32 GB)
Raid Devices : 2
Total Devices : 2
Preferred Minor : 2
Persistence : Superblock is persistent
Update Time : Sun Dec 22 05:30:36 2013
State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0
UUID : c343c79e:91c01009:fcde78b4:bad0b497
Events : 0.224
Number Major Minor RaidDevice State
0 8 2 0 active sync /dev/sda2
1 8 18 1 active sync /dev/sdb2
If you want to test the message sent without waiting the next sunday, you can do
/etc/cron.weekly/raid-status.sh
====nospare====
====nospare====
A system with 6 physically present harddrives thus will be formated Raid6 _not_ Raid5. Resulting capacity of course will be "n-2".
A system with 6 physically present harddrives thus will be formated Raid6 _not_ Raid5. Resulting capacity of course will be "n-2".
'''Note:''' with the release of version 7.6 and 8.0, the commandline parameter "sme nospare" has been changed to "sme spares=0" . In addition, you may also select the number of spare(s) implemented [0,1,or 2].
'''Note:''' with the release of version 7.6 and 8.0, the commandline parameter "sme nospare" has been changed to "sme spares=0" . In addition, you may also select the number of spare(s) implemented [0,1,or 2].
==== remove the degraded raid ====
when you install the smeserver with one drive with a degraded raid, you will see a 'U_' state but without warnings. If you want to leave just one 'U' in the /proc/mdstat and stop all future questions about your degraded raid state, then :
mdadm --grow /dev/md0 --force --raid-devices=1
mdadm --grow /dev/md1 --force --raid-devices=1
after that you will see this
# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sda1[0]
255936 blocks super 1.0 [1/1] [U]
md1 : active raid1 sda2[0]
268047168 blocks super 1.1 [1/1] [U]
bitmap: 2/2 pages [8KB], 65536KB chunk
unused devices: <none>
====Resynchronising a Failed RAID====
====Resynchronising a Failed RAID====
[root@sme]# mdadm --add /dev/md2 /dev/hda2
[root@sme]# mdadm --add /dev/md2 /dev/hda2
Once you type the command the following message will appear, appropriate for your device.
[root@sme] mdadm: hot added /dev/hda2
It important to know that your devices are likely to be different, E.G your device could be /dev/sda2 or you may have more than two disks, including a hot standby. These details can always be determined from the mdstat file. Once the raid resync has been started, the progress will be noted in mdstat. You can see this real time by:
[root@sme]# watch -n .1 cat /proc/mdstat
[root@sme]# watch -n .1 cat /proc/mdstat
Also check your driver cards, since a faulty card can destroy the data on a full RAID set as easily as it can a single disk.
Also check your driver cards, since a faulty card can destroy the data on a full RAID set as easily as it can a single disk.
{{Tip box| we could use a shortcut for the raid rebuild :
mdadm -f /dev/md2 /dev/hda2 -r /dev/hda2 -a /dev/hda2}}
====Convert Software RAID1 to RAID5====
====Convert Software RAID1 to RAID5====
{{Note box|msg=these instructions are only applicable if you have SME8 and a RAID1 system with 2 hd in sync; new drive(s) must be of the same size or larger as the current drive(s)}}
{{Note box|msg=these instructions are only applicable if you have SME8 or greater and a RAID1 system with 2 hd in sync; new drive(s) must be of the same size or larger as the current drive(s)}}
{{Warning box|msg=Please make a full backup before proceeding}}
{{Warning box|msg=Please make a full backup before proceeding}}
{{Warning box|msg=Newer versions of mdadm use the v1.x superblocks stored at the beginning of the block device, which could overwrite the filesystem metadata. You’ll need to be starting with a v0.9 metadata device for the above instructions to work (which was the default for years).First, check the existing superblock version with:
{{Warning box|msg=Newer versions of mdadm use the v1.x superblocks stored at the beginning of the block device, which could overwrite the filesystem metadata. You’ll need to be starting with a v0.9 metadata device for the above instructions to work (which was the default for years).First, check the existing superblock version with:
sfdisk /dev/sdc < tmp.out
sfdisk /dev/sdc < tmp.out
</li><li>Repeat the last step for each new hd (sdd, sde ecc.).
</li><li>Repeat the last step for each new hd (sdd, sde etc.).
</li><li>Create the new array
</li><li>Create the new array
mdadm --create /dev/md2 -c 256 --level=5 --raid-devices=2 /dev/sda2 /dev/sdb2
mdadm --create /dev/md2 -c 256 --level=5 --raid-devices=2 /dev/sda2 /dev/sdb2
mdadm --add /dev/md2 /dev/sdc2
mdadm --add /dev/md2 /dev/sdc2
</li><li>Repeat the last step for each new hd (sdd2, sde2 ecc.)
</li><li>Repeat the last step for each new hd (sdd2, sde2 etc.)
</li><li>Grow the array
</li><li>Grow the array
