Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

joshbgosh10592

Members
  • Joined

  • Last visited

  1. Good luck. I've reinstalled the docker container and macOS, checked permissions, everything mentioned in these forums and I've never gotten more than the first backup to run successfully. I've given up.
  2. I just updated from 6.10.0 to 6.10.3 immediately after doing a "shrink array" to replace an empty data drive with a much larger drive. I did select the "Parity is already valid" checkbox when I performed it Now, however, when I reboot the server, the array doesn't automatically start... The server is assigned a static IP address via it's NIC, and I have a somewhat complex NIC setup with two bonded (802.3ad) 10Gb NICs, two bonded (also 802.3ad) 1Gb NICs, as well as two other independent NICs with their own IPs. I'm wondering if the license check is happening before the NICs are activated? This wasn't an issue with any other version of unRAID though and I've had this setup since I believe 6.8.
  3. Not OP, but I also have a similar annoyance. I have the API disconnect error as well. Going off what you're saying about the ALLOWED_ORIGINS, I access my server via nas.domain.com, but without any port forwarding so it's only accessible internally. Is there a way to add nas.domain.com to the ALLOWED_ORIGINS property, or is that a security hazard because technically domain.com is routable?
  4. Didn't know that, thank you! I performed that, removed the existing disk from TM, and erased the .sparcebundle and allowed TimeMachine to create a new one and successfully creates the first backup. However, anything after, still the same thing for some reason... This is driving me nuts.. Attempting to mount 'smb://timemachine@timemachine._smb._tcp.local./TimeMachine' 2022-06-28 23:16:43 Mounted 'smb://timemachine@timemachine._smb._tcp.local./TimeMachine' at '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine' (208.91 GB of 536.87 GB available) 2022-06-28 23:16:43 Initial network volume parameters for 'TimeMachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 60, QoS: 0x0, attributes: 0x1C} 2022-06-28 23:16:44 Configured network volume parameters for 'TimeMachine' {disablePrimaryReconnect: 1, disableSecondaryReconnect: 0, reconnectTimeOut: 30, QoS: 0x20, attributes: 0x1C} 2022-06-28 23:16:44 Skipping periodic backup verification: not needed for an APFS sparsebundle 2022-06-28 23:16:45 'Josh’s MacBook Pro.sparsebundle' does not need resizing - current logical size is 510.03 GB (510,027,366,400 bytes), size limit is 510.03 GB (510,027,366,400 bytes) 2022-06-28 23:16:45 Mountpoint '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine' is still valid 2022-06-28 23:16:45 Checking for runtime corruption on '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine/MacBook Pro.sparsebundle' 2022-06-28 23:17:22 Failed to attach using DiskImages2 to url '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine/MacBook Pro.sparsebundle', error: Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading} 2022-06-28 23:17:22 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine', Disk Management error: { Target = "file: Target = "file:///Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine/"; 2022-06-28 23:17:22 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-2DDB7F096A54/TimeMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.} 2022-06-28 23:17:22 Waiting 60 seconds and trying again. 2022-06-28 23:17:22 Cancelling backup because volume '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine' was unmounted. 2022-06-28 23:17:22 Requested backup cancellation or termination 2022-06-28 23:17:23 Backup cancelled (22: BACKUP_CANCELED) 2022-06-28 23:17:23 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine', Disk Management error: { Target = "file: Target = "file:///Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine/"; 2022-06-28 23:17:23 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./714A1D80-0056-45C2-8FC5-4ADB7F096A65/TimeMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.} 2022-06-28 23:17:23 Cleared pending cancellation request
  5. I have not, but actually, I'd rather not have time machine working than reinstall macOS and have to set everything up again lol
  6. I figured I'd give it some time, but the initial backup was June 14th and multiple times a day, I've tried to kick off a manual backup to no avail..
  7. Yup, that was my problem... I was trying to change the username and thought that was all I'd need, thank you! However... I had very high hopes of this! Setting up TM was super simple. However, I still cannot get it to sync after the first time.. I don't understand why it's throwing "Operation not supported by device"... 2022-06-25 01:02:02 Running for notifyd event com.apple.system.powersources.source 2022-06-25 01:02:32 TMPowerState: 2 2022-06-25 01:02:32 Not prioritizing backups with priority errors. lockState=0 2022-06-25 01:02:32 Starting automatic backup 2022-06-25 01:02:32 Attempting to mount 'smb://timemachine@timemachine._smb._tcp.local./TimeMachine' 2022-06-25 01:02:34 Mounted 'smb://timemachine@timemachine._smb._tcp.local./TimeMachine' at '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine' (212.63 GB of 536.87 GB available) 2022-06-25 01:02:34 Initial network volume parameters for 'TimeMachine' {disablePrimaryReconnect: 0, disableSecondaryReconnect: 0, reconnectTimeOut: 60, QoS: 0x0, attributes: 0x1C} 2022-06-25 01:02:34 Configured network volume parameters for 'TimeMachine' {disablePrimaryReconnect: 1, disableSecondaryReconnect: 0, reconnectTimeOut: 30, QoS: 0x20, attributes: 0x1C} 2022-06-25 01:02:35 Skipping periodic backup verification: not needed for an APFS sparsebundle 2022-06-25 01:02:36 'MacBook Pro.sparsebundle' does not need resizing - current logical size is 510.03 GB (510,027,366,400 bytes), size limit is 510.03 GB (510,027,366,400 bytes) 2022-06-25 01:02:36 Mountpoint '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine' is still valid 2022-06-25 01:02:36 Checking for runtime corruption on '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F3869E31C2/TimeMachine/MacBook Pro.sparsebundle' 2022-06-25 01:03:15 Failed to attach using DiskImages2 to url '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine/MacBook Pro.sparsebundle', error: Error Domain=NSPOSIXErrorDomain Code=19 "Operation not supported by device" UserInfo={DIErrorVerboseInfo=Failed to initialize IO manager: Failed opening folder for entries reading} 2022-06-25 01:03:15 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine', Disk Management error: { Target = "file: Target = "file:///Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine/"; 2022-06-25 01:03:15 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.} 2022-06-25 01:03:15 Waiting 60 seconds and trying again. 2022-06-25 01:03:15 Cancelling backup because volume '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine' was unmounted. 2022-06-25 01:03:15 Requested backup cancellation or termination 2022-06-25 01:03:16 Backup cancelled (22: BACKUP_CANCELED) 2022-06-25 01:03:16 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine', Disk Management error: { Target = "file: Target = "file:///Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine/"; 2022-06-25 01:03:16 Failed to unmount '/Volumes/.timemachine/timemachine._smb._tcp.local./365D6DA7-1C3D-454E-AA94-D1F38d7f34eaa/TimeMachine', error: Error Domain=com.apple.diskmanagement Code=0 "No error" UserInfo={NSDebugDescription=No error, NSLocalizedDescription=No Error.} 2022-06-25 01:03:16 Cleared pending cancellation request
  8. I cannot figure out what I'm doing wrong... I leave everything default (so the container creates the share required) and run the chown command, but timemachine still is writing to the docker image. I believe I've read everything in these two pages but haven't found anything I'm forgetting to do.
  9. I removed the container and openrct2 folder and was able to get it to read an old .sv6 file I had previously, but I still get the "Unable to connect to server" error when I connect, but it lets me right in anyway without any other issues. Also, because OpenRCT2 now has their own save format, Name.park, is there anything besides changing the filename within the Docker settings that needs done to get the server to use that file? I tried and it just reverted to my old save file (not the docker default). But if I try to revert the save to the docker default's "docker.sv6", it doesn't honor my change.... Thank you, I really appreciate the help so far!
  10. Assuming you mean /mnt/user/appdata/openrct2/user-data/config.ini, they are set to what I customized it to: player_name = "Josh" default_password = "CustomSecret" server_name = "CustomName" server_description = "Custom Description. advertise = true advertise_address = "" master_server_url = "" That's strange that since the password is on by default for your container, yet I am not prompted to enter it.. I also should note that currently I do not have ports forwarded so I manually entered my NAS's IP address in my OpenRCT2 client to connect locally. However I don't see my server being advertised within the master server. Maybe because the address property is null?
  11. Thank you for looking into it! So, the server customization, such as the name and description (even though it's not prompting for a password or a welcome message, maybe because my client is already a known client with a key?), however the save file specified in the Docker settings isn't being honored for some reason. It keeps defaulting to "docker.sv6" instead of the filename I have listed. Somehow, even after I overwrite the "docker.sv6" with my own file. I'm confused on how that's even possible, unless that save file is cached somewhere..? Might also be something to note, when I do connect to the server running within Docker, I get a "unable to connect to server" red error right away, but it connects anyway.
  12. the appdata share is set to prefer. I'm assuming it should be only? There's been plenty of room on that cache pool though, so it shouldn't have moved to an HDD.
  13. (For OpenCTR2) Not the person who asked the question, but I'm also having that issue. I'm changing that value, as well as other values within /mnt/array_cache/appdata/openrct2/user-data/config.ini, such as default_password (that should require users to enter a password, right?) and it appears that the container is ignoring me partially. server_name, description is working, however.
  14. I'm able to create the first backup without issues, but any backup afterwards just ends up "Preparing Backup" and then Stopping... macOS 12.3.1, unRAID 6.9.1
  15. Yup, sorry, like I said, I felt like a complete noob and was making a stupid, simple mistake. Thank you! I'm very new to dockers and forgot that their data is just a folder inside the appdata share.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.