Jclendineng

Members
  • Posts

    201
  • Joined

  • Last visited

Everything posted by Jclendineng

  1. Lifetime licenses are not sustainable. But I do agree that update roadmap will need to be less opaque to allow users to see what they are paying for. This is going from an enthusiast platform to a commercial endeavor and that comes with more responsibility. That said, pricing is reasonable and extensions are 39/year which is not very much, you buy hundreds of dollars of hard drives, and server hardware, and don't have 39/year to support the software? Change is hard but imo this is a good step. Also this literally affects none of us, we are all legacy, so Im not sure why anyone's complaining.
  2. Ultimately don't care what LT does but I have to say, subscription makes a lot more sense than current model. From a business standpoint I have always questioned the current model, 1 time purchases are never profitable. The 80 or whatever I paid for my license is not going to sustain the business. They HAVE to come up with a value proposition that includes a paid model, and this may or may not be the ticket, we will see. It's a good start though. I hate subscriptions as much as the next person but everyone has support contracts, think of it as a support contract. All that said, the bar will need raised to make the residual sub worth it for people. TLDR; Residual income is needed to keep LT afloat, this is probably a great plan
  3. Not just you, this was delisted for some time seems to be resolved now though.
  4. I have a motherboard with a NCT6799D-R sensor chip, supposedly in the latest 6* kernel but no luck. Does not load in sensors or sensors-detect, and no temp sensors show up. NCT6687 driver was installed as a plugin but that does not work. NCT6799D-R has a driver but it does not appear unraid uses it, what can I do? Modern AM5 boards use this chip (at least ASUS). edit. Per this, it’s not in fully until Linux kernel 6.5. https://www.phoronix.com/news/Linux-6.5-NCT6799D Any chance we can get this?
  5. Thank you! Yea that makes sense, why spin up a mongo instance just for this. Thank you for the explanation, that’s helpful.
  6. I see 3 unifi controllers in the App Store, the official one that's being discontinued, a new one using a new DB, and this one, what's the difference in this one? What's different here vs official? Thanks!
  7. Unifi introduced port profiles a long time ago and enabled blocking by default on some ports, I had upgraded my switches and didn't check the updated port profiles.
  8. Updated, no issues. I changed back to macvlan from ipvlan when I updated to 6.12.3, and added static Macs to all my docker containers again like pre-6.12 times. So far so good, no crashes or indications that it will crash yet.
  9. First of all, great work! I did as instructed and macvlan works well so far. Question: I have 3 NICs, eth0 and eth1/eth2, I disabled bridging on eth0, eth1/eth2 is using bonded LACP, with a few VLANs that docker is using. Is it recommended that I disable bridging on ALL interfaces and only use bonding? current Docker network below: root@Unraid:~# docker network ls NETWORK ID NAME DRIVER SCOPE 410ede2fc44b br1 macvlan local 8ef814bdd249 br1.10 macvlan local 24c58ff2a324 br1.15 macvlan local 18d59eef887b br1.20 macvlan local a65a073f4cd7 bridge bridge local 8002478340ab eth0 macvlan local f6e5f48f1e23 host host local 5882761c0802 none null local
  10. Going to throw my hat in the ring again, same issues. I switched to ipvlan which isn’t ideal as I need each docker to have a static ip that I hand out from my router. This works for now but eagerly waiting for a fix since this wasn’t an issue in previous releases.
  11. Thank you for the release notes vs RC5. It really helps know what to test. Looking good!
  12. Following as this release broke it for me as well. I switched to ipvlan but it really sucks because I can’t have static ips/macs now. All ips share 1 mac meaning I can no longer manage in my firewall. Quite a pain but I spose better than crashing all the time.
  13. Number 3 is a good point, never had any issues with number 2, numerous restarts, and number 1 isn’t really an issue, it’s in the release notes and it already requires the user to be somewhat familiar with zfs for now. It’s a power user feature and I didn’t have any issues with this particular item. That said, like you said it will be resolved in 6.13…I don’t have any issues not having an array though, setup is super simple (moving from ssd to platter would be nice, that I am looking forward to).
  14. So I upgraded and it looks like nothing changed per se other than naming. I have a data pool and a cache pool with a dummy usb as an array. I can only use the mover to copy from data/cache to array vs cache as primary, data as secondary, and the mover moves between cache and data. It would be nice to move between pools since I have a nvme pool as a cache pool and a data pool with only platter drives. Otherwise solid update, nothing broke, 10 or so datasets and 30 odd dockers all started just fine after upgrade.
  15. It hasn't happened since, my assumption is I was snapshotting the docker dataset, it was at 10k snapshots or so, and the whole server reset due to that, so this is most likely related to the other report I posted. I "resolved" that in the other thread by limiting snapshots and maintaining good snapshot cleanup scripts, resolving this as Im 99% sure that was the cause.
  16. So I followed best practices, Ill mark this as "fixed" but for people reading this, I disabled snapshots on the docker dataset, that will not prevent snapshots when docker images are updated, and the release notes still dont say anything about managing them, but that info can be found in the link JorgeB posted above. Basically, dont auto snapshot docker images as they are legacy and lead to 5 minute plus slowdowns on the "Main" page when you reach 8000 snapshots or so. I worked around this by setting my default page at login to dashboard so if snapshots got out of hand I could still log in, I dont auto snapshot docker dataset, and I have a user script that automatically cleans up snapshots and docker images that arent cleaned up on its own. That leaves me with around 600 snapshots for around 30 docker applications, and a 8 second load time when I hit the Main page, which is acceptable.
  17. Yes I set it up per the release notes, but looking through the link you posted, maybe this isnt a great idea, seems like the docker zfs storage isnt super ready for prime time...thank you!
  18. Just an FYI or perhaps this is indeed a bug, but docker, when switched to directory mode, creates a ZFS set for each downloaded dependency or container. This leads to massive slowdowns in the UI, specifically on the "Main" page. It also sets up snapshots by default and I dont see an easy way to disable them on the docker share, so I end up with hundreds of baseline snapshots, and I had over 8000 last night leading to not being able to log in until I ssh'ed in and manually cleared them all. I tested this morning by deleting the entire docker share, setting it up, and noting that it does create snapshots still even though I dont have it scheduled to snapshot. If this is expected slowdown then may we recommend NOT using the directories mode for docker storage as it really had a large impact on performance in the UI. My docker created 350 datasets, I don't have many dockers, only 25-30, but thats enough to increase UI load times to 30 seconds or so.
  19. FYI for anyone searching for this, after RC3, docker has a new "directories" mode that creates a zfs dataset per container. This creates many snapshots, and ZFS Master takes a solid 2-3 minutes to load. Go into settings, and in management settings, select Dashboard instead of Main on log in or you will hang for a long time at first log in. I tested with baseline 350 snapshots (1 per docker dependency) and it was still super slow, I had 8000 snapshots last night and it just hard crashed and wouldn't let me log in to the GUI. I asked in the RC3 thread how to disable snapshots on 1 dataset as disabling them on the docker set should help with this issue.
  20. How do you disable snapshots for a particular dataset?
  21. Mine is the same way. Cant access the UI, had a crash after upgrading to RC3 but didnt get any logs. It takes about 5 minutes for the UI to finally load but then just hangs...potentially a plugin issue? RC2 worked fine but hard to tell with 0 release notes