DSM 7.1 DSM7.1 introduces new drive vendor-locking parameters

Currently reading
DSM 7.1 DSM7.1 introduces new drive vendor-locking parameters

589
317
NAS
RS1221+, DS1517+, RS819, RS217
Operating system
  1. macOS
Mobile operating system
  1. iOS
How unfortunate am I to have 6 (non-Synology) SSDs to all go from perfect health to 'Critical' with the completely coincidental installation of the latest DSM7.1. No matter if the drive is young or older, no matter what batch they are from or how many bytes written.

Or, is it a new way of vendor locking non-Synology drives by the retrospective back-door method Synology likes to hose us with...?

 20220504-Syno-RS1221+DSM7.1 SSD Lifetime Critical-SSD Details.png


Please excuse me for taking a negative view on Synology's intentions here. This comes hot on the heals of Synology refusing to provide me with technical, diagnostic or indeed any warranty support on what appeared to be a PCIe power issue until I removed and replaced all the drives fitted to this NAS with the equivalent (ludicrously expensive and unavailable) Synology SSDs. My own more detailed diagnostics traced the PCIe power issue to a bad Synology NIC, which was replaced using my own money.

Clearly there are zero actual issues on these drives, just a tweak to the SMART data on DSM 7.1-42661 Update 1 to make them look like they are all out of life and in need of urgent replacement. It should bring a nice burst of profit to Synology, upselling new Synology SSDs to anyone who accepts this undocumented change as truthful.

How do we get off this terrible Synology train and in the interim how do I keep this NAS going?

:eek:



[In no way am I suggesting that the developers of smartmontools (an open source project that Synology uses for SMART data on DSM) are either complicit or even aware that their software on Github is being manipulated in this way.]
 
570
180
NAS
DS620slim, DS415+
Operating system
  1. Linux
  2. macOS
  3. Windows
Mobile operating system
  1. Android
  2. iOS
Last edited:
That is really ugly. There seems to be something with the attribute that calculates/holds the lifespan of your SSD.
maybe shutdown of run a smart test and see if it resets the counter?

Fortunately my 6 SSD (mix of 3 Brands but no wd) are not affected and still running fine after the upgrade.
-- post merged: --

did you try to change (in configuration screen, notifications) to remove the warning for this lifespan level and the message for incompatible disks?
 
589
317
NAS
RS1221+, DS1517+, RS819, RS217
Operating system
  1. macOS
Mobile operating system
  1. iOS
That is really ugly. There seems to be something with the attribute that calculates/holds the lifespan of your SSD.
maybe shutdown of run a smart test and see if it resets the counter?

Fortunately my 6 SSD (mix of 3 Brands but no wd) are not affected and still running fine after the upgrade.
-- post merged: --

did you try to change (in configuration screen, notifications) to remove the warning for this lifespan level and the message for incompatible disks?

I did indeed change the notifications and whilst this stopped the warning emails the Critical failures and are still showing as in the screenshot above, plus the orange status LEDs on the front panel.

I've not run an addition SMART test just in case that takes the drives / volume offline.

Maybe I could tweak something via CLI?

☕
 
208
46
NAS
DS918+, DS414j
Operating system
  1. Linux
  2. Windows
  3. other
Mobile operating system
  1. Android
I had this with an HDD, had to copy all the data off, remove it and add it again. All happy again now (still got the data on a second external drive for the time being). Not amused.
 

jeyare

Subscriber
2,424
806
NAS
Synology, TrueNAS
Operating system
  1. Linux
  2. Windows
Few facts related to this problem which Syno (un)support will deny, only in principle:

1. Synology DSM uses native SmartMonTools for SMART monitoring purposes. Similarly as each (more bigger) storage vendors or OS developers.

2. Thanks to this SMART (Self-Monitoring, Analysis and Reporting Technology) standards defined they can monitor health status of any storage device. Reason why the tool it does exist -also in their GUI or CLI DSM parts.

3. When Synology did a customization of their GUI based on “customized” reality bending from the native tool (smartmontools) verdict to lie their customers - it is a crossed red line.

Robbie, send here pls a status from the smartctl for each the drives - it is necessary to publish to any channels as dangerous behavior from Syno HQ.
 
589
317
NAS
RS1221+, DS1517+, RS819, RS217
Operating system
  1. macOS
Mobile operating system
  1. iOS
@jeyare

Ok thanks, very fair questions.

