@MattSpeller said:

@BRRABill said:

Is ioSafe and Synology the same thing?\

Yeah but ioSafe has better BBQ's

lol

I reboot without a problem, and the mounting of the array is managed properly by xen without the entry in fstab.

@JaredBusch said:

@Romo said:

I believe he was asking about the drive itself, regular drive for any computer vs a drive you would put on a nas

There is no difference in them. You simply pick the drive that meets the specs you need. there is no such thing as a drive for NAS. no matter what certian companies try to market to you.

Yes you can put any drive on a NAS, but there is a reason most people recommend WD Reds for 24/7 use. I believe @scottalanmiller post http://www.smbitjournal.com/2014/05/understanding-the-western-digital-sata-drive-lineup-2014/ answers the OP's question, at least if using WD for drives

@JaredBusch said:

@BRRABill said:

What makes a drive a "NAS drive"?

it is network attached storage. that is all nothing else.

I believe he was asking about the drive itself, regular drive for any computer vs a drive you would put on a nas

Good morning everyone

@DustinB3403 said:

@Romo The typo's have been addressed.

Great, this way more people can follow the guide

@scottalanmiller remeber to change the line that targets devices sd[a-d] to sd[b-e],

There is also a typo in the last line,
device-config:device=/dev/md10 should be /dev/md0 following that guide

options found by default

No it is not there by default best option would be mkfs.ext3

Don't believe it was quite ready for him yet. At least not from only looking at the OP of this thread. @scottalanmiller hasn't yet changed several things from there

I am ready!

@mlnews said:

@Dashrender said:

Missing Scott's talk.

He's on right now prepping, about to start.

Can you share a link please

Thats the screenshot of the array detail as you can see the array goes from sd[b-e]

@DustinB3403 said:

@Romo

You mean

mdadm --create /dev/md0 --level=10 --raid-devices=4 /dev/sd[b-e]

Need to be very certain we aren't attempting to overwrite the OS USB

Yes, sorry I just copied the OP to show the order. The array needs to start with sdb, sda is the usb

We should also add that he needs to finish the array building before trying to add the filesystem

watch cat /proc/mdstat to see it build in real time

And also @scottalanmiller i only get mkfs.cramfs mkfs.ext2 and mkfs.ext3 as available fs by default

I believe it should be in this order:

modprobe raid10
chmod a+x /etc/sysconfig/modules/raid.modules
mdadm --create /dev/md0 --level=10 --raid-devices=4 /dev/sd[a-d]
cat /proc/mdstat

Yes in my setup sda simulates to be the usb, thats why the array starts with sdb

I got a blank output after fixing madadm to mdadm

echo "modprobe raid10" > /etc/sysconfig/modules/raid.modules
modprobe raid10
chmod a+x /etc/sysconfig/modules/raid.modules

mdadm --create /dev/md0 --level=10 --raid-devices=4 /dev/sd[a-d]

Loading the modules to kernel need to go before creating the md device