fonzie

Do I run the NewPerms tool to restore the write settings to my drives? I know that it says only to do this when transitioning from an older version of unRAID, but I don't know what else to do and I need to gain write access back on my unRAID server. This is the syslog when trying to create a new folder within the Never Been Kissed directory Feb 11 18:25:50 media avahi-daemon[10926]: Files changed, reloading. Feb 11 18:25:50 media avahi-daemon[10926]: Service group file /services/smb.service changed, reloading. Feb 11 18:25:50 media emhttp: shcmd (264): pidof rpc.mountd &> /dev/null Feb 11 18:25:50 media emhttp: shcmd (265): /etc/rc.d/rc.atalk status Feb 11 18:25:51 media avahi-daemon[10926]: Service "media" (/services/smb.service) successfully established. Feb 11 18:26:03 media emhttp: shcmd (266): :>/etc/samba/smb-shares.conf Feb 11 18:26:03 media avahi-daemon[10926]: Files changed, reloading. Feb 11 18:26:03 media emhttp: Restart SMB... Feb 11 18:26:03 media emhttp: shcmd (267): killall -HUP smbd Feb 11 18:26:03 media emhttp: shcmd (268): smbcontrol smbd close-share 'Movies' Feb 11 18:26:03 media emhttp: shcmd (269): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Feb 11 18:26:03 media avahi-daemon[10926]: Files changed, reloading. Feb 11 18:26:03 media avahi-daemon[10926]: Service group file /services/smb.service changed, reloading. Feb 11 18:26:03 media emhttp: shcmd (270): pidof rpc.mountd &> /dev/null Feb 11 18:26:03 media emhttp: shcmd (271): /etc/rc.d/rc.atalk status Feb 11 18:26:04 media avahi-daemon[10926]: Service "media" (/services/smb.service) successfully established. Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:13 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:27:17 media shfs/user: shfs_mkdir: mkdir: /mnt/cache/Movies/Never Been Kissed (1999)/New folder (30) Read-only file system Feb 11 18:30:30 media sshd[3920]: Accepted none for root from 192.168.1.103 port 50959 ssh2 Feb 11 18:30:59 media shfs/user: shfs_mkdir: create_path: /mnt/cache/Movies/(500) Days of Summer (2009) Movies/(500) Days of Summer (2009)/test folder /mnt/disk7/Movies/(500) Days of Summer (2009) (30) Read-only file system Feb 11 18:31:12 media shfs/user: shfs_mkdir: create_path: /mnt/cache/Movies/(500) Days of Summer (2009) Movies/(500) Days of Summer (2009)/test folder /mnt/disk7/Movies/(500) Days of Summer (2009) (30) Read-only file system

So I got the replacement hard drive, precleared it, rebuilt it, and fixed the filesystem structure on it. I also ran a parity check right after that and there were no sync errors detected. I no longer have a faulty drive or bad SMART reports. I thought I would be okay, but I still cannot create folders within any of my shares. It says I do not have the permission from within Windows File Explorer. Looking at the error log that couchpotato is giving me, it seems like my shares are still set as read-only. How do I fix this? What else could be the problem?

