March 11, 201610 yr unRAID OS Version: 6.1.9 Description: update-smart-drivedb is broken How to reproduce: At the command line, type: update-smart-drivedb Expected results: The command should return: /usr/share/smartmontools/drivedb.h updated from branches/RELEASE_6_2_DRIVEDB Actual results: instead it returns: /usr/share/smartmontools/drivedb.h.error: rejected by /usr/sbin/smartctl, probably no longer compatible Other information: The fix is to modify the url in line 43 of /usr/sbin/update-smart-drivedb from: SRCEXPR='http://sourceforge.net/p/smartmontools/code/HEAD/tree/$location/smartmontools/drivedb.h?format=raw' to: SRCEXPR='https://sourceforge.net/p/smartmontools/code/HEAD/tree/$location/smartmontools/drivedb.h?format=raw' (i.e. change from http to https) The corresponding bug and changeset on the smartmontools website is: https://www.smartmontools.org/ticket/659 https://www.smartmontools.org/changeset/4223 As an extension to this, it would be nice if unRAID shipped with a newer version of /usr/share/smartmontools/drivedb.h so there would be less of a reason to run the update.
March 11, 201610 yr As a work around, you can stick this in your /boot/config/go file sed -i -e '/^SRCEXPR=/s/http/https/' /usr/sbin/update-smart-drivedb
March 27, 201610 yr As a work around, you can stick this in your /boot/config/go file sed -i -e '/^SRCEXPR=/s/http/https/' /usr/sbin/update-smart-drivedb The only problem with your sed replacement command is if, in a future release of unRAID, we fix the url in update-smart-drivedb then running it will actually break the url. Same thing would happen if you ran your sed command twice or more right now, it'll generate an additional 's' each time after 'http'. A safe and future proof replacement (aka idempotent) would be to add two separate colons: sed -i -e '/^SRCEXPR=/s/http:/https:/' /usr/sbin/update-smart-drivedb
March 27, 201610 yr Nice catch. I just reread that this morning and was thinking something about the regex was bothering me.
April 1, 201610 yr What was the reply on this from LT? Are they going to run with this disabled on 6.2 or fix it as is suggested above?
April 1, 201610 yr What was the reply on this from LT? Are they going to run with this disabled on 6.2 or fix it as is suggested above? Did you see this answer? http://lime-technology.com/forum/index.php?topic=47875.msg458810#msg458810
April 1, 201610 yr What was the reply on this from LT? Are they going to run with this disabled on 6.2 or fix it as is suggested above? Did you see this answer? http://lime-technology.com/forum/index.php?topic=47875.msg458810#msg458810 Nope. Thanks for the pointer bonienl!
April 6, 201610 yr Not sure I can mark this as completely solved, but Tom indicated he would look into including the latest update with each release, and has done so in unRAID 6.2-beta21 - - Updated smartmontool drivedb.h
May 7, 201610 yr Author The beta20 thread is locked, so I'll copy the latest info here: For the time being, I have created a separate plugin, which allows to set up a update schedule for the SMART database (it will make the necessary correction in the SMART script to do a correct update). The plugin can be installed by copying and pasting the URL below into the plugin manager. https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.smart.drivedb.plg Configuration of the plugin is under Settings -> Scheduler -> SMART DriveDB (by default no schedule is active) Thanks for this bonienl! I haven't installed it yet, but I looked at the code and I have a request - after the install fixes the update-smart-drivedb script, can it go ahead and run the script one time rather than wait for the cron job? That would let me remove it from my go script altogether. Thanks!
May 8, 201610 yr The beta20 thread is locked, so I'll copy the latest info here: For the time being, I have created a separate plugin, which allows to set up a update schedule for the SMART database (it will make the necessary correction in the SMART script to do a correct update). The plugin can be installed by copying and pasting the URL below into the plugin manager. https://raw.githubusercontent.com/bergware/dynamix/master/unRAIDv6/dynamix.smart.drivedb.plg Configuration of the plugin is under Settings -> Scheduler -> SMART DriveDB (by default no schedule is active) Thanks for this bonienl! I haven't installed it yet, but I looked at the code and I have a request - after the install fixes the update-smart-drivedb script, can it go ahead and run the script one time rather than wait for the cron job? That would let me remove it from my go script altogether. Thanks! The very latest beta will have both the latest database file and the URL correction built-in. This will let unRAID start with the proper set up, you can still use the plugin - if you want - to look for future updates.
May 8, 201610 yr Author The very latest beta will have both the latest database file and the URL correction built-in. This will let unRAID start with the proper set up, you can still use the plugin - if you want - to look for future updates. That is great, it sounds like 6.2 will be at a very good starting point. And if people want to keep the smartdb current they can use your fix, since the call to it was removed from the built-in monitor script. It seems like your fix is pretty important to 6.1.x, since the monitor script calls update-smart-drivedb repeatedly and can bring the webgui down if left unmodified: https://lime-technology.com/forum/index.php?topic=39510.msg458315#msg458315 This particular problem is hard to diagnose, so I was thinking of suggesting that the new Fix Common Problems plugin should recommend installing your fix if update-smart-drivedb contains the bad url. Or do you disagree? Just wondering why it isn't with the rest of your dynamix plugins in CA.
May 9, 201610 yr The very latest beta will have both the latest database file and the URL correction built-in. This will let unRAID start with the proper set up, you can still use the plugin - if you want - to look for future updates. That is great, it sounds like 6.2 will be at a very good starting point. And if people want to keep the smartdb current they can use your fix, since the call to it was removed from the built-in monitor script. It seems like your fix is pretty important to 6.1.x, since the monitor script calls update-smart-drivedb repeatedly and can bring the webgui down if left unmodified: https://lime-technology.com/forum/index.php?topic=39510.msg458315#msg458315 This particular problem is hard to diagnose, so I was thinking of suggesting that the new Fix Common Problems plugin should recommend installing your fix if update-smart-drivedb contains the bad url. Or do you disagree? Just wondering why it isn't with the rest of your dynamix plugins in CA. The plugin was written as a quick and dirty workaround, perhaps I should give it more formal status. In my opinion the better approach for unRAID 6.1 is to get it corrected in unRAID itself instead of relying on a 3rd party plugin.
May 10, 201610 yr The very latest beta will have both the latest database file and the URL correction built-in. This will let unRAID start with the proper set up, you can still use the plugin - if you want - to look for future updates. That is great, it sounds like 6.2 will be at a very good starting point. And if people want to keep the smartdb current they can use your fix, since the call to it was removed from the built-in monitor script. It seems like your fix is pretty important to 6.1.x, since the monitor script calls update-smart-drivedb repeatedly and can bring the webgui down if left unmodified: https://lime-technology.com/forum/index.php?topic=39510.msg458315#msg458315 This particular problem is hard to diagnose, so I was thinking of suggesting that the new Fix Common Problems plugin should recommend installing your fix if update-smart-drivedb contains the bad url. Or do you disagree? Just wondering why it isn't with the rest of your dynamix plugins in CA. The plugin was written as a quick and dirty workaround, perhaps I should give it more formal status. In my opinion the better approach for unRAID 6.1 is to get it corrected in unRAID itself instead of relying on a 3rd party plugin. Just an FYI, tomorrow's? update to fix common problems is going to flag blacklisted plugins as an error (doesn't affect this one), and issue warnings for plugins not known to CA (this would fall under that) Only way to really easily flag all of the v6.0 only plugins out there that may still be installed on various servers (and shouldn't be), as all plugins within CA are 6.1 compatible, and this is the only plg I'm aware of in the forums that is 6.1 and not within CA (except for WIP plugins)
June 11, 201610 yr Author Current status: 6.2b22 includes the following fixes to resolve this: an updated version of smartmontools, which fixes the bad url in update-smart-drivedb drivedb.h is current update-smart-drivedb is no longer called by the monitor script The only potential remaining issue that is that eventually drivedb.h will get stale. To resolve, users can manually run update-smart-drivedb, or use bonienl's plugin (if that sticks around) For 6.1.9, you can either add the "sed" command listed above to your go file, or you can install bonienl's plugin If there is ever a 6.1.10 relese, it would be nice if it shipped with a good url in update-smart-drivedb and a current drivedb.h file.
Archived
This topic is now archived and is closed to further replies.