Tharnax

Same issue. Just updated this plugin to the latest version: 2023.03.31 and now navigating into any shares folder results in the same result: No errors. Version:

You are correct, I couldn't see the issue reviewing the code via terminal, however, when I opened it via the Shares (Dynamic File Manager plug-in - although don't quote me that might not be how it worked it might be Unraid OOTB capability), I was able to navigate through Shares to the Nexcloud config folder and open the config.php file where there was a clear red X beside the line with an issue. Upon further review, I identified it was the line above which was missing the comma at the end. Such as small difference but that "tool" / capability helped me resolve the issue but highlighting the area of the issue in the code. If I was to make a recommendation to Spaceinvader One, it would be to utilize this capability in this tutorial videos because then any manual updates a user is making it would be more apparent if they make a minor mistake while following along. Thanks all for your feedback.

Hoping for some support with NextCloud. I've been watching and following SpaceInvader One's tutorial on setting up NextCloud on Unraid - Part 1. Everything was working as per the step by step process. I completed the install of MariaDB, installed NextCloud, confirmed it was running set it up on the MariaDB,, setup a user, etc.. All working great. I got to about 20.50 in the lined video where the next step is to configure NextCloud to work with the personal domain. I made all the necessary configuration changes in the config.php file and saved the file. I restarted Nextcloud container and now I am recieving the following error msg in the log file which I had not received previously. Wondering if anyone had any thoughts / recommendations? PHP Fatal error: Uncaught Error: Typed static property OC::$server must not be accessed before initialization in /config/www/nextcloud/cron.php:192 Stack trace: #0 {main} thrown in /config/www/nextcloud/cron.php on line 192 I attempted to look up a potential fix but honestly this is way above my head which is why I'm reaching out to the experts on this community to see if you have any advise, for a noob. Thanks! Please disregard, after opening the config.php file in a different application I see where I omitted a comma in one of the statements. I didn't want to delete this post incase someone comes across it in the future.

I am experiencing similar issues. I've made no changes to anything related to the Deluge setup other then applying the latest update yesterday. After applying the latest update the Unraid docker says it is running however, when I click on it and open the WebUI, I receive a message on the browser that the site cannot be reached and related apps are stating they are unable to communicate with Deluge. These are the errors I see the log file: 2023-03-19 08:29:38,892 DEBG 'start-script' stdout output: 2023-03-19 08:29:38 TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity) 2023-03-19 08:29:38 TLS Error: TLS handshake failed 2023-03-19 08:29:38,892 DEBG 'start-script' stdout output: 2023-03-19 08:29:38 SIGHUP[soft,tls-error] received, process restarting

Thanks for following up. It was pretty quick and it added to the array without issue but it was late yesterday here so I didn't do anything further. I reviewed the shares, folder and file structures today and it all looks good. I've started the rsync of the data from the next 8TB drive onto the array, all looks good so far. Very much appreciate everyone's input and assistance, I would have been lost and likely done more harm then good without it.

Thanks for your reply. Formatting underway.

Rebuild finally finished. Selected "Done". Stopped the Array and restarted it in Normal Mode. It looks like all came back successfully, I've attached the diagnostics log just in case. Disk2 is showing as "Unmountable: Unsupported partition layout". I anticipated this as it hadn't been added to the array yet only "cleaned'. I am asking for confirmation that I should be good to Format Disk 2 as the next step? Thank you. server-diagnostics-20220623-1727.zip

@itimpi - Thank you for clarifying, that helps me breath a sigh of relief. As this is a new setup, I'm not concerned with not being able to write to the array while the rebuild is running. I still have another 7 hours in the data-rebuild process but if you could advise on the anticipated next step I should do following the data-Rebuild that would be appreciated. Then I know what to expect or do next so I don't "guess" myself into another potential concern. Yes, I did check the emulated disk before starting and it all looked okay from my perspective, as the folder structured appeared accurate not that I necessarily know what I'm looking for.

Fingers crossed but after the disk clean of Disk 2, I did shut down the server and replace the SATA controller and restart. That's when I started to follow the steps above. Sounds like I made the mistake of not just starting the array in normal mode.