I didn't have time to run smartctl and match the attributes for all the drives on all the tools today but I did do so for the 'worst drive' of the 6, which is in bay 1. The other drives will undoubtedly have better attributes recorded but in all cases they were marked 'Critical' by DSM due to the "smartctl" reporting.

Drive 1 on DSM, it is physically the oldest, with around 2-1/4 years powered and 26 power cycles:

 20220504-Syno-RS1221+DSM7.1 SSD Lifetime Critical-Drive 1 SMART Attributes.png


Using the DSM version of smartctl:

Code:
[email protected]'s password:

Synology strongly advises you not to run commands as the root user, who has
the highest privileges on the system. Doing so may cause major damages
to the system. Please note that if you choose to proceed, all consequences are
at your own risk.

[email protected]:~$ sudo -i
Password:
[email protected]:~# cat /proc/mdstat
Personalities : [raid1] [raid6] [raid5] [raid4] [raidF1]
md5 : active raid1 sata5p5[0] sata7p5[1]
      17573494400 blocks super 1.2 [2/2] [UU]
      
md3 : active raid5 sata3p6[0] sata4p6[5] sata1p6[4] sata2p6[3] sata8p6[2] sata6p6[1]
      14651234560 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
      
md2 : active raid5 sata1p5[5] sata4p5[6] sata2p5[4] sata8p5[3] sata6p5[2] sata3p5[1]
      4859657280 blocks super 1.2 level 5, 64k chunk, algorithm 2 [6/6] [UUUUUU]
      
md1 : active raid1 sata1p2[0] sata5p2[7] sata4p2[6] sata7p2[5] sata2p2[4] sata8p2[3] sata6p2[2] sata3p2[1]
      2097088 blocks [8/8] [UUUUUUUU]
      
md0 : active raid1 sata1p1[0] sata5p1[7] sata4p1[6] sata7p1[5] sata2p1[4] sata8p1[3] sata6p1[2] sata3p1[1]
      2490176 blocks [8/8] [UUUUUUUU]
      
unused devices: <none>

Drive 1 = sata1p6

[email protected]:~# smartctl -a -d ata /dev/sata1p6
smartctl 6.5 (build date Oct  7 2021) [x86_64-linux-4.4.180+] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     WD Blue / Red / Green SSDs
Device Model:     WDC  WDS400T2B0A-00SM50
Serial Number:    1926D7420114
LU WWN Device Id: 5 001b44 4a8e02f24
Firmware Version: 411030WD
User Capacity:    4,000,787,030,016 bytes [4.00 TB]
Sector Size:      512 bytes logical/physical
Rotation Rate:    Solid State Device
Form Factor:      2.5 inches
Device is:        In smartctl database [for details use: -P show]
ATA Version is:   Unknown(0x0ff0), ACS-4 T13/BSR INCITS 529 revision 5
SATA Version is:  SATA >3.2 (0x1ff), 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Wed May  4 13:39:45 2022 BST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)    Offline data collection activity
                    was never started.
                    Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)    The previous self-test routine completed
                    without error or no self-test has ever
                    been run.
Total time to complete Offline
data collection:         (    0) seconds.
Offline data collection
capabilities:              (0x11) SMART execute Offline immediate.
                    No Auto Offline data collection support.
                    Suspend Offline collection upon new
                    command.
                    No Offline surface scan supported.
                    Self-test supported.
                    No Conveyance Self-test supported.
                    No Selective Self-test supported.
SMART capabilities:            (0x0003)    Saves SMART data before entering
                    power-saving mode.
                    Supports SMART auto save timer.
Error logging capability:        (0x01)    Error logging supported.
                    General Purpose Logging supported.
Short self-test routine
recommended polling time:      (   2) minutes.
Extended self-test routine
recommended polling time:      (  10) minutes.

SMART Attributes Data Structure revision number: 4
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME                                                   FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct                                            0x0032   100   100   ---    Old_age   Always       -       0
  9 Power_On_Hours                                                   0x0032   100   100   ---    Old_age   Always       -       19959
 12 Power_Cycle_Count                                                0x0032   100   100   ---    Old_age   Always       -       26
