HK-Steve Posted June 23, 2019 Share Posted June 23, 2019 Hi Everyone, Had some interesting behaviour after adding more RAM, My Parity check halved it's speed or worse. My Tower3 had 1x 16Gb of RAM, added 1x stick of 16Gb of the same model and brand, was seen properly in bios and UnRaid. But my Parity check went from about 110Mb/s, went to 70mb's... I removed the 16Gb of RAM, Parity check went back to 110Mb/s My Tower2 had 1x 8Gb of RAM, added 1x stick of 8gb of exactly the same model and brand, was seen properly in bios and UnRaid. But my Parity check went from about 80Mb/s, went to 3mb's... I removed the 8Gb of RAM, Parity check went back to 80Mb/s Did I miss something when I added the RAM, configuration?? Do I need to do anything other than adding the RAM stick to the motherboard and boot into UnRaid? The Diagnostic is from my Tower3 while running the Parity check with the 32Gb of Ram installed. Appreciate your always valuable advice tower3-diagnostics-20190623-0849.zip Quote Link to comment
JorgeB Posted June 23, 2019 Share Posted June 23, 2019 More RAM won't slow down a parity check, a failing disk will: Jun 22 06:02:22 Tower3 kernel: md: disk13 read error, sector=136846664 Jun 22 06:02:22 Tower3 kernel: md: disk13 read error, sector=136846672 Jun 22 06:02:22 Tower3 kernel: md: disk13 read error, sector=136846680 Jun 22 06:02:22 Tower3 kernel: md: disk13 read error, sector=136846688 Jun 22 06:02:22 Tower3 kernel: md: disk13 read error, sector=136846696 Jun 22 06:02:22 Tower3 kernel: md: disk13 read error, sector=136846704 Quote Link to comment
HK-Steve Posted June 23, 2019 Author Share Posted June 23, 2019 Hmm, I do not see that error. Quote Link to comment
HK-Steve Posted June 23, 2019 Author Share Posted June 23, 2019 Would I see that as Smart error?? Or would that be a cable issue? Quote Link to comment
JorgeB Posted June 23, 2019 Share Posted June 23, 2019 For now they are not reported as pending sectors, so not the usual monitored attributes, but you should be getting an "array has errors" system notification, also the problem can be seen on the SMART report, this attribute should be 0 on a healthy WD drive ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE 1 Raw_Read_Error_Rate POSR-K 200 200 051 - 177 and mostly these, these are recent UNC @ LBA errors, aka read errors, and this is a disk problem, not cable/connection related.: Error 401 [16] occurred at disk power-on lifetime: 31143 hours (1297 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 53 9f bf c0 40 00 Error: UNC at LBA = 0x1539fbfc0 = 5697945536 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 04 00 00 00 00 01 53 9f bc 18 40 00 22:15:53.114 READ FPDMA QUEUED 60 04 00 00 00 00 01 53 9f b8 18 40 00 22:15:53.106 READ FPDMA QUEUED 60 04 00 00 00 00 01 53 9f b4 18 40 00 22:15:53.100 READ FPDMA QUEUED 60 04 00 00 00 00 01 53 9f b0 18 40 00 22:15:53.092 READ FPDMA QUEUED 60 04 00 00 00 00 01 53 9f ac 18 40 00 22:15:53.085 READ FPDMA QUEUED Error 400 [15] occurred at disk power-on lifetime: 31143 hours (1297 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 4f 8c ed 08 40 00 Error: UNC at LBA = 0x14f8ced08 = 5629603080 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 04 00 00 00 00 01 4f 8c ec 18 40 00 22:08:05.744 READ FPDMA QUEUED 60 04 00 00 00 00 01 4f 8c e8 18 40 00 22:08:05.737 READ FPDMA QUEUED 60 04 00 00 00 00 01 4f 8c e4 18 40 00 22:08:05.730 READ FPDMA QUEUED 60 04 00 00 00 00 01 4f 8c e0 18 40 00 22:08:05.724 READ FPDMA QUEUED 60 04 00 00 00 00 01 4f 8c dc 18 40 00 22:08:05.716 READ FPDMA QUEUED Error 399 [14] occurred at disk power-on lifetime: 31143 hours (1297 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 4a 85 20 58 40 00 Error: UNC at LBA = 0x14a852058 = 5545205848 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 04 00 00 00 00 01 4a 85 20 18 40 00 21:58:50.189 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 85 1c 18 40 00 21:58:50.183 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 85 18 18 40 00 21:58:50.175 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 85 14 18 40 00 21:58:50.169 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 85 10 18 40 00 21:58:50.162 READ FPDMA QUEUED Error 398 [13] occurred at disk power-on lifetime: 31143 hours (1297 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 4a 73 26 50 40 00 Error: UNC at LBA = 0x14a732650 = 5544027728 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 04 00 00 00 00 01 4a 73 24 18 40 00 21:58:39.064 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 73 20 18 40 00 21:58:39.057 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 73 1c 18 40 00 21:58:39.050 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 73 18 18 40 00 21:58:39.043 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 73 14 18 40 00 21:58:39.036 READ FPDMA QUEUED Error 397 [12] occurred at disk power-on lifetime: 31143 hours (1297 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 4a 68 38 f8 40 00 Error: UNC at LBA = 0x14a6838f8 = 5543311608 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 04 00 00 00 00 01 4a 68 38 18 40 00 21:58:30.968 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 68 34 18 40 00 21:58:30.961 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 68 30 18 40 00 21:58:30.955 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 68 2c 18 40 00 21:58:30.948 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 68 28 18 40 00 21:58:30.942 READ FPDMA QUEUED Error 396 [11] occurred at disk power-on lifetime: 31143 hours (1297 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 4a 48 f3 70 40 00 Error: UNC at LBA = 0x14a48f370 = 5541262192 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 04 00 00 00 00 01 4a 48 f0 18 40 00 21:58:14.117 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 48 ec 18 40 00 21:58:14.111 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 48 e8 18 40 00 21:58:14.104 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 48 e4 18 40 00 21:58:14.098 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 48 e0 18 40 00 21:58:14.091 READ FPDMA QUEUED Error 395 [10] occurred at disk power-on lifetime: 31143 hours (1297 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 4a 08 43 e8 40 00 Error: UNC at LBA = 0x14a0843e8 = 5537022952 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 04 00 00 00 00 01 4a 08 40 18 40 00 21:57:42.351 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 08 3c 18 40 00 21:57:42.345 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 08 38 18 40 00 21:57:42.338 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 08 34 18 40 00 21:57:42.331 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 08 30 18 40 00 21:57:42.324 READ FPDMA QUEUED Error 394 [9] occurred at disk power-on lifetime: 31143 hours (1297 days + 15 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER -- ST COUNT LBA_48 LH LM LL DV DC -- -- -- == -- == == == -- -- -- -- -- 40 -- 51 00 00 00 01 4a 06 bb 90 40 00 Error: UNC at LBA = 0x14a06bb90 = 5536922512 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 04 00 00 00 00 01 4a 06 b8 18 40 00 21:57:38.179 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 06 b4 18 40 00 21:57:38.172 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 06 b0 18 40 00 21:57:38.166 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 06 ac 18 40 00 21:57:38.159 READ FPDMA QUEUED 60 04 00 00 00 00 01 4a 06 a8 18 40 00 21:57:38.153 READ FPDMA QUEUED Quote Link to comment
HK-Steve Posted June 23, 2019 Author Share Posted June 23, 2019 Once again johnnie.black, You are AWESOME, Thanks. I did not get any error notification, But I just went to the logs and I do see that error. Should have gone there myself first, Sorry...... Lesson learned. And learning every day. Much appreciated. Quote Link to comment
JorgeB Posted June 23, 2019 Share Posted June 23, 2019 35 minutes ago, HK-Steve said: I did not get any error notification Make sure system notifications are enable: Settings -> Notification Settings -> System notifications Quote Link to comment
HK-Steve Posted June 23, 2019 Author Share Posted June 23, 2019 Thanks, were turned on, but once a week. Modified the settings. Much appreciated. Quote Link to comment
HK-Steve Posted June 23, 2019 Author Share Posted June 23, 2019 I have a disk problem on Tower2 also, Looks like johnnie.black nailed it... Awesome. Much appreciated 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.