You did a factory default and the problem persists?
On the Dashboard can you go to Configure > Health > Download Logs? Extract the contents of the zip file. What do initrd.log and partition.log look like?
WARNING: GPT (GUID Partition Table) detected on '/dev/sda'! The util fdisk doesn't support GPT. Use GNU Parted.
Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md2 doesn't contain a valid partition table Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/sda: 801.6 GB, 801569726464 bytes 256 heads, 63 sectors/track, 97071 cylinders, total 1565565872 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000
Device Boot Start End Blocks Id System /dev/sda1 1 1565565871 782782935+ ee GPT
Disk /dev/md0: 4293 MB, 4293906432 bytes 2 heads, 4 sectors/track, 1048317 cylinders, total 8386536 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000
Disk /dev/md1: 536 MB, 536858624 bytes 2 heads, 4 sectors/track, 131069 cylinders, total 1048552 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000
Disk /dev/md2: 796.7 GB, 796734570496 bytes 2 heads, 4 sectors/track, 194515276 cylinders, total 1556122208 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000
Disk /dev/dm-0: 786.0 GB, 785979015168 bytes 255 heads, 63 sectors/track, 95556 cylinders, total 1535115264 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000
That is odd. A factory default should have wiped the disk and set it up properly.
Did you by any chance format the disk in a PC first?
If so, what OS is that PC running (e.g. Windows XP)?
If you can hook the drive up to a PC, delete the partitions on the disk (but not format it) and then put the disk back in the NAS and do another factory default.
If using a Mac/Linux machine you can alternatively hook the disk up to that and use e.g. dd to write zeroes to the start of the disk to remove the partition table.
I just bought a ReadyNAS Ultra 6 plus, and 6 3TB Seagate Barracuda disks. I had the same problem. ReadyNAS identified each of them with just 746 GB. I did factory default reboots with all six drives in them, and with just one, and none worked. They kept coming up with just 746 GB per disk. Finally, I updated to the most recent firmware: RAIDiator 4.2.21 (http://www.readynas.com/?p=6469). I had to do this as a local update, because when I tried to do it as a remote one, it was also giving me trouble. So I downloaded the image from the link in the page I posted the url for here, and then used the local update option in the Frontview.
I then did the factory default reboot with just one disk, and set the volume to X-RAID when prompted by the setup software, and It identified the space in the disk as 2794 GB, which I'm assuming is the 3TB Seagate claims, and allocated 2790 GB to it. Now I've just added the second drive, with the machine still on, and is resyncing the volume in the background. It has also identified the second drive as 2794 GB, and I'm assuming it will allocate 2790 GB to it as well. I say I'm assuming bc this process takes like 3 hours, so it's still in the middle of it.
I did not have to remove any partition or do anything to the disks. I know some time has passed from the last post in this, but I hope that this info is still of use to anyone buying a new ReadyNAS.
alfinmass the ARM devices such as the Duo v2 (x8x8x has one of these) have always had GPT support so it should've recognised the full capacity of the disk immediately on that. Though sometimes if disks have been used previously (e.g. in a PC) they might not be recognised properly due to the way they've been formatted.
For the x86 devices like the Ultra 6 Plus GPT support was added in 4.2.16. So it sounds like your NAS came with 4.2.15 or earlier. Now that you've updated the firmware to 4.2.21 you could do a factory default with all disks installed if you like. This would probably be quickest.
Do note that the NAS like most PCs measures using TiB (i.e. 1 TiB = 1024^4 Bytes) whereas disk manufacturers use TB (i.e. 1TiB = 1000^4 Bytes). However like with PCs, there isn't a distinction in the naming between TiB and TB, so TB is used. So 3TB (disk manufacturers measurement) = 3000 / 1024 ^ 3 * 1000 ^ 4 = 2794GB (NAS/PC measurement). There is a 4GB partition dedicated to the OS.
For the x86 devices like the Ultra 6 Plus GPT support was added in 4.2.16. So it sounds like your NAS came with 4.2.15 or earlier. Now that you've updated the firmware to 4.2.21 you could do a factory default with all disks installed if you like. This would probably be quickest.
Actually its not just about quickest.
If you add 3 TB drives one at a time, you can't expand beyond a 11 TB volume. So when you add the 5th disk you won't be able to use all the space on it, and the sixth disk is only useful if you choose dual redundancy.
So if your goal is to get a full 15 TB volume, you need to do a factory default with at least 4 of your 3 TB disks in place.
