AnnHashaway

I'll give you a Buffalo Nickel if you can remember anything that pointed you in the right direction. This is the EXACT issue I have been having for two months. Extracting ...PHP Warning: require(/config/www/nextcloud/updater/../version.php): failed to open stream: No such file or directory in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 658 PHP Fatal error: require(): Failed opening required '/config/www/nextcloud/updater/../version.php' (include_path='.:/usr/share/php7') in phar:///config/www/nextcloud/updater/updater.phar/lib/Updater.php on line 658 Round, and round, and round I go...

Great, thank you.

Is there a clean way to schedule auto-restarts for specific docker containers? I have been battling with Nextcloud and MariaDB for over a year now, and I haven't been able to find an effective solution to maintaining its performance speed consistently. The only method that works is restarting MariaDB, which brings the speed back to usable. Until I find the issue, I would like to simply have the docker container restart a few times a day so Nextcloud will continue to work when I'm away from the server. Any easy way to do this?

Attached

Attached denali-diagnostics-20210808-0831.zip

I am almost 1% in the rebuild at the writes to the parity are zero. EDIT: Should I zero out the drive with unassigned devices and try again?

I have been using this parity disk for a few years now. I have had a few power outage incidents with some data loss, but was able to use offsite backups to restore the data. I wonder if something happened at that point and I didn't notice. Is there a way to re-initiate it like a new parity drive and have it build the parity from scratch? Everything important is backed up locally and remotely, so I'm not worried about taking a swing. Thanks for you help.

I ran a diagnostics immediately after, just in case. Attached. denali-diagnostics-20210805-1610.zip

The last two times I have run a parity check, there are no reads or writes on the parity drive and it ends with over a billion errors. Unraid still says the Parity is valid. Whats the best way to start diagnosing this?

Ran xfs_repair -v on disk2, rebooted, and formatted disk3 again. Diagnostics attached denali-diagnostics-20190909-1651.zip

Here is a fresh set after another format attempt. This is done straight from the array while mounted. It only takes about 20 seconds to complete, and returns to the same Unmountable message. denali-diagnostics-20190909-1448.zip

Restarted the system. Same result. Diagnostics attached. denali-diagnostics-20190908-1610.zip

Attached. Thanks. denali-diagnostics-20190907-1548.zip

OK, I was able to format without taking it out of the array. It only took a few seconds, and I am getting the same readout of Unmountable. Are these the diagnostics I should post?

The Parity Sync / Data Rebuild process has finished, and the disk remains unmountable. (Attached) I am now going to move the drive to UA and run format.

The empty file system is ok. I can restore. The issue is I have run format on it probably 10 times. It fails to format each time in Unassigned Devices.

It is currently 5% through the Parity Sync / Data Rebuild process. Should I wait that out, or go ahead and add it back to unassigned devices and format?

I have an 8TB red parity and three 4TB red data drives. I took the server apart because I was going to change some parts, but ended up putting it all back together the same way. Once I booted back up, I am getting this message on one of the drives: Unmountable: Unsupported partition layout I have everything backed up, so I have tried to format the drive, preclear it, everything I could find for the last few weeks on the forums. No matter what happens, it comes back to this. When I preclear, the preclear fails after a day or so. (I attached the latest preclear report.) The only thing I haven't done is pull the drive and format it in another computer. I am not sure if that would work. Any ideas? Are there any other reports I can add here to help? Thank you. preclear_disk_WD-WCC7K0KE9C88_2123.txt