88
edits
Changes
From SME Server
Jump to navigationJump to searchspello
{{Level|Advanced}}
{{Level|Advanced}}
{{Warning box|Get it right or you will lose data. '''Take a backup!''' Let the raid sync, this can take quite a while.}}
SME Servers Raid Options are largely automated, if you built your system with a single hard disk simply logon as admin and select Disk Redundancy to add a new drive to your RAID1 array. The same procedure is used if you have a disk failure in a RAID array and you have replaced that failed disk.
But with the best laid plans things don't always go according to plan, these are the processes required to do it manually.
See also: [[Hard Disk Partitioning]] and [[Raid#Resynchronising_a_Failed_RAID]]
== HowTo: Manage/Check a RAID1 Array from the command Line ==
== HowTo: Manage/Check a RAID1 Array from the command Line ==
=== What is the Status of the Array ===
=== What is the Status of the Array ===
[root@ ~]# '''smartctl -l selftest /dev/sdb'''
[root@ ~]# '''smartctl -l selftest /dev/sdb'''
You can refer to this page for more information how activate or understand the Analysis and Reporting Technology (SMART) [[Monitor_Disk_Health]]
{{Note box|if you need to change the disk due to physical failure found by the smartctl command, install a new disk of the same capacity (or more) and enter the following commands to recreate new partitions by copying them from healthy disk sda.}}
{{Note box|if you need to change the disk due to physical failure found by the smartctl command, install a new disk of the same capacity (or more) and enter the following commands to recreate new partitions by copying them from healthy disk sda.}}
[root@ ~]# '''sfdisk -d /dev/sda > sfdisk_sda.output'''
[root@ ~]# '''sfdisk -d /dev/sda > sfdisk_sda.output'''
[root@ ~]# '''sfdisk /dev/sdb < sfdisk_sda.output'''
[root@ ~]# '''sfdisk /dev/sdb < sfdisk_sda.output'''
GPT Disks
Larger disks will be GPT Disks, sfdisk will not work - you will need to use gdisk and partx (parted)
[root@ ~]# '''yum install gdisk'''
The copy the partition table from a good disk to the new disk, the first line will copy the partition table from disk sda to sdd, the second will randomize the GUID
[root@ ~]# '''sgdisk /dev/sda -R /dev/sdd'''
[root@ ~]# '''sgdisk -G /dev/sdd'''
To view the partitions use partx
[root@ ~]# '''partx -l /dev/sdd'''
If you want to reinstate the same disk without replacing it, go to the next step.
If you want to reinstate the same disk without replacing it, go to the next step.
== HowTo: Write the GRUB boot sector ==
== HowTo: Write the GRUB boot sector ==
{{Warning box|as the dd command is named "data destroyer" you need to be extremely prudent and sure of the name of source partition and/or destination. At first you should skip the dd command, Step 1 below, and attempt to install grub without it, see Step 2 below. If grub can be installed without using dd, then Step 1 can be discarded. }}
*1.dd
[root@ ~]# '''dd if=/dev/sda1 of=/dev/sdb1'''
[root@ ~]# '''dd if=/dev/sda1 of=/dev/sdb1'''
*2.grub
[root@ ~]# '''grub'''
[root@ ~]# '''grub'''
Running "embed /grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
Running "embed /grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded.
succeeded
succeeded
Running "install /grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/grub/stage2 /grub/grub.conf"... succeeded
Running "install /grub/stage1 (hd0) (hd1)1+16 p (hd0,0)/grub/stage2 /grub/grub.conf"... succeeded
Done.
Done.
grub> '''quit'''
grub> '''quit'''
<noinclude>
<noinclude>[[Category:Howto]][[Category:Administration:Storage]]</noinclude>
[[Category:Howto]]
[[Category:Administration:Storage]]
</noinclude>
