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.

unRAID trial expiring while running docker safe new permissions

Featured Replies

Hi,

 

I was having permission problems with some of my files not being accessible over a public smb share so i started a the Docker safe new permssions task in order to fix this.. the warning stated it would take a long time but for the 4.5TB of files on the server it has been running for nearly three days now and my trial is expiring in 9hrs (i thought a long time would be 2 days max..i was wrong). I'm not sure if the process has crashed but i can't access the GUI from a different browser so i assume it is still running fine.

 

Do i need to worry about the the trial expiring during the task?

 

Regards.

The impact of the trial expiring should be that you can no longer start the array.  Existing operations should continue, though.

  • Author

Cool thanks for the info. I hope this thing finishes soon. So i can purchase a license.

Sent from my ONEPLUS A3003 using Tapatalk

1 hour ago, Bilal Yassine said:

it has been running for nearly three days now

Something's gone wrong.  Unless you've got about a billion files on your server.  Basic worst case is a few hours tops.   Has the pop up progressed at all?  

  • Author

hi thanks for the response.

 

it finished with disk1 and moved onto disk2 fairly quickly then it got stuck on the share with a vast bulk of the data. tbh i just tried to login using a browser on a different machine to the one i initiated the permissions task on and i was able to access the UI so i assumed it had completed even though other browser was just sitting there i then restarted the server .

 

my log (the button on the right side of the menubar)  currently shows:

Sep 18 15:50:02 unApollo kernel: eth0: renamed from vethc9501fd
Sep 18 15:50:02 unApollo kernel: docker0: port 3(vethdc1fd7a) entered blocking state
Sep 18 15:50:02 unApollo kernel: docker0: port 3(vethdc1fd7a) entered forwarding state
Sep 18 15:50:02 unApollo root: 5 seconds sleep before starting nextcloud
Sep 18 15:50:06 unApollo vsftpd[16581]: connect from 127.0.0.1 (127.0.0.1)
Sep 18 15:50:07 unApollo root: Starting nextcloud
Sep 18 15:50:07 unApollo kernel: docker0: port 4(vethea67431) entered blocking state
Sep 18 15:50:07 unApollo kernel: docker0: port 4(vethea67431) entered disabled state
Sep 18 15:50:07 unApollo kernel: device vethea67431 entered promiscuous mode
Sep 18 15:50:07 unApollo kernel: docker0: port 4(vethea67431) entered blocking state
Sep 18 15:50:07 unApollo kernel: docker0: port 4(vethea67431) entered forwarding state
Sep 18 15:50:07 unApollo kernel: docker0: port 4(vethea67431) entered disabled state
Sep 18 15:50:07 unApollo kernel: eth0: renamed from veth25840e5
Sep 18 15:50:07 unApollo kernel: docker0: port 4(vethea67431) entered blocking state
Sep 18 15:50:07 unApollo kernel: docker0: port 4(vethea67431) entered forwarding state
Sep 18 15:50:07 unApollo root: 5 seconds sleep before starting Krusader
Sep 18 15:50:12 unApollo root: Starting Krusader
Sep 18 15:50:12 unApollo kernel: docker0: port 5(veth5818905) entered blocking state
Sep 18 15:50:12 unApollo kernel: docker0: port 5(veth5818905) entered disabled state
Sep 18 15:50:12 unApollo kernel: device veth5818905 entered promiscuous mode
Sep 18 15:50:12 unApollo kernel: docker0: port 5(veth5818905) entered blocking state
Sep 18 15:50:12 unApollo kernel: docker0: port 5(veth5818905) entered forwarding state
Sep 18 15:50:12 unApollo kernel: docker0: port 5(veth5818905) entered disabled state
Sep 18 15:50:12 unApollo kernel: eth0: renamed from veth3427095
Sep 18 15:50:12 unApollo kernel: docker0: port 5(veth5818905) entered blocking state
Sep 18 15:50:12 unApollo kernel: docker0: port 5(veth5818905) entered forwarding state
Sep 18 15:50:12 unApollo root: CA Docker Autostart Manager Finished
Sep 18 15:50:16 unApollo vsftpd[17866]: connect from 127.0.0.1 (127.0.0.1)
Sep 18 15:50:26 unApollo vsftpd[18457]: connect from 127.0.0.1 (127.0.0.1)
Sep 18 15:50:36 unApollo vsftpd[19090]: connect from 127.0.0.1 (127.0.0.1)
Sep 18 15:50:46 unApollo vsftpd[19573]: connect from 127.0.0.1 (127.0.0.1)
Sep 18 15:50:56 unApollo vsftpd[20111]: connect from 127.0.0.1 (127.0.0.1)
Sep 18 15:51:01 unApollo emhttp: shcmd (118): chmod 0777 '/mnt/user/zoneminder_data'
Sep 18 15:51:01 unApollo emhttp: shcmd (119): chown 'nobody':'users' '/mnt/user/zoneminder_data'
Sep 18 15:51:06 unApollo vsftpd[20724]: connect from 127.0.0.1 (127.0.0.1)
Sep 18 15:51:16 unApollo vsftpd[21227]: connect from 127.0.0.1 (127.0.0.1)
Sep 18 15:51:26 unApollo vsftpd[21755]: connect from 127.0.0.1 (127.0.0.1)
Sep 18 16:40:01 unApollo rc.diskinfo[30949]: process started. To terminate it, type: rc.diskinfo --quit


i'm a little concerned now that it says its started chmod operations so i guess this means i restarted prematurely...(i'm such a newb)

 

 

Edited by Bilal Yassine
forgot my manners

Archived

This topic is now archived and is closed to further replies.

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.