I'm having issues getting the NZBGet docker to start. I used to have it running perfectly without issues until one day it just stopped running. I think it had something to do with filesystem corruption, so I repaired the file system and got out of the "read-only" state I was locked in. I thought that would solve my problems but it has not. I removed the docker container and files. Erased all traces of NZBGet and tried to start fresh. Yet I still cannot get the docker to run. I attached the log file: ------------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io We do accept donations at: https://www.linuxserver.io/donations ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- finding fastest mirror 1. mirror.os6.org Latency: 15 ms Org: os6.org Status: Up to date Speed: 1 Gbps 2. mirrors.namecheap.com Latency: 25 ms Org: NameCheap.com Status: Up to date Speed: 1 Gbps 3. ubuntu.securedservers.com Latency: 26 ms Org: Secured Servers LLC Status: Up to date Speed: 100 Mbps New config file saved to /defaults/sources.list We are now refreshing packages from apt repositories, this *may* take a while Ign http://mirror.os6.org trusty InRelease Get:1 http://mirror.os6.org trusty-updates InRelease [64.4 kB] Get:2 http://mirror.os6.org trusty-security InRelease [64.4 kB] Get:3 http://mirror.os6.org trusty Release.gpg [933 B] Get:4 http://mirror.os6.org trusty Release [58.5 kB] Get:5 http://mirror.os6.org trusty-updates/main Sources [313 kB] Get:6 http://mirror.os6.org trusty-updates/restricted Sources [5,219 B] Get:7 http://mirror.os6.org trusty-updates/universe Sources [186 kB] Get:8 http://mirror.os6.org trusty-updates/multiverse Sources [5,113 B] Get:9 http://mirror.os6.org trusty-updates/main amd64 Packages [875 kB] Get:10 http://mirror.os6.org trusty-updates/restricted amd64 Packages [23.4 kB] Get:11 http://mirror.os6.org trusty-updates/universe amd64 Packages [436 kB] Get:12 http://mirror.os6.org trusty-updates/multiverse amd64 Packages [14.1 kB] Get:13 http://mirror.os6.org trusty-security/main Sources [129 kB] Get:14 http://mirror.os6.org trusty-security/restricted Sources [3,920 B] Get:15 http://mirror.os6.org trusty-security/universe Sources [37.9 kB] Get:16 http://mirror.os6.org trusty-security/multiverse Sources [2,164 B] Get:17 http://mirror.os6.org trusty-security/main amd64 Packages [517 kB] Get:18 http://mirror.os6.org trusty-security/restricted amd64 Packages [20.2 kB] Get:19 http://mirror.os6.org trusty-security/universe amd64 Packages [160 kB] Get:20 http://mirror.os6.org trusty-security/multiverse amd64 Packages [4,643 B] Get:21 http://mirror.os6.org trusty/main Sources [1,335 kB] Get:22 http://mirror.os6.org trusty/restricted Sources [5,335 B] Get:23 http://mirror.os6.org trusty/universe Sources [7,926 kB] Get:24 http://mirror.os6.org trusty/multiverse Sources [211 kB] Get:25 http://mirror.os6.org trusty/main amd64 Packages [1,743 kB] Get:26 http://mirror.os6.org trusty/restricted amd64 Packages [16.0 kB] Get:27 http://mirror.os6.org trusty/universe amd64 Packages [7,589 kB] Get:28 http://mirror.os6.org trusty/multiverse amd64 Packages [169 kB] Fetched 21.9 MB in 4s (4,906 kB/s)

This device is $300 and you must also have a subscription. Why not just opt for an HDHomerun? Are there any benefits to this other than the additional tuners?

Okay, so if I understand you correctly my process should be: 1. Buy new disk and preclear it 2. rebuild new precleared disk as disk 6 3. try to fix the filesystem with reiserfsck 4. use the old disk 6 which is about to fail as a backup in case some files are lost when repairing the filesystem on the new drive is this correct?

Looking at the SMART report I'm finding these two lines highlighted in yellow which according to my research may mean that my drive is about to or already is failing. Should I even bother with trying to rebuild the file system and likely losing some data while it tries to do so....or should I replace this drive and use my Parity to rebuild the new replacement data drive? # Attribute Name Flag Value Worst Threshold Type Updated Failed Raw Value 187 Reported uncorrect 0x0032 099 099 000 Old age Always Never 1 188 Command timeout 0x0032 100 098 000 Old age Always Never 38655492112

I got this on Disk 6: So I attempted to run the code --rebuild-tree and then I get the following page: reiserfsck 3.6.24 ************************************************************* ** Do not run the program with --rebuild-tree unless ** ** something is broken and MAKE A BACKUP before using it. ** ** If you have bad sectors on a drive it is usually a bad ** ** idea to continue using it. Then you probably should get ** ** a working hard drive, copy the file system from the bad ** ** drive to the good one -- dd_rescue is a good tool for ** ** that -- and only then run this program. ** ************************************************************* Will rebuild the filesystem (/dev/md6) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do): So I type "Yes" without the quotations and select check, but it just kicks me back to the previous page and doesn't seem do much of anything to rebuild the filesystem on it. What am I doing wrong? And according to the writing up there...I should be backing up the harddrive before doing this filesystem restore?

I have attached my full diagnostics zip. It does seem to be experiencing read-only errors. *Also, I have the inability to start up my VM due to it being read-only I think. media-diagnostics-20160111-1619.zip

Yesterday I found I have suddenly been unable to create new folders in my Movies share. I can delete existing files and view the movies but once I try to create a new folder anywhere within that share, I get a "You need permission to perform this action" notification. I haven't changed security settings or added users or anything like that. In fact, when I first got the issue last night, the first thing I did was remove all the users except root (it didn't help). I also tried running the "take ownership" command from within windows with a registry hack I found online. I ran it in the root of the Movie share, but it ran very quickly and I don't think it actually worked. Because I've run it in the past and the process usually take a while to go through all the files. I read quickly in the forums someone who had a similar issue once before, they posted their syslog and were told that it was a reiserfs problem. Most of my drives are in that format and I also have 3 drives in my array that have given me some concerns over their SMART status. Two of them have a command timeout with a number following it. And another has a command timeout in addition to a "reported uncorrect: 1" Not sure what any of this means or how it can affect me. I am planning on running a parity check tonight and hoping this all gets corrected. If anyone has any advice I would greatly appreciate it.