Crap! And no, I didn't start it in normal mode. I made a best guess based on those instructions and since it based on the note it didn't seem to matter if it was normal mode or maintenance mode I made the wrong choice. I'll let the rebuild complete and then as you stated, see if it is mountable.

Nothing in the instructions "https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself" suggested that I can't use maintenance mode, it just stated if you star the array in maintenance mode you will need to press the Sync button to start the rebuild. Sounds like a made the wrong assumption that maintenance mode is a "safer" approach. Hopefully I haven't made things worse, I'm very much learning as I go. What do you mean no drives are mounted? This is what I see in the Array Devices:

Clear finished, powered down the server. Replaced the SATA controller, the 16TB was connected to the Marvel SATA controller so for the moment it is now connected to the new SATA controller. Powered up the server and followed the steps as per the manual: Stop array Unassign disabled disk Start array so the missing disk is registered Important: If the drive to be rebuilt is a data drive then check that the emulated drive is showing the content you expect to be there as the rebuild process simply makes the physical drive match the emulated one. Is this is not the case then you may want to ask in forums for advice on the best way to proceed. Stop array Reassign disabled disk Start array to begin rebuild. If you start the array in Maintenance mode you will need to press the Sync button to start the rebuild. Started the area in maintenance mode and it did present the Sync button. It appears a sync "Data-Rebuild" is now in progress. So far it all appears to be okay but I've attached a latest diagnostics log incase you have an opportunity to take a look and see if there are any concerns. I hope, so far so good. Thanks for your help! server-diagnostics-20220622-1932.zip

Hi All, thank you for your continued analysis. Here is an image of the Array: I've also attached the latest diagnostics. Parity / Disk 1 & Disk 2 are all brand new in the last few weeks. Disk 2 I purchased first and utilized it to copy some data from the old WHS 2011 server on to another Unraid server I am building, so Disk 2 wasn't completely empty but the data that was on Disk 2 is backed up and Disk 2 is fine to be added to the array. I assumed it would be cleaned / formatted then added to the existing array of Parity + Disk 1. Both Parity and Disk 1, were fresh right out of the packaging and added to this brand new Unraid install. All the other Unassigned disks you see below are from the old WHS 2011 server, and once I get the array working with Parity + Disk 1 + Disk 2, I will mount and rsync copy the data over from each of the unassigned disks. As each disk's data is copied onto the array, I will clear / format it and add it to the array. Note: I will only be adding back in the 3x 8TB drives, not the 3x 3TB drives and I'll be adding two 500GB SSD drives (Raid 1) for cache once all is said and done. Please let me know if I should stop the current array process or not? Worst case if the parity drive will rebuild the array on Disk 2, then I can re-add Disk 1 as a new disk. If Disk 2 is being added to the array as a new "empty" disk, then I should power down server, fix the connection settings and restart the server confirm Disk 1 is "active" and then re-build the array? Thank you! server-diagnostics-20220622-1341.zip

Awesome, thank you @JorgeB, very much appreciate the replies. Since it is approximately 6 hours from completion, I'll let it run. Besides it'll allow time for the new SATA controller to arrive so I can install it at the same time.

Thank you both for your input. Disk 2 is currently doing the following: Is it okay to power down the server while the above activity is occurring or should I wait until it completes? Upon power down I'll check all the cables and move the drives to the onboard Intel SATA controller so it gets them off them Marvel SATA controller to hopefully increase stability. I'll remove the Marvel SATA controller at the same time if it isn't recommended for Unraid. @JorgeB - I see on another thread you recommended an IO CREST Internal 5-Port Non-Raid SATA III controller card. This is a Canadian Amazon site but it appears to be the same card: https://www.amazon.ca/Internal-Non-Raid-Controller-Desktop-Bracket/dp/B07ST9CPND/ref=sr_1_4?crid=2FEEM476N86H9&keywords=IO+CREST+Internal+5+Port+Non-Raid+SATA+III&qid=1655902223&sprefix=io+crest+internal+5+port+non-raid+sata+iii%2Caps%2C256&sr=8-4. Do you still recommend this card? Seems like I can order it and get it same day to replace the Marvel controller card.