chris1259

Thank you for the explanation. Thus far, all the drives i have replaced have either failed or gone offline (disabled). In each case, i replaced the disk with a new one and rebuild did the rest. Next time i will place the array in maintenance mode, and review what repair options are available.

I formatted the unmountable disk outside of the server to confirm no bad sectors were found. I did not return this newly formatted disk to the array. From the link you provided, it sounds like the file system had become corrupted, and i may have been able to fix it. What is unclear to me is the difference between an unmoutable corrupted drive, and a drive that is no longer working. Why does the data rebuild work on a dead drive, but not a drive that was replaced because it was unmountable. Thanks.

unRaid v6.12.9 9 X 12TB Seagate Exos X14 Drives 2 of the drives are parity drives. After upgrading to v6.12.9 from 6.12.8 and rebooting, the server automatically started a parity check. I let it run and it found 11733 errors. After another reboot one of the data disks reported as unmountable. I replaced the drive and the rebuild started; however, i noticed my main network share that was 84% full, now only reported 70% full. The data rebuild finished successfully with zero errors after i replaced the disk. The unmountable disk was tested outside of the server and had no issues, including a full format. Since 2016, i have replaced bad disks before and never lost data. All important data was backed up on other devices, and i should be able to restore most of what i lost from there. I am now trying to understand what happened. Any help is appreciated! diagnostics-20240401-1203.zip

"The client noticed that the server is not Elasticsearch and we do not support this unknown product" This is the same issue i had when i tested both elasticsearch dockers available in community applications for v6.6.2 and v7.10.2 at the time. Does this message have anything to do with licensing / forking the project? I installed Elasticsearch 8, as suggested by JAnguita, from the repository "docker.elastic.co/elasticsearch/elasticsearch:8.11.1", but it did not help. Additionally: On v8.11.1, running "/usr/share/elasticsearch/bin/elasticsearch-plugin install --batch ingest-attachment" no longer works and provides the message: "[ingest-attachment] is no longer a plugin but instead a module packaged with this distribution of Elasticsearch -> Please restart Elasticsearch to activate any plugins installed" I don't see occ installed, and do not know the name of the module.

Thanks for the update. How did you discover the fix and where did you install the docker container from?

No i have not.

Could this be referring to unRaid's OS and not the container? Open terminal in unRaid cp /etc/sysctl.conf /etc/sysctl.backup nano /etc/sysctl.conf paste vm.overcommit_memory = 1 save and reboot

I still have the same issue. Now running v6.12.4 Nextcloud v27.0.2 elasticsearch v6.6.2

Running v6.12.0-rc4.1 Tested both elasticsearch dockers available in community applications for versions 6.6.2 and 7.10.2. Up to this point everything appears to be working. When i run ./occ fulltextsearch:test at /var/www/html/, in the Nextcloud v26.0.1 container i receive the error: .Testing your current setup: Creating mocked content provider. ok Testing mocked provider: get indexable documents. (2 items) ok Loading search platform. (Elasticsearch) ok Testing search platform. fail In ProductCheckTrait.php line 32: The client noticed that the server is not Elasticsearch and we do not support this unknown product fulltextsearch:test [--output [OUTPUT]] [-j|--json] [-d|--platform_delay PLATFORM_DELAY] Is this a known issue? Or does this have anything to do with licensing / forking the project? I have not tried a more recent version of the elasticsearch yet. Thank you.

"If the GUI cannot be accessed for any reason then using the diagnostics command from the Linux command line level will generate the same information and put the resulting zip file into the logs folder on the flash drive." Of course it's that easy 🙂 Thanks. I will give it another go and report back.

If i could reach the server via SSH, is there a command i could run that would generate the diags? Thanks.

I wanted to report an issue i experienced with v6.12.0-rc5. In short, 12+hrs after upgrading i lose access to the Web UI and samba shares. I did not check SSH, and I was not able to check the server locally before rolling back to v6.12.0-rc4.1, which has been stable, including all other RC's before 5. Gracefully powering down the server with a press of the power button will bring the server back, however, the issue repeats itself 12+hrs later. If anyone has any suggestions on what log i should monitor please let me know. Thank You. diagnostics-20230503-0805.zip

First, thank you to @muwahhid and @rob_robot as their posts were very helpful. Running v6.12.0-rc4.1 Tested both elasticsearch dockers available in community applications for versions 6.6.2 and 7.10.2. Up to this point everything appears to be working. When i run ./occ fulltextsearch:test in the Nextcloud v26.0.1 container i receive the error: .Testing your current setup: Creating mocked content provider. ok Testing mocked provider: get indexable documents. (2 items) ok Loading search platform. (Elasticsearch) ok Testing search platform. fail In ProductCheckTrait.php line 32: The client noticed that the server is not Elasticsearch and we do not support this unknown product fulltextsearch:test [--output [OUTPUT]] [-j|--json] [-d|--platform_delay PLATFORM_DELAY] Is this a known issue? Or does this have anything to do with licensing / forking the project? I have not tried a more recent version of the elasticsearch yet. Thank you.

This issue is not longer present since upgrading Firefox to v96.0.1 / v96.0.2 on Windows.

Today i was not able to log into the WebUI after FireFox updated to v96.0 using the default username/password. Internet Explorer on Windows 10 21H2 did not work either. I had to use Microsoft Edge on Windows 10 21H2. I did not test Chrome. Firefox v95.0.1 on Xubuntu (Linux) does work. I am not asking for a fix, just sharing info.