Napryc

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!

I've followed the stesp as described, and everything is back to normal. Big up to gfjardim for the quick update ! Thanks!

Hi, I've updated to the latest "Unassigned Devices", then upgraded to Unraid 6.1. I had one SSD and one SMB share configured. Since the update, it seems there is an issue with the SMB mount, as you can see on the screenshot: While it appears online, I can't actually access the content in the share, you can also note that sizes are all at 0, which was not the case before There is also a PHP error message mixed in the header: Warning: Division by zero in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 28 I can declare a new SMB, but it fails mounting. Trying to change the path associated to the share, I get another PHP error: Warning: require_once(/update.htm): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 337 Fatal error: require_once(): Failed opening required '/update.htm' (include_path='.:') in /usr/local/emhttp/plugins/unassigned.devices/UnassignedDevices.php on line 337 If you have any suggestion or want me to run some tests, let know. Thanks.

Teracopy is a free program which allows to copy and perform checksums, you can find it here: http://codesector.com/teracopy

Hi, thank you for all the information, suggestions and comments... I think I will go for the i7 and Gigabyte board... I think I got fooled regarding ECC support, as Gigabyte states on the site that the board has "Support for non-ECC memory modules" which I translated - obviously too fast as I didn't find any mention - that it actually supports ECC memory Again, thanks a lot!

Hi garycase, Ford Prefect, I didn't think about the Xeon option... from Plex forums, HT is not mandatory, but provide faster transcoding, so it's a nice to have feature. However, i5 should do the job properly, especially because I won't have that much simultaneous transodes (2, maybe 3). Here in Europe, Xeon E1230v2 and i7-3770 are similar prices, and about $90 more expensive than i5-3570, so it's too be considered... Moving to a server-grade mobo is not something I had in mind neither, but since the Gigabyte is already $260, would there be a server-grade mobo around this price which offer the same features I'm interested in ? Especially, this mobo offers 9 on-board SATA ports, and I haven't seen any LGA1155 Supermicro mobo with that much ports. Anyway, I have few options: 1. i5-3570 + Gigabyte GA-Z77X-UD5H: It will cover my needs, can limit upgrade possibilities 2. i7-3770 + Gigabyte GA-Z77X-UD5H: More expensive than (1), can limit upgrade possibilities but brings HT 3. E1230v2 + Gigabyte GA-Z77X-UD5H + basis Graphic Card: A bit more expensive than (2), but add ECC support and provide more flexibility for future upgrade 4. E1230v2 + server-grade mobo + basis Graphic Card: More expensive, but provide highest quality. Problem, might require a SATA extension card to handle 8 drives So far, I'm quite happy with my current Gigabyte mobo, which has been running for almost 3 years with no problems... so I tend to believe this new Gigabyte should also be robust... what would bring a server-grade mobo ? What is the good point of ECC memory in Unraid usage ? Other question, that Gigabyte mobo has 2 GbE ports, 1 Atheros and 1 Intel. If I remember properly, Unraid can now do Ethernet Port aggregation... woudl this be possible even if it's 2 different brands? Not very important at the moment, but who can say :-) Anyway, thanks again for all your comments!

Hi, I'm currently considering the upgrade of my unraid server. The main goal is to get the server able to run properly Plex Server (transcoding Full HD movies) which is currently not possible with my Celeron E1400 (hit 100% CPU when transcoding). So far, my choice is the following: - Motherboard: Gigabyte GA-Z77X-UD5H. Details about it can be found here: http://www.gigabyte.us/products/product-page.aspx?pid=4440# - CPU: Intel i5-3570 I believe it should be more than enough to allow Plex Server to handle at max 2 simultaneous transcodings. Few questions: - Should I consider 8GB for RAM, or 4GB is enough ? - Is the stock fan coming with the i5 silent (I currently use the stock fan with my E1400 and it's quiet) ? Any other comments and/or suggestions are welcome! Thanks! Napryc

Ran a parity check over night... more than 20000 errors detected. Since I have several files impacted, I tend to think that the parity is correct, but not the data on drive. I got a new hard drive today, will install it in the tower as replacement of the problematic drive, will see what happen when Unraid will be rebuilding it

