Because a simple thing as a driver update can loose your array, i'm not against software raid in a test environment and to a certain extent Raid1.
I have heard this reason quite a few times as a reason not to use software raid and have in certain instances used it myself. It is pretty valid for motherboard raid controllers but not so much for Linux. The raid arrays are transportable between machines with a reasonable closeness of mdadm version.
If the hardware raid card failed you are stuck either having to have a spare available or going out to find one. If a Linux software raid array fails due to a software issue, just put a prepatch version of that distro on another machine and mount there or revert the patch on the original machine (if possible). Software raid is much cheaper and the main area hardware raid beats it is offloading the processing to a dedicated processor and having a BBU for power outages. Also, don't forget that hardware raid controllers can also have firmware patchs which could also kill the array, although you would obviously hope the manufacturer have done some decent testing).
But Raid0,5 should be a no no with any data you value.
Totally agree with raid0. Not so much with raid5. Depends how many belts and braces you think would be required to hold your trousers up. Raid5 with 4 disks should not be used ?. Raid 6 for 4 disks and you may as well use Raid10. Of course, any data you value should be backed up to a non raid set anyway.
It simple doesn't bring any of the benefits of using raid in the first place.
Sorry ?. Raid0 and Raid5 do not bring the benefits of raid ?. Guess that depends on what you believe the benefits to be. For me, personally, in a home environment, both bring benefits over not having a raid array. Of course I could have missunderstood what you were trying to get at
.
Maybe, but in Linux the RAID array config/info is stored on the disks, so as long as your data array is separate to your install which is what I am doing, I can reinstall linux, rescan for the array and mount it.
Yep, very handy.
It really is horses for courses.... In a non-critical environment then software raid should be fine (not motherboard raid). In a critical environment you would want the reassurance of at least a BBU so hardware raid would be the obvious choice but then everything is usually a balance of cost / benefits.
Nikumba has not yet specified what the server will be used for, where it will be located (home / work) and what is the value of the data to be stored.
A lot of people here may well be from a corporate environment and so can share experiences on best practices from there whilst others are home users who may consider those practices to be pure overkill in their environments. Horses for courses.
Nikumba, can you enlighten us on;
Where the server will be used (Home/Work):
What will the array be used to store:
How important is the data for you:
Are you having a separate backup:
How much downtime can you tolerate if you lost the array:
What sort of budget is available:
With the answers to those questions, people can tailor the answer a lot better for your needs.
RB