October 8, 20187 yr Tried to add two new, WD Red 6TB drives to my server, using one to replace the parity and then the second as a data drive. Steps I followed: Spin down array Shutdown Disconnect current parity cables Install (2) 6TB drives Reboot Spin down array Assign one of 6TB drives as parity Restart array Once it came up, it only registered 2.2TB drive as parity. The largest data disk prior to my steps was a 2TB drive. Since I didn't notice the parity was the wrong size I went through the process of clearing and formatting the old parity and the new data drives. Obviously the new data drive was formatted to 2.2TB as well, presumably because it can't be larger than the parity. Note that when I look at the two new 6TB drives, the Information section clearly shows they are 6TB drives so not sure why it did what it did. Attached Diagnostics, thanks for the advice in advance. tower-diagnostics-20181007-1635.zip Edited October 8, 20187 yr by kanwisch SOLVED
October 8, 20187 yr Community Expert Google 2.2TB limit and you will see that this was a problem with older gear.
October 8, 20187 yr Community Expert LSI SAS 1xxx controllers are limited to 2.2TB, it should detect the full 6TB if you connect them on the onboard SATA controller, also you're on a very old Unraid release, you should update to latest.
October 8, 20187 yr Author 20 hours ago, Frank1940 said: Google 2.2TB limit and you will see that this was a problem with older gear. Thanks for that tip, I'll look into it and come back to mark this solved once I validate this is the cause. Appreciate the pointer!
October 8, 20187 yr Author 13 hours ago, johnnie.black said: LSI SAS 1xxx controllers are limited to 2.2TB, it should detect the full 6TB if you connect them on the onboard SATA controller, also you're on a very old Unraid release, you should update to latest. Yup, LSI 1068e SAS. Thanks again guys for the pointers, I've got a direction. SOLVED
Archived
This topic is now archived and is closed to further replies.