After update from 6.9.6-1 to -2: SMART stopped working w error

Hi, I'm a newby on OMV and started 14 days ago with a Raspi4b + Samsung SSD 840EVO in an external sata/usb case (JMicron chip).

Before the update today to the most recent version everything was fine.

After the update to 6.9.6-2 S.M.A.R.T stopped working.

syslog shows the following error:

Nov  3 15:11:31 omv omv-engined[46651]: /dev/sda: Unknown USB bridge [0x152d:0x0580 (0x201)]
Nov  3 15:11:31 omv omv-engined[46651]: Please specify device type with the -d option.
Nov  3 15:11:31 omv omv-engined[46651]: 
Nov  3 15:11:31 omv omv-engined[46651]: Use smartctl -h to get a usage summary
Nov  3 15:11:31 omv omv-engined[46651]:  (file=/usr/share/php/openmediavault/system/storage/smartinformation.inc, line=138)

I started smartctl manually with -d sat:

sudo smartctl -a -d sat /dev/sda

This works perfectly. But I don't know how to proceed ... and where to insert this -d option in the omv or smartmontools-configuration

Could anybody help me to solve this issue?

KR

Juergen

many thanks. I will try to open the ticket at smartmon tools.

Quote from votdev

There is a section in their FAQ how to submit a request easily.

Thanx. I read through the FAQ and tried the first command:

smartctl -t short /dev/sda

I've got the error message straight away:

/dev/sda: Unknown USB bridge [0x152d:0x0580 (0x201)]
Nov 3 15:11:31 omv omv-engined[46651]: Please specify device type with the -d option.

So the problem is not with my Samsung 840 Evo SSD (which is included in smarttools-db) but with the USB Controler (JMicro) I suppose.

So I'm not able to create the report-file they are asking for in the faq.

Nevertheless: I opened a ticket and waiting for a reply.

I could not really wait and read a little bit more in the FAQ:

Could missing drive database entries be added locally?

Yes. Create a separate local drive database file with the desired entries. The entries in this file prepend and may override the entries in the installed or builtin database. The default path of the local drive database is usually /etc/smart_drivedb.h. On Windows, it is drivedb-add.h in the directory where smartctl.exe is installed. See -B [+]FILE, --drivedb=[+]FILE section on smartctl man page for the configured default path and further info. The default path is also included in the smartctl -h output.

So, I did "smartctl -h", searched for the -B option, found the standard path

"/var/lib/smartmontools/drivedb/drivedb.h"

and added the following at the end:

// Graugear

{ "USB: Graugear SATA enclosure ; ", // USB 3.0

"0x152d:0x0580",

"", // 0x0201

"",

"-d sat"

},

I could not believe it, but SMART was working again ! Cannot say how long (maybe until the next update), but we will see.

Quote from votdev

You should set the environment variable OMV_CRON_WEEKLY_UPDATE_SMART_DRIVEDB_ENABLED to no.

Thanks for this.

In the meantime I created the local config file /etc/smart_drivedb.h and made the entry there. According to the help documentation this should not be overwritten.

So I'll wait for the next automatic update from omv and see what will happen.

In case of deletion I'll set the environment variable.

Quick status update:

This morning at around 7am the scheduled update of the smartmontools drivedb was done by omv.

/var/lib/smartmontools/drivedb/drivedb.h

was updated and my manually added device disappeared as expected.

Nevertheless SMART ist still working on my device.

So, I'm convinced now that my local entry in

/etc/smart_drivedb.h

is really working as expected and adding the entries made inside to the global db automatically.

Good news for people who quickly have to add local devices to smartctl.

But anybody else should check this again to be 100% sure before communicating to a broader base.

To finally document: Issue is solved by creating a local drivedb.h file like stated in

FAQ – smartmontools

Could missing drive database entries be added locally?

Yes. Create a separate local drive database file with the desired entries. The entries in this file prepend and may override the entries in the installed or builtin database. The default path of the local drive database is usually /etc/smart_drivedb.h. On Windows, it is drivedb-add.h in the directory where smartctl.exe is installed. See -B [+]FILE, --drivedb=[+]FILE section on smartctl man page for the configured default path and further info. The default path is also included in the smartctl -h output.

Ticket with smartmontools still open and in progress.

Quote from jata1

Hi All. I have the exact same issue with the same USB bridge ID - see below

Code

[0x152d:0x0580 (0x7601)]

Do I need to also raise a ticket or is this covered as a ticket has already been raised for the device/controller?

What additional info do I need to fix this locally?

Can someone help me get all the details I need as I'm not sure all of the USB enclosure/controller details...

Display More

I can't follow you. Everything is in this thread. Especially in #10 and #15.

Create /etc/smart_drivedb.h (sudo nano /etc/smart_drivedb.h) with the following content (do copy and paste):

// Your device - just a comment for your yourself
{ "USB: SATA enclosure ; ",       // USB 3.0
"0x152d:0x0580",
"", // 0x0201
"",
"-d sat"
},

Don''t forget to save. Thats it. You don't have to open another ticket at smartmontools..