tgeng Posted July 31, 2021 Share Posted July 31, 2021 I have two Samsung 860Evo 2TB, and when I tried to use one as data and the other one as parity, Unraid told me "Disk in parity slot is not biggest" and array is not permitted to start. I know the topic about "HPA mode", but I'm not using Gigabyte motherboard, my machine is HPE Microserver 10+ and the command hdparm indicates that HPA is disabled for both disks. Any clues for what's going on? Thanks ! tower-diagnostics-20210731-1847.zip Quote Link to comment
itimpi Posted July 31, 2021 Share Posted July 31, 2021 Not sure why they are reported as different sizes, but in the syslog I see Jul 31 18:46:46 Tower kernel: mdcmd (1): import 0 sdc 2048 1953513560 0 Samsung_SSD_860_EVO_2TB_S597NJ0NB20380F Jul 31 18:46:46 Tower kernel: md: import disk0: (sdc) Samsung_SSD_860_EVO_2TB_S597NJ0NB20380F size: 1953513560 Jul 31 18:46:46 Tower kernel: md: disk0 new disk Jul 31 18:46:46 Tower kernel: mdcmd (2): import 1 sdb 64 1953514552 0 Samsung_SSD_860_EVO_2TB_S597NJ0NB18397B Jul 31 18:46:46 Tower kernel: md: import disk1: (sdb) Samsung_SSD_860_EVO_2TB_S597NJ0NB18397B size: 1953514552 Jul 31 18:46:46 Tower kernel: md: disk1 new disk which suggests they are not exact;y the same size. You could try swapping them over and see if UnRaid then lets you start the array. Quote Link to comment
tgeng Posted July 31, 2021 Author Share Posted July 31, 2021 12 minutes ago, itimpi said: Not sure why they are reported as different sizes, but in the syslog I see Jul 31 18:46:46 Tower kernel: mdcmd (1): import 0 sdc 2048 1953513560 0 Samsung_SSD_860_EVO_2TB_S597NJ0NB20380F Jul 31 18:46:46 Tower kernel: md: import disk0: (sdc) Samsung_SSD_860_EVO_2TB_S597NJ0NB20380F size: 1953513560 Jul 31 18:46:46 Tower kernel: md: disk0 new disk Jul 31 18:46:46 Tower kernel: mdcmd (2): import 1 sdb 64 1953514552 0 Samsung_SSD_860_EVO_2TB_S597NJ0NB18397B Jul 31 18:46:46 Tower kernel: md: import disk1: (sdb) Samsung_SSD_860_EVO_2TB_S597NJ0NB18397B size: 1953514552 Jul 31 18:46:46 Tower kernel: md: disk1 new disk which suggests they are not exact;y the same size. You could try swapping them over and see if UnRaid then lets you start the array. tried to swap them and i was able to start the array. but i really don't want to move all the data... the weird thing is that the command `hdparm` shows the same size i'd better cancel the order for another two 860 evo, since the tiny difference. thank you for the reply! Quote Link to comment
JorgeB Posted August 1, 2021 Share Posted August 1, 2021 SSDs have the same size, but the first one was was likely formatted before v6.9.x, the new alignment now makes them have a smaller partition. Quote Link to comment
trurl Posted August 1, 2021 Share Posted August 1, 2021 Note that SSDs in the array can't be trimmed. Quote Link to comment
tgeng Posted August 2, 2021 Author Share Posted August 2, 2021 On 8/1/2021 at 6:10 AM, JorgeB said: SSDs have the same size, but the first one was was likely formatted before v6.9.x, the new alignment now makes them have a smaller partition. Thanks! So the only way is to transfer the data and reformat it? Quote Link to comment
JorgeB Posted August 3, 2021 Share Posted August 3, 2021 10 hours ago, tgeng said: So the only way is to transfer the data and reformat it? Not just reformat, but you need to delete the existing partition so the new layout is used. 1 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.