- Joined
- Feb 15, 2014
- Messages
- 20,194
Original message is below.
UPDATE:
This problem seems to affect older versions as well, to some extent, at least after a rollback is performed. Confirmed in 201505040117.
WHAT IS GOING ON?
FreeNAS is generating a smartd.conf file that has longer lines than smartd will accept (maximum 256 characters per line).
Line length is influenced by the email address (directly) and the specific settings. Each selected day/hour/whatever adds a few characters.
smartd.conf can be found under /usr/local/etc#
WORKAROUND:
This workaround has been confirmed to work on both 201505040117 and 201505100553.
Removing some days from the SMART short test schedule results in shorter lines, which are then correctly parsed by smartd. SMART long tests shouldn't be run with enough frequency for this to be a problem.
Long email addresses may also cause this issue - the only workaround in that case is to use a shorter one.
Bug is being tracked here.
Original message follows:
Background info:
Updated to 9.3 201505040117 [henceforth 0504] two days ago, no issues.
Today, after updating to 9.3 201505100553 [henceforth 0510], smartd refuses to start. Yellow warning, manual service restart doesn't work.
Troubleshooting steps:
Apparently, some changes to smartd were Ready For Release a few days ago, including the addition of the warning if smartd doesn't restart and, if I understand correctly, some sort of automatic addition of disks to the testing schedule (for disk replacements and stuff).
These changes are still marked as Staged, but the status has been outdated on other issues before when they were Ready For Release, so it seems possible that these did in fact make it into 0510 and contain a bug.
I'd like to ask if anyone has anything to add before I file a bug report.
For completeness' sake, hardware specs:
UPDATE:
This problem seems to affect older versions as well, to some extent, at least after a rollback is performed. Confirmed in 201505040117.
WHAT IS GOING ON?
FreeNAS is generating a smartd.conf file that has longer lines than smartd will accept (maximum 256 characters per line).
Line length is influenced by the email address (directly) and the specific settings. Each selected day/hour/whatever adds a few characters.
smartd.conf can be found under /usr/local/etc#
WORKAROUND:
This workaround has been confirmed to work on both 201505040117 and 201505100553.
Removing some days from the SMART short test schedule results in shorter lines, which are then correctly parsed by smartd. SMART long tests shouldn't be run with enough frequency for this to be a problem.
Long email addresses may also cause this issue - the only workaround in that case is to use a shorter one.
Bug is being tracked here.
Original message follows:
Background info:
Updated to 9.3 201505040117 [henceforth 0504] two days ago, no issues.
Today, after updating to 9.3 201505100553 [henceforth 0510], smartd refuses to start. Yellow warning, manual service restart doesn't work.
Troubleshooting steps:
- Reboot. No change.
- Checked smartctl output for all drives. All drives have SMART enabled and show nothing unusual in their logs.
- Rolled back to 0504, smartd is working as expected, as far as I can tell.
Apparently, some changes to smartd were Ready For Release a few days ago, including the addition of the warning if smartd doesn't restart and, if I understand correctly, some sort of automatic addition of disks to the testing schedule (for disk replacements and stuff).
These changes are still marked as Staged, but the status has been outdated on other issues before when they were Ready For Release, so it seems possible that these did in fact make it into 0510 and contain a bug.
I'd like to ask if anyone has anything to add before I file a bug report.
For completeness' sake, hardware specs:
Supermicro X10SLM+-F
Intel Core i3 4330
2x Crucial 1.35V 8GB UDIMMs
6x WD Red 3TB EFRX
Seasonic G-550
Intel Core i3 4330
2x Crucial 1.35V 8GB UDIMMs
6x WD Red 3TB EFRX
Seasonic G-550
Last edited:
