• OmegaMan@lemmings.world
    link
    fedilink
    English
    arrow-up
    32
    ·
    5 days ago

    “third-party HDDs”

    In my day we just called these… HDDs. Anytime something so ubiquitous has to be labeled third-party, you know who the bad guy is instantly.

  • MSids@lemmy.world
    link
    fedilink
    English
    arrow-up
    14
    ·
    5 days ago

    I really love my Synology NAS (DS220+). I don’t anticipate needing to replace it anytime soon, but given how well it’s treated me, I would almost certainly replace it with a 2024 model instead of a newer one if I had to, given this new limitation.

    This decision from them seems short-sighted, I hope they reverse it.

  • ☂️-@lemmy.ml
    link
    fedilink
    English
    arrow-up
    19
    ·
    edit-2
    6 days ago

    buying brand name is almost always a bad idea when it comes to computers.

    take advantage of their modularity, people. desktops are still popular for a reason.

      • DasAlbatross@lemmy.world
        link
        fedilink
        English
        arrow-up
        8
        ·
        7 days ago

        Oh, you mean my biggest problem?!

        I’ve just resorted to using the shell to set permissions on stuff. For the most part everything works but I’ve had issues with NFS shares. I think some of that was copying from Windows and Windows trying to do things it shouldn’t but once I just manually set things up I was able to back all my stuff up.

        VMs and apps run in their own little areas so they just happily hum along.

      • LucidNightmare@lemm.ee
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        5 days ago

        As the poster above stated, permissions and the way things are explained for those permissions or the settings in general are vague as fuck to someone who has just now dipped their toes into the OS. It’s a headache to learn, but once you get it setup (I recommend using Obsidian to keep some notes for your future self on how you set it up) it does relatively work absolutely fine.

        Is there any thing in particular you need info on? I used Kagi Assistant during the moments where I didn’t fully understand why things were the way they were, i.e. “I want to use this like I use my Synology, what the hell is an ACL??”. I may be able to fumble you along like I did myself! :P

        EDIT: I guess I could actually try to answer your question. What I did was create my own admin account and group and named them my name. After creating them, I logged into my newly made account (or tried to!) until I realized I didn’t have the same permissions as the TrueNAS_admin account, so I essentially copied those. I then logged in successfully this time, so I made sure I could do what I could do on the admin account. I could, so I then made sure the truenas_admin account was disabled. (or, I believe I did. I may not have, so look into that before you try it). Then I used Kagi Assistant to give me a general overview of what permissions my admin account should have so that I can always access whatever the hell I want on my own setup. I am at work right now, but I wrote down the list of groups that you would add to your Auxiliary Groups. Some that I do remember are: apps, libvert (and the other virt. These are needed for you to use the NAS as a VM, which I did want to try out since my Synology is way too under powered for any real VM tinkering) and whatever groups the truenas_admin account has. If you’d like the full list, I can try to remember to give it to you, but once I am home, I usually have too much going on for me to remember things.

        After that, I am actually able to do mostly what I want for my own setup. I’m a single person using it all the time, so your mileage and needs will probably vary. :)

        • Cort@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 days ago

          I think the biggest problem I’m having with it is making virtual machines that have access to my Nas, and containerized apps as well.

          Trying to setup ersatz tv and give it access to my Plex library, but it can’t seem to access it.

          The other thing I’d like to figure out is how to passthrough a GPU to a VM so I can output video, but that’s way beyond ACL issues

  • Fades@lemmy.world
    link
    fedilink
    English
    arrow-up
    13
    ·
    6 days ago

    Haha wow what an absolutely HORRIBLE descision, wtf?! So glad I went with QNAP!!

  • ImInPhx@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    32
    ·
    7 days ago

    They’ve been implementing this for a while with some of their models. There’s an excellent script that is actively maintained to get around their shit policies.

    I’m only using a Synology (ds1823xs+) because I got a killer deal. (Sometimes I still wish I went with unraid.) I’ve never encountered any issues using unapproved hard drives with this script.

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

      • ImInPhx@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        6
        ·
        7 days ago

        Ha! I bought a plex lifetime pass years ago while on sale. Maybe one day I’ll switch to jellyfin- maybe sooner than I think.

        On a positive note synologys brtfs is pretty cool. If anything, it’s one less thing I don’t need to worry about.

        • filister@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          6 days ago

          I also bought a Plex pass years ago on sale and back then the app was fabulous, nowadays it is simply meh. I am still running it, but seriously considering switching to Jellyfin

  • Let's Go 2 the Mall!@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    ·
    6 days ago

    I love my synology router and had considered buying a NAS. That’s a deal breaker for me though. I have a proxmox machine running ubuntu server as a “NAS” right now so I’ll stick with that.

    • TBi@lemmy.world
      link
      fedilink
      English
      arrow-up
      34
      ·
      7 days ago

      You shouldn’t have to do this though and I won’t buy another Synology if this is how they treat buyers.

      • remon@ani.social
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        15
        ·
        7 days ago

        Mh, I’m not sure. This is only the case for enterprise versions and it kind of makes sense that you want to strongly encourage people to use verified drives in their buisness solutions.

          • Orygin@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            2
            arrow-down
            8
            ·
            edit-2
            6 days ago

            You mean the medium enterprise tier of their line up ?
            Yes consumers can buy them, but the real market for this will indubitably buy whatever is recommended hardware anyway.
            I see this as a nothing burger. If they ever change this for the real consumer hw maybe we can cry, but until then…

            Edit: I knew posting this would drown in down votes. Lemmy is as dumb as reddit and will follow whatever bandwagon they see.
            Come argue if you think I’m wrong, instead of surfing on sensationalism and down voting blindly.

  • Reygle@lemmy.world
    link
    fedilink
    English
    arrow-up
    10
    ·
    6 days ago

    I’ve only seen the “non supported drive installed” notification once and in my experience it affected absolutely nothing about the device.

    • Luminocta @lemm.ee
      link
      fedilink
      English
      arrow-up
      9
      ·
      6 days ago

      In my experience it blocks out some other notifications that might be interesting.

      Also the Synology branded SSDs are like 3x the price of a WD alt.

      Crazy how they’re just going to make such a nice brand go to shit.

      • Reygle@lemmy.world
        link
        fedilink
        English
        arrow-up
        6
        ·
        6 days ago

        They’re all updated to the latest DSM, maybe any change is just on new models shipping.

        We use a LOT of their small 2 bay units at customer sites, and the latest we’ve installed were using Synology brand drives, so not sure about those

        • theparadox@lemmy.world
          link
          fedilink
          English
          arrow-up
          4
          ·
          5 days ago

          According to this article, that linked a German press release from Synology as their source, it will impact 2025 “+” models.

          Synology is just jumping on the “turn the screws” bandwagon. Looks like I’ll be finding another alternative with my next upgrade or recommendation, that or DIY. I don’t respond well to this kind of bullshit.

          • Reygle@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            5 days ago

            In my scenario- ~25 clients with onsite (and replicated) backups, a new Truenas machine every time isn’t a feasable thing, so fingers crossed they don’t start increasing the markup on their “branded” drives. Ugh.

        • AlDente@sh.itjust.works
          link
          fedilink
          English
          arrow-up
          6
          ·
          6 days ago

          When they say “the 2024 Synology models and older are not affected by this change”, it makes me think it’s either very recent or still ongoing, as you said.