A software developer and Linux nerd, living in Germany. I’m usually a chill dude but my online persona doesn’t always reflect my true personality. Take what I say with a grain of salt, I usually try to be nice and give good advice, though.

I’m into Free Software, selfhosting, microcontrollers and electronics, freedom, privacy and the usual stuff. And a few select other random things, too.

  • 0 Posts
  • 60 Comments
Joined 3 months ago
cake
Cake day: June 25th, 2024

help-circle
  • Does anyone happen to know if there is a N100 model that supports HDMI-CEC so I can make my old TV set smart with a recent Kodi and maybe some retro-games? But I’d rather not let it consume 9W or whatever such a machine needs all day long. So it’d need to start and shut down on its own. Preferably without manual additional steps involved, hence the CEC…






  • If you google it, you’ll find lots of similar questions for O2. I think you have to contact their customer support and get that activated once.

    And have a look at your IPv4 and IPv6 addresses. Sometimes you can do it via IPv6 already, just not over IPv4 because there is some translation in the way. (In case they want too much money to give you a real IPv4 address.)

    Maybe you can try if you can open your FritzBox UI from the outside with your my.fritz address. I think that has IPv6 and a port forward in place (if activated).

    And btw: It’s perfectly fine to do it. People need storage and online collaboration. Access to their data while away.



  • Fair enough. I don’t have any first hand experience to offer. But I think I read a test of baby monitors in some consumer magazine a while back. As far as I remember few of them were good. Maybe you got one of the several bad models. My friends have some audio only monitors. They fail safe, you immediately hear static noise once the connection gets interrupted. But yeah, they only transmit a few hundred meters because it’s radio signals. It’s not like an IP cam where you can watch your baby from another continent.









  • I’m not sure if 3-4 times a day is a lot. I had computers (especially laptops) which were way more aggressive with spinning up and down the disks. Maybe you can look it up. A decent (enterprise(?)) hdd should have some datasheet available including info about how often you can powercycle or spin them up/down.

    And I wouldn’t wake up disks deliberately. If you don’t mind the 5-10s waiting, you can just spin them down at the end of the day and leave them that way. The next day they’ll either spin up on first access, or they won’t. And save that one cycle. I’m not sure though if you can change the spindown timeout during the day without also waking it up. I mean you could run a script that spins them down at 22:00 and sets the timeout to 1h, and at 07:30 you run a script to keep them awake for a 6h period. But you’d need to test if changing that setting wakes them up. Or I’d rather not run a script like that. Sometimes executing hdparm spins up a disk, even if unnecessary.





  • hendrik@palaver.p3x.detoSelfhosted@lemmy.worldOS recommendations
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    2 months ago

    That is indeed a good question. Is this something RAID is bothered with at levels 0 and 1? I think in this case it’s the job of the filesystem to care for that. But you should probably let the periodic task run that does scrubbing like once per week. You could also experience other issues than just bitrot. For example bad sectors and one of the hdds slowly degrading.

    In the end I don’t think a RAID1 can do much about bitrot and other RAID woes. There are no checksums or anything to correct for that. You’d probably need some other technology for that. But it’s probably the same for a ZFS mirror. And everything better than that needs more than 2 hdds.