• 28 Posts
  • 399 Comments
Joined 2 years ago
cake
Cake day: June 7th, 2023

help-circle
  • Yes, but is this them being assholes, or them wanting to make sure that users aren’t making their system unreliable? I think there would be a huge distinction there.

    For example, say a user wanted to create a cache drive using an SSD. But because the user doesn’t know better, they buy the cheapest crap they can find, install it, and set up caching. But because they’re using cheap shit, the drive is slow and the user reports poor performance, system hangups, and other instability.

    Wouldn’t it be in Synology’s best interest to say “here’s a list of drives we know will give you the best experience.”?

    Now, Synology has already done that, but users are ignoring it and continue to use poor storage drives expecting to use pretty sophisticated features. What now? Well, Synology disables those features.

    For example:

    De-duplication, lifespan analysis, and automatic HDD firmware updates could also disappear on non-approved drives

    Um, yeah. That makes sense. If a shitty hard drive can’t reliably get firmware updates through the NAS, why on earth would they want to keep that option enabled? Same with lifespan analysis. If a crappy drive isn’t using modern standards and protocols for measuring and logging errors and performance data, Synology really can’t “enable” this to work, can they?

    That’s what I think is happening. Although, this could be just greed, too. I don’t think there’s any real problem for most users, unless they say that we can’t use fairly common, high-quality NAS drives from Seagate or WD and must use their own branded drives. I’d have a huge problem with that.


  • Are we overreacting? Hasn’t Synology always had a list of “certified” drives for their NAS’, which end up being the same HDDs we would tend to use anyway?

    I can understand that they don’t want people using any garbage storage drives, which could increase failure and make Synology NAS’ look unreliable.

    Unless something has changed, this is how they’ve always done it, just like how every laptop manufacturer will say which RAM and storage works best (for reliability and performance) on their machines.


  • Yes, incoming.

    Outgoing is another can of worms.

    I try to run any of my iot devices on an isolated network. At most, they can see eachother, and that’s it.

    Some devices need an internet connection, unfortunately.

    The best you can do, if you’re unable to block their collection outright, is to run them through a tracker-blocking DNS (either self-hosted or something like Adguard DNS).

    That can minimize unnecessary pings home.

    Personally, if I think that a device is being malicious in their attempts to phone home, I stop using the device. I also try to make an effort to not get a smart device, if the alternative (unconnected option) works fine.

    Digital minimalism is one way to protect ourselves from rampant data collection and profiling.






  • Someone below mentioned Aurora, Bazzite’s sister. I currently use Bluefin, which is another of Bazzite’s sisters, also on Framework,

    I know nothing about these… but I just installed Aurora in Boxes to try, and damn, it’s nice. Maybe a little “too busy”, but it’s got everything I could ask for out of the box (no need for extension manager). I might replace Mint with Aurora on my MiniPC, but if it’s as unbreakable as they say, it may replace Fedora.

    Right now, Fedora has still be very stable, but since I’m staring from scratch, I might as well get it right the first time. I’ll be experimenting more to see which I prefer.





  • I really appreciate that. I really do.

    Considering how the EU is now looking to make a distro… based on Fedora… I’m more comfortable with the idea.

    And you are right, FOSS projects are a collaboration, and I think it’s worth for me to explore the best option for me, rather than what I feel might be the best option.

    That said, I’m backing up my Home folder, I’ve got memtest loaded on a flash drive ready to run, and I’ll be prepping Fedora 41 to install once that’s all done :)



  • conflating big American tech firms that steal your data with big America tech firms that make FOSS is just silly.

    For sure. But also seeing Americans as friends and allies… and now we (Canada and the rest of the world, but not Russia) are being attacked with threats on our sovereignty, just doesn’t seem normal anymore.

    Nothing that used to be logical can be taken as such now. An American tech that makes FOSS is still an American tech. And I hate even having to say that, because I would have gladly supported American FOSS just a few months ago.



  • I had tried several, actually. But Ubuntu was installed through an external SSD.

    To create the bootable drive, I’ve tried Rufus, Ventoy, and Etcher. I believe Etcher was the last one, and the one that got me to actually install Ubuntu.

    Could be an issue with Secure Boot in BIOS.

    Secure Boot and Bitlocker were turned off before I installed anything, as I know these could be issues. I haven’t turned either back on, but will once I get this to be stable.


  • Thank you.

    Just run the update command again in the GUI or terminal. If it doesn’t work, we’ll have to dig into apt with verbose logs but I haven’t had apt break on me for over a decade unless I deleted something I shouldn’t have.
    

    Nothing needed to be updated. One package was “deferred”, and that was the “ubuntu-drivers-common”.

    Is Firefox installed as a snap/flatpak? That only happens with me occasionally when I installed flatpaks, they’re just slower. Canonical can be a real arse about this stuff, they might switch packages to snaps without telling you and you might only come to know about it once you dig deeper.
    

    Default Firefox, and I just checked, and it’s listed as Snap package.

    All of these issues seem to related to your storage medium. Is the SSD OK? Open up the process monitor, sort by ascending order of disk writes/reads and open your applications one by one to see which one of them is the culprit.
    

    Full chkdsk was performed before installing Linux on my SSD. In the Western Digital utility (in Windows), everything tested OK, too. No issues in the S.M.A.R.T. logs, either.

    Rebooting suddenly is not normal. Unfortunately, you’ll have to go through logs for this one. Simple ones are dmesg and journalctl, we can dig deeper into them if you want to.
    

    I don’t know if it actually rebooted, or if it just closed everything and returned on the login screen. I wasn’t home when it happened, I just came back to that :(

    But that was days ago. And it hasn’t happened since.

    I’ll be running a proper memtest shortly, and will post an update once that’s done.