[GH-ISSUE #241] No drive found and "bad substitution" errors #88

Closed
opened 2026-03-07 19:15:19 +03:00 by kerem · 4 comments
Owner

Originally created by @ev1lm0nk3y on GitHub (Feb 10, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/241

Using the 3.4 release:

$ sudo -s /syno_hdd_db.sh -snr
Password:
/volume1/homes/ryan/Synology_HDD_db-3.4.84/syno_hdd_db.sh: line 105: ${1,,}: bad substitution
Synology_HDD_db v3.4.84
DS923+ DSM 7.2.1-69057-3
/volume1/homes/ryan/Synology_HDD_db-3.4.84/syno_hdd_db.sh: line 166: ${model,,}: bad substitution
StorageManager 1.0.0-0017

Using options: -snr
Running from: /volume1/homes/ryan/Synology_HDD_db-3.4.84/syno_hdd_db.sh
/volume1/homes/ryan/Synology_HDD_db-3.4.84/syno_hdd_db.sh: line 659: ${vid,,}: bad substitution
/volume1/homes/ryan/Synology_HDD_db-3.4.84/syno_hdd_db.sh: line 592: ${1,,}: bad substitution

ERROR No drives found!
bebop% /usr/bin/env bash --version
GNU bash, version 3.2.54(1)-release (i686-pc-linux-gnu)
Copyright (C) 2007 Free Software Foundation, Inc.

===

M2 Drive is a WD Red SN700 1000GB and I didn't see that listed in the vendor list so I discovered the vendor id "1b96" and edited the file, but still no luck. The drive can't be used as a write cache at all, so it is kinda useless, decent for video playback i suppose

Originally created by @ev1lm0nk3y on GitHub (Feb 10, 2024). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/241 Using the 3.4 release: $ sudo -s <path to script>/syno_hdd_db.sh -snr Password: /volume1/homes/ryan/Synology_HDD_db-3.4.84/syno_hdd_db.sh: line 105: ${1,,}: bad substitution Synology_HDD_db v3.4.84 DS923+ DSM 7.2.1-69057-3 /volume1/homes/ryan/Synology_HDD_db-3.4.84/syno_hdd_db.sh: line 166: ${model,,}: bad substitution StorageManager 1.0.0-0017 Using options: -snr Running from: /volume1/homes/ryan/Synology_HDD_db-3.4.84/syno_hdd_db.sh /volume1/homes/ryan/Synology_HDD_db-3.4.84/syno_hdd_db.sh: line 659: ${vid,,}: bad substitution /volume1/homes/ryan/Synology_HDD_db-3.4.84/syno_hdd_db.sh: line 592: ${1,,}: bad substitution ERROR No drives found! bebop% /usr/bin/env bash --version GNU bash, version 3.2.54(1)-release (i686-pc-linux-gnu) Copyright (C) 2007 Free Software Foundation, Inc. === M2 Drive is a WD Red SN700 1000GB and I didn't see that listed in the vendor list so I discovered the vendor id "1b96" and edited the file, but still no luck. The drive can't be used as a write cache at all, so it is kinda useless, decent for video playback i suppose
kerem closed this issue 2026-03-07 19:15:19 +03:00
Author
Owner

@007revad commented on GitHub (Feb 12, 2024):

The script needs to be located on the Synology. Not on your computer.

DSM 7.2.1 has GNU bash, version 4.4.23(1)-release (x86_64-pc-linux-gnu).

I'm not sure what device bebop is or why it has bash version 3.2.54 but I'm assuming bebop is a computer?

<!-- gh-comment-id:1939736624 --> @007revad commented on GitHub (Feb 12, 2024): The script needs to be located on the Synology. Not on your computer. DSM 7.2.1 has GNU bash, version 4.4.23(1)-release (x86_64-pc-linux-gnu). I'm not sure what device bebop is or why it has bash version 3.2.54 but I'm assuming bebop is a computer?
Author
Owner

@007revad commented on GitHub (Feb 12, 2024):

The brands listed in the vendor list are brands that DSM does not already have in it's vendor id list. DSM already includes vendor id "1b96" as Sandisk.

<!-- gh-comment-id:1939742453 --> @007revad commented on GitHub (Feb 12, 2024): The brands listed in the vendor list are brands that DSM does not already have in it's vendor id list. DSM already includes vendor id "1b96" as Sandisk.
Author
Owner

@ev1lm0nk3y commented on GitHub (Feb 13, 2024):

Sure, but it can only be used as a read-only cache and I would like to make
it into a RW cache. I thought that this would help me get that done. If
not, then I'll keep looking

On Mon, Feb 12, 2024 at 2:53 PM Dave Russell @.***>
wrote:

The brands listed in the vendor list are brands that DSM does not already
have in it's vendor id list. DSM already includes vendor id "1b96" as
Sandisk.


Reply to this email directly, view it on GitHub
https://github.com/007revad/Synology_HDD_db/issues/241#issuecomment-1939742453,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABKXAAGNNEW7TU3IA6EGRFLYTKMM7AVCNFSM6AAAAABDCVIR2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZZG42DENBVGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

<!-- gh-comment-id:1940362222 --> @ev1lm0nk3y commented on GitHub (Feb 13, 2024): Sure, but it can only be used as a read-only cache and I would like to make it into a RW cache. I thought that this would help me get that done. If not, then I'll keep looking On Mon, Feb 12, 2024 at 2:53 PM Dave Russell ***@***.***> wrote: > The brands listed in the vendor list are brands that DSM does not already > have in it's vendor id list. DSM already includes vendor id "1b96" as > Sandisk. > > — > Reply to this email directly, view it on GitHub > <https://github.com/007revad/Synology_HDD_db/issues/241#issuecomment-1939742453>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABKXAAGNNEW7TU3IA6EGRFLYTKMM7AVCNFSM6AAAAABDCVIR2CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZZG42DENBVGM> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Author
Owner

@007revad commented on GitHub (Feb 13, 2024):

You need 2 identical NVMe drives to be able to create a read/write cache.

And you don't need this script to be able to do that.

<!-- gh-comment-id:1940372020 --> @007revad commented on GitHub (Feb 13, 2024): You need 2 identical NVMe drives to be able to create a read/write cache. And you don't need this script to be able to do that.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/Synology_HDD_db#88
No description provided.