165 Block_Erase_Count                                                0x0032   100   100   ---    Old_age   Always       -       8670086088
166 Minimum_PE_Cycles_TLC                                            0x0032   100   100   ---    Old_age   Always       -       4
167 Max_Bad_Blocks_per_Die                                           0x0032   100   100   ---    Old_age   Always       -       125
168 Maximum_PE_Cycles_TLC                                            0x0032   100   100   ---    Old_age   Always       -       47
169 Total_Bad_Blocks                                                 0x0032   100   100   ---    Old_age   Always       -       2899
170 Grown_Bad_Blocks                                                 0x0032   100   100   ---    Old_age   Always       -       0
171 Program_Fail_Count                                               0x0032   100   100   ---    Old_age   Always       -       0
172 Erase_Fail_Count                                                 0x0032   100   100   ---    Old_age   Always       -       0
173 Average_PE_Cycles_TLC                                            0x0032   100   100   ---    Old_age   Always       -       13
174 Unexpected_Power_Loss                                            0x0032   100   100   ---    Old_age   Always       -       3
184 End-to-End_Error                                                 0x0032   100   100   ---    Old_age   Always       -       0
187 Reported_Uncorrect                                               0x0032   100   100   ---    Old_age   Always       -       0
188 Command_Timeout                                                  0x0032   100   100   ---    Old_age   Always       -       77
194 Temperature_Celsius                                              0x0022   066   048   ---    Old_age   Always       -       34 (Min/Max 18/48)
199 UDMA_CRC_Error_Count                                             0x0032   100   100   ---    Old_age   Always       -       0
230 Media_Wearout_Indicator                                          0x0032   001   001   ---    Old_age   Always       -       0x015d011e015d # in decimal = 1498962329949
232 Available_Reservd_Space                                          0x0033   100   100   004    Pre-fail  Always       -       100
233 NAND_GB_Written_TLC                                              0x0032   100   100   ---    Old_age   Always       -       52013
234 NAND_GB_Written_SLC                                              0x0032   100   100   ---    Old_age   Always       -       60468
241 Host_Writes_GiB                                                  0x0030   253   253   ---    Old_age   Offline      -       41122
242 Host_Reads_GiB                                                   0x0030   253   253   ---    Old_age   Offline      -       187404
244 Temp_Throttle_Status                                             0x0032   000   100   ---    Old_age   Always       -       0

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       00%     19949         -
# 2  Short offline       Completed without error       00%     19781         -
# 3  Short offline       Completed without error       00%     19613         -
# 4  Short offline       Completed without error       00%     19445         -
# 5  Short offline       Completed without error       00%     19277         -
# 6  Short offline       Completed without error       00%     19109         -
# 7  Short offline       Completed without error       00%     18942         -
# 8  Short offline       Completed without error       00%     18774         -
# 9  Short offline       Completed without error       00%     18606         -
#10  Short offline       Completed without error       00%     18494         -
#11  Short offline       Completed without error       00%     18318         -
#12  Short offline       Completed without error       00%     18150         -
#13  Short offline       Completed without error       00%     17982         -
#14  Short offline       Completed without error       00%     17814         -
#15  Short offline       Completed without error       00%     17646         -
#16  Short offline       Completed without error       00%     17478         -
#17  Short offline       Completed without error       00%     17310         -
#18  Short offline       Completed without error       00%     17142         -
#19  Short offline       Completed without error       00%     16974         -
#20  Short offline       Completed without error       00%     16806         -
#21  Short offline       Completed without error       00%     16640         -

Selective Self-tests/Logging not supported

[email protected]:~# smartctl -a -d ata /dev/sata1p6 -P show
smartctl 6.5 (build date Oct  7 2021) [x86_64-linux-4.4.180+] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

Drive found in smartmontools Database.  Drive identity strings:
MODEL:              WDC  WDS400T2B0A-00SM50
FIRMWARE:           411030WD
match smartmontools Drive Database entry:
MODEL REGEXP:       WDC WDBNCE(250|500|00[124])0PNC(-.*)?|WDC  ?WDS((120|240|250|480|500)G|[124]00T)(1B|2B|1G|2G|1R)0[AB](-.*)?
FIRMWARE REGEXP:    .*
MODEL FAMILY:       WD Blue / Red / Green SSDs
ATTRIBUTE OPTIONS:  165 Block_Erase_Count
                    166 Minimum_PE_Cycles_TLC
                    167 Max_Bad_Blocks_per_Die
                    168 Maximum_PE_Cycles_TLC
                    169 Total_Bad_Blocks
                    170 Grown_Bad_Blocks
                    171 Program_Fail_Count
                    172 Erase_Fail_Count
                    173 Average_PE_Cycles_TLC
                    174 Unexpected_Power_Loss
                    230 Media_Wearout_Indicator
                    233 NAND_GB_Written_TLC
                    234 NAND_GB_Written_SLC
                    241 Host_Writes_GiB
                    242 Host_Reads_GiB
                    244 Temp_Throttle_Status
