February 12, 20188 yr Hi, I recently added a new data disk to my 6.4 installation, giving a total of 4 data disks and 1 cache drive (plus a single parity disk). I just noticed that only the newly added disk will show any SMART attributes - all the other disks just report "Can not read capabilities". They definitely all used to report fine, and I remember being able to see the SMART attributes for all 6 drives (including the new one) recently as I checked the power-on time for the new drive after I installed it. Can anyone suggest why the 5 old drives have stopped reporting but the new one is still OK? Many thanks, Tim
February 12, 20188 yr I have the exact same problem except it works on all but one. Sorry to hijack thread. (Disk6 in diagnostics) fileserver-diagnostics-20180212-1027.zip Edit: Also note I just rebuilt disk 6 due to a cable issue. It was doing this before the rebuild though. Just coincidence I guess. Edited February 12, 20188 yr by RAINMAN
February 12, 20188 yr Community Expert 1 hour ago, RAINMAN said: I have the exact same problem except it works on all but one. Sorry to hijack thread. (Disk6 in diagnostics) On the main page click on the problem disk, scroll down to "SMART notification value", change to "RAW" click apply, change back to "use default", apply again. This should also fix the OP's problem but would need the diags to confirm.
February 12, 20188 yr 1 hour ago, johnnie.black said: On the main page click on the problem disk, scroll down to "SMART notification value", change to "RAW" click apply, change back to "use default", apply again. This should also fix the OP's problem but would need the diags to confirm. Perfect. Fixed it for me. Thanks
May 10, 20188 yr On 2/12/2018 at 11:29 AM, johnnie.black said: On the main page click on the problem disk, scroll down to "SMART notification value", change to "RAW" click apply, change back to "use default", apply again. This should also fix the OP's problem but would need the diags to confirm. Thanks - I just installed a 10TB Hitachi and my SMART values messed up. This fixed it!
Archived
This topic is now archived and is closed to further replies.