ph_

Resolved it by first duplicating the 2 affected shares then deleting the old ones and renaming the new ones to the previous names on unraid. That solved the lock sign on the shares in OSX. Then removed and then recreated the crashing nextcloud sync connection. not elegant... but did the job.

Hi, I am aware that Mac OS SMB issues are an ongoing topic and seem to come in multiple flavours... here comes my contribution .... Some context: My setup consists of the unraid server, 2 apple laptops and a windows PC. On the unraid server I have a few private shares. To access them I have one user set up I use for smb access on all mentioned client machines. In addition to this I also run nextcloud which uses these shares as external storage and I have clients set up on the windows pc and the main macbook to sync files. This has worked ok for a few days now. The issue: At some point I noticed on the mac, that the nextcloud client would crash after a few seconds. I could narrow down the cause of the crash to 2 folders which sync the contents of 2 shares by stopping all other synchronisation. When mounting then these 2 suspicious shares via finder on the desktop, I noticed the padlock signs, however upon inspecting the properties the permissions for the correct user are read and write. Trying to write to the top directory of the 2 affected shares does not work e.g. /share1/, but strangely enough, I can write into a subdirectory of the share e.g. /share1/somefolder. All other shares behave as usual, no problems. On the PC side, I have no problems whatsoever. On the second mac laptop I have the same troubles as on the primary mac, but this one never had the nextcloud sync installed. So the trouble seems to be located with the shares themselves. I had a glance through the diagnostics and did not see anything obvious in the syslog.txt file, however I am not an expert. I would appreciate a holler if someone has come across this kind of problem and could kindly point me in the right direction. best, Ph unton-diagnostics-20240322-1256.zip Edit: Actually, I can delete files from a finder window in the top level of the problematic share , but I cannot drag and drop a file into it. Freefilesync also moves data back and forth without a problem... but nextcloud crashes on every sync attempt.

Hi @binhex , I tried another browser .... it works there instantly. In the initial browser clearing cached images and files and did the trick there. I did not know that a vnc could not appear to work because of some cookie / cash issue. Will keep it in mind. Many thanks, ph

Hi, I just updated Krusader, unfortunately the update seems to have introduced some problems, see below logs. The app does not work any more, the WebUI shows another error. Help would be appreciated. I am running Unraid 6.12.4. text error warn system array login int2: panel items: TSC 2024-03-18 01:28:15,361 DEBG 'start' stderr output: tint2: Systray composited rendering on tint2: nb monitors 1, nb monitors used 1, nb desktops 4 tint2: panel 1 uses scale 1 2024-03-18 01:28:15,423 DEBG 'start' stderr output: tint2: Kernel uevent interface initialized... 2024-03-18 01:28:15,424 DEBG 'start' stderr output: tint2: systray window 8388621 2024-03-18 01:28:15,424 DEBG 'start' stderr output: tint2: systray started 2024-03-18 01:28:15,666 DEBG 'start' stderr output: MESA: error: ZINK: vkCreateInstance failed (VK_ERROR_INCOMPATIBLE_DRIVER) 2024-03-18 01:28:15,667 DEBG 'start' stderr output: glx: failed to create drisw screen 2024-03-18 01:28:15,667 DEBG 'start' stderr output: failed to load driver: zink 2024-03-18 01:28:16,020 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 434 2024-03-18 01:28:16,024 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 435 error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 436 error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 437 error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 438 2024-03-18 01:28:16,029 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 439 2024-03-18 01:28:16,029 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 440 2024-03-18 01:28:16,030 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 441 2024-03-18 01:28:16,030 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 442 2024-03-18 01:28:16,031 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 443 2024-03-18 01:28:16,032 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 444 2024-03-18 01:28:16,032 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 445 2024-03-18 01:28:16,032 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 446 2024-03-18 01:28:16,032 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 447 2024-03-18 01:28:16,033 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 448 2024-03-18 01:28:16,033 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 449 2024-03-18 01:28:16,034 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 450 2024-03-18 01:28:16,034 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 15 minor 0 serial 451 2024-03-18 01:28:16,035 DEBG 'start' stderr output: error 3: BadWindow (invalid Window parameter) request 2 minor 0 serial 471 error 3: BadWindow (invalid Window parameter) request 20 minor 0 serial 472 2024-03-18 01:32:13,289 WARN received SIGTERM indicating exit request 2024-03-18 01:32:13,290 DEBG killing start (pid 70) with signal SIGTERM 2024-03-18 01:32:13,295 INFO waiting for start to die 2024-03-18 01:32:13,303 DEBG 'start' stderr output: Signal: 15 X connection to :0 broken (explicit kill or server shutdown). Signal: 15 In exit 2024-03-18 01:32:13,305 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23117275914576 for <Subprocess at 23117276021584 with name start in state STOPPING> (stdout)> 2024-03-18 01:32:13,306 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23117275846800 for <Subprocess at 23117276021584 with name start in state STOPPING> (stderr)> 2024-03-18 01:32:13,307 WARN stopped: start (exit status 143) 2024-03-18 01:32:13,310 DEBG received SIGCHLD indicating a child quit ** Press ANY KEY to close this window ** Best, ph

