Pete0

Hast du irgendwelche Docker am Laufen, die ggfs. auf einen Share zugreifen. Ich hatte z. B. das Thema mit dem Nextcloud-Docker. Ab einer bestimmten Version wurde die Festplatte, auf dem der Share für Nextcloud liegt, nicht mehr runtergefahren. Kannst du hören, dass die Festplatte in den Spin-Down geht und paar Sekunden später wieder startet? Oder fährt es gar nicht erst runter? Was für Platten sind es?

Is answered in the blog post.

Now I feel bad because my Basic license barely pays a single hour of a developers salary and I am using unRAID for exactly 2 years now. 😁

The blog post contains more information. It says: So I guess there is no time limit.

Today I was offered an update to the MariaDB container and installed, which I normally always do. Checking the protocol after starting I saw this messages: 2024-02-14 18:46:48+01:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.2.3+maria~ubu2204 started. 2024-02-14 18:46:48+01:00 [Note] [Entrypoint]: MariaDB heathcheck configation file missing, assuming desirable 2024-02-14 18:46:48+01:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade or creating healthcheck users) required, but skipped due to $MARIADB_AUTO_UPGRADE setting I know of the need sometimes to upgrade mariadb after an update but this time the message contains something of a healthcheck. Yet I still tryed to upgrade the database which was not required according to the output of mariadb-upgrade. I found out that the container has a shell script healthcheck.sh included but I don't know how to run it properly - or what exactly to do to get rid of the message. EDIT: I just added the environment variable MARIADB_AUTO_UPGRADE to the container - because I always intended to in the past so I wouldn't have to manually upgrade when necessery. After restarting the contianer with the variable the message was gone. Not sure why the manual upgrade didn't fix the issue but setting the variable seems to have done so. Maybe there is a parameter for mariadb-upgrade that I didn't use. 2024-02-14 18:58:21+01:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.2.3+maria~ubu2204 started. 2024-02-14 18:58:21+01:00 [Note] [Entrypoint]: MariaDB heathcheck configation file missing, assuming desirable 2024-02-14 18:58:21+01:00 [Note] [Entrypoint]: Starting temporary server 2024-02-14 18:58:21+01:00 [Note] [Entrypoint]: Waiting for server startup 2024-02-14 18:58:22+01:00 [Note] [Entrypoint]: Temporary server started. 2024-02-14 18:58:22+01:00 [Note] [Entrypoint]: Backing up system database to system_mysql_backup_11.2.3-MariaDB.sql.zst 2024-02-14 18:58:22+01:00 [Note] [Entrypoint]: Backing up complete 2024-02-14 18:58:22+01:00 [Note] [Entrypoint]: Creating healthcheck users 2024-02-14 18:58:32+01:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.2.3+maria~ubu2204 started. 2024-02-14 18:58:32+01:00 [Note] [Entrypoint]: MariaDB upgrade not required

I understand the recommendation but with limited space on the share this is not an option. The logs mention nothing that points to a reason. Further, there is no read/write activity. In unRAID, on the driver overview page, I can see that not a single byte is read or written to/from the drive where the nextcloud share is placed. But still it keeps the drives spun up. Both, the share drive in the array and the parity drive.

Browser only.

I didn't use any clients to sync. I only accessed it outside my home network to upload/download files.

Since the last view updates (I don't know, maybe 3 or 4 docker container updates ago) the nextcloud container keeps on spnning my parity drive and the drive on which the nextcloud share is located up. Does somebody else see this behaviour? As mentioned, couple of version ago it was working fine. Yes, the drives had to been spun up, each time I enter the webinterface of nextcloud by still the drives were able to spin down. The share for nextcloud is setup as Cache -> Array.

@JorgeB thank you for the link. I did a CLEAR CMOS and loaded optimized defaults and went through the BIOS again. There is no such thing as "Power Supply Idle Control" although I could have sworn that in the past I have seen this setting. Maybe it was removed after a BIOS update. There are other settings though, ERP Ready, Energy Star Ready, CEC Ready. Tha later two I leave usually disabled. But I enable ERP Ready. I also disabled now global C-States. Will this mean that my power drop of the server will go up? Will it go up considerably? Also my ECC RAM is running on 3200 MHz. This is not a D.O.C.P Profile, in fact, there is no profile stored on the RAM. Can I just lower the frequency in the BIOS for the RAM an expect no problem? As far as I know the highest supported speed is 3200 MHz. Not sure if lowering it would give me any benefit.

This morning at 8am my server shutdown and rebooted again. We had some storms in the past days and nothing happened on the server. Once I even saw the light flicker but the server was still running. This morning there were no storms. At least not visible to the eye that could cause any electrican interference. Until this morning the server was again running for about 2 or 3 weeks without any issue. It's just confusing to me. I looked through the log file and didn't find anything special. Maybe someone else does. It just needs a clean up of the many autofan messages. The server is now again doing a parity sync unraid-diagnostics-20230827-1117.zip 2023-08-27-unraid.log

@Joly0 steht was im log?

Um mein Problem zu analysieren habe ich ein USB Stick mit 32GB in einen bestehenden Raspberry Pi getan und darauf rsyslog eingerichtet, und unRAID in den Einstellung so konfiguriert, dass es dorthin loggen soll. Damit ebenen die Logs nach einem Neustart erhalten bleiben. Hat in Summe 20 MInuten gedauert und kann ich auf empfehlen, wenn du noch ein anderes Gerät in deinem Heimnetz hast.

I have. unRAID is now logging to a different server. Verified that it is working and now I am waiting for the next crash.

@kdwg Über eine SUV habe ich oft nachgedacht. So eine kleine APC zum sauber Runterfahren würde ja schon reichen. Aber ich lese immer wieder Berichte von Käufern, dass die Dinger stinken und da mein Server in der Wohnung steht, schreckt mich das sehr ab. Ich nutze Powertop Autotune. OOM sagt mir gar gerade nichts.