Goldmaster

It was taken from the krusader video That was on the old drive, the one that is showing hardly full, is the newer, larger drive. That's not a problem, as i don't need to access the drive over a network, only physically on the machine. It is strange how It's decided to work fine (for now).

Hi there, this is quite an annoying issue I have seen. I have 2 external drives that seam to not be showing up. i use luckybackup to mirror my shares onto the external drive. the external drive has filled and I have moved over to newer hard drive with larger capacity. So I dont have to change anything in my docker container, I had renamed the old hard drive by adding old to the end, and the newer larger hard drive named as my original hard drive. Problem is that both dont seam to want to show up. They both show up fine on another Windows pc and will show up without issue when passed though to windows 11 vm. But in krusader when I go to access the drives, i get nothing showing up for ages. i know it takes quote some time but never as long as this. This is what I am getting, its as if the drive is mounted but nothing is showing? Why was there such a long delay when windows would normally show drives instantly and now seams to not be working at all? The hard drive names are not conflicting at all. If i try and browse to the hard drive in terminal, i would get i/o error. External drives in the docker container of krusader are set to rw slave. I will add that it seems similar to this issue and have added my diagnostics file. Ok this is strange how generating a diagnostics file seams to have made the hard drive contents show up but krusader is quote slow. it seems that I am able to access the content though an unassigned folder, not via mnt/disks Can someone please explain this phenomena? hammerthread-diagnostics-20230301-1019.zip

Yes I have, I think its something to do with the docker container using the default https port that unraid uses, so there is a conflict. Update The network setting has to be Custom : br0 and then just put in a port value. Not sure why the docker opens at port 8080 still?

Just a quick question, for some reason when I press the web ui globe icon, the megasync docker container opens to port 8080. Even though I have changed to a completely different port. I can't remember how I was able to access the web ui. I have tried custom docker network and bridge.

Running the plugin right now and is very useful to have. A useful feature would be a feature to shut down or put a server to sleep once the pre clear is done? The plugin could tell dynamix s3 sleep not to shut the server down or put it to sleep if a pre clear is running

Will there be a fix in the container so that this doesn't have to be added. Took me ages to figure out that I had to add this to extra parameters. Could be useful to add the info into the docker container.

sadly this seams to not start as well checked ports and everything else. been running for an hour and nothing

Hi there, im getting the issue of directory bread errors found. unraid starts fine without any issue. I have tried file check without issue. I can only assume that my usb stick drops offline and then reconnected itself. cable is ok as i wont be getting this issue. I have got my diagnostic file. hammerthread-diagnostics-20221122-1137.zip

I had issue with memory integrity where windows 11 instantly blue screens after windows suggests to enable core isolation protection. The fix is to boot into safe mode, then open windows defender and switch off that way. Or manually edit the registry

Thank you. only issue is that some files have seamed to copy. Maybe duplicate but running mover doesn't move and replace. is there a way to say run say sudo mv -r /mnt/cache /mnt/disk1 or something like that? idearly in gui frendly way. Issue was that my server had gone to sleep, so hasn't been able to move everything in a whole go?

Thank you. So its a case of copy stuff off the samsung drive to the wd drive. but im not sure how this cache pool thing works, I take it is a case of set wd drive as cache, then stop vm and docker service and copy stuff from samsung drive to wd drive. Unassign Samsung drive from unraid. install windows or debian on the drive?

Humm. Didn't think of that. Not sure how I would go about moving appdata, domains ect off the Samsung drive to the wd drive. There is space to do it.

Iam afraid not. it is the only m.2 drive I have, and the other is used for cache. I have tried Debian install and I still have the exact same error. I am on bios version 0701.

I hope @limetech can add this as default as a slight fix. Just testing Windows 11 as a vm and this fix solved it for me as i had code 43 errors. i take it that nvidia is making it much harder to run gpus in a vm envioment?

I have tried 6.11 and I am still getting issues. its deafeningly the m.2 drive. I don't know why or how.

yes there is, so not sure if group permissions for folders are meant to have read, write and execution ticked and files for owner set to execution as well? I think all the tick boxes are ment to be ticked so that the numeric value for folders and files is 777?

the files are being downloaded from mega onto the unraid server and it is being ran with uid 99, gid 100, and umask 000. the files are not corrupted or anything as i can view them fine in the mega app

Sorry, its the megasync docker container

hi there just a minor issue. for files that have been synced down onto a shared folder, the files are showing as rw and thats it instead of rw rw rw. so when i access the share in windows, i can't open any of the files. I guess I have to chmod 777 the folder and files? any chance of a fix or what might be causing this issue?

Im having same issues with the web. page doesnt load, but only in inconeto.

I think something has covertly changed my xml or something as I did this exact fix marked as solved but when i waked my server from sleep, the vm now doesn't want to boot at all. even with this fix. I take it should be like this <features> <acpi/> <apic/> <hyperv mode='custom'> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> <kvm> <hidden state='on'/> </kvm> </features> Even with the xml set like this, it fails to boot and I get 2022-08-01T11:36:43.432586Z qemu-system-x86_64: vfio_err_notifier_handler(0000:2d:00.0) Unrecoverable error detected. Please collect any data possible and then kill the guest The only thing I have done is removed the nvdia plugin and that was it. it seams to have had issues waking from sleep. After trying out the fix and brefly working, I have (once again) downgraded to 6.9 its strange as if the m.2 drive cant boot. tianocore really need to fix these kind of issues. I wonder if unraid do patch the issue they could submit a merge request so that others will receive the same fix?

little strange with this issue. if you dont have the nvidia plugin, then even with that fix. the vm will still not work. i removed the nvidia plugin as i think there maybe a conflic between foldingathome wanting to use the gpu and the vm using the gpu. not sure why as i can fold fine on cpu.

Where have you read this? Bit strange for a perfectly working gpu to have issues like this. its quite modern only 2016. Id more likely guess that latest hardware would have temporary issues if open source drivers are not available or been updated for support.

I did try vnc and that failed. I think it maybe that I have to reinstall windows 11 as I updated from windows 10 to 11. My motherboard does support windows 11 out of the box.

Hi there, is there a way to backup any projects that you have starred to zip files? Please.