mirror of
https://github.com/007revad/Synology_M2_volume.git
synced 2026-04-26 00:06:14 +03:00
[GH-ISSUE #162] Fail to get disk vender Lexar SSD NM620 1TB #38
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_M2_volume#38
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @burianvlastimil on GitHub (Jul 1, 2024).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/162
Hello, I have bought new Lexar NVMe drives and want to set them up as RAID1 storage.
But I received the error Fail to get disk vender Lexar SSD NM620 1TB.
Is this something I should care about or not? The process of creating the pool seems to be functioning.
However, I have doubts if I later run the https://github.com/007revad/Synology_HDD_db script, whether it will work?
Thanks and cheers.
@007revad commented on GitHub (Jul 1, 2024):
The https://github.com/007revad/Synology_HDD_db script will fix the unknown vendor issue (which causes an Unknown firmware version error in Storage Manager).
If your Synology has a Ryzen, Intel Celeron J4025 or J4125, or Realtek RTD1619B CPU you won't even need Synology_M2_Volume as after running Synology_HDD_db you will be able to create the storage pool and volume in Storage Manager.
@burianvlastimil commented on GitHub (Jul 1, 2024):
I admit, I am unsure how you mean it now. I meant after DSM upgrade, which will happen sooner or later, I am instructed by your script to run the
dbscript. Should I do it now? My NAS basic details:https://www.synology.com/en-us/products/DS923+#specs
Screens:
@burianvlastimil commented on GitHub (Jul 1, 2024):
After running your
dbscript and rebooting, it is showing HS/MAXIO --> what is that pls?@007revad commented on GitHub (Jul 22, 2024):
You can change it to Lexar with: