[–] 2 points 3 weeks ago (1 child)

That's the one thing I don't like about Truenas. It technically can spin down disks, but there's no way to force them. You can set the idle timer to 5 minutes, but then it constantly spins them back up again. Now I just power the entire system down with home assistant outside of the usage hours and I can power it up again with home assistant using wake on Lan.

A bit goofy, but it works for me

  • source
  • parent
  • context
  • [–] 2 points 2 months ago (1 child)

    Is the steam anywhere close to the launch location though? No idea how this shit works but I assume that would need all kinds of piping and valves and in the end it'll probably less efficient than converting to electricity and using that

  • source
  • parent
  • context
  • [–] 4 points 3 months ago

    Traffic congestion will always be a thing. The real world is too unpredictable. You can't pack a highway full of cars and expect them to drive highway speeds. One animal jumping on the road and you'll have a massive accident because nobody can avoid anyone

  • source
  • parent
  • context
  •  

    I'm in a really weird situation, yesterday I installed Linux (Fedora Kinoite) on my mothers laptop (An old Asus F550C) and it worked perfectly fine. Great! Or so I thought.

    We needed a few files from Windows 10, so I put that drive in, put the files on a USB stick, put the Linux drive back in and... Nothing? It recognizes the drive, but not the Linux boot option. I put the drive in my pc and it works fine, the boot drive is also still detected in the laptop just fine.

    What the hell could it be??

    • The laptop is fine (Windows drive works perfectly)
    • The drive is recognized in bios (But not the boot option)
    • The drive works fine in my desktop and can boot to Fedora
    • The laptop can boot to the USB drive I used to create the install
    • Yesterday it worked just fine
    • I went through the bios, but can't find any settings related to this (Secure boot did not fix it)

    Update: the issue is solved! Windows somehow wiped the efiboot entry.

    I mounted the drive from a live usb and ran

    sudo efibootmgr --create --disk /dev/sda --part 1 --label "Fedora" --loader '\EFI\fedora\shimx64.efi'

    After rebooting, the system works again!

    view more: next ›