Napryc

Hi, switched to Ubuntu 24.04 as well, much better, although I had the feeling i was hanging much less after upgrading to latest Unraid release. However, I hava another issue with Ubuntu: a couple of times, I got black screen and only option was to force stop the VM... couldn't find a clue in logs about what happen ! Anyway, will stay on Ubuntu and try to sort this out! Happy new Year!

Well, I have one of my VMs (Debian 10) running a couple of dockers, but it's usually up for a short time for testing purposes, I'll have it running for longer time to see if it happens. I have one VM running usually all day with no problems, no docker and Debian 10 too. The Debian 13 VM hanging has no docker neither, and nothing fancy really, just being used for web development. I have another Debian 13 VM, but also used sparsely, no docker neither and no issue ; but I'll test it for longer time and see if it has the same issue!

Hi, did you finally figure out what caused your issue? I'm having the same behaviour, after some time, I lose keyboard and mouse on the VM, although I can still connect to it. It seems to me Debian 13 could be part of the problem, I have several VMs running, and the only one hanging is Debian 13! Best

Thanks, zpool import has been very useful, everything is back to normal now!

Ok, so I have received my new mobo, and reinstalled everything. Now, when I start Unraid, I can see the pools, but they are all set with one slot only, and no drive attached. All my drives are listed under the Unassigned Devices section. I had the Unassigned plugin installed, so I thought it could create some issues, removed it, but no difference (with the plugin, each drive had the proper mounting point being shown) Any suggestion? Should I just allocate the drives manually? I have the diagnostics zip from the crash, so I can probably get the organisation of the devices from there. Thanks!

No RAID controllers used , so that's great news! I knew it was the case for the classic unraid arrays, so I was hoping it would be the same for zfs pools! Thanks for confirming, I'll just have to wait for my new mobo now! Thanks!

Hello, over the last days, I've built my new Unraid server, full SSD and ZFS pools only, to replace my aging one (still using ReiserFS, some disk running for more than 11 years...). I did the migration of my data, dockers and VMs smoothly. And I was starting using as my daily NAS, the old one was offline! So, everything was fine until my motherboard suddenly died... Now is the question: considering I'll have a new motherboard, probably not the same model than the dead one, will I be able to rebuild the pools and keep everything in place. I have 3 pools: 1 for VMS and 1 for Dockers, two SSDs each, in mirror mode The main pools, 7 SSDs, configure in Raidz2 mode So, will Unraid be able to correctly combine the disks so the pools are good once I've installed the new mobo and plugged all the SSDs? Not that it's critical, as the old one is still up and running, but I'd like not to repeat again the process (especially copying again my 20 TB data!!) Thanks, Cyril.

I can confirm, jaquanor solution works perfectly fine and, in my case, both with TigerVNC and noVNC!

Hi, I have the same issue after I've upgraded to 6.12.6, and had to rollback to 6.12.4 to have it working properly! I suspect the latest qemu update from 6.12.5 to be the cause of the issue, as I get "no scancode found" errors in the logs: 2023-12-18T11:23:41.712890Z qemu-system-x86_64: warning: no scancode found for keysym 65107 2023-12-18T11:23:41.836811Z qemu-system-x86_64: warning: no scancode found for keysym 65107 2023-12-18T11:23:43.053309Z qemu-system-x86_64: warning: no scancode found for keysym 35 2023-12-18T11:23:43.189724Z qemu-system-x86_64: warning: no scancode found for keysym 35 2023-12-18T11:23:44.908544Z qemu-system-x86_64: warning: no scancode found for keysym 123 2023-12-18T11:23:45.068083Z qemu-system-x86_64: warning: no scancode found for keysym 123

Hi, after 2 hectic days, I have the feeling my PSU is dying. Yesterday, all of a sudden, one of my disks (disk 5) became unavailable. Checking the logs, it made me first suspect a cable issue, so I changed the SATA cable, restarted the array, and rebuild started. During the rebuild, it failed with another disk (disk 1) showing as unavailable (resulting in loads of read errors in the logs). So I though I might have touched the cables , checked and pressed on each of them, restarted the array, all disks here, disk 1 SMART test OK, rebuild starts, then fails after a while on disk 5. I changed the SATA port where it was plugged, restarted, rebuild restarts but failed again on disk 5. Since I had a spare disk, decided to replace disk 5. Restart, and now, disk 1 throws thousands of read errors on rebuild. Stopping the rebuild, try to access disk 1 attributes & capabilities tabs in the UI, but it's all empty. As I had tried different SATA cables and ports, decided to plug disk 1 on another power line. Restarted the array, all disks up, no errors, rebuilding is running for 2+ hours now (~80MB/sec), where incidents were occurring in the first minutes, and SMART attributes are fine on both disks. Since the power plugging of the drives didn't change in months, I would suspect the PSU is giving less power ; is it possible? My PSU is a 11+ years old Seasonic 460W Fanless 80Plus Platinum, properly sized (checked various online PSU calculators, all estimates are under 350W where the PSU efficiency should be around 414W). So, do you think this could be the PSU not being able anymore to provide enough power? If so, any good suggestion for a good, silent PSU to use? Thanks!

Faced the same issue, but you can find explanation when displaying the Web UI: Starting with 7.2, JWT is now enabled by default and a default secret key is generated. So, you can either do rjlan's way, or get the generated secret key from onlyoffice using the following command from the console: sudo docker exec a1eeea35c900 /var/www/onlyoffice/documentserver/npm/json -f /etc/onlyoffice/documentserver/local.json Value can be found here: services.CoAuthoring.secret.session.string Then edit the onlyoffice settings in Nextcloud: Parameters > OnlyOffice > Secret Key Save and you're good to go!