[email protected]:~#

Same drive, when removed and tested with a real copy of smartctl (ie not the versions modified by Synology) so now showing to be in full health:

Code:
ID    Name                            Value        Threshold        Health
5    Reassigned NAND block count        0            None            N/A
9    Power-On Count                    19960        None            N/A
12    Drive Power Cycle Count            28            None            N/A
165    WD Internal                    8670086088    None            N/A
166    WD Internal                    4            None            N/A
167    WD Internal                    125            None            N/A
168    WD Internal                    47            None            N/A
169    Total Bad Blocks                2899            None            N/A
170    Grown Bad Blocks                0            None            N/A
171    Program Fail Count                0            None            N/A
172    Erase Fail Count                0            None            N/A
173    WD Internal                    13            None            N/A
174    Unexpected Power Loss Count        3            None            N/A
184    WD Internal                    0            None            N/A
187    Reported Uncorrectable Errors        0            None            N/A
188    Command Timeout Count            77            None            N/A
194    Temperature                    82.4ºF | 28ºC    None            N/A
199    CRC Error Count                0            None            N/A
230    Media Wear Out Indicator            1.93%        None            N/A
232    Available Reserve Space            100%            4%            N/A
233    NAND GB Written TLC                52016        None            N/A
234    NAND GB Written SLC                60472        None            N/A
241    Total GB Written                41125        None            N/A
242    Total GB Read                    187409        None            N/A
244    Temperature Throttle Status        Off            None            N/A

Same drive again, using WD's own SSD Dashboard tool:

 20220504-WD SSD Dashboard-Status .png


For a belated attempt at brevity, the smartctl attributes for this 'worst' drive via WD's Dashboard tool are identical to the real version of smartctl shown above. So no functional issues with this drive according to WD and the real copy of smartctl, so the health issues are only shown by DSM's local build version of 'smartctl'.

Is this the kind of drive data you seek for all 6 drives?

I did grab a little more than the above but I can be back with this machine tomorrow to be meticulous with each drive if needed.

☕
 

jeyare

Subscriber
2,424
806
NAS
Synology, TrueNAS
Operating system
  1. Linux
  2. Windows
Robbie,
I would like to change your conclusion:
So no functional issues with this drive according to WD and the real copy of smartctl, so the health issues are only shown by DSM's local build version of 'smartctl'.

to:

So no functional issues with this drive according to WD and the real copy of smartctl, and also by smartctl from CLI DSM. So the health issues are only shown by DSM's GUI = which isn’t in line with all the mentioned tests (incl. their CLI source).

Evidence from your Synology DSM native smartctl results:
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Error logging capability: (0x01) Error logging supported. General Purpose Logging supported.
SMART overall-health self-assessment test result: PASSED
SMART Error Log Version: 1
No Errors Logged

My conclusion is still in the same line - DSM GUI doesn’t show results from the SmartMonTools, but from “custom translation” of them = data bending based on Synology needs.
 

jeyare

Subscriber
2,424
806
NAS
Synology, TrueNAS
Operating system
  1. Linux
  2. Windows
follow my DSM6 JSON list of drives from:
/var/lib/disk-compatibility/
here you can find version of JSON db list called:
yourNASmodel_host.db
yourNASmodel_host.db.new

Because I'm not DSM7 positive, try to find also these files:
NASmodel_host_v7.db
NASmodel_host_v7.db.new
which are already uploaded into DSM6 (why???)


I can't find there your (incl. the DSM7 ver files):
- drive PN: WDS400T2B0A-00SM50
- or Firmware: 411030WD
1651733065695.png

1651733114250.png


So, check these files in your DSM, when you can't find your SSDs there, try this workaround:
- backup these files first
- edit the files by VSC or by
1651732517166.png


Try to enter there:
JSON:
,"WDS400T2B0A-00SM50":{"411030WD":{"compatibility_interval":[{"compatibility":"support"}]},"default":{"compatibility_interval":[{"compatibility":"support"}]}}

you will get new correct db file:
1651732988296.png