Yep. This came out in my syslog: Dec 30 13:15:35 media kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Dec 30 13:15:35 media kernel: sas: ata11: end_device-1:0: dev error handler Dec 30 13:15:35 media kernel: sas: ata12: end_device-1:1: dev error handler Dec 30 13:15:35 media kernel: sas: ata13: end_device-1:2: dev error handler Dec 30 13:15:35 media kernel: sas: ata14: end_device-1:3: dev error handler Dec 30 13:15:35 media kernel: sas: ata15: end_device-1:4: dev error handler Dec 30 13:15:35 media kernel: ata15.00: HPA detected: current 625140335, native 625142448 So what steps do I take now to rectify the problem? Obviously I will be swapping out the motherboard. But I want to preserve all my data and avoid any corruption if possible.

After doing more research, I think my Gigabyte motherboard might be causing an issue. It has dual bios and I'm pretty sure it has HPA. I've had it running like this for a few months now, so I don't know how much damage I've done to all my hard drives with those hidden partitions. I'm going to swap out the new gigabyte motherboard with my original asus motherboard that gave me no errors.' If that turns out to be the problem, how do I reverse the damage that has been done to my hard drives by the HPA? for example, how do I narrow down which drives were affected?

Okay, so I just had another drive failure. I went to tools-->diagnostics and saved the zip file. My concern is that the zip contains passwords and information from some of my dockers. I want to post the zip as soon as possible so can someone please tell me if it is safe to do so, or which files I should exclude from the zip. thanks.

I have two servers each with a "Shows" share. My main unRAID server is running emby through the dockers. I can add the Shows share that is running on that server easily due to the docker remaping. The only issue I am having is being able to add the Shows share from my second unRAID machine to the emby library on myk primary rig. How is this accomplished? I'm not an expert with command line...so if that is necessary for permissions or something please simplify it for me. hehe thanks

I got it working somehow after removing the docker and reinstalling several times. I think it had something to do with the linuxserver.io yesterday because I noticed a few of their dockers weren't installing properly. They are all good now.

That is the drive that failed. I just swapped the cables that were connected on the backplane of the Norco. I moved the top ones that were connected to the SATA2 Serial ATA II PCI-Express and connected them where the SAS2LP were. I restarted twice and haven't seen the "Error PD Device Not Ready" notification. I'm going to set a new config so that I can have all my drives functioning again...and then I will wait for another drive to give me an error. Once it does, I will do as you suggested and post a complete zip from the diagnostics page.

I'm not sure. I've had lots of drive failures in different drives, so I would just go to tools-->new config and take note of the drive order. restart it and set up the drives in the same order again. What I'll do right now is change the two SAS cables from the top two back planes to the bottom ones and see if there is an issue. I'll get back to you

