deano_southafrican

Absolute legend! This seems to have sorted it out, Parity running at normal speeds! Couldn't have done it without you guys @JorgeB @trurl! Edit: with ---> without... oops!

Thanks, I prioritised my VM over the other stuff as I only had a small SSD, my other (NVMe) SSD keeps unmounting so for stability had to move it all onto the array. Should be able to get a new SSD for this exact purpose soon as I've also just upgraded to the Pro license!

Big thanks to you both, learning experience for sure! Have attached the new diagnostics after having replaced the cable. Power cable looked fine to me and is supporting another drive on the same strand so I've only replaced the data cable. It's now showing as "Unmountable: not mounted". tower-diagnostics-20220620-1804.zip

I'm guessing it's this bit? "Jun 20 04:40:14 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED Jun 20 04:40:14 Tower kernel: ata5.00: cmd 60/40:f0:80:5d:45/05:00:39:00:00/40 tag 30 ncq dma 688128 in Jun 20 04:40:14 Tower kernel: res 40/00:10:50:6b:45/00:00:39:00:00/40 Emask 0x50 (ATA bus error)" Will follow your advice re: replacing cables and follow up.

In the diagnostics, where do you see these errors, how are they represented? Thank you, once I'm home tonight I'll replace the cables and post new diagnostics.

Still experiencing similar issues with Disk3. Parity is averaging 26Mb/s... tower-diagnostics-20220620-1032.zip

So after reseating things and checking my server, I've booted up like normal and Disk3, the same disk giving the issues shows up as "Unmountable". In a short amount of research IO have found people talking about this: xfs_repair -v /dev/md3 and: I want to make sure I'm on the right track, I don't actually care about the data on this particular drive so happy to format it but I'd like to try get to the bottom of it all and test to see if the drive is failing or if it's just a coincidental error.

Connection meaning the physical connections? What gives you this impression so I know what to look for in the logs? I'll test cables and see if I can sort it out. Thanks for your help!

I've downloaded them straight from Tools > Diagnostics and haven't changed them in any way. I've tried downloading again... tower-diagnostics-20220618-2343.zip

I took advantage of the sale and upgraded my license today from Basic to Pro. Part of that upgrade process required me to stop and restart the array. After stopping the array my server become somewhat uncontrollable via the WebUI. After a while I opted to reboot the server which it did. After that it took a while to come back up and immediately I started hearing a high pitched noise from one of my drives. Subsequent read errors appeared on one of the disks in the array followed by parity sync errors. My parity check normally takes about 3 hours to complete, however it's now on 25% after 6 and a half hours. The affected disk is one that only keeps my network backups and has no other data, fortunately! I have no idea when it comes to diagnosing disk issues or what exactly could have gone wrong but while the parity check is running I can't run the SMART test on the drive. What am I looking at here? Replace the disk? Something that can be repaired? I'm wanting to get this sorted out so I can safely update to the latest stable release (from 6.9.2). Any advice greatly appreciated. TLDR: Please see if there's anything badly wrong in the diagnostics? tower-diagnostics-20220618-2210.zip

@SmartPhoneLover This works brilliantly after significant testing! Your template in unRAID was super easy to set up, thanks a million! Just putting this out there incase you or anyone else has or will figure it out... I'm having a real hard time setting this up in Nginx. I'm trying to set it up on my domain under a CNAME on Cloudflare. where I think the issue lies is the fact that it requires a specific subdirectory (ie. /admin or /login). I've tried everything else and just can't seem to get it to work.

Love it! Got it up and working in almost no time at all. Question; is there a way to add other users or is the point only to be able to send files out? What if I'd like to send files between family members for example? Edit: I should really stop skim reading... Answer to my question - "It is similar to the discontinued Firefox Send, with the difference that only the admin is allowed to upload files."

Hey, thanks for this, excited to get it up and running. I'm having trouble unzipping the file... "End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in one of plik_db.zip or plik_db.zip.zip, and cannot find plik_db.zip.ZIP, period." Not sure if the file is corrupt or perhaps an error on my side?

I'd imagine it'd probably cause a crash of some description... If not it'll cause everything to run very slowly. Try it and see?

Honestly, was reading documentation and forums etc before installing on my unRAID server and eventually did it. Possibly the easiest thing I've ever done. Well done on a great container. I have used a small range of UDP ports and port forwarded manually, 10000:10010 UDP specifically. In NodeUI I am getting "most" (only symmetric NAT connections won't work?). Would using UPnP solve this or am I pretty much stuck like this? Not really familiar but going to do some reading up on the topic.

{SOLVED} Ok so basically the VM ran until there was no more physical space on the SSD at which point it froze. On the unRAID Web UI it showed the VM status as paused and would not start after that so I took the following steps: All of the files used for this VM were saved in a share called "windowsvmsource" with cache set to "Prefer" and a separate SSD cache pool dedicated to it. I had to force stop the VM. I set the "windowsvmsoure" to cache: yes and invoked the mover to transfer the files onto my array. I ran the VM once it was on the array and followed the steps outlined by JorgeB here: Once all steps were followed, I set the "windowsvmsource" back to cache: prefer and invoked the mover. Initially boot was very slow but has improved since and now the used space is smaller than the vdisk allocation and not continually growing, unnecessarily filling up the SSD. Thank you @Squid for helping me find this, it's been an interesting learning experience.

Appreciate the link, didn't know this... But it's not quite the same issue. My VM is used at the moment for web browsing and other simple tasks. I was sitting on the desktop and watching the space on the SSD decrease from 5GB free to zero within like 6 hours. No reason for the vdisk to be increasing in size. It also still reports 107GB as it did when I moved it to the SSD...

I finally got a small 120GB SATA SSD and have placed it into it's on cache pool formatted in BTRFS. I created a new share which I set to Cache: Prefer and chose the specific cache pool for the VM. In this share I placed my 100GB Vdisk, iso files and my Vbios for my GPU passthrough. There's nothing else with permission to use this cache pool or share. It started with the Vdisk at 107GB and the other files at just over 5GB and I watched it slowly increasing in size until it now says the entire disk is full. When I look at the Vdisk and other files, nothing has changed. In my Windows VM, I still have 20-30GB free on the Vdisk. Why is this happening?