Murac
Dabbler
- Joined
- Mar 18, 2015
- Messages
- 46
So this is my first post to this fine forum. I've generally always been able to find answers in existing threads but this one is curious. I get errors such as these:
After every single smart test, short and long. It cycles through all the different drives over time, without fail. My first question, is where is this self-test log located in the filesystem?
A few months back when smartd was having issues during certain updates (when the reporting was being debuted?) I believe I may have caused a permission issue with the log file. At that time, i was getting some sort of error that showed a path to the log file and something else along the lines of permission denied or does not exist. So, I thought I'd try and create the file myself, however, I most likely did not set the permissions properly, and once the bugs were fixed and rolled out in an update, the faulty file i created remained and created an obstacle for the reporting. Does this make any sense?
I know the drives are all testing without errors, it's just the reading of the test logs.
This has been bugging me for months and I've finally gotten the wherewithall to ask for help. I do appreciate you taking the time to tackle this problem! Thank you!
I haven't included my system specs because I don't see how it would be relevant, but I did build according to one of those guides using the intel c2750 quad-core boards so i'm pretty certain all components are kosher. also using 6 4-tb red drives in z2. I will quickly post any new information requested, if necessary.
final note is that I see my drives get up to 53C every so often during tests, should I be incredibly concerned with these numbers?
THANK YOU!!!!
-Murac
Code:
CRITICAL: Device: /dev/ada5, Read SMART Error Log Failed CRITICAL: Device: /dev/ada5, failed to read SMART Attribute Data CRITICAL: Device: /dev/ada3, Read SMART Error Log Failed CRITICAL: Device: /dev/ada3, Read SMART Self-Test Log Failed
After every single smart test, short and long. It cycles through all the different drives over time, without fail. My first question, is where is this self-test log located in the filesystem?
A few months back when smartd was having issues during certain updates (when the reporting was being debuted?) I believe I may have caused a permission issue with the log file. At that time, i was getting some sort of error that showed a path to the log file and something else along the lines of permission denied or does not exist. So, I thought I'd try and create the file myself, however, I most likely did not set the permissions properly, and once the bugs were fixed and rolled out in an update, the faulty file i created remained and created an obstacle for the reporting. Does this make any sense?
I know the drives are all testing without errors, it's just the reading of the test logs.
This has been bugging me for months and I've finally gotten the wherewithall to ask for help. I do appreciate you taking the time to tackle this problem! Thank you!
I haven't included my system specs because I don't see how it would be relevant, but I did build according to one of those guides using the intel c2750 quad-core boards so i'm pretty certain all components are kosher. also using 6 4-tb red drives in z2. I will quickly post any new information requested, if necessary.
final note is that I see my drives get up to 53C every so often during tests, should I be incredibly concerned with these numbers?
THANK YOU!!!!
-Murac