Mainfrezzer

Its a weird and very rare quirk of one of the gui check scripts that can ocasionally happen when the array/pool start and it takes a tat too long while the drives are being decrypted.

Nothing to worry about.

Havent seen that in a couple versions, as it was spoken about in the past so interesting to know its still happening.


Edit:

I found it!

https://forums.unraid.net/topic/195209-unraid-os-version-721-available/#findComment-1591570

wrong devices, you backup the md*p1 devices

delete the dashboard_setting.json on your flashdrive. its in /boot/config/

That issue is caused by using listing height fixed with unraid connect (or just having beta.3, which also gives you the perk of having a wonky Pluging page and a broken VM page).

Will hopefully be fixed soon.


Edit:

Heres a screenshot where to find it

set that to enabled

You have to place the .conf file in /mnt/user/appdata/copyparty like this


The whole program is extensive and i only dabbled with it a tiny bit



[global]
p: 3923 # listen on ports 8086 and 3939
e2dsa # enable file indexing and filesystem scanning
e2ts # and enable multimedia indexing
z, qr # and zeroconf and qrcode (you can comma-separate arguments)
# create users:
[accounts]
test: 123 # username: password
# create volumes:
[/w] # create a volume at "/" (the webroot), which will
. # share the contents of "." (the current directory)
accs:
r: * # everyone gets read-access, but
rw: test # the user "ed" gets read-write
Thats a very basic config as example

Der NIC verliert andauernd die Verbindung so wies aussieht.

Es ist definitiv ein Versuch wert das EEE Zeugs in der go file zu deaktivieren und dann zu gucken wie es sich verhält. Das EEE hatte zumindest bei mir schon seit der Beta Probleme verursacht mit dem neuen Kernel.


Edit: Der Intel GPU Call Trace ist schon etwas wilder

you probably logged into ghcr.io with docker at some point and the token ran out/permissions arent right.

 
docker logout ghcr.io  

Der ZFS Treiber für Docker wird nicht empfohlen weil das Probleme verursachen kann. Overlay2 sollte das zumindest verhindern. https://docs.unraid.net/unraid-os/release-notes/7.0.0/#add-support-for-overlay2-storage-driver
(besonders wenn diese shares auf xfs schreiben dürfen)
Davon abgesehen, wurde die Konfiguration von dem System Share vermurkst und existiert 2x, einmal als system.cfg und System.cfg. Löschen und neu speichern um das zu beheben. 

Wifi support will come soon based on the work done 

I would say, you fucked around and found out.

Reboot will fix that, unless you actually put that in your go file, then remove that line via the webgui or worst case by pluggin the usb into another pc to edit it out

Its as fast as the slowest disk is, if my memory serves me well, the 1 TB you use should absolutely fall in that speed that you observe, especially once you reach the end of the platter. If im not mistaken now, you should be about to reach the 1TB threshold, once that it is cleared, it should get faster since that drive does not contain any data to be tracked (if nothing is using the array at the same time)

Ich glaub es heißt da abwarten und Tee trinken, obwohl nen Downgrade auch möglich wäre um zu gucken ob es genau der selbe Bug ist
https://gitlab.com/qemu-project/qemu/-/issues/2571

 

yes, (for the gui mode mainly)

upgrade to 7.0.1, that should resolve your issue
 
 

try macvlan instead of ipvlan in the docker settings. seems like your router doesnt like mac addresses with multiple ips.

Have you ever tried to open the "Settings" page and going to "Management Access"?

This is getting really strange. At this point it might be easier to recreate the docker image

If you stop docker and start it again. Grab the output from the syslog after 
rc.docker: Docker daemon...  Started.
rc.docker: Starting network...


and if there is a message with "is already using parent interface br0" again

take the name, thats displayed, in the syslog message. As it was "network di-b3c2cf3baf6e" before and then type "docker network rm b3c2cf3baf6e"

obviously, you need to change it for whatever its gonna display in the syslog.

Schritt 1. Bau den Container
(Folgende Bilder sind nur exemplarisch)


Wenn der Vorgang erfolgreich war


gehts zu

Schritt 2.
(Das Template muss schon angepasst werden mit den Variablen die man selbst braucht, hier gehts nur ims Image)



Speichern und dann sollte das Ergebnis ungefähr so aussehen

Reading the changelog sometimes does wonders

 
Go on Tools and then on Preclear Disk (url would be serverip/Tools/Preclear)

Docker Service stoppen und dann einfach auf macvlan umstellen.

Remove the mapping that is pointing to /etc. thats fucking it up

this one

 
-v '/mnt/user/appdata/lms/config/':'/etc/':'ro'

I have no clue for what its needed BUT if its important, change the read-only to read-write

 
-v '/mnt/user/appdata/lms/config/':'/etc/':'rw'  

you have to enable websocket support


Edit: In case you have no clue how to do that in nginx, this needs to be in there
 
proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1;  

1: ive no clue
2: yes, you can also just copy paste the hole zip by hand and then subsequently run the "make_bootable.bat"