ich habs dann einfach noch einmal ausprobiert - ich kann bestaetigen, dass auch beim WU2 der betrieb headless (mit iGPU) ohne einen dummy plug moeglich ist. (es hatten sich da wie so oft einige probleme ueberlagert, deswegen die urspruengliche frage) lg

ok, danke dir - das ist ja schon einmal ein anhaltspunkt.

Hallo zusammen, nur eine kurze frage an nutzer/ kenner dieses mainboards - gehe ich recht in der annahme, dass man den dummy plug fuer den headless betrieb bei dem board braucht ? ich benutze es mit einer igpu (i3 8100). ich habe zu dem thema nichts in der anleitung gefunden aber in anderen foren wurde generell erwaehnt, dass das bei manchen boards bei headless betrieb mit einer igpu von noeten ist. danke im voraus, Lg ph_

Update: I tried the Safe Mode with GUI. My settings: Spindown after 15 mins, Array is stopped as for one missing parity. Result: Disks stay spinning for 30mins, then at 31mins start spinning down, at 32 mins start spinning up again. Conclusion: Safe Mode does not make any difference. As for my goal to add a new drive to the array and reactivate it - seems I have to endure having that array spin up and down every few mins while it takes 2 days to pre-clear my 10TB ironwolf disk. Any other suggestions ? If I decide to downgrade to 6.10 again - that probably would mean that my dockers stop working (as they have been upgraded in the meantime) or introduce other new problems ? Possibly any changes to this strange behaviour in even newer versions of Unraid ?

Hi Simon, thx for the reply - alright, guess gonna give that safe mode a shot. While it might keep checking if disks are still there, why would it spin them up though, if the user has disabled the array ? If this is a design decision... it is a rather poor one. Cheers 🙂

Hi, as the headline says... I am certainly not the first person to have this problem, but I also could not find a conclusive solution to the issue. I am not keen on downgrading, as this will probably create new issues with docker images I have upgraded since switching from 6.10.0 to this newer version. So, array has been stopped, because I took out one of the parities. Hence there should be no reason whatsoever to spin up disks. I guess the problem was there before I took one of the parities out, I guess was less obvious then that something is going awry. If someone could advise where to look in the diagonstics - I checked syslog and it does not say much more then what I already know: .... Feb 20 12:44:13 Unton emhttpd: read SMART /dev/sdb Feb 20 12:44:25 Unton emhttpd: read SMART /dev/sdc Feb 20 12:59:03 Unton emhttpd: spinning down /dev/sdb Feb 20 12:59:15 Unton emhttpd: spinning down /dev/sdc Feb 20 13:00:13 Unton emhttpd: read SMART /dev/sdb Feb 20 13:00:25 Unton emhttpd: read SMART /dev/sdc .... What else can I check ? best! unton-diagnostics-20240220-1630.zip

