hansolo77

Hey all! So I pulled the trigger after watching a few YouTube videos and bought a license to FoundryVTT. I downloaded the Linux version from the website and then installed this docker. I saw in that 2nd post that I needed to extract the Linux version into the created appdata folder. I did that. Sorry for being ignorant, but uh... what do I do next? When I click the docker link for the drop down, I don't see an option for "WebUI" or similar. I'm usually pretty quick to pick thigs up but I don't even know where to start. UPDATE - Never mind. I figured out I just needed to go to the URL in my browser manually. Now I just need to figure out how to use it.

I see... it's almost like it's ignoring the data itself, and just blinding moving the entire thing at once. It's not taking "folder a" and moving it's contents to "disk 1, disk 2, disk 3".. it's literally taking ALL of "folder a" and moving it from "drive 5" to "drive 8" and not moving the contents around to other drives. I'm sure it's been suggested, but if not; perhaps a new future version could be more granular like that and take "all selected drives" and spread out the contents you select into them, rather than root folder to one drive.

Is support still available for this? I'm having trouble accomplishing stuff and I don't know what I'm doing wrong... I just added 3 20tb drives to my array. They were 12tb upgrades, so not really adding 60tb's... However, the combined added space gave me at least 38tb. I was having some errors reading another drive so I'm trying to use this tool to evacuate that drive so I can remove it from the array and do some tests on it. The drive is 20tb, and had about 4tb free. Every time I tried to select all the folders to move, it just crapped out with errors saying it was unable to move a specific folder because there isn't enough free space. I don't know what could be causing this. If I have 38tb free, and the drive (even at full capacity) is less than that. So why is it telling me there's not enough space? Another issue I noticed, every time I redesign the plan to just move root folders on the drive separately, they all end up going to the same drive. I select ALL the drives (except the cache), but it puts everything on say Disk 3. Then I'm getting flooding with alerts that Disk 3 is 93% full, 94%, 95%, etc. It's not using any of the other drives. When the process is finished, my Disk 3 is now sitting at 98% full and nothing else was used. So I go back to setup moving the next folder, and choose all the drives but Disk 3 and Cache. Then it moves everything to Disk 10, with the same results. I'm on my 3rd manual setup and now it wants to put everything on Disk 8. I don't understand. All my shares are set up to use High Water, and the drives with the most free space are the 3 new ones but this tool doesn't try to use any of them. Am I missing something? What I expected to happen was select select all the folders on the drive I want to evacuate, select all the drives in the array for it to "SCATTER" the folders into, and let it run for however long, come back and see the drive is empty and all the other drives are fuller. Instead I'm now having to go in manually and practically dictate every step from the folders to move and where to put them. Doesn't sound correct to me...

My plugin has been working for a couple of years, but recently it's not been working right. I haven't made any changes to any of the settings. I don't know if something changed with an update, or if something happened with my dockers, but the last few backups the plugin has made ended up with lots of errors about the dockers not restarting. I came home from work today and had another dozen emails about the dockers not starting. HOWEVER, when I checked, all the dockers were started fine. Checking the logs and the debug logs, it appears they're starting, just not as fast as the plugin would like. Is there a way to set a longer delay before it gives up and throws an error?

Well shucks. I uninstalled the ca.mover.tuner app, rebooted, and tried to manually start the mover again. And wouldn't you know.. it's working now? Not sure what's going on. I'll try to let this go and if I see a problem (or not) I'll report it.

I'm not sure what I'm doing wrong. I've been using Unraid for serveral years now, and it's never really choked like this. My cache pool is completely full, and whenever I try to run the mover the log says "mover is running" but clearly it's not. When I watch my "MAIN" tab, I can see the activity on the pool, and there is no data being read or written on either the array or the cache pool. I was using a CA that added some mover tweaks. I disabled that app so I'm using just the default mover. I also enabled the mover log. It definitely reports that it's running but nothing is actually happening. I thought maybe I had some docker or VM that could be interfering so I stopped all that and disabled the docker/vm managers. Still same results. I then decided to try and just do a reboot, thinking maybe there is some stale file in use that's locked things up. When the system came back it wanted to do a parity check (odd also). I cancelled the parity check, attempted to run the mover manually again with the same results. That's when I decided to come here and post a thread seeking help. Any ideas? Attached is my complete diagnostics support package.kyber-diagnostics-20250116-1741.zip

I’ve been using nzbget for a couple of years. Never had any problems.

