Difference between revisions of "Linux Software RAID and SATA Hot Swap"
Jump to navigation
Jump to search
(Created page with "I know there are a million pages online about Linux Software RAID, but I wanted to record my own experience with it. My home server has four RAID1 arrays: * 160GB, for my boo...") |
|||
| Line 1: | Line 1: | ||
I know there are a million pages online about Linux Software RAID, but I wanted to record my own experience with it. | I know there are a million pages online about Linux Software RAID, but I wanted to record my own experience with it. | ||
| − | My home server has | + | My home server has a lot of storage: |
| − | * 160GB, for my boot volume, on one of the motherboard's RAID controllers | + | * a 160GB RAID1 array, for my boot volume, on one of the motherboard's RAID controllers |
| − | * 500GB, for backups, again on a RAID controller | + | * a 500GB RAID1 array, for backups, again on a RAID controller |
| − | * 2TB, for | + | * a 2TB RAID1 array, for home directories and virtual machines, on a RAID controller |
| − | * 3TB, for other stuff, using software RAID. | + | * a 3TB RAID1 array, for other stuff, using software RAID. |
| + | * a single 3TB drive, for daily backups of my 3TB array | ||
My motherboard is a number of years old now, and the onboard controllers could not do RAID for 3TB drives, as they only recognized them as 873GB. So I left these as standard drives, and set them up in software RAID. | My motherboard is a number of years old now, and the onboard controllers could not do RAID for 3TB drives, as they only recognized them as 873GB. So I left these as standard drives, and set them up in software RAID. | ||
| Line 13: | Line 14: | ||
* Control over rebuilds, being able to add/remove disks | * Control over rebuilds, being able to add/remove disks | ||
* Not being tied to a specific RAID controller with a specific firmware version. If the motherboard were to die, I can easily move the drives. | * Not being tied to a specific RAID controller with a specific firmware version. If the motherboard were to die, I can easily move the drives. | ||
| + | * No reboots required to work with the drives | ||
| + | * Linux can do SATA hot swap, so I don't need to power down to swap a disk | ||
The minor performance hit isn't an issue, so the pros far outweigh the cons. | The minor performance hit isn't an issue, so the pros far outweigh the cons. | ||
| + | |||
| + | ==Fiasco #1: The 500GB Array== | ||
| + | |||
| + | I decided to do the 500GB array first, since it was small and quick to work with. | ||
| + | |||
| + | I moved the data off the drive, rebooted the server to get into the BIOS, and deleted the array. | ||
Revision as of 10:45, 22 January 2015
I know there are a million pages online about Linux Software RAID, but I wanted to record my own experience with it.
My home server has a lot of storage:
- a 160GB RAID1 array, for my boot volume, on one of the motherboard's RAID controllers
- a 500GB RAID1 array, for backups, again on a RAID controller
- a 2TB RAID1 array, for home directories and virtual machines, on a RAID controller
- a 3TB RAID1 array, for other stuff, using software RAID.
- a single 3TB drive, for daily backups of my 3TB array
My motherboard is a number of years old now, and the onboard controllers could not do RAID for 3TB drives, as they only recognized them as 873GB. So I left these as standard drives, and set them up in software RAID.
My goal for this endeavor was to convert my 500GB and 2TB over to software RAID. The reasons being:
- Actually getting notifications regarding any issues
- Control over rebuilds, being able to add/remove disks
- Not being tied to a specific RAID controller with a specific firmware version. If the motherboard were to die, I can easily move the drives.
- No reboots required to work with the drives
- Linux can do SATA hot swap, so I don't need to power down to swap a disk
The minor performance hit isn't an issue, so the pros far outweigh the cons.
Fiasco #1: The 500GB Array
I decided to do the 500GB array first, since it was small and quick to work with.
I moved the data off the drive, rebooted the server to get into the BIOS, and deleted the array.