• Posts

  • Joined

  • Days Won


LammeN3rd last won the day on April 30 2018

LammeN3rd had the most liked content!

1 Follower

About LammeN3rd

  • Birthday April 30


  • Gender
  • Location

Recent Profile Visitors

1441 profile views

LammeN3rd's Achievements


Rookie (2/14)



  1. Is there a compelling reason that there is a Red error notification when there is a update for the plugin? from my perspective this should not be red since it's just a plugin update not something really bad.... There have been quite some Updates the last couple of weeks and I still jump every time I see a red error 😬
  2. Great to hear! I've switched my UniFi Docker back to macvlan will report back if the issue comes up again
  3. to be honest, I don't think it makes real sense to test more than the first 10% of an ssd, this would bypass this issue on all but completely empty ssd's. and ssd's don't have any speed difference for different positions of used flash when doing 100% read speed test, for a spinning disk this makes total sense but from a flash perspective a read workload has no difference as long there is data there.
  4. you could have a look at het used space on a drive level, but that's not that easy when drives are used in BTRFS raid other than 2 drives in raid1. NVMe drives usually report namespace utilisation so looking at that number and testing only the Namespace 1 utilization would do the trick. this is the graph from one of my NVMe drives: and this is the used space (274GB):
  5. Just to make sure I understand it right. The flat line that basically indicates the max. interface throughput is trimmed (empty) space on the SSD? Yes, the controller or interface is probably the bottleneck
  6. that's the result of trim, when data is deleted from a modern SSD trim is used to tell the controller that those blocks are free and can be erased, the controller does that and marks those blocks / pages as zeroes. when you try to read from these blocks the ssd controller does not actually read the flash it just sends you zeroes as fast as it can. this is the reason ssd's used in the unraid parity array can not be used with trim since that will invalidate the parity.
  7. Hi, I would recommend against this workaround. Besides the complications and performance impact from running this vm the main reason not to do this and use a router in bridge mode is that you lose acces to your unraid server if there is anything wrong with anything. that could be the routing vm or anything with unraid / the hardware...... sounds like a to complicated solution for a simple problem.....
  8. please add this to the help notes in Unraid, when I started with Unraid I googled around for this info and having it in the help text will help a lot of new users
  9. LammeN3rd

    Squid is 50!

    Happy birthday squid!!
  10. found a few more places with the same issue, these are all places I found: opening log from top right corner opening the log of an individual VM Settings --> VM Manager --> View Libvirt LOG opening Console from a Docker (both from docker tab as well as Dashboard) The following places do not have the issue and work as normal: opening Terminal from top right corner opening a docker log from docker tab if I find any others I will update
  11. systemlog under the tools tab works fine, so no reason to switch browsers just yet
  12. In safari opening the log window (top right corner) shows the login screen, the terminal and or the logs from docker containers work as normal. In Firefox the log window opens and shows the log like in 6.7.2
  13. I suggest looking at your BIOS! from the above log it seems you are running a 2011 version the last version available is from feb 2019 for my Poweredge T630 the BIOS from Feb 2019 fixed my issue!
  14. Quick update, I've done a lot of testing removing plugins, disabling Virtual machines and Docker before I rolled back the firmware of my intel NIC (i350) and Bios that I had updated recently. After the BIOS downgrade to 2.9.1 I've not seen the issue for days upgrading tot 2.10.5 brings back the crashes! I've not reinstalled my plugins so I can't be 100% sure its the BIOS but if anyone else has this issue I highly recommend looking at your BIOS!!