Partially working - One drive still unsupported

Question

Partially working - One drive still unsupported

b-col opened this issue 9 months ago · comments

Hello,

I am running this script on a DS920+ running DSM 7.2-64570 Update 1. After running with -nr and rebooting, I see one of my drives is now supported, while the other still has the firmware warning message.

Before:
https://i.imgur.com/jdCYAW3.png

After:
https://i.imgur.com/SIkkoTx.png

I should mention that I have also ran your Synology_enable_M2_volume script.

Dave Russell · Answer 1 · Fri Nov 17 2023 14:16:04 GMT+0800 (China Standard Time)

What do the following commands return?

echo "'$(cat /sys/block/nvme0n1/device/model)'"

echo "'$(cat /sys/block/nvme0n1/device/firmware_rev)'"

echo "'$(cat /sys/block/nvme0n1/device/rev)'"

echo "'$(cat /sys/block/nvme1n1/device/model)'"

echo "'$(cat /sys/block/nvme1n1/device/firmware_rev)'"

echo "'$(cat /sys/block/nvme1n1/device/rev)'"

Dave Russell · Answer 2 · Fri Nov 17 2023 14:30:42 GMT+0800 (China Standard Time)

And these commands:

synonvme --vendor-get /dev/nvme0

synonvme --model-get /dev/nvme0

synonvme --sn-fr-get /dev/nvme0

synonvme --vendor-get /dev/nvme1

synonvme --model-get /dev/nvme1

synonvme --sn-fr-get /dev/nvme1

bcollins · Answer 3 · Fri Nov 17 2023 21:14:29 GMT+0800 (China Standard Time)

Here you go!

https://i.imgur.com/lBtC1SP.png

Dave Russell · Answer 4 · Sat Nov 18 2023 04:39:36 GMT+0800 (China Standard Time)

Sorry. Those last 6 commands should have included sudo.

sudo synonvme --vendor-get /dev/nvme0

sudo synonvme --model-get /dev/nvme0

sudo synonvme --sn-fr-get /dev/nvme0

sudo synonvme --vendor-get /dev/nvme1

sudo synonvme --model-get /dev/nvme1

sudo synonvme --sn-fr-get /dev/nvme1

bcollins · Answer 5 · Sat Nov 18 2023 06:00:33 GMT+0800 (China Standard Time)

Thanks, much better results this time 👍
https://i.imgur.com/EgBS9Lw.png

Dave Russell · Answer 6 · Sat Nov 18 2023 08:20:15 GMT+0800 (China Standard Time)

The model and firmware version look okay.

Can you tell me what this command returns:

jq . /var/lib/disk-compatibility/ds920+_host_v7.db | grep -A 21 Lexar

bcollins · Answer 7 · Sat Nov 18 2023 08:23:36 GMT+0800 (China Standard Time)

https://i.imgur.com/XRe5tQ6.png

Dave Russell · Answer 8 · Sat Nov 18 2023 11:14:00 GMT+0800 (China Standard Time)

It looks like DSM is not checking the drive database for drives that don't return the vendor.

I've had a couple of people report the same issue, but they were using some Chinese brand NVMe drives they bought cheap off Alibaba. When they tried known brand NVMe drives everything worked as it should.

One last thing I can think of testing is to see if this is something new in DSM 7.2-64570 Update 1

Do you want to do the following:

Download this zip file to your home folder on your Synology. 64570_synonvme.zip
Unzip the downloaded file so that synonvme is in your home folder.
Then in SSH check you're in your home folder:
echo "$PWD"
That should return /var/services/homes/b-col (or whatever your username is)
Set the correct permissions on the downloaded synonvme:
chmod 755 $HOME/synonvme
Run the following command to see if it returns the vendor for the Lexar NVMe drive:
sudo $HOME/synonvme --vendor-get /dev/nvme0

bcollins · Answer 9 · Sun Nov 19 2023 05:54:27 GMT+0800 (China Standard Time)

In fairness, Lexar are essentially in that same bracket given they're now owned by Longsys.

I've ran through those steps and am still getting the "Fail to get disk vender" error 😞

I'd guess not, but are there any options around manually setting the drive vendor?

Dave Russell · Answer 10 · Sun Nov 19 2023 07:02:33 GMT+0800 (China Standard Time)

