My Nest just forgets about timers about 20% of the time. This is me, daily.
- “Set a 10 minute timer”
- “OK, 10 minute timer starting now”
- “How much time is left?”
- “It doesn’t look like you have any timers”
My Nest just forgets about timers about 20% of the time. This is me, daily.
Ah, the age old “right” vs “effective” argument.
Thanks for the followup!
This timing is very interesting with the Yuzu/Citra shutdown - do you suspect the change has anything to do with not want to make money from a Nintendo emulator as be less of a target? Or is there something fundamentally different about Drastic?
Same combo, can use it on android (and probably iOS), windows, linux; the plugins really extend Obsidian’s abilities.
Awesome to see, good luck to you!
If you’re looking for tips, I’d try to set up Prowlarr first if you intend to use it, it’ll save some reconfiguration down the line.
Though I don’t find anything as complex as mounting and permissions in the *arrs, haha.
But my favorite part about tinkering with home servers is just learning a little at a time, expanding naturally. It’s easy to find guides that are the “ultimate, best server configs”, but unless you understand what benefits they’re offering, you can’t really determine what fits best for YOUR needs.
I started with CouchPotato on Windows years ago and now have *arrs running through docker on headless boxes and keep adding on fun services.
Meanwhile, I have a Oneplus 7t and can’t find support for custom roms. I was actually considering a Pixel with GrapheneOS.
kill -9
Just tested, thanks for the suggestion! It killed a few instances of rsync
, but there are two apparently stuck open. I issued reboot
and the system seemed to hang while waiting for rsync
to be killed and failed to unmount the zpool.
Syslog errors:
Dec 31 16:53:34 halnas kernel: [54537.789982] #PF: error_code(0x0002) - not-present page
Jan 1 12:57:19 halnas systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (file watch) being skipped.
Jan 1 12:57:19 halnas systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (timer based) being skipped.
Jan 1 12:57:19 halnas kernel: [ 1.119609] pcieport 0000:00:1b.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 12:57:19 halnas kernel: [ 1.120020] pcieport 0000:00:1d.2: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 12:57:19 halnas kernel: [ 1.120315] pcieport 0000:00:1d.3: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 22:59:08 halnas kernel: [ 1.119415] pcieport 0000:00:1b.0: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 22:59:08 halnas kernel: [ 1.119814] pcieport 0000:00:1d.2: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 22:59:08 halnas kernel: [ 1.120112] pcieport 0000:00:1d.3: DPC: error containment capabilities: Int Msg #0, RPExt+ PoisonedTLP+ SwTrigger+ RP PIO Log 4, DL_ActiveErr+
Jan 1 22:59:08 halnas systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (file watch) being skipped.
Jan 1 22:59:08 halnas systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (timer based) being skipped.
Jan 2 02:23:18 halnas kernel: [12293.792282] gdbus[2809399]: segfault at 7ff71a8272e8 ip 00007ff7186f8045 sp 00007fffd5088de0 error 4 in libgio-2.0.so.0.7200.4[7ff718688000+111000]
Jan 2 02:23:22 halnas kernel: [12297.315463] unattended-upgr[2810494]: segfault at 7f4c1e8552e8 ip 00007f4c1c726045 sp 00007ffd1b866230 error 4 in libgio-2.0.so.0.7200.4[7f4c1c6b6000+111000]
Jan 2 03:46:29 halnas kernel: [17284.221594] #PF: error_code(0x0002) - not-present page
Jan 2 06:09:50 halnas kernel: [25885.115060] unattended-upgr[4109474]: segfault at 7faa356252e8 ip 00007faa334f6045 sp 00007ffefed011a0 error 4 in libgio-2.0.so.0.7200.4[7faa33486000+111000]
Jan 2 07:07:53 halnas kernel: [29368.241593] unattended-upgr[4109637]: segfault at 7f73f756c2e8 ip 00007f73f543d045 sp 00007ffc61f04ea0 error 4 in libgio-2.0.so.0.7200.4[7f73f53cd000+111000]
Jan 2 09:12:52 halnas kernel: [36867.632220] pool-fwupdmgr[4109819]: segfault at 7fcf244832e8 ip 00007fcf22354045 sp 00007fcf1dc00770 error 4 in libgio-2.0.so.0.7200.4[7fcf222e4000+111000]
Jan 2 12:37:50 halnas kernel: [49165.218100] #PF: error_code(0x0002) - not-present page
Jan 2 19:57:53 halnas kernel: [75568.443218] unattended-upgr[4110958]: segfault at 7fc4cab112e8 ip 00007fc4c89e2045 sp 00007fffb4ae2d90 error 4 in libgio-2.0.so.0.7200.4[7fc4c8972000+111000]
Jan 3 00:54:51 halnas snapd[1367]: stateengine.go:149: state ensure error: Post "https://api.snapcraft.io/v2/snaps/refresh": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
I believe there’s another issue. ZFS has been using nearly all RAM (which is fine, I only need RAM for system and ZFS anyway, there’s nothing else running on this box), but I was pretty convinced while I was looking that I don’t have dedup turned on. Thanks for your suggestions and links!
I did, great suggestion. It never recovered.
Thank you! I ended up connecting them directly to the main board and had the same result with rsync, eventually the zpool becomes inaccessible until reboot (ofc there may be other ways to recover it without reboot).
Awesome, thanks for giving some clues. It’s a new build, but I didn’t focus hugely on RAM, I think it’s only 32GB. I’ll try this out.
Edit: I did some reading about L2ARC, so pending some of these tests, I’m planning to get up to 64gb ram and then extend with an l2arc SSD, assuming no other hardware errors.
They’re Seagate Exos, https://www.seagate.com/products/cmr-smr-list/ and appear to be CMR
You can show more ads with more quantity, any ad driven platform will trend that way.
I’ve only bought one phone new retail, the rest have been used from eBay for my partner and I. I’ll typically go with a reseller (they typically have better prices and Buy It Now, instead of individuals who still like the auctions).
I like to support reusing items as a matter of course and am willing to skip out on the unboxing fun, like peeling the stickers off, etc. I don’t recall any issue I’ve had that wasn’t resolved quickly by the seller.
Thanks for the tip, I’m trying to be google-free, so I’m testing it out. A little too late for election season, oh well