Hello,

I apologize ahead of time, if the answer for this is in an older thread but I have been unable to find it.

 

I am running a VM with UNRAID 5.0.5 with 3 x 1TB Drives (Including Parity).

Yesterday I got WD 4TB Raid that I wanted to become my new parity drive so in the future I can go directly to 4TB.  When I put it in, it showed the drive as 2.2TB (So MBR).

 

I took it out of the array changed it to GPT and put it back in.  UNRAID changed it right back to MBR with a size of 2.2TB.

Now at the moment this is no big deal as non of my data drives are bigger than 1 TB,

but with an addition of a 4TB drive will the parity drive reparation then or am I doing something wrong?

 

Thank You.

Yesterday I got WD 4TB Raid that I wanted to become my new parity drive so in the future I can go directly to 4TB.  When I put it in, it showed the drive as 2.2TB (So MBR).

It sounds like the controller you have the drive connected to does not support large drives. Could you post a list of your hardware? Motherboard, HBA's, etc? Also, a syslog might contain some clues.

Here is my build.

I also use ESXI VM hosting w/ vCenter.  I am passing through the raid controller to the VM.  The raid controller is used for UNRAID

 

• Intel Xeon E3-1230 V3 3.3GHz Quad-Core
  
• Rosewill 550W ATX12V / EPS12V
  
• 4 x Kingston 8GB 240-Pin DDR3 SDRAM ECC Unbuffered DDR3 1600 Server Memory
  
• Rosewill RSV-L4500
  
• Rosewill RSV-L4500
  
• ASUS P9D-M Micro ATX Server Motherboard
  
• Intel SASUC8I RAID Controller Card SATA/SAS PCI-E x8
  

 

 

Not sure what to look for in the syslog.  Nothing sticks out.  WDC is the new parity Hitachi was the old parity

 

Jul 18 18:46:39 raid emhttp: Device inventory:
Jul 18 18:46:39 raid emhttp: ST1000DM003-1CH162_Z1D7VHMN (sdb) 976762584
Jul 18 18:46:39 raid emhttp: WDC_WD40EFRX-68WT0N0_WD-WCC4E76XE2J9 (sdc) 2147483647
Jul 18 18:46:39 raid emhttp: Hitachi_HDT721010SLA360_STN607MS0J3HBK (sdd) 976762584
Jul 18 18:46:39 raid emhttp: ST1000DM003-1CH162_Z1D5E8PQ (sde) 976762584
Jul 18 18:46:39 raid kernel: mdcmd (1): import 0 8,32 2147483612 WDC_WD40EFRX-68WT0N0_WD-WCC4E76XE2J9
Jul 18 18:46:39 raid kernel: md: import disk0: [8,32] (sdc) WDC_WD40EFRX-68WT0N0_WD-WCC4E76XE2J9 size: 2147483612
Jul 18 18:46:39 raid kernel: mdcmd (2): import 1 8,64 976762552 ST1000DM003-1CH162_Z1D5E8PQ
Jul 18 18:46:39 raid kernel: md: import disk1: [8,64] (sde) ST1000DM003-1CH162_Z1D5E8PQ size: 976762552
Jul 18 18:46:39 raid kernel: mdcmd (3): import 2 8,16 976762552 ST1000DM003-1CH162_Z1D7VHMN
Jul 18 18:46:39 raid kernel: md: import disk2: [8,16] (sdb) ST1000DM003-1CH162_Z1D7VHMN size: 976762552
Jul 18 18:46:39 raid kernel: mdcmd (4): import 3 0,0
Jul 18 18:46:39 raid kernel: mdcmd (5): import 4 0,0
Jul 18 18:46:39 raid kernel: mdcmd (6): import 5 0,0

 

 

 

 

Apparently that card can not format drives greater than 2.2TB. But if the drive is formatted before adding it to the card then it can see the full size of the drive.

Apparently that card can not format drives greater than 2.2TB. But if the drive is formatted before adding it to the card then it can see the full size of the drive.

 

http://ark.intel.com/PT-BR/products/39105/Intel-RAID-Controller-SASUC8I

 

It uses the same BR10i controller, LSI1068, so no support for 2TB+ disks.

 

The onboard card should work ok, I think.

Thanks guys, did not notice this when buying the card.

Will purchase something else instead.

The LSI 1068E controller used on that card does not support drives > 2TB.

 

You'll need to use a different controller card to support your new drive.

 

Sorry for the repetitive post ... I was downloading the detailed specs for the card and then the 1068E, and confirming that there's no firmware update to resolve it -- and by the time I posted the info was already there.

 

In any event, I can confirm that there's no update that will resolve this, so you will indeed need a newer card with > 2TB support.

 

Note that if you don't need the full 4TB right now, and want to use the disk with your current system, you can make it effectively a 2TB drive by using the SetMax function in the free HDAT2 utility.

 

Thanks,

For the most part unRAID seems to handle that automatically.  The moment I added the drive it unRaid just treated it as a 2.2TB drive and set it up as a parity drive then I added the old parity drive as new drive.

 

Maybe it just appears thats its working.  I will post an update if I notice something weird.