starred/Synology_HDD_db

Fork 0

mirror of https://github.com/007revad/Synology_HDD_db.git synced 2026-04-25 13:45:59 +03:00

[GH-ISSUE #303] When you are in an all-SSD environment, you may find an HDD error #106

New issue

Closed

opened 2026-03-07 19:15:38 +03:00 by kerem · 5 comments

kerem commented

2026-03-07 19:15:38 +03:00

Owner

Originally created by @proxy2008 on GitHub (Jun 12, 2024).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/303

By blocking the code below, it works fine

# Check hdds array isn't empty
if [[ ${#hdds[@]} -eq "0" ]]; then
    ding
    echo -e "\n${Error}ERROR${Off} No drives found!" && exit 2
else
    echo -e "\nHDD/SSD models found: ${#hdds[@]}"
    num="0"
    while [[ $num -lt "${#hdds[@]}" ]]; do
        echo "${hdds[num]}"
        num=$((num +1))
    done
    echo
fi

I guess if this can be controlled by adding a parameter

Originally created by @proxy2008 on GitHub (Jun 12, 2024). Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/303 By blocking the code below, it works fine ``` # Check hdds array isn't empty if [[ ${#hdds[@]} -eq "0" ]]; then ding echo -e "\n${Error}ERROR${Off} No drives found!" && exit 2 else echo -e "\nHDD/SSD models found: ${#hdds[@]}" num="0" while [[ $num -lt "${#hdds[@]}" ]]; do echo "${hdds[num]}" num=$((num +1)) done echo fi ``` I guess if this can be controlled by adding a parameter

kerem closed this issue

2026-03-07 19:15:38 +03:00

kerem commented

2026-03-07 19:15:39 +03:00

Author

Owner

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

Which Synology NAS model? And which DSM version?

Are they SATA or SAS SSDs?

@007revad commented on GitHub (Jun 12, 2024): Which Synology NAS model? And which DSM version? Are they SATA or SAS SSDs?

kerem commented

2026-03-07 19:15:39 +03:00

Author

Owner

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

I'm not seeing the issue in a NAS with just SATA SSDs and NVMes.

Are you using just NVMe drives?

@007revad commented on GitHub (Jun 12, 2024): I'm not seeing the issue in a NAS with just SATA SSDs and NVMes. Are you using just NVMe drives?

kerem commented

2026-03-07 19:15:39 +03:00

Author

Owner

@proxy2008 commented on GitHub (Jun 13, 2024):

I'm not seeing the issue in a NAS with just SATA SSDs and NVMes.

Are you using just NVMe drives?

Yes, it is possible to emulate all NVMe drives on the SA6400 machine to deploy the Synology system

@proxy2008 commented on GitHub (Jun 13, 2024): > I'm not seeing the issue in a NAS with just SATA SSDs and NVMes. > > Are you using just NVMe drives? Yes, it is possible to emulate all NVMe drives on the SA6400 machine to deploy the Synology system ![image](https://github.com/007revad/Synology_HDD_db/assets/7359075/a04a1b85-2871-427c-a6d2-cd391d9dc662) ![image](https://github.com/007revad/Synology_HDD_db/assets/7359075/db91bc47-1cfb-482b-8eae-428379fb7dc7)

kerem commented

2026-03-07 19:15:39 +03:00

Author

Owner

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

Do you want to try this new release https://github.com/007revad/Synology_HDD_db/releases/tag/v3.5.91

commit c43662d

@007revad commented on GitHub (Jun 13, 2024): Do you want to try this new release https://github.com/007revad/Synology_HDD_db/releases/tag/v3.5.91 [commit c43662d](https://github.com/007revad/Synology_HDD_db/commit/c43662d)

kerem commented

2026-03-07 19:15:39 +03:00

Author

Owner

@proxy2008 commented on GitHub (Jun 14, 2024):

Thank you for providing such an important and useful tool, and I will use it when reworking the system.

@proxy2008 commented on GitHub (Jun 14, 2024): Thank you for providing such an important and useful tool, and I will use it when reworking the system.

kerem referenced this issue

2026-03-07 19:17:32 +03:00

[PR #123] [MERGED] Develop #277

kerem referenced this issue

2026-03-11 11:51:53 +03:00

[GH-ISSUE #106] Routine of RAM size evaluation not sufficient and might cause issues #542

kerem referenced this issue

2026-03-11 11:52:09 +03:00

[GH-ISSUE #107] Calculation of mixed units will fail in RAM total size #541

kerem referenced this issue

2026-03-12 16:30:58 +03:00

[GH-ISSUE #106] Routine of RAM size evaluation not sufficient and might cause issues #751