I have six 2TB HDDs in my Dell R710 server.  I set one as a parity drive and the rest as disks for the array.  I formatted the disks and it took 5 or 6 hours to run a parity check.  This is what it looks like now.  Did I miss a step or is something wrong?  All of my drives say Unmountable.

 

Assuming the disks don't contain any data you just need to formatted them, after checking the "Yes I want to do this" box.

Tried that.  They are still showing as Unmountable after the format. 

Were these new drives?

I bought the server on eBay last week and it came with the drives.  They are all Dell Enterprise Class SATA 3.0 drives which I believe are rebranded Western Digital RE4 drives.  Do you think there might be something wrong with them?

 

The trial license limits the number of devices to three plus the USB drive, so you won't be able to mount all of them.  Try removing three of the drives and see if it works then.  If so, the others will likely be usable with a paid for license. 

 

Trial license restrictions are shown on the download page here...  https://lime-technology.com/download/

 

Paid for versions here... https://lime-technology.com/registrationkeys/

Okay, starting over.  I'll report back when the parity check is done.  Wish me luck.

Presumably these are past infant mortality so they may be OK. After the parity check go to Tools - Diagnostics and post the complete diagnostics zip so we can check the drives for SMART issues.

Here is a diagnostic check I ran before I pulled three of the drives.  I'll post the new one once the parity check completes. 

unraid-diagnostics-20160521-1816.zip

The 3 disk array looks ok now, disk are already formatted, looks like the existing partition on the disks were causing issues, this is for disk2 but it's the same for all other disks:

 

May 20 18:10:55 Tower emhttp: shcmd (346): mkdir -p /mnt/disk2

May 20 18:10:55 Tower emhttp: shcmd (347): set -o pipefail ; mount -t auto -o noatime,nodiratime /dev/md2 /mnt/disk2 |& logger

May 20 18:10:55 Tower root: mount: unknown filesystem type 'zfs_member'

May 20 18:10:55 Tower emhttp: shcmd: shcmd (347): exit status: 32

May 20 18:10:55 Tower emhttp: mount error: No file system (32)

May 20 18:10:55 Tower emhttp: shcmd (348): umount /mnt/disk2 |& logger

May 20 18:10:55 Tower root: umount: /mnt/disk2: not mounted

 

May 20 18:16:47 Tower emhttp: shcmd (461): mkdir -p /mnt/disk2

May 20 18:16:47 Tower emhttp: shcmd (462): set -o pipefail ; mount -t auto -o noatime,nodiratime /dev/md2 /mnt/disk2 |& logger

May 20 18:16:47 Tower root: mount: /dev/md2: more filesystems detected. This should not happen,

May 20 18:16:47 Tower root:        use -t <type> to explicitly specify the filesystem type or

May 20 18:16:47 Tower root:        use wipefs( to clean up the device.

May 20 18:16:47 Tower emhttp: shcmd: shcmd (462): exit status: 1

May 20 18:16:47 Tower emhttp: mount error: No file system (1)

May 20 18:16:47 Tower emhttp: shcmd (463): umount /mnt/disk2 |& logger

May 20 18:16:47 Tower root: umount: /mnt/disk2: not mounted

Here is my current diagnostics now that I just have three disks connected and my parity sync is complete.

unraid-diagnostics-20160522-0348.zip

Everything look fine, you can now add the other disks, to maintain parity they will have to be cleared, using unRAID this will take a few hours, array will be unavailable during that time.

 

You can also use the preclear beta plugin, allows to clear the disks before so adding them is instantaneous.

 

Whatever way you use they will have to be formatted after adding them to the array.