So, the rebuild-tree completed and corrected some files. the following reiserfsck --check did show no error. However, I still had the same issues wit the video. Since I had a copy of one of them, I did a binary compare, which concluded as "files are different". Replaced the one in Unraid with the legacy copy, no more issue. So, it seems the parity is having the wrong information, since it rebuilt the drive as it is now. Don't know what can have impacted it for files which had not been written when I got this issue... Any suggestion about what could be done next ?

Hi Joe, thanks for helping! Did run a new reiserfsck --check, which did abort, because the previous reiserfsck --rebuild-tree was aborted. So, I gave another chance to reiserfsck --rebuild-tree; seems to work now and started to correct some files... looks like there is still few hours to complete (it's already running for 4h30); so I will look at that when I wake up tomorrow morning!

Hi, I'm running Unraid 5.0rc10 for a while now with no issues, until early last week. One morning, I noticed one of my data drive had a red ball. Looking at the logs, I got the confirmation that some issue occurred over the night while mover started. See extract of logs below: Feb 18 03:40:17 Mediaserver kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x400101 action 0x6 frozen Feb 18 03:40:17 Mediaserver kernel: ata2.00: irq_stat 0x08000000, interface fatal error Feb 18 03:40:17 Mediaserver kernel: ata2: SError: { RecovData UnrecovData Handshk } Feb 18 03:40:17 Mediaserver kernel: ata2.00: failed command: WRITE DMA EXT Feb 18 03:40:17 Mediaserver kernel: ata2.00: cmd 35/00:00:a0:a1:83/00:04:7c:00:00/e0 tag 0 dma 524288 out Feb 18 03:40:17 Mediaserver kernel: res 50/00:00:47:00:cc/00:00:7c:00:00/e0 Emask 0x10 (ATA bus error) Feb 18 03:40:17 Mediaserver kernel: ata2.00: status: { DRDY } Feb 18 03:40:17 Mediaserver kernel: ata2: hard resetting link Feb 18 03:40:17 Mediaserver kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Feb 18 03:40:17 Mediaserver kernel: ata2.00: configured for UDMA/33 Feb 18 03:40:17 Mediaserver kernel: ata2: EH complete Feb 18 03:40:17 Mediaserver kernel: ata2.00: exception Emask 0x10 SAct 0x0 SErr 0x400100 action 0x6 frozen Feb 18 03:40:17 Mediaserver kernel: ata2.00: irq_stat 0x08000000, interface fatal error Feb 18 03:40:17 Mediaserver kernel: ata2: SError: { UnrecovData Handshk } Feb 18 03:40:17 Mediaserver kernel: ata2.00: failed command: WRITE DMA EXT Feb 18 03:40:17 Mediaserver kernel: ata2.00: cmd 35/00:00:a0:a1:83/00:04:7c:00:00/e0 tag 0 dma 524288 out Feb 18 03:40:17 Mediaserver kernel: res 50/00:02:00:00:00/00:00:00:00:00/a0 Emask 0x10 (ATA bus error) Feb 18 03:40:17 Mediaserver kernel: ata2.00: status: { DRDY } Followed later by this: Feb 18 03:40:20 Mediaserver kernel: md: disk2 write error Feb 18 03:40:20 Mediaserver kernel: handle_stripe write error: 2089002288/2, count: 1 Feb 18 03:40:20 Mediaserver kernel: md: disk2 write error Feb 18 03:40:20 Mediaserver kernel: handle_stripe write error: 2089002296/2, count: 1 Feb 18 03:40:20 Mediaserver kernel: md: disk2 write error Feb 18 03:40:20 Mediaserver kernel: handle_stripe write error: 2089002304/2, count: 1 Feb 18 03:40:20 Mediaserver kernel: md: disk2 write error Feb 18 03:40:20 Mediaserver kernel: handle_stripe write error: 2089002312/2, count: 1 Feb 18 03:40:20 Mediaserver kernel: md: disk2 write error Feb 18 03:40:20 Mediaserver kernel: handle_stripe write error: 2089002320/2, count: 1 Feb 18 03:40:20 Mediaserver kernel: md: disk2 write error Feb 18 03:40:20 Mediaserver kernel: handle_stripe write error: 2089002328/2, count: 1 Feb 18 03:40:20 Mediaserver kernel: md: recovery thread has nothing to resync So, I performed SMART test on the drive, nothing shown up. Reading in the wiki, suggested that it could be related to something else than drive, so I opened the server, check the cables and seemed the SATA cable was not fully plugged (since I had to move the server few days before, could be the reason why it moved). Once I plugged it back properly, I decided to re- initialize the drive. Stopped the array, remove the disk, started the array, stopped again, re-assigned the drive, and let the parity rebuild to be done. Everything was looking fine, until I tried access some of the content stored on that disk. Using XBMC (Frodo) on both my PC and on an Openelec box, movie playback was showing some artefacts, and stopped laying back after few minutes (movies were on the disk prior to the issue). So, I stopped the array, performed reiserfck test: reiserfsck --check started at Sat Feb 23 08:40:09 2013 ########### Replaying journal: Done. Reiserfs journal '/dev/md2' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. \/ 2 (of 14// 4 (of 161\/170 (of 170/block 91002061: The level of the node (11010) is not correct, (1) expected the problem in the internal node occured (91002061), / 21 (of 161// 84 (of 170/block 71424461: The level of the node (33321) is not correct, (1) expected the problem in the internal node occured (71424461), / 32 (of 161\/ 27 (of 170-block 92646861: The level of the node (11861) is not correct, (1) expected the problem in the internal node occured (92646861), / 43 (of 161//123 (of 149|block 129990861: The level of the node (58975) is not correct, (1) expected the problem in the internal node occured (129990861),/ 47 (of 161|/ 52 (of 170|block 68691661: The level of the node (48791) is not correct, (1) expected the problem in the internal node occured (68691661), /150 (of 161// 93 (of 170-block 115648461: The level of the node (24388) is not correct, (1) expected the problem in the internal node occured/ 3 (of 14-/114 (of 161|/ 56 (of 161|block 37180036: The level of the node (57260) is not correct, (1) expected the problem in the internal node occured/ 4 (of 14-/140 (of 148|/103 (of 170\block 117741261: The level of the node (36482) is not correct, (1) expected the problem in the internal node occured/ 5 (of 14|/161 (of 165// 24 (of 170/block 125421261: The level of the node (58497) is not correct, (1) expected the problem in the internal node occured/ 7 (of 14// 83 (of 170|/ 73 (of 170/block 147162061: The level of the node (57552) is not correct, (1) expected the problem in the internal node occured/ 9 (of 14|/114 (of 170|/ 50 (of 170-block 162368461: The level of the node (62602) is not correct, (1) expected the problem in the internal node occured (162368461),/138 (of 170|/162 (of 170-block 166573261: The level of the node (35703) is not correct, (1) expected the problem in the internal node occured/ 10 (of 14\/ 22 (of 170\/138 (of 170/block 175904461: The level of the node (8612) is not correct, (1) expected the problem in the internal node occured (175904461),/ 35 (of 170-/ 40 (of 170-block 177978061: The level of the node (33819) is not correct, (1) expected the problem in the internal node occured (177978061),/ 42 (of 170// 68 (of 170/block 179379661: The level of the node (16992) is not correct, (1) expected the problem in the internal node occured (179379661),/140 (of 170// 48 (of 170/block 182861261: The level of the node (49115) is not correct, (1) expected the problem in the internal node occured/ 11 (of 14|/ 17 (of 135// 22 (of 170\block 190566861: The level of the node (59600) is not correct, (1) expected the problem in the internal node occured (190566861),/ 22 (of 135|/108 (of 170|block 194042061: The level of the node (6611) is not correct, (1) expected the problem in the internal node occured/ 14 (of 14\/ 27 (of 136// 69 (of 170-block 113792461: The level of the node (60719) is not correct, (1) expected the problem in the internal node occurefinished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 19 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Sat Feb 23 09:07:35 2013 Launched the rebuld-tree as indicated: reiserfsck --rebuild-tree started at Sat Feb 23 09:15:26 2013 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 366373557 blocks marked used Skipping 23115 blocks (super block, journal, bitmaps) 366350442 blocks will be read 0%.. left 177973105, 27759 /secsync_buffers: buffer list is corrupted Aborted Now the disk appears unformatted in Unraid: root@Mediaserver:~# mount /dev/md2 /mnt/disk2 mount: /dev/md2: can't read superblock I tend to believe that it might be a hard disk related issue... but any comment is welcome! Thanks!