Jump to content

KZ7

Members
  • Posts

    3
  • Joined

  • Last visited

KZ7's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Hi, I'm in the process of upgrading my Unraid server to new hardware. I'm going from an i7 4790k to a Ryzen 3900. I have some new storage available and I want to reconfigure my Array and create new pools. Current Storage: Cache Pool: 2x 256MB SSD (BTRFS mirrored) Array: 3x 14TB HDD, 2x 8TB HDD. 44TB Capacity New storage available: 2x 2TB NVMe 1x 14TB HDD 1x 8TB HDD My main uses cases are: Home Assistant VM Plex/media storage Backups Windows Back Time machine Photographs and Documents (encrypted?) Google Photos sync Deduped with my own photo file mgmt Network file share A few other dockers and Linux VMs. I think the unRAID array can handle media storage and file sharing. What I want to do differently is to start making use of deduplication, compression and snapshotting for my backups. I want snapshotting for my appdata (docker + VMs). What I want to figure out how to how to nest use my NVMe drives. I want my appdata to be entirely on NVMe and then use any remaining space to accelerate file sharing and backups. Redundancy is not important for some appdata, but it is for the rest (including backups and file shares). Does ZFS or BTRFS let me do any of this better? It seems like ZFS vs Btrfs seems to be less technical as they seem to be even on features. (FWIW I have a lot more experience with btrfs - my main dev machine has a single btrfs pool with multiple disks). I'd like to get some recommendation on how to structure my Array and Pools and whether to go with btrfs or zfs. I think the unRAID integration is probably more of a selling point than the filesystem it self. Thanks for reading!
  2. Hey, I'm trying to use an old Quadro 4000 and the available driver versions do not suppoprt it. Is it possible to instal the 390.xx driver thru this plugin? Dmesg: [ 23.316462] NVRM: The NVIDIA Quadro 4000 GPU installed in this system is NVRM: supported through the NVIDIA 390.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 535.129.03 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... [ 23.320676] NVRM: No NVIDIA GPU found. [ 23.322568] MCE: In-kernel MCE decoding enabled. [ 23.322824] nvidia-nvlink: Unregistered Nvlink Core, major device number 241 [ 23.482843] nvidia-nvlink: Nvlink Core is being initialized, major device number 241 [ 23.483714] NVRM: The NVIDIA Quadro 4000 GPU installed in this system is NVRM: supported through the NVIDIA 390.xx Legacy drivers. Please NVRM: visit http://www.nvidia.com/object/unix.html for more NVRM: information. The 535.129.03 NVIDIA driver will ignore NVRM: this GPU. Continuing probe... [ 23.489120] NVRM: No NVIDIA GPU found.
  3. It looks like the filesystem on sdd1 is corrupt which ends up causing the docker images mounted on that filesystem to become readonly. The docker image errors are a result of the corruption on /dev/sdd1. Jan 7 08:27:09 Nasgard kernel: BTRFS critical (device sdd1): corrupt leaf: root=2 block=948912128 slot=56, unexpected item end, have 134231043 expect 13315 Jan 7 08:27:09 Nasgard kernel: BTRFS: error (device sdd1) in __btrfs_free_extent:6805: errno=-5 IO failure Jan 7 08:27:09 Nasgard kernel: BTRFS info (device sdd1): forced readonly
×
×
  • Create New...