I have been having some issues with my unRAID build these past few months and I've been pulling my hair out trying to resolve them. I've troubleshooted for months now and finally realized that I haven't used the greatest help possible, which is all you experts on this forum. So let me give you a little backstory. I had been running my original unRAID build for a few years with absolutely no problems but it was time for an upgrade because I wanted to use all the nice new features that unRAID 6 brought to the table (VM, dockers, etc) My OLD original underpowered hardware: Motherboard: ASUS M4A785-M CPU: AMD Sempron 2.8GHz RAM: 2GB Corsair XMS 675MHz (2x1GB sticks) SATA ADAPTER: Supermicro AOC-SAS2LP-MV8 SATA ADAPTER: SATA2 Serial ATA II PCI-Express (Silicon Image SIL3132) PSU: Corsair 650W Total of 10 drives (including parity and cache) I upgraded quite a few things in my box, namely the motherboard, ram, cpu, power supply, added two video cards and a new case. I guess the only original things I kept were the drives and the expansion cards and of course the flash drive. Shortly after, I started experiencing problems with drives. The first time it happened 2 drives "failed" on me so I thought I had data loss and replaced them. It happened again soon after and I realized the chances of that many hard drives failing were very unlikely. So I ran preclears on my two original "failed" drives on a separate computer and they passed... which confirmed my suspicion that it was a problem with some piece of hardware in my new unRAID build and not the drives themselves. I began to systematically test each hardware component to rule out issues. -tested the PSU and it is working properly and does have enough juice to supply power to my entire rig (feel free to cross check this as I may be wrong) -swapped out the two SAS to SAS 36-Pin cables and that seems to be working fine as well -swapped out and tested both the SAS RAID controller card and the SATA2 RAID controller card with my buddy who has two identical cards, and that doesn't seem to be the problem. I also moved them to different slots on the motherboard -changed some bios settings on the SAS controller to the same settings that my buddy has on his (he owns the same card and has no issues) *****One thing to mention is that I get an "Error PD device not ready" sometimes when booting up unRAID and I must press any key on the keyboard to continue booting up. I noticed that when this happens is the times when I usually have drive missing or disabled issues. This didn't use to happen with my old unRAID setup. Curiously enough, my friend gets the same "Error PD device not ready" notification sometimes, but he does not have any drive issues at all. (he does have a different motherboard and CPU though) *****The errors have occurred on different drive trays...so they are not isolated to the same slot every time. At this point, I'm thinking it may either be a motherboard issue (maybe the PCI slots cannot supply the full capacity to all the drives I have and the additional 2 gpu cards I have added) or maybe the backplanes on my new NORCO case are faulty?? Could it be a RAM issue or the Norco Reverse breakout cables? Here's my setup for reference. Maybe some keen eyes can find something that I overlooked or am not aware of: M/B: Gigabyte Technology Co., Ltd. - 990FXA-UD3 http://www.newegg.com/Product/Product.aspx?Item=N82E16813128514 CPU: AMD FX-8350 Eight-Core @ 4000 http://www.newegg.com/Product/Product.aspx?Item=N82E16819113284&cm_re=amd_8350-_-19-113-284-_-Product RAM: 16384 MB (max. installable capacity 32 GB) http://www.newegg.com/Product/Product.aspx?Item=N82E16820148540 GPU1: SAPPHIRE Radeon HD 4830 DirectX 10.1 100265L 512MB 256-Bit GDDR3 PCI Express 2.0 x16 http://www.newegg.com/Product/Product.aspx?Item=N82E16814102822 GPU2: EVGA 02G-P4-3658-KR GeForce GTX 650 Ti BOOST SuperClocked 2GB 192-bit GDDR5 PCI Express 3.0 http://www.newegg.com/Product/Product.aspx?Item=N82E16814130910 SATA ADAPTER: Supermicro AOC-SAS2LP-MV8 Add-on Card, 8-Channel SAS/SATA Adapter with 600MB/s per Channel http://www.amazon.com/Supermicro-AOC-SAS2LP-MV8-8-Channel-Adapter-Channel/dp/B005B0Z2I4/ref=sr_1_10?ie=UTF8&qid=1451497676&sr=8-10&keywords=sas+card SATA ADAPTER: SATA2 Serial ATA II PCI-Express RAID Controller Card (Silicon Image SIL3132) http://www.monoprice.com/product?p_id=2530 CABLES: 2x Norco C-SFF8087-4S Discrete to SFF-8087 Reverse Breakout Cable http://www.amazon.com/Norco-C-SFF8087-4S-Discrete-SFF-8087-Breakout/dp/B002MK7F0Y/ref=sr_1_1?ie=UTF8&qid=1451505475&sr=8-1&keywords=reverse+breakout+cable+norco CABLES: 2x 1m 30AWG Internal Mini SAS 36-Pin SFF-8087 Male to Mini SAS 36-Pin SFF-8087 Male Cable http://www.amazon.com/gp/product/B008VLHOR2?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s01 PSU: Corsair RM750 http://www.newegg.com/Product/Product.aspx?Item=N82E16817139055&cm_re=corsair_rm750-_-17-139-055-_-Product Case: NORCO 4224 http://www.amazon.com/NORCO-Mount-Hot-Swappable-Server-RPC-4224/dp/B00BQY3916/ref=sr_1_1?s=pc&ie=UTF8&qid=1451507089&sr=1-1&keywords=norco+4224 Total of 12 Drives (including Parity and Cache) link to full size image: http://i.imgur.com/YrWzxaH.jpg I just got a missing drive error this morning when I started doing a parity check so I shut it down and came here for help. I can supply additional information for each additional drive in my array if that would be helpful in determining my problem. Just let me know. thanks.

I gave up trying to erase the files so I unmounted the SSD and ran a preclear on it even though people don't recommend it. After the preclear finished, I added the SSD back as a cache and formatted it. All is well now.

