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

Claudio_Sergiacomo

Are are you quoting the same things again?

The ID that you needed is already there.

        ID 2109:0817 VIA Labs, Inc.

Yes I did quoted the same thing based in your message that I did in in my own post instead of answering your quote. As for the ID... it is there but I can't see the SMART data of the hard drives connected USB through PINAS and all happened when Updated OMV last monday

So still don't know what to do to get my SMART data back to OMV as it was working before the update

Zitat von Claudio_Sergiacomo

So still don't know what to do to get my SMART data back to OMV as it was working before the update

If you just read the posts since the beginning, you'll find what file to edit to fix it.

Sorry, but I'm a bit tired for "piggy-backing"

Zitat von Teschbert

So, to be honest: I don't know what you expect. Everything is written down in this thread.

Just read from the beginning for details.

In summary:

You create a file /etc/smart_drivedb.h and put the required entries in there -- the most important is this information from #41: 2109:0817

Example is in this thread.

Are you searching for somebody who execute for you?

Alles anzeigen

Not playing devil's advocate, but I was having the same problem as Claudio_Sergiacomo. I have the same "USB Hub", but on an Argon EON.

For some reason that I still don't understand, the S.MA.R.T /etc/smart_drivedb.h file cannot identify the Via Labs USB3 Hub with ID 2109:0817.

 |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 5000M
     ID 2109:0817 VIA Labs, Inc.  
     |__ Port 4: Dev 5, If 0, Class=Mass Storage, Driver=uas, 5000M
         ID 1741:1156  
     |__ Port 2: Dev 4, If 0, Class=Mass Storage, Driver=uas, 5000M
         ID 174e:1155 

I don't know if I'm using the correct terms, but as it returns two separate IDs within ID 2109:0817 (1741:1156 and 174e:1155) I had to add the following keys to be able to identify my HDDs

//My VIA Labs info
{ "USB: ; USB3 Hub", // USB3->SATA, USB-C->SATA
"0x174e:0x1155",
"", // 0x0100
"",
"-d sat"
},
{ "USB: ; USB3 Hub", // USB3->SATA, USB-C->SATA
"0x1741:0x1156",
"", // 0x0100
"",
"-d sat"
},

This way I managed to make SMART find my HDDs.

EDIT:

I think the correct command to get the information is:

udevadm info --query=all --name=/dev/sdX | grep -i -e "vendor_id" -e "model_id"
# (X being the letter referring to the storage you need to discover)

With the information from this command, the information to be placed in the file would look like this

{ "USB: ; name_of_your_hub", // Comment
"0xVENDOR_ID:0xMODEL_ID",
"",
"",
"-d sat" // Device type
},

Thanks biofx I do have the same ARGON EON enclosure.. So were you able to fix the SMART issue with those commands?

Hello,

I had the same issue after upgrading to the same version, "biofx" has the right solution :

First I has to execute the following commands :

udevadm info --query=all --name=/dev/sda | grep -i -e "vendor_id" -e "model_id"

Which show :

E: ID_USB_MODEL_ID=1155

E: ID_USB_VENDOR_ID=174e

udevadm info --query=all --name=/dev/sdb | grep -i -e "vendor_id" -e "model_id"

Which show :

E: ID_USB_MODEL_ID=1156

E: ID_USB_VENDOR_ID=1741

I also have an Argon EON so the values are the same.

Then, into the file /var/lib/smartmontools/drivedb/drivedb.h I added (remember if you are not using an Argon EON : "0xVENDOR_ID:0xMODEL_ID") :

//My VIA Labs info

{ "USB: ; USB3 Hub", // USB3->SATA, USB-C->SATA

"0x174e:0x1155",

"", // 0x0100

"",

"-d sat"

},

{ "USB: ; USB3 Hub", // USB3->SATA, USB-C->SATA

"0x1741:0x1156",

"", // 0x0100

"",

"-d sat"

},

Reboot and it works!

Thanks so much Teschbert and again biofx for the help. After learning how to change permissions on the files and directories I was able to do the drivedb.h file as well as placing the new file smart_drivedb.h. All is working perfect now... I will wait for the next update to see if the smart_drivedb.h file will avoid to have to re-enter the configuration again to see the SMART information. A side note for the users of the ARGON EON enclosure. I'm frustrated with the respberry pi fundation having changed the layout of the pi 5, so it won't work in our enclosure. Let's hope ARGON will redesign the EON for the pi 5 and improve the ventilation for better heat dissipation.

I just have updated OMV and the SMART monitoring remains working normal for both USB controllers on my system so the /etc/smart_drivedb.h does work just fine.

/etc/smart_drivedb.h

LIS Raid card added?add-on database file

Also ，I didn't find this file

Hello,

I had the same problem but with my usb stick where OMV is installed:

Created the file with this content:

{ "USB: SanDisk 3.2Gen1 ; ",
"0x0781:0x5583",
"", // 0x100
"",
"-d scsi"
},

Problem solved, thanks for such usefull informations.