Note: this viewer helps you find incorrect part of the code (missing bracket, ...) if it happens during the code manipulation.

Test the result within your DSM GUI. Maybe restart will be needed.

Conclusion:
- my DSM6 db host file contains 836 records = HDD/SSD
- but it is different for diferent models (file size)
 

jeyare

Subscriber
2,424
806
NAS
Synology, TrueNAS
Operating system
  1. Linux
  2. Windows
BTW:
official SMART logs, which are in line with the setup of GUI = date creation, you can find here:
/var/log/smart_result/
compressed into TAR file, which contains all defined drives (by the GUI SMART test enabled):
1651735608189.png


When you open every single file (by Notepad), you will get results from the SMART test defined by the DSM GUI - but your DSM GUI shows the results differently.

and
her you can check additional related last logs:
/var/log/smart_quick_log
/var/log/smart_extend_log

You can use this evidence also for the new Ticket for Syno support.

Yeap, they can use a fairytale about:
Synology will not provide technical support if your device is not on the Synology Products Compatibility List.
This is the list of all compatible WD drives for your model :unsure::
1651736167596.png

So, I would ask them:
1. Entire model range of WD RED (WDxxEFAX) is not supported? Because I didn't find it in your Synology Products Compatibility List for my NAS model. But you can find the EFAX models within the JSON DB files mentioned in my previous post = compatible.
2. While WD RED Pro - WD4003FFBX 4/6/8/10TB are supported (compatible), why not the same HDD/same model/same architecture/same firmware/... for the 2TB capacity with model number WD2002FFSX? Note - the diff btw FFBX and FFSX is in a cache capacity only.


Yes, they have also defined conditions more specifically:
Compatibility issues
If you use incompatible devices, or devices that are not on the List, it may result in the following issues:
  • The system cannot detect the device.
  • The system cannot always detect the device.
  • The system is unstable.
  • Unexpected problems arise.
If problems regarding product compatibility occur when you use an untested device, Synology Technical Support may not be able to offer you any assistance. Therefore, be sure to choose the compatible ones on the List for your Synology products and pay attention to the notices in each category.

But your drives are:
- detected by the system
and
- the system is stable
- there is no unexpected problem because the native DSM7 tool = smartctl, incl SMART logs, are OK.
Then:
- there isn't a compatibility issue - just the issue related to inconsistent GUI status (vs CLI).

Cheers
(F.ck them all)
 
589
317
NAS
RS1221+, DS1517+, RS819, RS217
Operating system
  1. macOS
Mobile operating system
  1. iOS
These WD drives were on the original list but like many others they have been subsequently removed since the time of purchase. For my NAS the only SSDs that are now permitted are the Synology-branded ones - nothing else. The Synology data sheet for the 21+ series still reflect the previous position of Synology SSDs being 'Recommended', rather than the new position of 'Mandated'.

What I think we are seeing is that different Syno NAS generations or CPU type are experiencing vendor locking issues at different rates on different components.

For example, I do not doubt that many 920 users have just found that the latest DSM update left them with just a blinking blue light, now traced to the use of some 3rd party RAM. My Ryzen-based NAS still works though, but it already had a RAM vendor issue, albeit one that could be overcome with careful purchasing. The Xeon crowd have had restrictions that pre-date the Ryzen CPUs, so we are all moving at different rates and times, but the direction is generally bad.

I'd also guess that most users do not get to test their warranty, so the latent issue of Synology cancelling all support has yet to arise for them.

Of course, Synology is on the path of making even a NIC a proprietary module/connection with their latest consumer DS and prosumer RS series. No need to have vendor soft locking when you make the hardware with an odd square 'module bay' rather than a regular PCIe connection.

Not looking good.

☕
 

Rusty

Moderator
NAS Support
5,397
1,589
www.blackvoid.club
NAS
DS718+, DS918+, 2x RS3614RPxs+
Router
  1. RT1900ac
  2. RT2600ac
  3. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
The Synology data sheet for the 21+
Just seen that you are on x21 model.

True, the newer models from + and xs range will be more and more effected by this and there is also indication that syno will start to offer non -ENT drives (from 1TB up to 8TB) to accompany the current HAT and HAS lineup. These drives will probably not be 7200, but time will tell.

There is also (100% certain) more "proprietary" HW coming but I am not at liberty to say, so yes, Syno is moving to a direction of a proper appliance model. 10G modules are just starting but there is more to come.

