Leaderboard

Habe ich zufällig gerade entdeckt, jetzt werden die Toshibas nochmal interessanter: https://www.hardwareluxx.de/index.php/news/hardware/festplatten/61040-ab-jetzt-direkte-herstellergarantie-bei-toshiba-mg-enterprise-laufwerken.html

Well, Frigate, it's not that important. 😉 (Sorry - I just couldn't resist.)

Alright, got it working again with a forked image. If anyone else wants to try (I do recommend spinning up a different copy, just for testing purposes). All you have to do is swap the repository of the GUS package / Docker container to this (right-click the Docker Containers Icon --> Edit --> find "repository"): kylek29/grafana-unraid-stack-2023:latest That is a new forked image, which adds additional layers to the grafana-unraid-stack image by testdasi. Changes made: Add a new install script that will install the new apt-key certs from Grafana/Influxdb, then reinstall latest InfluxDb/Telegraf, and perform clean up. Added tweaks to the healthcheck command so that it fires every 30seconds and will wait 30seconds for the machine to start (I noticed it often failed with the original images 0s parameters). Fixed a bug where the healthcheck status would fail and not detect the Grafana Server pid. It will now display the proper statuses of starting, healthy, and unhealthy. Fixed an issue where Tini (init handler) was failing. To look at the code and Dockerfile, see here: https://github.com/kylek29/misc_code/tree/main/unRAID/Grafana-Unraid-Stack For general usage, see the original post. This is just a fix layer.

https://virtio-fs.gitlab.io/howto-windows.html

Hi there, sharing experience and a guide on how i got this working.. Unraid version: 6.12.0-rc5 Hardware: ASROCK X670E PRO RS + AMD Ryzen 9 7900 + DDR5 + Cache NMVE I have been trying to get the plex container to transcode using hw but was not succesful until I found somebody in Reddit referencing this dockerfile in github. This is the first time I build an image so after few tinkering I think I got it to work. Here are the steps I used incase anybody see this relevant. Github: skjnldsv/docker-plex As I said, this is my first time I build an image. I went into plex and created a text file dockerfileplex.txt and copied the code in github into it. I could see in the dockefile the person is loading the standard plex image but with a series of modules, libraries....I am not an expert on docker so dont understand 100% I used the following CLI command to build the image: docker build - < dockerfileplex.txt After few minutes, the image is created and you are given an image id: in my case this was: 07804fbb5c05 Then I used the usual code I use with the standard plex docker to create a new container but referencing the image I just created before: in my case this was: docker run -d \ --name=plex-amd \ --net=host \ -e PUID=1000 \ -e PGID=1000 \ -e TZ=Etc/UTC \ -e VERSION=docker \ -e PLEX_CLAIM= `claim-GLgDsgXXXXXXXXXXX_` \ -v /mnt/cache/appdata/plex-amd:/config \ -v /mnt/user/Media:/media \ --device=/dev/dri:/dev/dri \ --restart unless-stopped \ 07804fbb5c05 You can see the new plex container in the list of containers in unraid and you can stop start restart as usual. once this was up and the setup of the server is up, hw transcoding is working and I managed to get 3/4 streams working on the same time. I installed AMD Radeontop tool and I show below the usage of the iGPU for transcoding...when that picture was taken only one stream was on. Ig any question, please comment and will do my best to guide on the process above.

Make a backup of /config/network.cfg on the flash drive Then first try making a change (any change) to the bond0 / br0 entries and apply. If it didn't refresh it to get rid of the extraneous entry, try to edit it (any editor should work) and delete this section IFNAME[5]="eth7" PROTOCOL[5]="ipv4" USE_DHCP[5]="no" IPADDR[5]="192.168.60.200" NETMASK[5]="255.255.255.0" and then all the sections after it rename them from [6] to be [5], [7] to be [6] etc.

