tr0910

Members
  • Content Count

    1436
  • Joined

  • Last visited

Community Reputation

41 Good

About tr0910

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. I've attempted to move the docker image to ZFS along with appdata. VM's are working. Docker refuses to start. Do I need to adjust the BTRFS image type? Correction, VM's are not working once the old cache drive is disconnected.
  2. ZFS was not responsible for the problem. I have a small cache drive and some of the files for docker and VM's still comes from there for startup. This drive didn't show up on boot. Powering down, and making sure this drive came up, resulted in VM and docker behaving normally. I need to get all appdata files moved to ZFS and off this drive as I am not using it for anything else.
  3. I have had one server on 6.9.2 since initial release and a pair of ZFS drives are serving Docker and VM's without issue. I just upgraded a production server 6.8.3 to 6.9.2 and now Docker refuses to start and VM's on the ZFS are not available. Zpool status looks fine pool: MFS2 state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that do
  4. If I understand you right, you are suggesting that I just monitor the error and don't worry about it. As long as it doesn't deteriorate it's no problem. Yes, this is one approach. However if these errors are spurious and not real, reseting them to zero is also ok. I take it there is no unRaid parity check equivalent for ZFS? (In my case, the disk with these problems is generating phantom errors. The parity check just confirms that there is no errors)
  5. I have a 2 disk ZFS being used for VM's on one server. These are older 3tb Seagates. And one showing 178 pending and 178 uncorrectable sectors. UnRaid parity check usually finds these errors are spurious and resets everthing to zero. Is there anything similar to do with ZFS?
  6. Thx, using ZFS for VM and Dockers now. Yes, its good. Only issue is updating ZFS when you update unRaid. Regarding unraid and enterprise, it seems that the user base is more the bluray and DVD hoarders. There are only a few of us that use unRaid outside of this niche. I'll be happy when ZFS is baked in.
  7. A few months ago, there was chatter about ZFS being part of unRaid supported file systems. @limetech was expressing frustration with btrfs. What is the current status of this?
  8. Likely the top one will perform best if you can get all the cores busy, but I have never used this Dell. What processor does it have? The second machine has higher clock rate so individual core performance will be better. It will really depend on your planned usage, and whether your apps will be able to utilize all the cores. Often, you find that some utilities or apps are single core only, so having massive numbers of cores is useless for that app. I am using Xeon 2670v1 based servers and find that sticking a second cpu in with another 16 cores is not that much of a
  9. Well in your case you want all your storage in the fast zone. I also want to have ZFS continue to work and VM's continue to run even if the unRaid array is stopped and restarted. Then unRaid will be perfectly able to run our firewall's, and pfSense without the (your firewall shuts down if the array is stopped).
  10. I've been running my VM's of a pair of old 2tb spinners using ZFS. I have been amazed that it just works, and I don't notice the slowness of the spinners for running VM's. The reason I switched was for the snapshot backups. I love the ability to just snapshot my windows VM back to a known good state. I look forward to having ZFS baked in more closely to unRaid. I still have one VM on the SSD with BTRFS but I can't see any speed benefit to the SSD compared with the ZFS spinners. I have a Xeon 2670 with 64GB ECC ram. Lesser RAM and/or non ECC RAM may not be such a good option.
  11. So the process for those who have 6.8.3 and some version of your plugin is update ZFS plugin then update unRaid to 6.9rc1 then reboot? My unRaid only finds an update to the ZFS plugin from November, not your December one.
  12. Herrobin-diagnostics-20201130-0353.zipe is new diagnostics file. Disk is WDC - 7804.
  13. @Frank1940 The rebuild completed successfully, but another drive showed 200 errors during the rebuild process. Does this mean that errors were replicated into the newly built drive and it is not fully perfect? I have 2 parity drives, so that other WDC EZRS can go bad without further issue...
  14. Here part of the syslog on the old server just before it locked up. Nov 27 20:06:54 Robin root: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Nov 27 20:06:54 Robin avahi-daemon[9235]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Nov 27 20:06:54 Robin avahi-daemon[9235]: Successfully dropped root privileges. Nov 27 20:06:54 Robin avahi-daemon[9235]: avahi-daemon 0.7 starting up. Nov 27 20:06:54 Robin avahi-daemon[9235]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! Nov 27 20:06:54 Robin avahi-daemon[9235]: Successfully called chro