We’re not seeing this issue either
I forgot to mention that I am not running this on an x21 model so that also makes a difference.
 

jeyare

Subscriber
2,424
806
NAS
Synology, TrueNAS
Operating system
  1. Linux
  2. Windows
Syno implementation of the SmartMonTools isn't native. Reasons:
- smartmontools use /etc/smartd.conf ... for defined cyclic health check/s
- in case of DSM (6) - it's empty file
- so, user defined task must be defined somewhere

Next:
there is also for every disk directory:
/run/synostorage/disks
here you can find all the devices (sda, ...)

Each device has an independent directory. This directory contains also files:
- compatibility ... which contains just status: support
- compatibility.lock ... no content
- force_compatibility ... which contains just status: support
- smart ... which contains just status: normal
- smart_damage_weight ... which contains just status: 0

all of the statuses are available from the JSON DB (mentioned in my post above) or from smartctl
all of them were last modified from the last boot up

@Robbie - check the values there
 
589
317
NAS
RS1221+, DS1517+, RS819, RS217
Operating system
  1. macOS
Mobile operating system
  1. iOS
True, the newer models from + and xs range will be more and more effected by this and there is also indication that syno will start to offer non -ENT drives (from 1TB up to 8TB) to accompany the current HAT and HAS lineup. These drives will probably not be 7200, but time will tell.

I'm sure you didn't mean to Rusty but your line above seems to suggest that newer models will be more and more effected. It would more correct to say that the current concern is the retrospective action on older in-use models, caused by undocumented changes in DSM7 updates.

At time of purchase the only DSM version available for my RS1221+ was DSM6.2.x and that I migrated these SSDs seamlessly from a DS1517+ that was also using DSM6.2.x. There was no suggestion at that time that a few versions of DSM7 later that such problems would be dealt to me by the hand of Synology via firmware updates.

If manufacturer's can induce additional costs or trigger unwarranted failures via software updates then then the customer has no hope. Synology changed the deal after the fact - this is bad.
 

Rusty

Moderator
NAS Support
5,397
1,589
www.blackvoid.club
NAS
DS718+, DS918+, 2x RS3614RPxs+
Router
  1. RT1900ac
  2. RT2600ac
  3. MR2200ac
Operating system
  1. macOS
Mobile operating system
  1. iOS
Synology changed the deal after the fact - this is bad
Indeed this is bad and I would like to know that this is something that can be reproduced, but I guess there will be more and more similar situations.

My RS from 2014 also started to report on the RED line drives that I am using "unsupported" drives, but not incompatibles and I was able to use them after moving to 7.1, so the situation is not the same as yours but one of the cases that their new hdd policy has as documented.

I'm sure you didn't mean to Rusty but your line above seems to suggest that newer models will be more and more effected
This is not confirmed, but IMHO this will happen in the future especially with the release of "lower spec" drives. Will this mean that non +/xs model will be effected, maybe but it is obvious that with no HW change (unit or drives) only DSM update, these HDD "problems" are affecting also older models as well, just as mine RS xs model from 2014.
 

Create an account or login to comment

You must be a member in order to leave a comment

Create account

Create an account on our community. It's easy!

Log in

Already have an account? Log in here.

Similar threads

UPS's with AVR (Automatic Voltage Regulation) are worth the added expense... They'll take care of voltage...
Replies
13
Views
1,121
  • Question
So just in case anyone else gets this problem I thought I'd do an update. It turned out I was having this...
Replies
8
Views
929
I haven’t bothered trying to mate any of our 5UPS’s to any of 3 NAS’s, or IT Gear, or TV or Sat gear...
Replies
91
Views
12,344
I can confirm that this worked for me with DSM 7.1 Enable SSH on `Control Panel/Terminal & SNMP` Boot up...
Replies
10
Views
318
I think there’s a link on the bottom that would have said sign in using another method. From there you...
Replies
4
Views
417
RESOLVED: Synology Support applied a hot patch to my NAS that corrected the R/W cache issue causing the...
Replies
2
Views
1,588
Hi. If I share a folder in my Drive with another user, who uses Windows (3.0.1) or macOS (3.0.1) Drive...
Replies
0
Views
618

Welcome to SynoForum.com!

SynoForum.com is an unofficial Synology forum for NAS owners and enthusiasts.

Registration is free, easy and fast!

Trending threads

Top