Line 12: |
Line 12: |
| | | |
| 2011-03-06: added a warning box to RAID1 -> RAID5 conversion: note taken from http://www.arkf.net/blog/?p=47 | | 2011-03-06: added a warning box to RAID1 -> RAID5 conversion: note taken from http://www.arkf.net/blog/?p=47 |
| + | |
| + | |
| + | From Bug 6632 and 6630 a suggested sequence for Upgrading a Hard Drive size is detailed below after issue when attempting to sync a new drive when added first as sda |
| + | |
| + | ====Upgrading the Hard Drive Size after HD fail==== |
| + | Note: these instructions are applicable if you have a faulty HD on a RAID system with more than one drive and intend to upgrade the sizes as well as replacing the failed HD. They are not applicable to a single-drive RAID 1 system, and increasing the useable space on such a system by cloning the existing single drive to a larger drive is not supported. See http://bugs.contribs.org/show_bug.cgi?id=5311 |
| + | |
| + | * CAUTION MAKE A FULL BACKUP! |
| + | * Ensure you have e-smith-base-4.16.0-33 or newer installed. [or Update to at least 7.1.3] |
| + | |
| + | HD Scenario - Current 250gb drives, new larger 500gb drives |
| + | |
| + | # Remove old 250gb HDD from sdb, leave old 250gb drive as sda on its own and boot up. |
| + | # Shutdown, connect one new 500gb drive as sdb and boot up |
| + | # Login to the admin panel and manage raid to add new (larger) drive to system. |
| + | # Wait for raid to fully sync |
| + | # Do full reboot with those 2 drives in place (1 original, 1 new) |
| + | #Shutdown again, disconnect the original drive, and connect the new drive just sync'd as sda (in place of original) |
| + | # Boot up again with just the one new drive in place, and confirm it boots OK. |
| + | #Shutdown, and connected the other 500gb drive as sdb |
| + | # Boot up login to admin panel and add sdb to the array, and wait for raid to fully sync. |
| + | # Reboot with both drives in place, and check RAID health is OK. |