Falcowe

I have been using my UnRaid Server to host TimeMachine (TM) backups for a number of years now. However around the time of updating to 6.11.x I seem to be plagued with issues around TimeMachine. I have tried troubleshooting this to the best of my ability but I seem to be stuck at the moment. I keep getting errors; most recently on my Mac an error (112) that seems to indicate that the disk either disconnected or that for whatever reason TM doesn't have the access/permissions to the disk that it needs. And therefore don't complete any further backups past the first one. I seem to be able to set up an initial TM backup but I can't seem to get it to do the incremental backups. Of the things I have tried over the past year or so to fix this are the following: 1. Completely deleting the share and creating a new backup share and starting completely from scratch. Both Public and Private permissions on the share, and making sure TM is selected in the SMB options. 2. Tried re-writing permissions to the time machine share (but may have failed at doing it), from both Unraid console and MacOS Terminal 3. Tried verifying backup on MacOS 4. Tried following SpaceInvaders guide on migrating TM backup to 6.11.x All of this has been unsuccessful. I am still having persistent issues backing-up my Mac to my server. So I am hoping I can find some help here. Thanks in advance for your assistance it is greatly appreciated. treadstone51-diagnostics-20230616-0722.zip

Hey skios, thanks for your help. Sadly the changes to the config file didn't change the errors I'm getting. And there don't appear to be any errors in the log of nextcloud that would indicate why noting is uploading over a certain size. The changes I made to the config file were: <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'random characters', 'passwordsalt' => 'different randoom characters', 'secret' => 'longer string of random characters', 'trusted_domains' => array ( 0 => 'LAN IP: And nexcloud port', 1 => 'mycloudURL', ), 'trusted_proxies' => array ( 0 => 'swag', ), 'dbtype' => 'mysql', 'version' => '19.0.6.2', 'overwrite.cli.url' => 'https://LANIP:different nextcloud port', 'overwriteprotocol' => 'https', 'overwritehost' => 'mycloudURL', 'dbname' => 'MyServerName+cloud', 'dbhost' => 'LANIP:DPPort', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'its_me!', 'dbpassword' => 'myPassword', 'installed' => true, 'maintenance' => false, 'theme' => '', 'loglevel' => 2, ); Any further ideas?

Oops I completely missed your request to post the config.php. Now your Hide sensitive info makes sense! Ok here it goes: <?php $CONFIG = array ( 'memcache.local' => '\\OC\\Memcache\\APCu', 'datadirectory' => '/data', 'instanceid' => 'random_string_of_characters', 'passwordsalt' => 'a_different_random_string_of_characters', 'secret' => 'not_your_string_of_random_characters_;)', 'trusted_domains' => array ( 0 => 'LAN-IP:NexcloudPort', 1 => 'URL-for-nextcloud', ), 'dbtype' => 'mysql', 'version' => '19.0.6.2', 'overwrite.cli.url' => 'https://LAN-IP:DifferentNextcloudPort', 'dbname' => 'NameOfHost', 'dbhost' => 'LAN-IP:dbHostPort', 'dbport' => '', 'dbtableprefix' => 'oc_', 'mysql.utf8mb4' => true, 'dbuser' => 'MyUserName', 'dbpassword' => 'MyPassword', 'installed' => true, 'maintenance' => false, 'theme' => '', 'loglevel' => 2, ); Also, how do you post code or other things so they show up in that box you can scroll through?

No it doesn't. I do get a different error though than the upload and edit side gets. For the upload and editing I get the error: "An unknown error has occurred". And nothing happens after that. With the upload only I get the error: "Could not upload "[FILE NAME]" ". I this case it was a mov file. Finally you left a note to "Please hide sensitive info!" did I post sensitive info? I thought I hadn't.

Hey Skois, so I edited my php-local.ini file and changed my upload_max_filesize=100G as well as the other changes you made in the first block of text but I am still having the same issue for uploads when not logged in. My php file now reads: ``` ; Edit this file to override php.ini directives and restart the container date.timezone = America/Los_Angeles upload_max_filesize=100G memory_limit=8G max_execution_time=7200 max_input_time=7200 post_max_size=100G max_file_uploads = 200 default_socket_timeout = 7200 ``` Any other suggestions?