hey, sorry, I have not dealt with this for a while now. So, no I have not fixed it yet. Any enlightenment in the meantime ? Cheers

Replying to my own post, there is some info on the german corner of the forum: I guess you easily get obsessed with saving power if you have electricity prices as skyhigh as in germany....

Hi, I have read here and there that certain NVME drives might be responsible for Systems not being able to reach lower power states such as C7 or C8. If this is the case, is there some guidance which models are proven good in that respect and which ones are troublesome and thus better to be avoided for low power server builds? In particular, I was interested in experience with Enterprise NVME drives as many of those have capacitors onboard preventing data loss in a case of sudden power failure which seems like a great feature to have (although maybe not necessary if you have a UPS?) . Point being that those types of drives are apparently especially uncooperative when it comes to low power management. I would appreciate some insight being shared or links with more information. Many thanks!

Hi Iqgmeow, many thanks for your help - I managed to follow your instructions and overleaf is running now! I was able to set up an admin account by using the command: grunt user:create-admin [email protected] in the overleaf console. I can access overleaf now via the local ip adress, but the access via domain over Nginx Proxy Manager does not work yet. It is a tad strange, as for running behind a proxy according to the documentation you apparently need to set the following variables: SHARELATEX_SECURE_COOKIE=true SHARELATEX_BEHIND_PROXY=true SHARELATEX_SITE_URL=https://overleaf.mydomain.com but once you do set them in the unraid template, you get an error relating to cookies when trying to sign into overleaf. https://github.com/overleaf/overleaf/issues/1032 no matter if those variables are set up or not, I get a 404 Error when trying to access via the URL. I have seen a few nginx configuration file examples in relation to overleaf, they have a couple more entries then mine - The nginx Proxy manager config files generated through the WebUi have just a limited amount of options, including the enabling of websockets - but nowhere is an explanation if these additional entries are actually a necessity or not. In case you have come across that issue and a solution, please do let me know.

Hi everyone, I am having trouble setting up the overleaf docker template. I would appreciate if someone could help me out or could point my to a comprehensive tutorial if that exists. Unfortunately, the github page of overleaf gives no answers for these kind of problems. I am intending of running overleaf behind the Nginx Proxy Manager, this works fine for other dockers as jellyfin and airsonic, so that part should not be totally wrong on my side. I have downloaded the template of overleaf as well as redis and mongodB and filled in templates to the best of my knowledge (see below), however the site refuses to connect with 404 Error, respectively ERR_CONNECTION_REFUSED. The overleaf docker runs in a proxynet with the Proxymanager, the database are on "bridge". The webui port had to be changed to something else than 80 so it is not conflicting with the Unraid main UI. I am not sure what the exact problem is, but it seems the service is just not running hence nothing can be found at the adress. Actually when refreshing the docker page, you see that Overleaf keeps stopping, too. I am not entirely clear if redis and mongodb are appropriately connected. In the template for mongodb I Ieft all the default values and in overleaf I have the following to establish the connection, I also tried leaving out the "mongodb://" part but it does not make any difference. It is weird the template asks for a URL and not for a "host" as it does for Redis. The overleaf log looks like this, I am not sure if says it can connect or if it is checking if it can. But looking at the top, I would say it cannot connect to the database and then shuts down as a result: I also notice that the overleaf console does not stay open, so I cannot use it. MongoDBs log looks like this: For Redis I have also used the default host and port and inserted it in the overleaf template. The Redis log looks like this: Following advice here: https://github.com/overleaf/overleaf/issues/1032 I have also tried to remove a few of the overleaf template variables such as: SHARELATEX_SITE_URL SHARELATEX_SECURE_COOKIE SHARELATEX_BEHIND_PROXY In retrospect this does not seem to make sense, as it specifically refers to setups with behind proxies, but it did not make any difference either. I also removed SHARELATEX_REDIS_PASS following this post: Lastly, I wonder about that neither Redis or Overleaf produce a folder in my appdata directory, mongoDB does - is this behavior normal ? Can anyone point me in the right direction please ? Also happy to give more info. Many thanks in advance.