Ranensol Posted August 29, 2019 Share Posted August 29, 2019 (edited) Hi there, first time posting here, so please go easy on me History: I had a small 3 drive array with a 2TB parity, 2TB Disk 1, and 500GB Disk 2. I wanted to expand my capacity, and Disk 1 died, so I bought 2 x 4TB Toshiba HDWQ140 NAS drives with a view to replacing the parity with a 4TB drive, and having a 4TB Disk 1, the old 2TB parity as Disk 2, and removing the dead 2TB and 500GB drives. Now: I installed one 4TB drive last night and set it up as parity 2, waited until it'd finished setting up that drive, and today I've shifted Parity 1 to Disk 1 (removing the dead 2TB drive in the process). I've just noticed however that the 4TB parity drive is showing as a 2.2TB drive in the unRaid (6.7.2) GUI: In the drive details though it's showing as a 4TB drive: I have since dropped the other 4TB drive in the box to see how that gets identified and it also shows as 2.2TB but 4TB on the drive details screen. I've searched the net and forums and couldn't find any similar posts relating to unRaid and drive size, so apologies if this has already been covered, but does anyone have any idea what could be wrong? Any and all help appreciated! Thanks Edited August 29, 2019 by Ranensol Quote Link to comment
JorgeB Posted August 29, 2019 Share Posted August 29, 2019 That's likely a controller issue, diags would confirm. Quote Link to comment
trurl Posted August 29, 2019 Share Posted August 29, 2019 Probably your controller only supports drives up to 2.2TB Go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post. 1 Quote Link to comment
Ranensol Posted August 29, 2019 Author Share Posted August 29, 2019 Ahh nuts... it's a pretty old box tbf, really hope it's not that 😛 Thanks for the quick replies, diagnostics attached! unraid-diagnostics-20190829-1405.zip Quote Link to comment
JorgeB Posted August 29, 2019 Share Posted August 29, 2019 1st gen LSI controllers only support up to 2.2TB, only SAS2 o SAS3 support larger, you can use the onboard SATA controller, though change it to AHCI mode if available. 1 Quote Link to comment
Ranensol Posted August 29, 2019 Author Share Posted August 29, 2019 Excellent, thanks again for the quick response and detailed info! I'll take a look in the BIOS for the AHCI settings and juggle the drives around and see what I can do. On a side note, I did take a look through those diagnostics and couldn't make a lot out tbh (my fault not the logs), can I ask where you found the relevant info please? or is that too broad a question? Quote Link to comment
JorgeB Posted August 29, 2019 Share Posted August 29, 2019 In this case all the info needed was on the syslog.txt (but same things could be seen on other files,e.g. lspci.txt and lsscsi.txt): This shows that the Intel SATA controller is set to IDE mode: Aug 28 18:49:01 Tower kernel: ata_piix 0000:00:1f.2: version 2.13 Aug 28 18:49:01 Tower kernel: ata_piix 0000:00:1f.2: MAP [ P0 P2 P1 P3 ] And this shows that the LSI is an older SAS1 model: Aug 28 18:49:01 Tower kernel: ioc0: LSISAS1064E B1: Capabilities={Initiator} 1 Quote Link to comment
Ranensol Posted August 29, 2019 Author Share Posted August 29, 2019 Ahh I see, that's great, thanks again for the help! Quote Link to comment
Ranensol Posted August 30, 2019 Author Share Posted August 30, 2019 Just a final update here, I've moved the 4TB parity drive to the motherboard and it's being picked up as 4TB not 2.2TB now. Once that's done rebuilding I'll drop the 500GB and put the other 4TB in and all will be well. Thanks one last time for the help! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.