jztreso

Seemed like a dns i had running was blocking the port. Works now.

Hey i've been looking into the idea of making a cached games share for my unraid gaming VM, but to me it doesn't look like the caching system in unraid covers my needs, or maybe there's something I don't understand about the different caching methods? The most logical approach I found was to use the array as main storage and the cache as second storage option (move from Array -> Cache) But this presents me with a couple issues: 1st issue i find is that if my game library exceeds the 1tb of my cache drive (which it will quickly) how does unraid know which files and folders to move to the cache drive? I was hoping unraid prefers the most frequently/recently used files to store on the cache, but as far as i can tell there's no tiered caching system in unraid? 2nd issue is, is there a way to invoke the mover to move the files to the array, once the're being read on the drive? If i use the array as the initial download path, that mean they won't be on the cache, once i want to play them. I was hoping there would be an option to move the files to cache upon reading, but afik there's not a way to mitigate this either? If there's a way to set this up in mover, with a docker/plugin or perhaps passthrough the ssd to the vm and use host caching instead? Cheers

Ended up sending back the drive - talked with customer service and looks like it's probably a hardware defect rather than unraid acting up.

Just tried downloading Music-assistant and it behaved similar to what i experienced when updating qbittorrent, but with a different error message: IMAGE ID [1005227837]: Pulling from music-assistant/server. IMAGE ID [e1caac4eb9d2]: Already exists. IMAGE ID [51d1f07906b7]: Pulling fs layer. Downloading 100% of 3 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [fe87ad6b112e]: Pulling fs layer. Downloading 100% of 12 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [4d8ccb72bbad]: Pulling fs layer. Downloading 100% of 244 B. Verifying Checksum. Extracting. Pull complete. IMAGE ID [8100581c78dd]: Pulling fs layer. Downloading 100% of 3 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [3d1c47d32dcd]: Pulling fs layer. Downloading 100% of 93 B. Download complete. Extracting. Pull complete. IMAGE ID [c089b4cae7a5]: Pulling fs layer. Downloading 100% of 203 MB. Verifying Checksum. Download complete. Extracting. IMAGE ID [b3c6b210aa7f]: Pulling fs layer. Downloading 100% of 78 MB. Verifying Checksum. Download complete. IMAGE ID [3273c87dc306]: Pulling fs layer. Downloading 100% of 16 MB. Verifying Checksum. Download complete. IMAGE ID [4f4fb700ef54]: Pulling fs layer. Downloading 100% of 32 B. Verifying Checksum. Download complete. TOTAL DATA PULLED: 316 MB Error: failed to register layer: flate: corrupt input before offset 110304872

Hey since i downloaded 6.12.8 I wasn't able to open qbittorrent. Yesterday after i had updated unraid, i saw another update for Binhex qbittorrent was available, but when it finished extracting everything it came up with an error, referring to something saying "Sync input/output error". I didn't save the exact error, but tried reinstalling the docker instead. Now when i download the docker it appears with the following error in the logs: https://hub.docker.com/u/binhex/ XSLoader.pm did not return a true value at /usr/lib/perl5/5.38/core_perl/Fcntl.pm line 61. Compilation failed in require at /usr/lib/perl5/5.38/core_perl/POSIX.pm line 17. BEGIN failed--compilation aborted at /usr/lib/perl5/5.38/core_perl/POSIX.pm line 17. Compilation failed in require at /usr/sbin/ts line 54. BEGIN failed--compilation aborted at /usr/sbin/ts line 54. I have tried downgrading to 6.12.6 together with previous docker flags but to no avail, so I decided to just update again. I've attached the diagnostics in hopes someone can help - *ve unly been using unraid for around 4 month so i'm still fairly new and kinda lost on whether this is an unraid or a binhex problem? tower-diagnostics-20240221-1805.zip

I have 16gb on a 5 drive setup (3 array, 1 cache and one for installs) I run pretty much the full arr suite, about 15 dockers, jellyfin with both friends and family using it, lots of home automation and sometimes a lightweight linux vm and i think i have yet to break 10gb.

I ran memtest for about 16 hours without any errors, so i'd say my ram isn't the issue here. I've created a new config and removed the drive, so i'm running without backup, but ever since the array has been working flawlessly. I'm RMA'ing the drive tonight - will post an update if something interesting happens, otherwise it was probably just a dead drive.

Hi i've attached it here sofusnas-diagnostics-20240106-2325.zip

Hi i'm sort of new to unraid, but i'm familiar with linux and networking from work and has been tinkering with setting up my new server for the past two months. I bought x2 16tb seagate exos x18 drives a little over a month ago, and for some reason they've been acting a little weird ever since i installed them. First time it looked like drive1 corrupted and i deceided to just re-format the drives and build a new parity. It looked like things were working for a bit, while i was setting up my dockers and services, but i realised when torrenting stuff, the drives would constantly spin up and down. I don't have the logs from back then, but the logs was the same as in this post: I tried swapping the sata cables and try different connectors on my MB to see if that did something. Some more troubleshooting later and i'm stuck at disk1 not wanting to mount, with the following log error, when starting the array: Jan 6 16:35:24 SofusNAS emhttpd: Mounting disks... Jan 6 16:35:24 SofusNAS emhttpd: mounting /mnt/disk1 Jan 6 16:35:24 SofusNAS emhttpd: shcmd (2331): mkdir -p /mnt/disk1 Jan 6 16:35:24 SofusNAS emhttpd: /usr/sbin/zpool import -d /dev/md1p1 2>&1 Jan 6 16:35:27 SofusNAS emhttpd: pool: disk1 Jan 6 16:35:27 SofusNAS emhttpd: id: 1254277220385983428 Jan 6 16:35:27 SofusNAS emhttpd: shcmd (2332): /usr/sbin/zpool import -N -o autoexpand=on -d /dev/md1p1 1254277220385983428 disk1 Jan 6 16:35:31 SofusNAS kernel: WARNING: Pool 'disk1' has encountered an uncorrectable I/O failure and has been suspended. I hope someone can help me find out if this is an issue i can fix or if the drive is faulty. I don't care for the data on the array, since i'm still just testing stuff and trying to get it to run smoothly, so any attempt at getting the array to function is appreciated!