I just got a new unRAID server going but I ran into a little hiccup. I set up an SSD as a cache drive. The SSD had a windows operating system along with some random folders. I did not preclear or format it. When I started my new array, It automatically created some shares on my server which I could not delete no matter how hard I tried because I could not delete anything on the cache drive. I removed the drive and formatted it to try to avoid any more issues. I re-inserted the SSD as a cache in my array and everything seemed good. I tried to set up the docker.img in the root of the cache drive when I realized what was happening. I am not getting access to the SSD drive in my unRAID server. When I try to open it through Windows Explorer I get the error: "You do not have permission to access [ip of unraid]\cache. Contact your network administrator to request access." When I try enabling the docker share...something is preventing the image from being written onto the cache. I can access any other folders whether they are disk shares or user shares but I do not have access to the cache. How can I resolve this? thanks

NzbGet had been working properly for a few months now, until today. It just stopped responding and started shutting itself down even though I have it set to autostart. I checked the logs and it was showing an error with the username and password not matching (I have not changed them). So I backed up the config from the appdata directory and uninstalled the container and data thinking I could do a fresh install and re-input my settings. nzbget still won't start though. Here is what the log shows: ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- Ign http://mirror.cogentco.com/pub/linux/ubuntu/ trusty InRelease Get:1 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security InRelease [64.4 kB] Get:2 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates InRelease [64.4 kB] Get:3 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty Release.gpg [933 B] Get:4 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/main Sources [128 kB] Get:5 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/restricted Sources [3,920 B] Get:6 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/universe Sources [36.5 kB] Get:7 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/multiverse Sources [2,165 B] Get:8 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/main amd64 Packages [495 kB] Get:9 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/restricted amd64 Packages [20.2 kB] Get:10 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/universe amd64 Packages [158 kB] Get:11 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/multiverse amd64 Packages [4,642 B] Get:12 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/main Sources [309 kB] Get:13 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/restricted Sources [5,219 B] Get:14 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/universe Sources [183 kB] Get:15 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/multiverse Sources [5,116 B] Get:16 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/main amd64 Packages [851 kB] Get:17 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/restricted amd64 Packages [23.4 kB] Get:18 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/universe amd64 Packages [431 kB] Get:19 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/multiverse amd64 Packages [14.1 kB] Get:20 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty Release [58.5 kB] Get:21 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/main Sources [1,335 kB] Get:22 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/restricted Sources [5,335 B] Get:23 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/universe Sources [7,926 kB] Get:24 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/multiverse Sources [211 kB] Get:25 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/main amd64 Packages [1,743 kB] Get:26 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/restricted amd64 Packages [16.0 kB] Get:27 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/universe amd64 Packages [7,589 kB] Get:28 http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/multiverse amd64 Packages [169 kB] Fetched 21.9 MB in 10s (2,152 kB/s) Reading package lists... ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- Ign http://mirror.cogentco.com/pub/linux/ubuntu/ trusty InRelease Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security InRelease Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates InRelease Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty Release.gpg Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/main Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/restricted Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/universe Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/multiverse Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/main amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/restricted amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/universe amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-security/multiverse amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/main Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/restricted Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/universe Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/multiverse Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/main amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/restricted amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/universe amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty-updates/multiverse amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty Release Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/main Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/restricted Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/universe Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/multiverse Sources Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/main amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/restricted amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/universe amd64 Packages Hit http://mirror.cogentco.com/pub/linux/ubuntu/ trusty/multiverse amd64 Packages Reading package lists... How can I get it back up and running? and preferably with my old config settings intact. Thanks.

Thanks for your help guys. I FTP'd to the unRAID machine and manually deleted the zoneminder folder after uninstalling the container. I re-installed the docker and re-mapped the port from 80 to 8024 and it installed properly. I have it running now.

In the unraid gui dashboard, click on the container's icon and select logs I even tried removing the container and the data and reinstalling. still didn't work. Log apache.conf already exists zm.conf already exists using existing mysql database using existing data directory using existing perl data directory creating symbolink links setting the correct local time increasing shared memory starting services * Starting MySQL database server mysqld ...done. * Checking for tables which need an upgrade, are corrupt or were not closed cleanly. * Starting web server apache2 * Starting ZoneMinder: failure

How do I check the logs? Oh and another thing. It keeps stopping itself even though I start it and have autostart set to "on"

Edit the container, don't change anything and hit save. It will recreate the container and see if that works I did just that, but it still does not work. The connection is refused. when I click the docker the browser opens the address: UnraidIPaddress:2424/zm/ that's the connection that gets refused. So I tried removing the "/zm/" from the Url and it takes me to the page:

I had Zoneminder installed for quite some time and it worked. But today I was trying to open the webui and I got the error message: "You don't have permission to access /zm on this server." I tried restarting the docker to no avail. any help would be appreciated. thanks.