Partitioning for Raid 5
I'm having issues trying to partition 4x 1tb harddrives. I booted in to the usb linux, tried "Everything Else" and selected the drives individually to partition, but then it gives me an error. Since I already have a OS drive (80gb drive son /sde/sde1), I don't actually want to install ubuntu again.
I would prefer to do it in bash, but I can't seem to find a HOWTO with clear directions. Any suggestions? |
As root
Code:
cat /etc/*release* You'll want eg 1. background info concepts https://raid.wiki.kernel.org/index.php/Linux_Raid 2. HOWTO http://www.linuxhomenetworking.com/w...re_RAID#RAID_5 |
at fdisk -l, this was the return:
Quote:
Also: Quote:
|
Quote:
|
So I managed get everything partitioned, awesome, but now it's giving me a wierd error.
Quote:
Suggestions? |
I think the implications of this page http://linux.die.net/man/8/mdadm (both syntax defn & examples) imply that the /dev/mdX name should come immediately after the -C
Code:
# also, use a single long line (ie no '\') & short circuit dev names |
Wwwooootttt!!! Thanks!!
|
So, that all worked (YAY!), but after I managed to get the network set up and mapped in to windows, I saw that it was only 800gb. so with a simple cat /proc/mdstat:
Code:
root@evocati-desktop:/home/evocati# cat /proc/mdstat |
Tricky to say; did you fdisk those to stay as FAT32, or as Linux RAID : partition type fd in fdisk ?
http://www.win.tue.nl/~aeb/partition...n_types-1.html Try Code:
fdisk -l Note that RAID5 'loses' 1 disk for parity https://en.wikipedia.org/wiki/Standa..._levels#RAID_5 and when you mkfs.ext3 (or mkfs.ext4), you 'lose' 5% reserved to root/OS usage. You can amend that at the mkfs time http://linux.die.net/man/8/mkfs.ext3 or later with tune2fs http://linux.die.net/man/8/tune2fs |
Quote:
Also: Code:
evocati@evocati-desktop:~$ sudo fdisk -l |
I'm not sure how mdadm will handle MS FAT32 disks and in any case you are limited by FAT32 itself, which is very old(!) tech and will not address that size of disk I believe.
Why don't you use a native Linux FS eg ext3/ext4? If you want to mount this afterwards from MSWin, there are drivers for ext3 under MS I believe, or (better) use network mounting via Samba or NFS. Actually, the disk partition types need to be set to 'fd' = Linux RAID. ext3/ext4 is the Filesystem type. |
I managed to get this all working last weekend. As it turns out, if you just use an EXT4 partition on the raid and a Fat32 (or MSDOS w/e) on the drives themselves with a GPT selection, it works just fine. I had some issues getting things cleaned up, but once I was able to get the system to recognize the full raid size, I was golden.
Now, I'm needing to go through and clean out the auto-mount fstab file so it stops pausing during boot and then change the raid name so it isn't some long list of numbers/letters... that's annoying. I'd prefer to have it auto-mount with a particular name so the rest of the comps can connect to it immediately. One odd thing is that one of the machines keeps having connectivity issues and dropping the connection. I've heard that that's been an issue, but I figured it was resolved. I'll have to get a screen shot the next time it happens. Either way, I now have 4Tb+ on a network. Yay. (2.73Tb WD Black Raid5 + 1.8Tb WD Green solo) Lastly, I didn't want to have to fool with the windows boxes incase there were something I needed to do to them. I wanted something that you could just plug a computer in to the router and be able to communicate with it immediately. The drivers seemed like one more thing to remember to get if I were to do a wipe. |
All times are GMT -5. The time now is 11:27 AM. |