Well... i hate to jinx things, that's typically how things are for me... but... I let the memtest run all night and all day today till I got home from work. Successfully completed 4 passes with 0 errors, and was running for like 23.5 hours. I spent the afternoon putting the new motherboard back into the case. Tested memory again with the mobo all screwed in. Got to about 8% (past the dreaded 4% and onto test #3) and shut down. Then I transferred all the M.2 drives, connected all the expansion cards and fan headers, and put the lid on it. Booted up and let it run the memtest again for 1 complete pass. Then I booted into Unraid. So far, everything is going good. I updated all the plugins and dockers. I then shut down the docker and VM manager and started a parity check. Usually I run the check on the first of the month anyway but I missed it. Plus, it auto-started a parity check as soon as Unraid was loaded (remember, it was crashing whenever I started the preclear.. so I think the boot up parity check was just clearing the dirty bit). Once the parity check finishes, I'm going to reboot (so it's a clean shutdown and clean startup) and then (( FINGERS CROSSED )) try to run another preclear.

Yeah his videos are really helpful. Glad it worked for you and you're up and running.

Watch spaceinvader’s video on YouTube

I bought new RAM from Amazon on Thursday. Was supposed to be 2-day, delivery on Saturday. Never got it, said it was delayed, then delayed again then delayed AGAIN. I just now got it. It's running a memtest now but so far the entire set looks ok. It made it past the 4% mark at least. Been running about an hour and is up to 35% pass. Hope it's good. Gonna let it run all night and through tomorrow until I get home. Fingers crossed.

Heh. I know right? I'm baffled. I told my brother, if different RAM has the same problem.. I'm done. It's not worth continuing with this hardware design. My next build won't be "gamer" centered. I had envisioned one day building a VM that I could stream games from it onto a smaller SBC in a different room. As it is, I've not really been able to have a stable system running for more than a year, just hosting a PLEX server. The next time I build a server, I'm going back to server-grade parts. SuperMicro/ASRockRack board, Xeon or similar CPU, ECC RAM. It's just a lot to buy from scratch. But it's definitely something I should probably start researching if new RAM doesn't fix it. I can't afford to buy a replacement CPU.

Well... good news / bad news time. Good News: Replacement motherboard arrived. Bad News: Might not have been the motherboard. Details: The motherboard arrived late last night so I couldn't play around with it until after I got off work today. I spent a couple of hours being really gentle with it. I kept it on the box on top of it's anti-static bag. I removed the CPU from the old motherboard and diligently cleaned off the old thermal paste. I also removed the paste from the heatsink. I ordered some new goop that arrived a week ago, and applied that. Hooked up the power, connected a video card AND... nothing. At least not at first. Prior to the swap (I still haven't screwed it in yet...) I did another test of each ram stick one by one and identified which ones were good and bad. The first thing I did was put just 1 stick in the designated SINGLE slot, and tried to boot. The motherboard has an LED indicator for various boot stages, and indicated immediately a problem with the DRAM. So I popped out the stick and put in the other one I designated as GOOD. THAT allowed me to boot. I went into the BIOS and updated it first thing (I remembered having a problem with the original BIOS not working well with the CPU when I first built my rig so I wanted to make sure I updated it. Once the update was done I went back into the BIOS and tweaked some settings, like making sure the fan speeds were all on FULL. This is a bare build still at this point. Nothing is connected except a usb keyboard/mouse dongle, the video card, cpu and ram. I plugged in the Unraid USB and went straight into Memtest. Within 10 seconds, it reached like 4% pass then FAILED. F^CK. I rebooted with one of the "bad" sticks, again LED indicated DRAM issue. So I tried the LAST stick, labeled BAD but surprisingly it's up to 37% PASS at this point. All the others are failing at around that 4% mark. I don't know what happened. Something took a bite out of my RAM though. Unless this kind of behavior is typical with a bad CPU? There does appear to be some weird oily/greasy like residue around the solder pins under the old motherboard where the RAM is. I checked and it's NOT on the new motherboard. Maybe I had a leak somewhere that jacked up the slots and then with it running 24/7 it damaged the sticks over time. In any case, I'm going to look and see if I can return/exchange the newer RAM I have. It's probably too late (3+ years) for the old RAM to get replaced. If I can't do an exchange with Amazon on the new RAM, I'm going to have to wait for Income Tax Refund to buy new. I'm tempted to get something else. I mean, I'm really good with computers and building; I doubt it had been running good for over a year then stopped working because of a compatibility thing. I'm not even overclocking these guys.. this is the base values (not even using the XMP setting). But, these are my first G.Skill sticks. Perhaps a replacement set should be a different brand? What are your thoughts? I know my friend @Idolwild built his server with essentially the same components and hasn't had any trouble. He has the same motherboard, CPU, and RAM. So should I tempt fate and buy another matching set of RAM that I've been using? Should I go with something else like Kingston or Corsair? I'm lost. Also.. is there a CPU tester like MEMTEST? I'd like to try and verify it's still ok, and the problem is actually with the RAM. Thanks!

Yeah I know.. I was generalizing. I have a RAID controller but it's not using any RAID settings, just straight JBOD. Even the BIOS detects and lists all the drives available for choosing for boot, although I'm not using it. As for the VMs, I think all I'm passing though is network, but even that might be something the VM manager does. Without having access to Unraid until my replacement motherboard arrives, I can't know for sure. If I can get Unraid to load with the new motherboard, I think I'll be good. It'll be upsetting if I have to rebuild my server data, but at least I know HOW. I was just wondering if it would all of sudden go to boot Unraid then halt at some issue due to hardware change. At first run, the only change would be the motherboard. The CPU and RAM and all the other stuff should be all the same.

Not expecting delivery for awhile (January 21st+). Curious.. with a new motherboard, even if it's the same model, would it interfere with Unraid? Would it be a simple drop-in plug and play, or is it going to require rebuilding Unraid from scratch again? I know the system runs off the flash drive, and it's thumbprinted... just curious if there are any complications with swapping out the motherboard. Also curious, though I don't see how, would it complicate things if I had to replace the CPU too? I'm not sure how it all works.