starred/Synology_M2_volume

Fork 0

mirror of https://github.com/007revad/Synology_M2_volume.git synced 2026-04-25 15:56:06 +03:00

[GH-ISSUE #181] Volume gets degraded after 24 hours #43

New issue

Closed

opened 2026-03-07 19:19:51 +03:00 by kerem · 2 comments

kerem commented

2026-03-07 19:19:51 +03:00

Owner

Originally created by @lucidlemon on GitHub (Dec 6, 2024).
Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/181

Hi there, i created a volume as described in the documentation, used SHR1 as raid mode.

My volume got degraded after just 4 hours, telling me one of the SSDs has failed, i ordered a new one, put that one in, repaired the volume after running the hdd script, it repaired, after one night it told me again that it is degraded.

Reason: One of those drives reports as "Drive Status: Critical" in the storage manager.

Is there something wrong with my synology or is that kinda normal behaviour?

Synology DS 920+
DSM 7.2.2-72806 Update 2
20gb RAM

Smart data tells me both SSDs are working fine:

sudo nvme smart-log /dev/nvme0
Smart Log for NVME device:nvme0 namespace-id:ffffffff
critical_warning                    : 0
temperature                         : 25 C
available_spare                     : 100%
available_spare_threshold           : 5%
percentage_used                     : 0%
data_units_read                     : 1,542
data_units_written                  : 152,723
host_read_commands                  : 45,332
host_write_commands                 : 826,921
controller_busy_time                : 2
power_cycles                        : 1
power_on_hours                      : 16
unsafe_shutdowns                    : 0
media_errors                        : 0
num_err_log_entries                 : 0
Warning Temperature Time            : 0
Critical Composite Temperature Time : 0
Temperature Sensor 1                : 25 C
Temperature Sensor 2                : 0 C
Temperature Sensor 3                : 0 C
Temperature Sensor 4                : 0 C
Temperature Sensor 5                : 0 C
Temperature Sensor 6                : 0 C
Temperature Sensor 7                : 0 C
Temperature Sensor 8                : 0 C

nvme smart-log /dev/nvme1
Smart Log for NVME device:nvme1 namespace-id:ffffffff
critical_warning                    : 0
temperature                         : 26 C
available_spare                     : 100%
available_spare_threshold           : 5%
percentage_used                     : 23%
data_units_read                     : 22,568,076
data_units_written                  : 99,160,041
host_read_commands                  : 495,945,576
host_write_commands                 : 3,030,234,315
controller_busy_time                : 7,186
power_cycles                        : 11
power_on_hours                      : 2,594
unsafe_shutdowns                    : 3
media_errors                        : 0
num_err_log_entries                 : 13
Warning Temperature Time            : 0
Critical Composite Temperature Time : 0
Temperature Sensor 1                : 26 C
Temperature Sensor 2                : 30 C
Temperature Sensor 3                : 0 C
Temperature Sensor 4                : 0 C
Temperature Sensor 5                : 0 C
Temperature Sensor 6                : 0 C
Temperature Sensor 7                : 0 C
Temperature Sensor 8                : 26 C

Originally created by @lucidlemon on GitHub (Dec 6, 2024). Original GitHub issue: https://github.com/007revad/Synology_M2_volume/issues/181 Hi there, i created a volume as described in the documentation, used SHR1 as raid mode. My volume got degraded after just 4 hours, telling me one of the SSDs has failed, i ordered a new one, put that one in, repaired the volume after running the hdd script, it repaired, after one night it told me again that it is degraded. Reason: One of those drives reports as "Drive Status: Critical" in the storage manager. Is there something wrong with my synology or is that kinda normal behaviour? Synology DS 920+ DSM 7.2.2-72806 Update 2 20gb RAM Smart data tells me both SSDs are working fine: ``` sudo nvme smart-log /dev/nvme0 Smart Log for NVME device:nvme0 namespace-id:ffffffff critical_warning : 0 temperature : 25 C available_spare : 100% available_spare_threshold : 5% percentage_used : 0% data_units_read : 1,542 data_units_written : 152,723 host_read_commands : 45,332 host_write_commands : 826,921 controller_busy_time : 2 power_cycles : 1 power_on_hours : 16 unsafe_shutdowns : 0 media_errors : 0 num_err_log_entries : 0 Warning Temperature Time : 0 Critical Composite Temperature Time : 0 Temperature Sensor 1 : 25 C Temperature Sensor 2 : 0 C Temperature Sensor 3 : 0 C Temperature Sensor 4 : 0 C Temperature Sensor 5 : 0 C Temperature Sensor 6 : 0 C Temperature Sensor 7 : 0 C Temperature Sensor 8 : 0 C ``` ``` nvme smart-log /dev/nvme1 Smart Log for NVME device:nvme1 namespace-id:ffffffff critical_warning : 0 temperature : 26 C available_spare : 100% available_spare_threshold : 5% percentage_used : 23% data_units_read : 22,568,076 data_units_written : 99,160,041 host_read_commands : 495,945,576 host_write_commands : 3,030,234,315 controller_busy_time : 7,186 power_cycles : 11 power_on_hours : 2,594 unsafe_shutdowns : 3 media_errors : 0 num_err_log_entries : 13 Warning Temperature Time : 0 Critical Composite Temperature Time : 0 Temperature Sensor 1 : 26 C Temperature Sensor 2 : 30 C Temperature Sensor 3 : 0 C Temperature Sensor 4 : 0 C Temperature Sensor 5 : 0 C Temperature Sensor 6 : 0 C Temperature Sensor 7 : 0 C Temperature Sensor 8 : 26 C ```

kerem closed this issue

2026-03-07 19:19:51 +03:00

kerem commented

2026-03-07 19:19:52 +03:00

Author

Owner

@007revad commented on GitHub (Dec 6, 2024):

What brand of NVMe drives are they?

A few people had similar issues with certain brands. Usually Chinese brands and Crucial if I remember correctly (which is strange because Crucial Memory is good).

@007revad commented on GitHub (Dec 6, 2024): What brand of NVMe drives are they? A few people had similar issues with certain brands. Usually Chinese brands and Crucial if I remember correctly (which is strange because Crucial Memory is good).

kerem commented

2026-03-07 19:19:52 +03:00

Author

Owner

@007revad commented on GitHub (Dec 6, 2024):

FYI With a DS920+ running DSM 7.2 or later you don't need this script.

Use https://github.com/007revad/Synology_HDD_db instead.

@007revad commented on GitHub (Dec 6, 2024): FYI With a DS920+ running DSM 7.2 or later you don't need this script. Use https://github.com/007revad/Synology_HDD_db instead.

kerem referenced this issue

2026-03-12 17:59:38 +03:00

[GH-ISSUE #43] Need to update M2 script when storage pool already created? #204

No labels

bug

pull-request

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_M2_volume#43

No description provided.

Rows
Columns