mgutt
Moderators
-
Joined
-
Last visited
Everything posted by mgutt
-
I replaced my SSD against a bigger one. I prepared this step by moving appdata from the SSD to the Array (while Docker was set to "no"). After replacing the SSD I was disappointed about the extremely low speed of the mover: As docker is set to "no" I stopped the mover by the "mover stop" command and used this command instead: rsync --remove-source-files --archive /mnt/disk6/appdata/ /mnt/cache/appdata & disown This caused an extreme boost on moving the files, because a simple rsync - instead of the mover - does not check for every single file if it is in use: Feature Request: If the docker service has been stopped and "appdata" files are moved, it should not use the "fuser" overhead. Instead it should move the files directly without any additional checks. This should not happen if "appdata" is an smb/nfs share and starting the docker service should be greyed out as long the mover is active in this special mode. The same could be done for the docker path and all other shares which are not smb/nfs shares I think. Or: Add a checkbox to the mover button, which allows starting the mover manually in "performance mode", which disables smb/nfs, docker and vm services.
-
My share "appdata" used my "cache" pool as an exclusive share. Now I wanted to replace the SSD of the "cache" pool against a bigger one. So I changed (without stopping the array) the "appdata" share configuration from: to: After that I started the mover and several hours later my nextcloud was broken (could not access relevant files). This was solved by rebooting the server. I assume that inside of the nextcloud container the mount to the exclusive share was still present, so it should not be possible to change this setting while docker is active. Sadly I didn't tested it inside of the Nextcloud container so I can't deliver the proof, but this seems to be the only plausible reason for me.
-
Vom Prinzip spricht nichts gegen Klettband. Viele nutzen das auch in Desktop PCs, um SSDs an ungewöhnlichen Stellen zu platzieren. Ich würde nur welches für den Außenbereich nehmen bzw welches was hitzebeständig ist. Ansonsten löst sich der Kleber.
-
Does this work? https://community.synology.com/enu/forum/1/post/140590
-
Bedenke, dass der Docker Dienst läuft. Vielleicht hat er in dem Moment Daten in die Image Datei geschrieben. Das Backup der Datei wäre dann eh kaputt.
-
Das docker.img konnte nicht gelesen werden, was beim laufenden Docker Betrieb evtl die Ursache sein könnte. Allerdings macht es auch keinen Sinn das zu sichern. Die Docker Umgebung (also das Image) enthält keine Nutzerdaten. Die liegen in appdata.
-
Einfach im Log nach fail oder error suchen. Ein Beispiel: Den Pfad gibt es also nicht.
-
You are probably using the host network for your container. The container setting to set the port forwarding has no meaning in this context. It is only active for the bridge network. Feel free to open a feature request at the official GitHub page of NPM to request for: - disable port 80 / http - Request a new VARIABLE to change the default ports 80 and 443 And/or use the bridge network.
-
Delete the container and then delete the directory /mnt/user/appdata/nginx-bla-bla The file manager plugin is useful for this.
-
Du hast nicht geschrieben wie weit der C-State nun runter ging und warum?! Ich würde erstmal eine Messung ohne alles machen. Manchmal sind es einzelne Slots und manchmal bestimmte Hardware.
-
I would say: Delete everything and restart from the beginning. Everything else sounds complicated: https://community.letsencrypt.org/t/certbot-renew-error-please-choose-an-account/206600/9 https://community.letsencrypt.org/t/please-choose-an-account-how-to-delete-an-account/212902
-
Ja, ich kann dir Komponenten raussuchen und bei Bedarf auch zusammensetzen. Am besten telefonieren wir mal und du beschreibst mir deinen Bedarf. Meine Kontaktdaten findest auf meiner Website: https://gutt.it
-
This should work: https://askubuntu.com/a/115625
-
Denkbar wären noch Nextcloud und Filebrowser.
-
Einfach nach der Modellbezeichnung googlen. Bei eBay gibt es zB was.
-
Naja. Die kommen sicher nicht vom Board und der CPU. Da läuft doch noch anderes im Leerlauf. Was hast du alles verbaut?
-
BTRFS macht nicht von sich aus die Sektoren kaputt. Entweder ist der RAM defekt oder die PCIe Verbindung der NVMe gestört. Letzteres ist ebenfalls in den Logs zu sehen. Bitte mal eine Diagnostics posten.
-
This isn't really helpful I think. I tested the Seasonic Titanium power supply and it's far away of being the best: https://gutt.it/seasonic-titanium-netzteil-bei-niedriglast-keine-option/
-
Has no impact regarding my tests: https://forums.unraid.net/topic/121551-erlaubt-der-neue-linux-kernel-stromsparende-amd-server/?do=findComment&comment=1337385
-
The go file should never be executed manually. It starts the unRAID WebGUI. You need to paste the commands line by line or use a separate script with the user scripts plugin. For example I'm not using the go file. I have a user script which gets executed on first array start. PS you should restart your server to avoid further problems with your execution of the go file.
-
Which are?
-
Yes. Sadly I can't find this newer version as download.
-
Jo, ich habe noch keine Enterprise SSD gesehen, die DIPM beherrscht und daher laufen die immer und ziehen alleine meist 3 bis 4W im Leerlauf pro Stück plus den Verlust der tiefen C-States, was auch noch mal 5 bis 10W ausmacht.
-
No. The display is switched off after some minutes. Then the Intel iGPU driver (which everyone should have installed) switches off the GPU. And as far as I know only then C10 is possible.
-
Maybe you could try to open a bug report: https://bugzilla.kernel.org/ Or learn C# or Rust, optimize the driver and pull it to the Linux Kernel 😅
