cuutip

I recently ran a parity check, and it said there were 202 errors. I am wondering has there been an app developed that identifies or is able to read the parity error log and display what the inconsistencies were. Also, in my research I went to Tools > Parity Problem Assistant and got the following error: Fatal error: Uncaught Error: Call to undefined function isArrayOperationActive() in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(522) : eval()'d code:35 Stack trace: #0 /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(522): eval() #1 /usr/local/emhttp/plugins/dynamix/template.php(71): require_once('/usr/local/emht...') #2 {main} thrown in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(522) : eval()'d code on line 35 Any help would be hot.

I would like to post an additional solution to the board. I had zero problems with the windows 10 smb/cifs homegroup shaing in v6.4.1 . My issue was the upgrade. Going from 6.4.1 to 6.8.x would break my smb shares completely. I did some forum searching, lots of reading, some config gap analysis checking and using the command smbstatus I discovered that the smb.conf line 'name resolve order = bcast lmhost host wins' was not working for me in samba v4.11.4. *I removed lmhost from the line for my samaba 4.11.4 configs.* now my shares work like they did in 6.4.1. happy guy here

I am not sure if this is a feature request/bug report or what. When I turn on destructive mode for UD+ then attempt to format my 5tb drive using NTFS, exFAT, or FAT32, it fails instantly. i checked into the issue and noticed that the format command used by UD+ uses MS-DOS MBR partition instead of letting you select MBR/GPT+. So my remedy was to open a webterminal, fdisk /dev/sd(#), create GPT+ partition and write. then refresh my screen and format. it keeps creating a MBR before the format, and does not allow for multi-partitioning in the format process to accommodate. however xfs, and btrfs work fine out of the box. I'm not sure if there is something I am missing or something I can do to help out, but I will be turning off destructive mode, format the drive on another box and reintroduce it to the UD+