fired

Es wurde ein neues Gerät im (HomeAssistant) Docker angelegt

Gibt es denn irgendwo eine inoffizielle Liste mit SSDs im Array die bei Usern problemlos liefen? Ich habe hauptsächlich WD Blue 1 / 2 TB als Sata und NVME verfügbar und will beim Server Umzug auf SSD only array umsteigen.

Found a very simple solution: Just had to wait a few hours. Didn't change anything but everything is running now as expected. I think it might have been a timeout issue with the remote proxy after SWAG container update?

Hi! I was using onlyoffice for a while now and was going to check out the Nexcloud Office App now with Collabora-CODE Server. I installed a Collabora-CODE server as a seperate docker this morning, downloaded Nextcloud Office App and everything went absolutely fine. Then i updated the nextcloud docker from an early October 22 version to the current latest build. Now when I try to edit a document, the nexcloud office try load a file for some 10 seconds or so and then throw the error "failed to load nextcloud office please try again later". I tried to delete and reinstall nextcloud office which didn't help. The Collabora Docker WebUI is reachable and working fine. Settings Page of Nextcloud office confirm that the server is reachable. Has anyone an idea how to troubleshoot this error? Can't find anything office related in my nextcloud.log

Hi, i am running Homeassistant via HassIO as a VM on my unraid 6.9.2 server. Today afternoon, the Webserver of the VM crashed (was still accessible via SSH) and in VM Manager i got an error message with not enough memory available. Seems that the whole VM Manager crashed. I rebootet Unraid, and turned on the VMs again. Since the restart, every time i start my VM there is running a "qemu-system-x86" at 100% on the assigned core and HassIO don't boot. I have to force stop the VM that the qemu task disappear. A normal stop on the VM still keeps it at 100% CPU load. Any clue how i can bring the VM back to life?

Unfortunatelly, i cannot access any smart data, as the device to not show up in any tool except the Windows Disc Manager. Anything he tells me is that an E/A error occures while trying to initialize the disc. Doesn't sound promising

Hi, I have my unraid server up for 14 days now and added the 2nd disc (Both WD Red Plus 4tb), which should act as my Parity drive. Before including the 2nd Disc to the array i performed a prelcear. Pre-Read running fine up to 40%, then a dd error occured which then leading to a bunch of further errors at approx 4:30 am (see attached log). Next morning when I looked onto my Unraid Server, the disk do not show up as an unnassing device, neither within the preclear plugin. I then attached the disk to my Windows System - Didn't show up in BIOS, but in the Windows Disc Manager (diskmgmt.msc). However, i could no re-initialize the disc there. It is possible that the Pre-Read killed the HDD? Could it be an issue with the MB or its ATA controllers? System is a ASRock J3455-ITX. Any suggestion if there is a chance to recover the HDD? Thanks a lot in advance, Alex preclear.disk.txt