There is a pci_vendor_ids.conf file that contains a list of hex vendor ids and the vendor name. Maybe adding Lexar to it will work.
We know the vendor name is Lexar so we just need to get the vendor id.

What do the following commands return:

sudo nvme id-ctrl /dev/nvme0 | grep NVME -A 5

sudo nvme id-ctrl /dev/nvme0 | grep -E ^vid | awk '{print $NF}'

bcollins · Answer 11 · Sun Nov 19 2023 07:21:52 GMT+0800 (China Standard Time)

https://i.imgur.com/IFpw9x4.png

Dave Russell · Answer 12 · Sun Nov 19 2023 07:30:54 GMT+0800 (China Standard Time)

Excellent.

Try the following:

sudo synosetkeyvalue /usr/syno/etc.defaults/pci_vendor_ids.conf 0x1d97 "Lexar Media"

If you already have storage manager open, close it and reopen it. Then check if storage manager is showing Lexar Media for the Lexar NVMe drive. If not reboot then check again.

bcollins · Answer 13 · Sun Nov 19 2023 08:21:18 GMT+0800 (China Standard Time)

That's got the correct vendor name showing in storage manager after a reboot 😄
https://i.imgur.com/6lh83Lk.png

I can also see it when rerunning the previous commands you listed:
https://i.imgur.com/aSD4Iz0.png

I tried rerunning the original hdd script and rebooting, however I still see the firmware error - Not sure if I jumped the gun here though.

Dave Russell · Answer 14 · Sun Nov 19 2023 08:50:27 GMT+0800 (China Standard Time)

It's great those changes made the vendor appear as it should. But it's disappointing that it's still showing the firmware error.

Try running syno_hdd_db.sh with -nrf

bcollins · Answer 15 · Sun Nov 19 2023 09:03:29 GMT+0800 (China Standard Time)

Same behaviour, unfortunately.

Dave Russell · Answer 16 · Mon Nov 20 2023 05:28:55 GMT+0800 (China Standard Time)

Maybe try running the Synology_enable_M2_volume script with the --restore option, then reboot.

Dave Russell · Answer 17 · Mon Nov 20 2023 05:34:37 GMT+0800 (China Standard Time)

I just found another pci_vendor_ids.conf file.

Try this command:

sudo synosetkeyvalue /usr/syno/etc/pci_vendor_ids.conf 0x1d97 "Lexar Media"

bcollins · Answer 18 · Mon Nov 20 2023 07:02:01 GMT+0800 (China Standard Time)

Okay, so some good progress.

I first ran your latest command to modify the pci_vendor_ids.conf file, rebooted, then reran the HDD script, but still had the issue.

Running the Synology_enable_M2_volume script with the --restore option, then rebooting with the HDD script set to run at boot has cleared the warning message 🎉

With that in mind, is there any need to run the Synology_enable_M2_volume script given I am still able to use the drives for storage right now?

Additionally, is there any harm in adding the two conf file commands to my boot script or is this unnecessary?

Dave Russell · Answer 19 · Mon Nov 20 2023 07:41:21 GMT+0800 (China Standard Time)

The Synology_HDD_db script is the only one I use.

Since I updated Synology_HDD_db to enable creating volumes in storage manager with non-Synology NVMe drives I don't run the Synology_enable_M2_volume script anymore.

You'd only need to run those commands again after a DSM update.

I'm updating the Synology_HDD_db script to detect "unknown" NVMe drives and automatically run those commands. So far I've got a list of 9 vendors that aren't in the pci_vendor_ids.conf files.

0x10ec TEAMGROUP
0x1987 Phison 
0x1c5c "SK Hynix" 
0x1cc4 UMIS 
0x1d97 SPCC/Lexar
0x1dbe ADATA 
0x1e49 ZHITAI 
0x1e4b HS/MAXIO
0x1f40 Netac

I also need to make up a vendor name for "unknown" NVMe drives that aren't in the script. I was thinking maybe "Contact 007revad" or just "007revad" or "el cheapo" 😄

bcollins · Answer 20 · Mon Nov 20 2023 19:25:11 GMT+0800 (China Standard Time)

Ah okay, I wasn't aware the volume features were added to the HDD script so that makes sense.

Really appreciate your help with this (especially over a weekend) 😄