• 2 Posts
  • 54 Comments
Joined 1 year ago
cake
Cake day: June 7th, 2023

help-circle






  • You might want to look up SMR vs CMR, and why it matters for NASes. The gist is that cheaper drives are SMR, which work fine mostly, but can time out during certain operations, like a ZFS rebuild after a drive failure.

    Sorry don’t remember the details, just the conclusion that’s it’s safer to stay away from SMR for any kind of software RAID

    EDIT: also, there was the SMR scandal a few years ago where WD quietly changed their bigger volume WD Red (“NAS”) drives to SMR without mentioning it anywhere in the speccs. Obviously a lot of people were not happy to find that their “NAS” branded hard drives were made with a technology that was not suitable for NAS workload. From memory i think it was discovered when someone investigated why their ZFS rebuild kept failing on their new drive.



  • This sounds like a FOSS utopian future :)

    There’s a few projects that have started towards this path with single-click deployable apps, you could even say HomeAssistant OS does this to some extent my managing the services for you.

    I believe one of the biggest hurdle for a “self hosting appliance” is resilience to hardware failure. Noone wants to loose decades of family photos or legal documents due to a SSD going bad , or the cat spilling water on their “hosting box”. So automated reliable off-site backups and recovery procedures for both data and configs is key.

    Databox from BBC / Nottingham University is also a very interesting concept worth looking in to:

    A platform for managing secure access to data and enabling authorised third parties to provide the owner authenticated control and accountability.






  • One way is to make a new “entity”, that’s not actually linked to your previous temperature sensor. I’m not familiar with how to tie them together in a “device” like how ZigBee2mqtt auto discovery does.

    So just add a new “sensor”/“entity”

      - name: "Sala_battery"
        unique_id: "temp_sala_battery"
        state_topic: "zigbee2mqtt/temp_sala"
        value_template: "{{ value_json.battery }}"
        unit_of_measurement: "%"
    

    Use MQTT Explorer to listen to your ZigBee2mqtt broker topic “zigbee2mqtt/temp_sala” to get the exact field name (battery, battery_state or some such)






  • That’s very strange, which distro and GPU was this? So I don’t recommend that to anyone?

    I’m assuming the GPU in question was Nvidia, since AMD and Intel make their driver opensource and baked in to the kernel. Sadly nVidias latest kernel (535) has been troublesome, so I’m still on the previous 525. nVidia is about to release 545, which looks to be very promising.

    Luckily on Ubuntu changing driver is as easy as opening the Additional Drivers application, selecting the driver version, hit apply and reboot. PopOS, Bazzite, and a few others comes with Nvidia drivers preinstalled.

    Best of luck if you try again in the future