mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #77] ERROR 6a Failed to update ds1821+_host_v7.db #532
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#532
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 @very-old-guy on GitHub (May 21, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/77
Trying to update the drive listing and I get this error message.
Synology_HDD_db v2.2.45
DS1821+ DSM 7.2-64551 RC
Using options: -nr
HDD/SSD models found: 6
CT2000BX500SSD1,061
CT2000MX500SSD1,033
WD80EFAX-68KNBN0,0A81
WD80EFAX-68LHPN0,0A83
WD80EFBX-68AZZN0,0A85
WD80EFZX-68UW8N0,0A83
M.2 drive models found: 2
KINGSTON SA2000M8/1000G,V0304B0
SA2000M8/1TB,T1103F0L
No M.2 cards found
No Expansion Units found
CT2000BX500SSD1 already exists in ds1821+_host_v7.db
CT2000MX500SSD1 already exists in ds1821+_host_v7.db
WD80EFAX-68KNBN0 already exists in ds1821+_host_v7.db
WD80EFAX-68LHPN0 already exists in ds1821+_host_v7.db
WD80EFBX-68AZZN0 already exists in ds1821+_host_v7.db
WD80EFZX-68UW8N0 already exists in ds1821+_host_v7.db
sed: -e expression #1, char 33: unknown option to `s'
ERROR 6a Failed to update ds1821+_host_v7.db
sed: -e expression #1, char 21: unknown option to `s'
ERROR 6a Failed to update ds1821+_host_v7.db
Support disk compatibility already enabled.
Support memory compatibility already disabled.
Max memory already set to 32 GB.
M.2 volume support already enabled.
Drive db auto updates already disabled.
DSM successfully checked disk compatibility.
@007revad commented on GitHub (May 23, 2023):
It looks like it's the / in the NVMe drives' model names that's causing the error.
KINGSTON SA2000M8**/1000G
SA2000M8/**1TB
They both appear to be 1TB Kingston SA2000M8 so I'm curious why their returning different model names.
I'll run some tests to reproduce the error so I can fix it.
@007revad commented on GitHub (May 23, 2023):
Can you try this version and confirm if it fixes your issue.
https://github.com/007revad/Synology_HDD_db/releases/tag/v2.2.47
@very-old-guy commented on GitHub (May 24, 2023):
Thank you. I am going to reply to this in two parts as I have been having one of the NVMe drives fail and the volume fall over. I have removed one that I think is a problem and it was added to the database ok. I will reinstall the second one and see what happens from there to see if the issue with failure was somehow related to the unrecognised drive. Here is the results from the first run. I will also update to full version of 7.2 before doing the second one.
Synology_HDD_db v2.2.47
DS1821+ DSM 7.2-64551 RC
Using options:
HDD/SSD models found: 6
CT2000BX500SSD1,061
CT2000MX500SSD1,033
WD80EFAX-68KNBN0,0A81
WD80EFAX-68LHPN0,0A83
WD80EFBX-68AZZN0,0A85
WD80EFZX-68UW8N0,0A83
M.2 drive models found: 1
SA2000M8/1TB,T1103F0L
No M.2 cards found
No Expansion Units found
CT2000BX500SSD1 already exists in ds1821+_host_v7.db
CT2000MX500SSD1 already exists in ds1821+_host_v7.db
WD80EFAX-68KNBN0 already exists in ds1821+_host_v7.db
WD80EFAX-68LHPN0 already exists in ds1821+_host_v7.db
WD80EFBX-68AZZN0 already exists in ds1821+_host_v7.db
WD80EFZX-68UW8N0 already exists in ds1821+_host_v7.db
Added SA2000M8/1TB to ds1821+_host_v7.db
Support disk compatibility already enabled.
Support memory compatibility already enabled.
M.2 volume support already enabled.
Drive db auto updates already enabled.
DSM successfully checked disk compatibility.
You may need to reboot the Synology to see the changes.
@very-old-guy commented on GitHub (May 24, 2023):
HI,
Found and successfully added the second drive. Unfortunately did not fix my failure issue. Thank you for your assistance.