M1L4

Beeing unsure i made following steps: - gone to "main page/array devices" - selected unmountable disk - went to "Disk 1 Settings/Check Filesystem Status" - removed -n option and hit "check" produced following notification Beeing scared of using the -L option, but not wanting to be a nuisiance I eventually started it regardless like mentioned in (one of multiple topics regarding that issue) - replaced newly set -n modifier with -L and hit start again produced following promt and initiated another parity Check on whole System - I`m unsure if the "parity override" option was set as the parity check was triggered automatically after xfs-repair check - thus unsure if I should let it continue - since Parity Check is in progress and I decided against stopping it for now, I can#T check File Recovery as we are still in Maintainence Mode - currently no Data present, not sure that is already an indication of possible success/failure

Hey Folks, (I´m following the "Need help? Read me First!" post. I hope it's matching adequatly) 1) Try the Fix Common Problems plugin! - was already installed & signaled issues and recommended steps. Since I couldn't follow them at the time, I shut the system down to prevent any changes to the situation 2) Syslog before shutdown - is lost as touched upon in my previous statement - the later retrieved one is attached 3) Smart Report - attached 4) System specifics - 4.1) Unraid Version: 6.12.8 - 4.2) plugins: - unbalanced 2024.01.26 - Unraid Connect 2024.03.06.0724 - AMD Vendor Reset 2022.07.21 - CA Auto Update Applications 2024.03.17 - CA Cleanup Appdata 2022.10.21 - Community Applications 2024.03.17 - Dynamix Cache Directories 2023.02.19 - Dynamix File Manager 2023.06.01 - Dynamix S3 Sleep 2023.03.23 - Dynamix Stop Shell 2023.02.05 - Dynamix System Buttons 2023.02.11 - Dynamix System Information 2023.02.05 - Dynamix System Statistics 2024.01.05 - Dynamix System Temperature 2023.02.04b - Fix Common Problems 2024.03.09 - FolderView 2024.01.22 - GUI Search 2023.08.31 - Intel GPU TOP 2023.09.13 - NerdTools 2024.02.17 - Network Statistics 2022.08.25 - Nuvoton NCT6687 Driver 2022.07.22 - Parity Check Tuning 2024.02.15 - Radeon TOP 2023.02.22 - Recycle Bin 2023.12.31 - Tasmota Power Monitor 2023.06.17 - Theme Engine 2023.01.17 - Tips and Tweaks 2024.01.26a - Unassigned Devices 2024.03.19 - Unassigned Devices Plus 2023.11.30 - Unassigned Devices Preclear 2024.02.22 - 4.3) Hardware - Motherboard: ASUSTeK COMPUTER INC. PRIME A520M-K , Version Rev X.0x | American Megatrends Inc., Version 3001 | BIOS dated: Wednesday, 2023-02-01 - CPU: AMD Ryzen 5 PRO 4650G with Radeon Graphics @ 3700 MHz - Disks: 3x Toshiba MG09ACA18TE (1x Parity, 1x Data, 1x intended Backup) 5) I recently configured some Shelly Plug S Devices to measure power consumption. For it's installation I shut down my server, but since my unraid System was still running a few hours later I just powered it down forcefully. After restart I noticed all my data missing. Apparently the disk had no filesystem or was ummountable. After panicking and recollecting myself, I powered the system down again to prevent furter detoriation. I think parity check was running as well and since I was unsure how the system would handle no disk vs parity data, I stopped the system again, while giving it all the time it wanted to. In one of the topics it was mentioned to start in maintainance mode, which triggered todays repair try session. I started it in maintainance, now no errors are shown neither on disk or parity, no writes no errors, as if its a complete never used before disk. The no error state frightened much more than the one with errors, which is why I started this thread. All logs are of the same session than this. Easy to follow steps would be appreciated. I feel a little alienated on unraid. 30y of windows usage, with many forceful shutdowns, but never had I any trouble regarding data corruption/preservation. Never did I imagine the trouble I would be inviting myself... Kind regards m1l4 megamind-diagnostics-20240327-2322.zip megamind-smart-20240327-2318.zip

[Moodle Setup Problems] First and foremost a big thanks to you bobalot for your time and progress on the moodle problem. I can confirm his approach working for me as well: ---taken steps--- --1-- After initial docker installation with default values - apart from database and moodle logins - I received following error: /opt/bitnami/moodle/config.php: No such file or directory ... Restoring persisted Moodle installation Originally I researched the 'no such file or dir' part, but www led me to believe that the 'restoring persisted installation' was the bigger issue. I removed the installation, later pruned, tried again - no success. But the crux was nothing I had thought about from the error msg: At some point I found bobalot's post and likewise could boot moodle by removing the bitnami part from the MoodlePath & Moodledata dirs: --2-- And likewise after reboot moodle wouldn't start again: realpath: /bitname/apache/conf: No such file or directory ... Running moodle install Script --3-- My next step was the addition of the Moodle_skip_bootstrap. Sidenote: I copied the name from somewhere with a space initally. Make sure you have a clean name^^ And volia - a running system for me as well. Just summarized different posts for future reference. The credit's all bobalot's for figuring out the steps needed. Much appreciated mate