you are viewing a single comment's thread
view the rest of the comments
[+] -18 points 1 year ago* (1 child)

Yup, been using that from the start, since none of the 20TB drives were "verified" when I bought them.

It's a bit annoying that you have to do that, but ultimately a non-issue.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 57 points 1 year ago (2 children)

    A non-issue??? That is absolutely an issue, because 90% of consumers won’t know about this fix. It’s outrageous that a consumer facing brand introduces such arbitrary vendor lock-ins, especially without reason. It’s just like HP with their ink lock. An absolute dick move and should not be supported in the slightest.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 1 year ago (1 child)

    Not to say I'm not annoyed and they definitely should not be doing this except for their enterprise line. Would I buy another Synology again, no definitely not.

    However most "consumers" buying a NAS are already pretty tech savvy. When this issue happened to me I googled it and found and applied the script in 15 or so minutes. Run the script essentially once a year or so when major updates come along. Hasn't been a huge issue. The issue will be if /when they block this script or other fixes.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 1 year ago

    Run the script essentially once a year or so when major updates come along.

    I've set it up in the task sheduler as a "on boot-up" task. Have never bothered with it through multiple updates.

  • source
  • parent