ezhik

Members
  • Content Count

    405
  • Joined

  • Last visited

  • Days Won

    1

ezhik last won the day on November 20 2020

ezhik had the most liked content!

Community Reputation

106 Very Good

1 Follower

About ezhik

  • Rank
    Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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
  2. If the partition table was improperly setup to begin with, this could very well be an issue though - am I wrong?
  3. 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...
  4. I could re-produce this at the cost of losing data on the array, I'll do a re-pro and post diagnostics.
  5. 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
  6. No stress man! Your work is greatly appreciated! We are back in business: --
  7. 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.
  8. 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.
  9. 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 Sams
  10. 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.
  11. -- 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
  12. 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!
  13. We are running 455.45.01, any benefit to push for 460.56?
  14. Successfully upgraded 3 (encrypted) systems from 6.8.3 to 6.9.0. One of the 6.8.3 systems was running nvidia-plugin, upgrade procedure: 0. Stop docker containers from auto-starting. 1. Download and upgrade to 6.9.0 without rebooting. 2. Go to plugins and select old nvidia plugin, select it and remove. 3. Reboot. 4. Install new nvidia plugin: https://raw.githubusercontent.com/ich777/unraid-nvidia-driver/master/nvidia-driver.plg 5. WAIT FOR PROPER INSTALL TO FINISH - IT TAKES TIME 6. Stop and start Docker service 7. Enjoy. NO