• Content Count

  • Joined

  • Last visited

Community Reputation

9 Neutral

About Jessie

  • Rank


  • Gender

Recent Profile Visitors

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

  1. It appears the issue is with the mail app. It is possible to log into a terminal and uninstall it. Then you do a repair and it will probably start. Once you get it started you can deal with the mail app. The issue with the mail app will probably be in the database engine. I'll offer to help if you want to persist with it.
  2. Getting an error message on nextcloud instances using mysql docker about support for version 21 of nextcloud. Does anyone know how to deal with this? I presume a merge to Mariadb would be the answer but I don't know how to do that. Any hints? Better still, a procedure to take away the guesswork.
  3. Me too. Coincided with the installation of my 9th array disk, installation of 2 extra secondary cache drives and upgrade to 6.9. So not sure what triggered it. I'm thinking it just has more to do during the timeout period of the shutdown. I just set the timeout to 100. Will see what happens.
  4. Is there a procedure to migrate nextcloud on a mysql database to mariadb?
  5. I upgraded my main unraid machine to 6.9 r2 I installed a secondary cache drive. It is for unraid caching only. Not sure of the number but when I transfer files I am getting cache full errors around the 100gb size. The secondary cache is 500gb. Is there a setting to tell unraid the size of the cache, or is this a bug?
  6. I think the c state issue was relevant to ryzen 1 systems. I've built plenty of systems on ryzen 2 and 3 platforms with no mods needed. Was it doing it before you adjusted the c states? Maybe reset the board back to factory and start again. For reference, I built on asus and gigabyte x170 platforms and x570 gaming x and b550 gaming x, all of which ran fine with r7 3770x. If you are passing through pci devices maybe isolate them and see if that is causing it. And as the previous person said, introduce your dockers one at a time to see if they are causing it.
  7. Do you have an array? (Mechanical hard drive) I assume you do. Try setting appdata, domains and system to disk 1 Then set cache to preferred. This will move them to the cache if there is enough room. Then try a move. You will probably find they stay on the array because they are active. so go to settings and turn docker engine off and move again. The directories should move to the cache. Then go back and turn docker on again. (I just added to this) Start again here Looking at your shares above, on a normal unraid setup, you would have media and s
  8. I've built quite a few Unraid systems over the past few years. I recently went to Ryzen. The first Ryzen3 was on a X570 platform (Gigabyte X570 Gaming X) Brilliant. You can change a setting in Cmos and it optimises the IOMMU allocations for Unraid passthrough. The next one I built was on a B550 platform. (Gigabyte B550 Gaming X) I went that way because the requirements of this machine didn't warrant an X570 and the B550's have a lower cost. I had trouble passing through a single Nvidia GT1030. I had previously followed Spaceinvaders methods for modifying a downloaded
  9. Which Ryzen version. I think the first gen chips had issues like this but there were workarounds. If it is a first Gen, spaceinvader one has some tutorials on youtube to resolve the problem. Years ago I had lockup problems on a x170 xeon platform and a firmware upgrade fixed it.
  10. Yeah, you can run everything as a single device, but the whole point of unraid is redundancy. At least it is for me. In Australia the cost of running 2 500gb ssd protected arrays is the same as running a single protected 1tb array. So if you were originally planning a single array on v6.83, halve the size of each ssd and buy twice as many and go to 6.9 for 2 arrays. My thinking is if you are going to use unraid, so you can break out into unprotected single arrays again, you might as well just build the system on a vanilla windows platform.
  11. As an alternative, have you considered going to v6.9 and running multiple caches? Then you can run your system as a standard setup including the shares. ie run the appdata/vm's on one cache and everything else on another cache. Then all of your data is protected.
  12. My daily user machine has been running fine for a few years until recently. It's a xeon e3-1231 with 32gb ecc on a supermicro X10sl7 motherboard. 9 drives plus a parity for the array and 4 cache drives It has 2 windows 10 vm's installed, although I normally only run 1. 2 instances of nextcloud with their associated collabora and swag dockers, and a few occasionally used dockers such as krusader. There are also a number of plugins primarily to keep the system healthy. Anyway all of this cruised along on an average cpu usage of 25% until recently. Then something happened.
  13. Looks like this is the culprit. WARNING: [pool www] server reached pm.max_children setting (5), consider raising it Any ideas where this setting resides?