Dousi

Hi Everyone I have a problem with my owncloud install. chbmb helped me confogure my install and there he fixed that the appdata folder is on the cache drive. now I synced my files to my owncloud. the problem I have is that the files are stored on the cachedrive and my cachedrive isn't that big, and its not parity protected. I changed the location in the install but it wont finish the setup then. now, how can I move the data Folder to a usershare? I use the official Owncloud docker, not dlandon. thanks an regards. Dousi

not an asshole at all, Im very happy you got it working!

its not just this docker, its the same with plex and duckdns

docker log: ErrorWarningSystemArrayLogin [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-app-niceness.sh: executing... [cont-init.d] 00-app-niceness.sh: exited 0. [cont-init.d] 00-app-script.sh: executing... [cont-init.d] 00-app-script.sh: exited 0. [cont-init.d] 00-app-user-map.sh: executing... [cont-init.d] 00-app-user-map.sh: exited 0. [cont-init.d] 00-clean-logmonitor-states.sh: executing... [cont-init.d] 00-clean-logmonitor-states.sh: exited 0. [cont-init.d] 00-clean-tmp-dir.sh: executing... [cont-init.d] 00-clean-tmp-dir.sh: exited 0. [cont-init.d] 00-set-app-deps.sh: executing... [cont-init.d] 00-set-app-deps.sh: exited 0. [cont-init.d] 00-set-home.sh: executing... [cont-init.d] 00-set-home.sh: exited 0. [cont-init.d] 00-take-config-ownership.sh: executing... [cont-init.d] 00-take-config-ownership.sh: exited 0. [cont-init.d] 00-xdg-runtime-dir.sh: executing... [cont-init.d] 00-xdg-runtime-dir.sh: exited 0. [cont-init.d] 10-certs.sh: executing... [cont-init.d] 10-certs.sh: exited 0. [cont-init.d] 10-cjk-font.sh: executing... [cont-init.d] 10-cjk-font.sh: exited 0. [cont-init.d] 10-nginx.sh: executing... [cont-init.d] 10-nginx.sh: exited 0. [cont-init.d] 10-vnc-password.sh: executing... [cont-init.d] 10-vnc-password.sh: exited 0. [cont-init.d] 10-web-index.sh: executing... [cont-init.d] 10-web-index.sh: exited 0. [cont-init.d] jdownloader2.sh: executing... [cont-init.d] jdownloader2.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] starting s6-fdholderd... [services.d] starting certsmonitor... [services.d] starting nginx... [certsmonitor] disabling service: secure connection not enabled. [services.d] starting xvfb... [nginx] starting... [xvfb] starting... [services.d] starting logmonitor... [services.d] starting statusmonitor... [statusmonitor] no file to monitor: disabling service... [logmonitor] no file to monitor: disabling service... [services.d] starting openbox... [openbox] starting... [services.d] starting x11vnc... [services.d] starting app... [x11vnc] starting... [app] starting JDownloader 2... 16/02/2019 18:23:14 passing arg to libvncserver: -rfbport 16/02/2019 18:23:14 passing arg to libvncserver: 5900 16/02/2019 18:23:14 passing arg to libvncserver: -rfbportv6 16/02/2019 18:23:14 passing arg to libvncserver: -1 16/02/2019 18:23:14 passing arg to libvncserver: -httpportv6 16/02/2019 18:23:14 passing arg to libvncserver: -1 16/02/2019 18:23:14 passing arg to libvncserver: -desktop 16/02/2019 18:23:14 passing arg to libvncserver: JDownloader 2 16/02/2019 18:23:14 x11vnc version: 0.9.14 lastmod: 2015-11-14 pid: 836 16/02/2019 18:23:14 Using X display :0 16/02/2019 18:23:14 rootwin: 0x43 reswin: 0x400001 dpy: 0xb6906a00 16/02/2019 18:23:14 16/02/2019 18:23:14 ------------------ USEFUL INFORMATION ------------------ [jdsupervisor] JDownloader2 not started yet. Proceeding... [services.d] done. 16/02/2019 18:23:14 X DAMAGE available on display, using it for polling hints. 16/02/2019 18:23:14 To disable this behavior use: '-noxdamage' 16/02/2019 18:23:14 16/02/2019 18:23:14 Most compositing window managers like 'compiz' or 'beryl' 16/02/2019 18:23:14 cause X DAMAGE to fail, and so you may not see any screen 16/02/2019 18:23:14 updates via VNC. Either disable 'compiz' (recommended) or 16/02/2019 18:23:14 supply the x11vnc '-noxdamage' command line option. 16/02/2019 18:23:14 X COMPOSITE available on display, using it for window polling. 16/02/2019 18:23:14 To disable this behavior use: '-noxcomposite' 16/02/2019 18:23:14 16/02/2019 18:23:14 Wireframing: -wireframe mode is in effect for window moves. 16/02/2019 18:23:14 If this yields undesired behavior (poor response, painting 16/02/2019 18:23:14 errors, etc) it may be disabled: 16/02/2019 18:23:14 - use '-nowf' to disable wireframing completely. 16/02/2019 18:23:14 - use '-nowcr' to disable the Copy Rectangle after the 16/02/2019 18:23:14 moved window is released in the new position. 16/02/2019 18:23:14 Also see the -help entry for tuning parameters. 16/02/2019 18:23:14 You can press 3 Alt_L's (Left "Alt" key) in a row to 16/02/2019 18:23:14 repaint the screen, also see the -fixscreen option for 16/02/2019 18:23:14 periodic repaints. 16/02/2019 18:23:14 GrabServer control via XTEST. 16/02/2019 18:23:14 16/02/2019 18:23:14 Scroll Detection: -scrollcopyrect mode is in effect to 16/02/2019 18:23:14 use RECORD extension to try to detect scrolling windows 16/02/2019 18:23:14 (induced by either user keystroke or mouse input). 16/02/2019 18:23:14 If this yields undesired behavior (poor response, painting 16/02/2019 18:23:14 errors, etc) it may be disabled via: '-noscr' 16/02/2019 18:23:14 Also see the -help entry for tuning parameters. 16/02/2019 18:23:14 You can press 3 Alt_L's (Left "Alt" key) in a row to 16/02/2019 18:23:14 repaint the screen, also see the -fixscreen option for 16/02/2019 18:23:14 periodic repaints. 16/02/2019 18:23:14 16/02/2019 18:23:14 XKEYBOARD: number of keysyms per keycode 7 is greater 16/02/2019 18:23:14 than 4 and 51 keysyms are mapped above 4. 16/02/2019 18:23:14 Automatically switching to -xkb mode. 16/02/2019 18:23:14 If this makes the key mapping worse you can 16/02/2019 18:23:14 disable it with the "-noxkb" option. 16/02/2019 18:23:14 Also, remember "-remap DEAD" for accenting characters. 16/02/2019 18:23:14 16/02/2019 18:23:14 X FBPM extension not supported. 16/02/2019 18:23:14 X display is not capable of DPMS. 16/02/2019 18:23:14 -------------------------------------------------------- 16/02/2019 18:23:14 16/02/2019 18:23:14 Default visual ID: 0x21 16/02/2019 18:23:14 Read initial data from X display into framebuffer. 16/02/2019 18:23:14 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120 16/02/2019 18:23:14 16/02/2019 18:23:14 X display :0 is 32bpp depth=24 true color 16/02/2019 18:23:14 16/02/2019 18:23:14 Listening for VNC connections on TCP port 5900 16/02/2019 18:23:14 16/02/2019 18:23:14 Xinerama is present and active (e.g. multi-head). 16/02/2019 18:23:14 Xinerama: number of sub-screens: 1 16/02/2019 18:23:14 Xinerama: no blackouts needed (only one sub-screen) 16/02/2019 18:23:14 16/02/2019 18:23:14 fb read rate: 1658 MB/sec 16/02/2019 18:23:14 fast read: reset -wait ms to: 10 16/02/2019 18:23:14 fast read: reset -defer ms to: 10 16/02/2019 18:23:14 The X server says there are 10 mouse buttons. 16/02/2019 18:23:14 screen setup finished. 16/02/2019 18:23:14 The VNC desktop is: 26a6d48f1350:0 0 ****************************************************************************** Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running: x11vnc -ncache 10 ... One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching [jdsupervisor] JDownloader2 no longer running. Exiting... [services.d] stopping services [services.d] stopping app... [services.d] stopping x11vnc... caught signal: 15 16/02/2019 18:23:21 deleted 40 tile_row polling images. [services.d] stopping openbox... [services.d] stopping statusmonitor... [services.d] stopping logmonitor... [services.d] stopping xvfb... [services.d] stopping nginx... [services.d] stopping certsmonitor... [services.d] stopping s6-fdholderd... [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 00-app-niceness.sh: executing... [cont-init.d] 00-app-niceness.sh: exited 0. [cont-init.d] 00-app-script.sh: executing... [cont-init.d] 00-app-script.sh: exited 0. [cont-init.d] 00-app-user-map.sh: executing... [cont-init.d] 00-app-user-map.sh: exited 0. [cont-init.d] 00-clean-logmonitor-states.sh: executing... [cont-init.d] 00-clean-logmonitor-states.sh: exited 0. [cont-init.d] 00-clean-tmp-dir.sh: executing... [cont-init.d] 00-clean-tmp-dir.sh: exited 0. [cont-init.d] 00-set-app-deps.sh: executing... [cont-init.d] 00-set-app-deps.sh: exited 0. [cont-init.d] 00-set-home.sh: executing... [cont-init.d] 00-set-home.sh: exited 0. [cont-init.d] 00-take-config-ownership.sh: executing... [cont-init.d] 00-take-config-ownership.sh: exited 0. [cont-init.d] 00-xdg-runtime-dir.sh: executing... [cont-init.d] 00-xdg-runtime-dir.sh: exited 0. [cont-init.d] 10-certs.sh: executing... [cont-init.d] 10-certs.sh: exited 0. [cont-init.d] 10-cjk-font.sh: executing... [cont-init.d] 10-cjk-font.sh: exited 0. [cont-init.d] 10-nginx.sh: executing... [cont-init.d] 10-nginx.sh: exited 0. [cont-init.d] 10-vnc-password.sh: executing... [cont-init.d] 10-vnc-password.sh: exited 0. [cont-init.d] 10-web-index.sh: executing... [cont-init.d] 10-web-index.sh: exited 0. [cont-init.d] jdownloader2.sh: executing... [cont-init.d] jdownloader2.sh: exited 0. [cont-init.d] done. [services.d] starting services [services.d] starting s6-fdholderd... [services.d] starting certsmonitor... [services.d] starting nginx... [certsmonitor] disabling service: secure connection not enabled. [services.d] starting xvfb... [nginx] starting... [xvfb] starting... [services.d] starting x11vnc... [services.d] starting logmonitor... [logmonitor] no file to monitor: disabling service... [x11vnc] starting... 16/02/2019 18:37:24 passing arg to libvncserver: -rfbport 16/02/2019 18:37:24 passing arg to libvncserver: 5900 16/02/2019 18:37:24 passing arg to libvncserver: -rfbportv6 16/02/2019 18:37:24 passing arg to libvncserver: -1 16/02/2019 18:37:24 passing arg to libvncserver: -httpportv6 16/02/2019 18:37:24 passing arg to libvncserver: -1 16/02/2019 18:37:24 passing arg to libvncserver: -desktop 16/02/2019 18:37:24 passing arg to libvncserver: JDownloader 2 16/02/2019 18:37:24 x11vnc version: 0.9.14 lastmod: 2015-11-14 pid: 785 16/02/2019 18:37:24 Using X display :0 16/02/2019 18:37:24 rootwin: 0x43 reswin: 0x200001 dpy: 0x94117a00 16/02/2019 18:37:24 16/02/2019 18:37:24 ------------------ USEFUL INFORMATION ------------------ [services.d] starting statusmonitor... [statusmonitor] no file to monitor: disabling service... [services.d] starting openbox... [openbox] starting... 16/02/2019 18:37:24 X DAMAGE available on display, using it for polling hints. 16/02/2019 18:37:24 To disable this behavior use: '-noxdamage' 16/02/2019 18:37:24 16/02/2019 18:37:24 Most compositing window managers like 'compiz' or 'beryl' 16/02/2019 18:37:24 cause X DAMAGE to fail, and so you may not see any screen 16/02/2019 18:37:24 updates via VNC. Either disable 'compiz' (recommended) or 16/02/2019 18:37:24 supply the x11vnc '-noxdamage' command line option. 16/02/2019 18:37:24 X COMPOSITE available on display, using it for window polling. 16/02/2019 18:37:24 To disable this behavior use: '-noxcomposite' 16/02/2019 18:37:24 16/02/2019 18:37:24 Wireframing: -wireframe mode is in effect for window moves. 16/02/2019 18:37:24 If this yields undesired behavior (poor response, painting 16/02/2019 18:37:24 errors, etc) it may be disabled: 16/02/2019 18:37:24 - use '-nowf' to disable wireframing completely. 16/02/2019 18:37:24 - use '-nowcr' to disable the Copy Rectangle after the 16/02/2019 18:37:24 moved window is released in the new position. 16/02/2019 18:37:24 Also see the -help entry for tuning parameters. 16/02/2019 18:37:24 You can press 3 Alt_L's (Left "Alt" key) in a row to 16/02/2019 18:37:24 repaint the screen, also see the -fixscreen option for 16/02/2019 18:37:24 periodic repaints. 16/02/2019 18:37:24 GrabServer control via XTEST. 16/02/2019 18:37:24 16/02/2019 18:37:24 Scroll Detection: -scrollcopyrect mode is in effect to 16/02/2019 18:37:24 use RECORD extension to try to detect scrolling windows 16/02/2019 18:37:24 (induced by either user keystroke or mouse input). 16/02/2019 18:37:24 If this yields undesired behavior (poor response, painting 16/02/2019 18:37:24 errors, etc) it may be disabled via: '-noscr' 16/02/2019 18:37:24 Also see the -help entry for tuning parameters. 16/02/2019 18:37:24 You can press 3 Alt_L's (Left "Alt" key) in a row to 16/02/2019 18:37:24 repaint the screen, also see the -fixscreen option for 16/02/2019 18:37:24 periodic repaints. 16/02/2019 18:37:24 16/02/2019 18:37:24 XKEYBOARD: number of keysyms per keycode 7 is greater 16/02/2019 18:37:24 than 4 and 51 keysyms are mapped above 4. 16/02/2019 18:37:24 Automatically switching to -xkb mode. 16/02/2019 18:37:24 If this makes the key mapping worse you can 16/02/2019 18:37:24 disable it with the "-noxkb" option. 16/02/2019 18:37:24 Also, remember "-remap DEAD" for accenting characters. 16/02/2019 18:37:24 16/02/2019 18:37:24 X FBPM extension not supported. 16/02/2019 18:37:24 X display is not capable of DPMS. 16/02/2019 18:37:24 -------------------------------------------------------- 16/02/2019 18:37:24 16/02/2019 18:37:24 Default visual ID: 0x21 16/02/2019 18:37:24 Read initial data from X display into framebuffer. 16/02/2019 18:37:24 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/5120 16/02/2019 18:37:24 16/02/2019 18:37:24 X display :0 is 32bpp depth=24 true color 16/02/2019 18:37:24 16/02/2019 18:37:24 Listening for VNC connections on TCP port 5900 16/02/2019 18:37:24 16/02/2019 18:37:24 Xinerama is present and active (e.g. multi-head). 16/02/2019 18:37:24 Xinerama: number of sub-screens: 1 16/02/2019 18:37:24 Xinerama: no blackouts needed (only one sub-screen) 16/02/2019 18:37:24 16/02/2019 18:37:24 fb read rate: 1584 MB/sec 16/02/2019 18:37:24 fast read: reset -wait ms to: 10 16/02/2019 18:37:24 fast read: reset -defer ms to: 10 16/02/2019 18:37:24 The X server says there are 10 mouse buttons. 16/02/2019 18:37:24 screen setup finished. 16/02/2019 18:37:24 The VNC desktop is: 26a6d48f1350:0 0 ****************************************************************************** Have you tried the x11vnc '-ncache' VNC client-side pixel caching feature yet? The scheme stores pixel data offscreen on the VNC viewer side for faster retrieval. It should work with any VNC viewer. Try it by running: x11vnc -ncache 10 ... One can also add -ncache_cr for smooth 'copyrect' window motion. More info: http://www.karlrunge.com/x11vnc/faq.html#faq-client-caching [services.d] starting app... [app] starting JDownloader 2... [jdsupervisor] JDownloader2 not started yet. Proceeding... [services.d] done. [jdsupervisor] JDownloader2 no longer running. Exiting... [services.d] stopping services [services.d] stopping app... [services.d] stopping openbox... [services.d] stopping statusmonitor... [services.d] stopping logmonitor... [services.d] stopping x11vnc... caught signal: 15 16/02/2019 18:37:33 deleted 40 tile_row polling images. [services.d] stopping xvfb... [services.d] stopping nginx... [services.d] stopping certsmonitor... [services.d] stopping s6-fdholderd... [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. System log: ErrorWarningSystemArrayLogin Feb 16 17:59:16 Tower kernel: eth0: renamed from veth1127de5 Feb 16 17:59:16 Tower kernel: device br0 entered promiscuous mode Feb 16 17:59:36 Tower kernel: device br0 left promiscuous mode Feb 16 17:59:36 Tower kernel: veth1127de5: renamed from eth0 Feb 16 18:01:01 Tower root: Fix Common Problems Version 2019.01.19 Feb 16 18:01:02 Tower root: Fix Common Problems: Error: Default docker appdata location is not a cache-only share Feb 16 18:01:02 Tower root: Fix Common Problems: Warning: Plugin community.applications.plg is not up to date Feb 16 18:03:31 Tower emhttpd: req (1): shareNameOrig=appdata&shareName=appdata&shareComment=&shareAllocator=highwater&shareFloor=0&shareSplitLevel=&shareInclude=&shareExclude=&shareUseCache=only&cmdEditShare=Apply&csrf_token=**************** Feb 16 18:03:31 Tower emhttpd: Starting services... Feb 16 18:04:53 Tower emhttpd: req (2): cmd=/plugins/dynamix.plugin.manager/scripts/plugin&arg1=update&arg2=community.applications.plg&csrf_token=**************** Feb 16 18:04:53 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin update community.applications.plg Feb 16 18:04:53 Tower root: plugin: running: anonymous Feb 16 18:04:54 Tower root: plugin: running: anonymous Feb 16 18:04:54 Tower root: plugin: creating: /boot/config/plugins/community.applications/community.applications-2019.02.16a-x86_64-1.txz - downloading from URL https://raw.github.com/Squidly271/community.applications/master/archive/community.applications-2019.02.16a-x86_64-1.txz Feb 16 18:04:54 Tower root: plugin: checking: /boot/config/plugins/community.applications/community.applications-2019.02.16a-x86_64-1.txz - MD5 Feb 16 18:04:54 Tower root: plugin: running: /boot/config/plugins/community.applications/community.applications-2019.02.16a-x86_64-1.txz Feb 16 18:04:55 Tower root: plugin: running: anonymous Feb 16 18:06:49 Tower kernel: eth0: renamed from vethe8dcbfd Feb 16 18:06:49 Tower kernel: device br0 entered promiscuous mode Feb 16 18:07:13 Tower kernel: device br0 left promiscuous mode Feb 16 18:07:13 Tower kernel: vethe8dcbfd: renamed from eth0 Feb 16 18:22:42 Tower kernel: eth0: renamed from veth463c8d5 Feb 16 18:22:42 Tower kernel: device br0 entered promiscuous mode Feb 16 18:23:05 Tower kernel: device br0 left promiscuous mode Feb 16 18:23:05 Tower kernel: veth463c8d5: renamed from eth0 Feb 16 18:23:10 Tower kernel: eth0: renamed from veth2086311 Feb 16 18:23:10 Tower kernel: device br0 entered promiscuous mode Feb 16 18:23:30 Tower kernel: device br0 left promiscuous mode Feb 16 18:23:30 Tower kernel: veth2086311: renamed from eth0 Feb 16 18:32:46 Tower kernel: mdcmd (44): spindown 3 Feb 16 18:32:46 Tower kernel: mdcmd (45): spindown 4 Feb 16 18:32:46 Tower kernel: mdcmd (46): spindown 6 Feb 16 18:32:47 Tower kernel: mdcmd (47): spindown 5 Feb 16 18:32:47 Tower kernel: mdcmd (48): spindown 7 Feb 16 18:37:23 Tower kernel: eth0: renamed from vethc2f5b6b Feb 16 18:37:23 Tower kernel: device br0 entered promiscuous mode Feb 16 18:37:41 Tower kernel: device br0 left promiscuous mode Feb 16 18:37:41 Tower kernel: vethc2f5b6b: renamed from eth0 it just doesnt work means that it does install succesfully and starts, but no gui shows up and then it just stopps. I'm no IT guy so Im struggling a bit with this troubleshooting. thanks

Hello all I've run my unraid server for quite some time now and had never had any problems. I ran owncloud, jd2 and Plex as docker containers. as I moved and had switched to mobile internetI could not serve plex to my users, So I switched to a standalone plex Server on Ubuntu. now I'm trying to get Plex/ nextcloud/ openvpn/ duckdns/ jd2 to run on the unraid server again, but I cant get a single docker to work properly. I'm running Unraid 6.6.6 had disabled docker, made a fresh start for itwith a new appdata folder am system folder, but it just wont work. I have read the faq and serched the web, but wasn't able to find a solution. currently i'm trying to instll jd2 from jlesage. Startcommand: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='JDownloader2' --net='br0' --cpuset-cpus='0,1' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'USER_ID'='99' -e 'GROUP_ID'='100' -e 'UMASK'='000' -e 'APP_NICENESS'='' -e 'DISPLAY_WIDTH'='1280' -e 'DISPLAY_HEIGHT'='768' -e 'SECURE_CONNECTION'='0' -e 'X11VNC_EXTRA_OPTS'='' -e 'TCP_PORT_7807'='7807' -e 'TCP_PORT_7907'='7907' -e 'TCP_PORT_5800'='7807' -e 'TCP_PORT_5900'='7907' -v '/mnt/user/Download/':'/output':'rw' -v '/mnt/user/appdata/JDownloader2':'/config':'rw' 'jlesage/jdownloader-2' 26a6d48f1350998b6b301f610800a65c038ea65062252a1a0c8f1d1d347d489a any tips from you guys? thank you for your help

now, I've got that new controller and moved all files from disk 5 as a preparation to replace it once everything else works properly. how am I gonna do that new parity resync? regards

I'll replace it then, thank for your help! I just finished the read check an it finished successfully, stating the parity is valid. would that mean that I can replace the disk 5 and restore the data from the parity drive?

I'm currently doing this. I've got this one: my controller is it possible to find out if its got this port multiplier thing? I'd go for an Adaptec then, as the LSI is very pricey for me....

how can I do that if its not the controller? how can I find out what it is? do you have a recommendation for a controller? I need at least 4 sata ports. how could I make this filesystem check?

Good day alltogether! I'm currently starting to panic a bit, as im afraid I might have lost some data... My parity disk appears to be faulty. and multiple hdd's have bad smart reports, while other who have good smart reports show no data on them... as I wanted to check if the parity disk is defect or if it work i had hooked it up to my mac and accidently formatted it, so I guess the parity ist not valid anymore, so no data reconstruction possible. in the dashboard.tiff pic you can see the faulty parity disc, as well as disc 3, 5 and 7 showing bad smart reports. in the Main screen.tiff pic you can see the data usage on disc 2 and in disk2.tiff pic there is no data visible. the smart says its OK and a self test shows its ok too... I added a diagnostics file too, for you pro's to check that out. now I am completely lost and have no idea what to do and hope you can guide me through this wich as low losses as possible... thank you all in advance and best regards. tower-diagnostics-20180128-0320.zip

That actually was it! Thank you, now I can access the UI! 3 Months not running because of such a simple thing... Thanks to all of you and best regards!

sorry, I thoght it wasn't necessary anymore. have it attached now. thanks for your help tower-diagnostics-20170708-1726.zip

sorry, it took so long for me to continue on this topic, but I've got loads of work to do and haven't got time to work an the Server sooner. now I've managed to get owncloud to boot no problm, but I cant access the web ui. when I go to the domain from local network or over the web, all I get is the integrated BMC web console. how can I access the web ui to start the owncloud array? thanks again for your help!

Ran for 24hours, no errors. still will look to get a diagnistics File now.

I am sorry it took so long for me to answer, but I am really busy at he moment and have some real struggle getting my server to run. I now cant get my server to boot again, it always has a kernel panic while booting. to resolve this, I will now try an older version of unraid. thats why I wasn't able to get a diagnistics file yet. I will post a s soon as it boots again. at the same time I cant access my Server from the web, and I am thinking that this might be because of the ipmi feature of the Mainboard. would this be possible? I can access the remote bmc console via the ip adress in my network, but nothing else. Is there a way to disable this bmc console? I was not able to find a solution. Thanks for your help! Florian