The reference is there. Part of bond0 [eth0] => Array ( [DHCP_KEEPRESOLV] => yes [DNS_SERVER1] => 8.8.8.8 [DNS_SERVER2] => 8.8.4.4 [DNS_SERVER3] => [DHCP6_KEEPRESOLV] => no [BONDING] => yes [BONDNAME] => bond0 [BONDNICS] => eth0,eth1 [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => yes [BRNAME] => br0 [BRNICS] => bond0 [BRSTP] => no [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => no [IPADDR:0] => 10.10.50.200 [NETMASK:0] => 255.255.255.0 [GATEWAY:0] => 10.10.50.1 [METRIC:0] => [USE_DHCP6:0] => yes [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => access ) [eth2] => Array ( [BONDING] => no [BONDNAME] => bond0 [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => no [BRNAME] => br0 [BRNICS] => [BRSTP] => 0 [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => no [IPADDR:0] => 192.168.70.200 [NETMASK:0] => 255.255.255.0 [GATEWAY:0] => [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => access ) [eth3] => Array ( [BONDING] => no [BONDNAME] => bond0 [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => yes [BRNAME] => br3 [BRNICS] => eth3 [BRSTP] => no [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => [IPADDR:0] => [NETMASK:0] => [GATEWAY:0] => [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => trunk [VLANID:1] => 4 [DESCRIPTION:1] => forexLAN [PROTOCOL:1] => ipv4 [USE_DHCP:1] => yes [IPADDR:1] => 169.254.31.118 [NETMASK:1] => 255.255.0.0 [GATEWAY:1] => link [METRIC:1] => [USE_DHCP6:1] => [IPADDR6:1] => [NETMASK6:1] => [GATEWAY6:1] => [METRIC6:1] => [PRIVACY6:1] => ) [eth5] => Array ( [BONDING] => no [BONDNAME] => bond0 [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => no [BRNAME] => br0 [BRNICS] => [BRSTP] => 0 [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => no [IPADDR:0] => 192.168.60.200 [NETMASK:0] => 255.255.255.0 [GATEWAY:0] => [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => access ) [eth6] => Array ( [BONDING] => no [BONDNAME] => bond0 [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => no [BRNAME] => br0 [BRNICS] => [BRSTP] => 0 [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => [USE_DHCP:0] => [IPADDR:0] => [NETMASK:0] => [GATEWAY:0] => [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => access ) [eth7] => Array ( [BONDING] => no [BONDNAME] => bond0 [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => no [BRNAME] => br0 [BRNICS] => [BRSTP] => 0 [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => no [IPADDR:0] => 192.168.60.200 [NETMASK:0] => 255.255.255.0 [GATEWAY:0] => [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => access ) [eth8] => Array ( [BONDING] => no [BONDNAME] => bond0 [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => no [BRNAME] => br0 [BRNICS] => [BRSTP] => 0 [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => yes [IPADDR:0] => [NETMASK:0] => 0.0.0.0 [GATEWAY:0] => [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => trunk [VLANID:1] => 5 [DESCRIPTION:1] => 10G_LAN [PROTOCOL:1] => ipv4 [USE_DHCP:1] => [IPADDR:1] => [NETMASK:1] => [GATEWAY:1] => [METRIC:1] => [USE_DHCP6:1] => [IPADDR6:1] => [NETMASK6:1] => [GATEWAY6:1] => [METRIC6:1] => [PRIVACY6:1] => ) [eth9] => Array ( [BONDING] => no [BONDNAME] => bond0 [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => yes [BRNAME] => br9 [BRNICS] => eth9 [BRSTP] => no [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => yes [IPADDR:0] => [NETMASK:0] => 0.0.0.0 [GATEWAY:0] => [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => trunk [VLANID:1] => 5 [DESCRIPTION:1] => 10 G_LAN [PROTOCOL:1] => ipv4 [USE_DHCP:1] => [IPADDR:1] => [NETMASK:1] => [GATEWAY:1] => [METRIC:1] => [USE_DHCP6:1] => [IPADDR6:1] => [NETMASK6:1] => [GATEWAY6:1] => [METRIC6:1] => [PRIVACY6:1] => ) [eth10] => Array ( [BONDING] => no [BONDNAME] => bond0 [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => no [BRNAME] => br0 [BRNICS] => [BRSTP] => 0 [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => no [IPADDR:0] => 192.168.70.200 [NETMASK:0] => 255.255.255.0 [GATEWAY:0] => [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => access ) [eth11] => Array ( [BONDING] => no [BONDNAME] => bond0 [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => yes [BRNAME] => br11 [BRNICS] => eth11 [BRSTP] => no [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => ipv4 [USE_DHCP:0] => yes [IPADDR:0] => 169.254.132.255 [NETMASK:0] => 255.255.0.0 [GATEWAY:0] => link [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => trunk [VLANID:1] => 4 [DESCRIPTION:1] => forexLAN [PROTOCOL:1] => ipv4 [USE_DHCP:1] => [IPADDR:1] => [NETMASK:1] => [GATEWAY:1] => [METRIC:1] => [USE_DHCP6:1] => [IPADDR6:1] => [NETMASK6:1] => [GATEWAY6:1] => [METRIC6:1] => [PRIVACY6:1] => ) [eth12] => Array ( [BONDING] => no [BONDNAME] => bond0 [BONDNICS] => [BONDING_MODE] => 1 [BONDING_MIIMON] => 100 [BRIDGING] => no [BRNAME] => br0 [BRNICS] => [BRSTP] => 0 [BRFD] => 0 [DESCRIPTION:0] => [PROTOCOL:0] => [USE_DHCP:0] => [IPADDR:0] => [NETMASK:0] => [GATEWAY:0] => [METRIC:0] => [USE_DHCP6:0] => [IPADDR6:0] => [NETMASK6:0] => [GATEWAY6:0] => [METRIC6:0] => [PRIVACY6:0] => [MTU] => [TYPE] => access ) )

This just solved a problem I've been having periodically. I was experiencing the 'bad time' from using an IP. thanks

...und dabei, eben bei den RCx-Versionen von unraid, Beobachtungen gemacht, was eben bei einer solchen "Migration" - die letztlich jeder User mal irgendwann machen muss - nicht funktioniert. Man kann in unraid als User nicht viel falsch machen...alles wird übers UI "gesteuert/gepflegt" und unraid läuft im RAM. Einziges Element, wo man selbst von Hand was verbocken könnte ist der GO-File auf dem Stick. Die verschiedenen Varianten einer Config, die durch Installation und Konfiguration von Plugins, Apps/Dockern und VMs entstehen, und dann auf einen neuen unraid Version (neue Versionen vom Kernel und notwendigen Tools und Programmen einer Distribution) noch funktionieren müssen, kann ein Developer nicht alle durchtesten Deine Beobachtung hilft den einzelnen Developern dabei, problematische Konfigurationen zu entdecken und zu analysieren, was da schief geht und auch bei anderen Usern schiefgehen kann/könnte - und Gegenmassnahmen zu ergreifen, die andere User vor dem selben Schicksal bewahren. Selbst wenn es ein "False Positive", aka User-Error ist, hilft das weiter. Community lebt vom mitmachen...Nehmen & Geben.

This was true with cheap routers 15+ years ago but all recent decent routers should have a means to reserve IP addresses within it DHCP pool range for use by devices that require static addresses. (My router actually has a feature which will convert a currently assigned DHCP address into a static address that is linked only to the MAC address of the currently assigned device. This means the computer will always get that IP address even if it uses DHCP. If I manually assign a IP address to be static, I have to have the MAC address as a part of the process.)

I've added a Recycle Bin setting to hide the .Recycle.Bin folder in the next release.

Hat geklappt 👍

...würde ich mal machen...vorher den redis Docker stoppen und den zugehörigen appdata Ordner mal sichern/kopieren...just in Case...

It has been known for some time that going through the fuse system used to support User Shares imposes an overhead that can limit maximum performance. The 6.12 release has an optimisation for what are currently known as "Cache Only" User Shares that by-passes the fuse system if a share only exists on a pool thus achieving the equivalent to the above without the user having to actually change their settings.

...sehr, sehr komisch....evtl ein Problem mit dem Stick? Aber dann mach mal ein Update auf die neueste 6.12RC6...da ist ein neuerer Linux Kernel dabei..evtl. läut es dann mit den USB3.2 Treibern besser? Jaja, es wird schon am Chip im dem Gehäuse liegen...aber evtl. in Kombo mit dem Brix...daher wäre als letzte Alternatuve einen USB Hub dazwischen zu schalten, der die beiden Interface Standards trennt.

It's been couple of days now, and the "pci=noaer" is working so far. Thank you!!

Sorry, aber euch ist schon klar, dass die GUI kein Passwort hat? Jeder doof in eurem Netz könnte auf die Art den ganzen Server platt machen.

...Deine Ausführungen sprechen in Rätseln...daher evtl auch 130 Hits und keine Antwort bisher? Die Anleitung ist für zwei Ubuntu Server...hat nix mit unraid zu tun und die Anleitubg hat auch nicht viel mit einem VPS zu tun. Ein VPS ist keine normale "Site"... nur weil Du da ubuntu installierst, heisst es nicht, dass Du vollen Zugriff auf die Netzwerk-Konfig hast - oder eben doch, was Du dann extra, selbst absichern musst. ...und daher verstehe ich Deine Ausführung leider garnicht...Du hast in unraid das WG-Plugin/Docker installiert und bis dann mittels putty und CLI-Befehlen aus der anderen "Anleitung" darauf losgegangen? Was erwartest Du denn dann davon für ein Ergebnis? Ich selbst nutze das WG Plugin in unraid nicht, sondern lokal einen "richtigen" Router mit direkter Wireguard Anbinding. Auch nutze ich einen VPS, der eigene Images erlaubt und daher habe ich da ebenfalls eine Router-VM mit Wireguard am Start. Daher kann ich wenig hefen. Kopieren von Schritten aus einer Anleitung, die nichtmal ansatzweise zu Deiner Umgebung passt führt eben nicht zum Ziel....und macht Deinen VPS (später auch Deinunraid, wenn der Tunnel steht) zum Einfallstor des Bösen. Mein Tipp wäre schrittweise, systematisch vorzugehen. So lernst Du auch, wie die Teile zusammenpassen und bei Problemen die Stellen einzugrenzen, wo es klemmt....fang also schrittweise an. Die Idee mit dem VPS ist nicht verkehrt. Suche Dir eine Anleitung, die auch die Firewall der VM sicher konfiguriert und eben nur WG Verbindungen durchlässt Fang damit an, WG Verbindungen anderer Clients, zB vom Phone (über LTE oder vom Sofa, über WiFi) oder Laptop mit dem VPS zu testen (auch gut für später, bei Problemen). WG ist ein Mesh, kein Site-2-Site/Client-Server VPN...es schadet nix und hilft später Probbleme zu debuggen. fang auf Seiten unraid neu an...konfiguriere das Plugin allein über das UI....hier im Forum gibt es bestimmt einen Support-Thread dafür. Wenn Du den VPS mit einem anderen Client am laufen hast, füge den unraid-Peer hinzu. Im Plugin musst Du als Erstes die Schlüssel generieren und dnn den öffentlichen Schlüssel wieder im VPS als unraid-peer hinterlegen. dann im Plugin noch den VPS als Peer Endpunkt eintragen. Dann sollte unraid die Verbindung zum VPS initiieren - wenn der Tunnel dann steht, ist der dann bidirektional. probiere den Tunnel aus ... Tools wie "ping" und "traceroute" (Win: "tracert") sind hilfreich ... verwende IPs, keine DNS Namen, also bei traceroute den Paraeter "-d" dabei nicht vergessen. Wenn der Tunnel zwischen unraid Host und VPS steht, kümmere Dich ums Routing der anderen Peers und um die erreichbarkeit von Dockern oder anderen Hosts im LAN. ...hope it helps.

No, the pre run script should be executed before the source check. That seems to be a bug. Or rather a misplacement. I wonder why it is checking retention after those error. I check this as well.

You can, you'll need do send one snapshot per disk, but it's not a problem as long as the pool has enough space, e.g.: zfs send disk1/dataset_name@snapshot_name | zfs receive pool_name/disk1 zfs send disk2/dataset_name@snapshot_name | zfs receive pool_name/disk2 etc These can also be incremental after the initial snap send.

I know this isn't comprehensive because I've spent a whopping 5 minutes looking at the syslog you uploaded, but there are some issues with your CPU and the Linux kernel used on this version of unRAID. Note this message: ACPI BIOS Error (bug): Could not resolve symbol [\_SB._OSC.CDW1], AE_NOT_FOUND (20220331/psargs-330) Reference: https://bugzilla.kernel.org/show_bug.cgi?id=213023 There may be further issues that would be easier to see outside of unRAID, such as doing a memory test to see if you have any RAM instability, etc. While I love how Linux stuff can run on anything, it can also... run on anything. Garbage in, garbage out, right? Still, you might try a newer version of unRAID (like 6.12 RC6 that released yesterday or the day before) to see if it's happier with your CPU. But again, this smacks of hardware (with a sprinkling of kernel-hardware incompatibility). I'll keep perusing and see if I find anything else specific you can look at.

UD mounts the share from ServerB within /mnt/remotes/someName. To get plex to see it, you add another Path to the template (edit Plex), and give it a host path of /mnt/remotes/someName with a container path of something like /ServerBMedia The within Plex, you edit the applicable library and add in /ServerBMedia to its list of folders. Rescan the library and they should all be there.

Nono. open your eyes :-))) the sorting of the list is just... strange. I once had this card too (its one with the widespread Aquantic Chipset), it CAN do 10G, but it is not recommended for Server use, it lacks many features to fulfill multiple requests and so on. Better get a real card from Intel or (used) Mellanox. Still, no idea why it is locked to 5G, maybe it thinks, there is not enough cpu power to handle 10G? (as I said, this card does not do much with offloading stuff..., its a cpu hog) But then, the switch could be fooled by the strange list too. Usually the list is sorted low to high speed, so one (like Jorge) could expect the last entry to be the fastest one. Maybe the Switch just always picks "last in list"? BTW: don't get fooled by the switch telling you, it would be a 10G connection. Many brands do report everything >1G as 10G, they dont know about 2,5G or 5G at all (with proper flow control they still work correctly with these lower speeds). You should try to FORCE the card to use 10G (usually you should force this on the switches' side, but because it already believes it is, forcing would not help I guess, but you can try, it wont harm anything) BTW2: even if you manage to establish a real 10G link with this card, don't dare to expect to see real 10G transfers. The best I ever got out of it was about 800Mb/s instead of 1100Mb/s. And not for long too...

I am running Z2. For my use case, any more than that would be excessive. These are WD Red Plus drives, so they should be pretty reliable. And all important data on this server will be backed up to a secondary server made from my old nas.

Did you use UD to create and manage the shares? Post diagnostics.

It's not recommend to use USB drives for Unraid. Their connection is unstable. Which means the USB HDD is running. Or are this even multiple HDDs?! Finally you should measure with the least amount of components possible, which means without those HDDs at all. As of my experience WD Black have negative impact on C-States and they can cause PCIe errors in the logs because of ASPM incompatibly. I don't know if it's because of the RGB, but a similar model is extremely inefficient: https://www.tweakpc.de/hardware/tests/netzteile/corsair_cx_f_rgb_550_650_750/s02.php I recommend PicoPSU or RM550x. But even now it does not explain the 63W which is measured through your USP. Are you sure its accurate? Or is your external USB HDD Case included?!

No one is forcing you to use ZFS, if you don't need or care for it don't use it.

I also like the second better, but either one looks great!

A quick follow up on how well this is working. I have the User Script cron job set to run twice a month, on the 14th and the 28th. Yesterday was the first time where the script ran automatically, where I wasn't triggering it while sitting beside watching. (After all, isn't automating things the reason we do this stuff?) I was sitting in a diner having breakfast, 200 miles away from home, when the attached Telegram texts started coming in. Don't you love when a plan comes together? 😁

you dont need to use the pia wireguard generator at all, i do all the hard work for you, all you need to do if you wish to switch endpoint is change the 'Endpoint' entry in the file /config/wireguard/wg0.conf, if you have edited this file or replaced it with a generated version then i would recommend deleting the file and restarting the container to get you back to a working state, then edit the file /config/wireguard/wg0.conf and change the line ENDPOINT to be the endpoint you want to connect to, e.g.:- Endpoint = slovenia.privacy.network:1337 not true, you can use either, the recommendation is always hostname, servers get shutdown all the time and if you tie yourself to an particular server (specify ip) then sooner or later you are in for a bad time.

Wenn du genau weißt das die parity ok ist kannst du es genau so machen. Ich hatte mal probleme mit einem Datenträger und musste das genau so machen , da der Datenträger als Fehlerhaft rausflog (In der zeit wurden keine Daten geändert), da ich mit Powertop rumexperimentierte und die erweiterungskarte wenn ich sie schlafen schickte die Sata Verbindungen abgeschossen hat und dadurch eine Fehlermeldung erzeugt wurde der Datenträger wäre fehlerhaft. Alles wieder richtig einbinden in die Slots (genau wie vorher) und sagen die Parität ist Valide.

I have the same Problem. OS Version 6.11 I dont like to delete all cookies. Instead, i use Chrome, if the noVNC Tab open, i go to the upper left Corner ("not safe" in Adress Bar (http/s)) an left Klick on it. There i can delete the specified cookies. Thats help me.

I am certain I have pinned down the problem. If you have large amounts of ram, and because vm.dirty_ratio is 20%, the mover is first writing to ram. For a long time, since you have lots of ram. It fills, and for some reason, the OS decides to write the buffer in a blocking manner to the disc. Blocking means no other IO on that drive until it is done. It starves all other processes of reads. What I have found out is, that when you reduce vm.dirty_ratio to 1%, you get more frequent "short" reads inbetween the writes, thusly giving plex a chance to serve the content. You will however impact writing performance if you set it too low. RIP Ram. Unraid needs to find a way to bypass the write cache for the mover, or needs to find a different solution to resolve the blocking IO problem. Maybe even try a different scheduler, one that always prioritises reads over writes - if that is possible.

SFTP in AMP uses ports like 2223,2224,2225 ext.... doesn't use the standard port of 22. But the main AMP core service uses 2223 which can access all servers with that one. Just hope my research in this helps Other users that are interested in this docker so they don't run into problems 😃

For me the solution earlier mentioned by isaacery was to create a new VM with exact the same configuration as the one which does not work (with the primary vDisk location pointing to the correct old disk). The new VM booted instantly without any problems. My problem started when I changed the Graphic card from VNC to the GPU (and back again as the VM did not start anymore). In VNC I got the message "Guest has not initialized the display (yet)".

Start a terminal session from unRAID GUI and type modprobe i915 if you get no errors, type the following: cd /dev/dri ls If all is well you should see the files indicated in the /dev/dri folder. If it all looks good and the drivers are loading, you should modify your go file on the flash drive to load the i915 drivers when the server is booted. I have the following entries in my go file. I am using hardware transcoding in both Plex and HandBrake. #Setup drivers for hardware transcoding in Plex modprobe i915 sleep 4 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri