Posts by biofx

Quote from 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?

Display More

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
},

Yes, it is. But I did not execute the option described in the note.

First of all, congratulations on the excellent work done at OMV.

Next, there are actually two problems:

The first is related to the subject. Every time I transfer large files or a large amount of data (something around 20GB +) from any machine (Linux or Windows) to OMV, I get an error of disconnection and I will check, then I realize that OMV has restarted.

Which brings us to my second problem, because of those unmanaged reboots the graphs in System Information -> Performance Statistics are lost. Only the data from the last Safe Restart / Shutdown is saved.

For the first problem, would anyone have an idea of what might be happening? Is there any way to check what is causing the restart? I already looked at the Message files, Systemlogs etc and I did not identify the problem.

For the second problem, without having to reboot the system safely, is there any way that data can be recorded?

OMV is installed in:

- Raspberry pi 4 - 4Gb with a GeekWorm case (X725, X729 Board and X729 Case)

- 02x 2.5 "Sata HDDs (1TB and 2TB)

- 5V 4A Power Supply (from GeekWorm)

- Raspberry pi OS booting from an USB pendrive

- OMV Version 5.5.21-1