https://help.nextcloud.com/t/upload-not-working-for-non-users/99265/4 Also I have been dm-ing with devnull and they have been helping me out.

So I wanted to update my issue if anyone is following along. I was able to get a bit of help from the Nextcloud support community and have discovered that it is actually a file size limitation somewhere. I have tried increasing my PHP file and NGIX max file seizes with no luck yet. But I suspect that I didn't increase the rights files as the file locations are different in the docker version than in the linux distros people are posting about on the Nextcloud forums. So I can upload files, I just can't upload file that are "large" (i.e. in excess of at least 50MB in size and I suspect smaller but I don't have an efficient way to test). The files that have been successfully uploaded are in the 10s of KBs range. So.... does anyone have a suggestion where I might look for what/why this is being limited? And why its only happening on upload/file drops where it's an 'unknown'/'guest' user? If I have someone log in there isn't an issue uploading big files which makes me think it nextcloud causing the issue and not something outside of Nextcloud (i.e. php setup or NGIX limitations).

Hello all, I have been trying to have other people upload files to a folder I have created on Nextcloud and created a share link to allow for uploading to the folder. However it was reported to me that they were having trouble and I was able to "recreate" the issue on my side. The issue: when uploading files to the shared folder all files no matter how I upload them (via drag and drop or the dialogue to upload files) immediately shows the error "An unknown error has occurred." On occasion I'll get an error along the lines of - Server connection lost - but that one has been far more inconsistent and I think it is related to whatever the problem is preventing any files from being uploaded. Now with all of that being said I can upload files if I am logged in as a user and that is the workaround I have created for the other person in this case but I would like to be able to simply share a link in the future and have other people be able to upload files to me. The other part in this case has been able to download files from the link without issue however uploading seems to be a problem. Which is strange. Why would downloading work but not uploading, any bight ideas here? Thanks for your help!

So an update to this topic. From initial testing the 4TB SSD I put in the server seems to have fixed the issue with ProTools, and therefore rendered the OS X compatibility moot since the overlying issue seems to be resolved. As such I'll mark it solved for now. But if anything new arises I'll be sure to document it here. Thanks 1812 for the suggestion!

Gosh it has taken me too long to respond. Thanks for the reply 1812 I'm looking at getting an SSD to put the sound library on but haven't pulled the trigger yet. Once I do I'll be sure to report back here though.

So I am working with AVID support to troubleshoot an issue in ProTools where the "workspace" of ProTools seems to be hanging trying to "collect subfolders" seeming associated with my sound effects library that is stored on my unRAID server. And one of the questions they asked is if "[unRAID] is optimized for OS X" which seems like a bit of a silly question to ask since SMB 3.0 is officially supported on OS X so I really don't see how unRAID really would have much to factor into this. But since I can't seem to find any documentation say specifically that OS X is supported connecting to unRAID via SMB I wanted to reach out here and see what you all had to say, and if anyone knew specifically about OS X compatibility. On a side note, a few more details about my issue seeing as it might be storage related. There are A LOT of small audio files that ProTools is trying to catalogue, and I wonder if that is the hang up of why this isn't working so well. I am running unRIAD on a 45drives AV15 with WD Gold HDDs on a Supermicro motherboard. I am connecting to the server via 10GbE from a MacPro 7,1 but obviously the spinning rust is the bottleneck in this situation not the network speed. If you need more details than that let me know, I'm happy to swamp you with as much info as you find helpful. My guess as to what is going on is the latency of accessing info off the array seeing as there is network overhead (however little) + array ZFS overhead + overhead in accessing info on a spinning disk. So I wonder if I would see an improvement in performance, and a resolution to my problem by moving the SFX libraries over to an SSD? And then would I be able to edit off the array if all projects were off an SSD? I just find this weird because I was told by a few people (over at 45drives and AVID) that spinning disks should be fine for editing off of on a NAS, but I have not found that to be the case at all. I appreciate you time in helping me with this. And maybe unRAID can become every ProTools owners dream, all the storage you ever needed and expandable when you run out to edit off of. Cheers!

Who's the newb?! I am! Thanks Jonathanm!

Solved: It was the optical drive. More particularly the optical disk in the drive. So strange. I pulled the disk out from the drive and the array immediately started. Same when I unplugged the optical drive. But the array also starts with the optical drive plugged in, with no disk in it. Also my install of 6.8.0 was not the issue even with the ungraceful shutdown. I was able to recopy everything back onto the boot flash and now have everything precisely the way it was before this weirdness. Please mark as SOLVED I can't seem to change the post header.

I cannot get the array to start under normal circumstances. So far only in maintenance mode. I’ll have to give that hardware troubleshooting a try tomorrow when I have more time, I’ll be sure to update this post with what I find out.

Hey Benson, so both of those prompts aren't returning immediately like they seem to in your screenshot. I think the next step for me to try is to move slots, however I can't see a reason why that would change anything because unRAID is detecting the disks, it just doesn't seem to be able to start the array. And it went from a working array to a non-functioning array without me physically touching the machine.

Benson, do you have an idea where to start with looking into this further?

Thanks Benson, it seems like this might be an issue for me to contact unRAID directly at this point. Unless any other forum members can chime in.

Ya the Parity-Check speed seems normal from past runs when the array was working properly. estimated time to completion as of this post is 5 hours. The disks are all 6TB disks. So if it is a file-system issue does that mean unRAID is corrupted? Or that the file system of the disks is the issue? If so will a parity check fix the issue or will there likely be something else that needs to be done? Thanks Benson et. al!

Sorry what do you mean? The Parity-Check (no correction writing) will be running for about 6 hours.

So I finally was able to start the array in maintenance mode. But it didn't start like it normally does, it still is taking a long time to do anything. I'll report back after the parity check is complete. The log isn't showing it getting stuck at any particular disk.

I have now reinstalled unRAID os on the flash drive and went back down to 6.7.2. The webgui shows up a LOT faster now but I still cant get the array to start. Still stuck on "Array Starting - Mounting disks" Here is a new diagnostic zip. treadstone51-diagnostics-20191214-2156.zip

So the array has been starting over night and is still mounting disks. Not normal behaviour I think. I also noticed that like in previous times the GUI reports high cpu usage and when I look at the Processes report in the GUI there is one task that has 100% CPU usage, could this be causing the disks not to mount? The server is trying to do this in safe mode at the moment.

I tried a Temp unRAID install and I was having a great deal of difficulty building a new array. There was a lot of lag in the GUI and when I finally got a couple of disks in place and clicked "Start" array nothing happened. So I then went and did the bios update and the firmware update for the supermicro board. And that hasn't helped anything either. In fact it seems that the BIOS update may have made things worse. Now after booting into the unRAID flash drive and into GUI mode (I have yet to try non-gui mode, but am currently giving GUI no plugins some time to boot up), I am getting a black screen and I can't bring up the web GUI either. Any ideas? I have not updated the LSI HBA but the fact its not even getting to the GUI anymore makes me think that isn't the issue. I will try to figure out which HBA I have and see if I can update it however I don't have a any PCI card so I suspect its something that is part of the Supermicro board and that it was taken care of with the BIOS and firmware updates. EDIT: The webGUI came back online, I have tried starting the array again, but still waiting 10 min later for the array to start. So I guess its good news, I haven’t made it worse.

New Diagnostics. The array is still "Starting - Mounting Disks" treadstone51-diagnostics-20191213-2001.zip

Squid, no I didn't rename the server. The logs were pulled both locally (i.e. Tower) and remotely (i.e. Treadstone). I have started the array again normally, and I will post new diagnostics soon (hopefully). I can't imagine anything in my network doesn't support Jumbo frames. But I am not 100% certain, would this cause the array not to start?