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.

Set of events that can affect appdata

Featured Replies

About 2 weeks ago i noticed something really strange with folders in my appdata share, i thought it was a hardware related issue and replaced, cable, cache drive and finally usb key.

 

it was happening after a specific set of events... adding a docker, changing a folder mapping in the template and/or in the appdata folder itself. after restarting the docker the appdata folder for that particular docker was displaying this with ls -lah

 

/bin/ls: cannot access build-area: No such file or directory
total 0
drwxrwxrwx 1 nobody users 39 Oct  3 14:44 ./
drwxrwxrwx 1 nobody users 84 Oct  3 14:42 ../
d??? ? ?      ?      ?            ? build-area/

 

annoyingly i couldn't reproduce it, so i thought it was something local to me and possibly hardware related.

 

if i issued rm -rf on the folder concerned it gave an error

 

rm -rf build-area
rm: cannot remove ‘build-area’: Is a directory

 

and rather oddly after the failed rm, the folder returned to normal when looked at with ls -lah

 

but the really worrying part was that any new dockers i added or any new folders created by existing dockers then had the same issue.. and mysql then stopped working, telling me all my tables were invalid, sickbeard, couchpotato and sabnzbd soon followed suit with their own errors.

 

restarting straight away after seeing the initial error and everything returns to normal, BUT once the appdata folders for the other dockers started exhibiting the same errors, their data was lost. this has happened to me twice now.

 

 

 

as i said before, i thought it was a hardware issue local to me ,until earlier, when i reproduced it on my second unraid box.

 

to reproduce, i added an app from CA via the dockerhub search method.... stopped the app. deleted one of the subfolders in appdata for the app, restarted the docker and got the errors above. needless to say, i rebooted pretty damn pronto.

 

unraid version 6.1.3

  • Author

So what changed since I tried to reproduce it on my box?

 

the weather, global interest rates, my socks.

So what changed since I tried to reproduce it on my box?

 

the weather, global interest rates, my socks.

 

Worryingly your pants aren't on that list. 

 

I'll rephrase, what steps did we miss out when testing it on mine? 

 

Would it help if I tried again?

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.