ezhik

Members
  • Posts

    416
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by ezhik

  1. Now we are talking! Top notch man!
  2. Looks good! I am not a fan of Intel stock CPU coolers, those are pretty bad :-/
  3. Which means perl and temperature monitoring won't work? That's not good news.
  4. Can confirm run into the same issue. Drives that are not assigned to an array and for example are used as passthrough drives for the VM, send out notifications for drives surpassing the default thresholds of 45C, regardless of the values you set.
  5. When it comes to software development, ideally the structure would be: 6.9.1 6 - Major 9 - Minor 1 - Patch -- With unRAID we have seen that Minor releases are treated as major and contain a lot of new features.
  6. Right, the OP did. Apologies there, got mixed up.
  7. The good old base64.
  8. Betas are not releases though, they are considered pre-release and are mainly used for testing purposes. When you say release, you mean the stable version and that takes on average 12+ months. Mind you, major releases require major resources
  9. 6.10 would be considered a major release, I wouldn't count it being until year end at the earliest.
  10. Also noticed that when you reset drive assignments, your settings get reset as well - I think that's wrong: The following settings get reset: Global disk settings [Disk Settings] - Enable auto start - Default file system - Shutdown time-out - Tunable (nr_requests) - Tunable (md_write_methods) [Global SMART Settings] - Default SMART notification value
  11. If the partition table was improperly setup to begin with, this could very well be an issue though - am I wrong?
  12. Interesting, I just re-did as well and it worked as intended... I did notice that there was a difference on the space required for the filesystem and this went down from 72GB to 69GB on a 10TB drive, wonder if this was the issue...
  13. I could re-produce this at the cost of losing data on the array, I'll do a re-pro and post diagnostics.
  14. Hey Team, Recently had to go through an exercise of downsizing the cache array on an encrypted array (and encrypted cache array). Only way to do so was via: 1. Tools -> New Config -> Preserve current assignments [Array slots]. 2. wipefs -a /dev/sd[y-z] # (clear filesystem from cache drives) 3. assign cache drives 4. Mark 'parity is already valid' 5. Start array 6. encounter unmountable drives -- The array was hosed at this point, can someone confirm this for me? have rebooted the server and re-created the array since data on it wasn't important, still pretty disappointing. The error was the partitions were not recognized.
  15. No stress man! Your work is greatly appreciated! We are back in business: --
  16. Not to be the one to complain, but we need to turn from reactive to proactive. I genuinely appreciate the support here and the dev work put in here, but couldn't this be anticipated and communicated out to the developer ahead of time? If we are trying to bridge the gap between core product devs and community devs, this could be avoided In either case, no harm no foul. The system is running and we can wait for the fix.
  17. Updated without any major issues except for nvidia plugin: I only see version "v" available. Any way to bring back the 'STABLE' drivers over 'BETA'? Although I do respect having an option for 'bleeding edge', I appreciate stability over features.
  18. I have 860's, no issues: root@u4:~# dmesg -T|grep -i 'lsi' [Sat Mar 13 12:48:52 2021] mpt2sas_cm0: LSISAS2308: FWVersion(16.00.00.00), ChipRevision(0x05), BiosVersion(07.31.00.00) root@u4:~# dmesg -T|grep -i 'samsung' [Sat Mar 13 12:48:52 2021] ata5.00: ATA-11: Samsung SSD 860 EVO 500GB, *, RVT03B6Q, max UDMA/133 [Sat Mar 13 12:48:52 2021] ata6.00: ATA-11: Samsung SSD 860 EVO 500GB, *, RVT03B6Q, max UDMA/133 [Sat Mar 13 12:48:52 2021] scsi 5:0:0:0: Direct-Access ATA Samsung SSD 860 3B6Q PQ: 0 ANSI: 5 [Sat Mar 13 12:48:52 2021] scsi 6:0:0:0: Direct-Access ATA Samsung SSD 860 3B6Q PQ: 0 ANSI: 5 root@u4:~# fstrim -v -a /etc/libvirt: 8 GiB (8588054528 bytes) trimmed on /dev/loop3 /var/lib/docker: 63.3 GiB (67954708480 bytes) trimmed on /dev/loop2 /mnt/cache: 874.8 GiB (939358191616 bytes) trimmed on /dev/mapper/sdf1
  19. Q: Is the 9207-8i P16 firmware still the only firmware that allows for trim with the latest mpt3sas driver in UNRAID 6.9.1? Or have they decided to allow it again in the driver? A: Have not tested it out, but you are more than welcome Q: Have you noticed any issues with the P16 firmware e.g. stability, data corruption etc? A: I am still rocking P16 firmware on 9207-8i and 9201-16i, haven't noticed any corruption, but then again - I don't open every file all the time and therefore - so far so good. Cheers.
  20. -- Same here, lots of entries - I tried to delete them, nothing happens. The logs show: Mar 3 14:42:00 unraid3 dnsmasq[12378]: no servers found in /etc/resolv.conf, will retry Mar 3 14:42:00 unraid3 dnsmasq[12378]: reading /etc/resolv.conf Mar 3 14:42:00 unraid3 dnsmasq[12378]: using nameserver 9.9.9.9#53
  21. Just to add some kudos for the development team - this is a MASSIVE update and a testament to the tremendous work by the development, testing and of course the community teams that have helped test this through-out the betas and the release candidates! Well done!
  22. We are running 455.45.01, any benefit to push for 460.56?