matt0013

Thank you for your help. Everything seems to be working great now. I did some searching and ended up getting rid of the extended permissions using setfacl -Rb /mnt/user/appdata/zoneminder. That took away the '+' sign that you called my attention to. ACL: Using Access Control Lists on Linux

I did set some permissions with WinSCP a long time ago; not related to Zoneminder though but it may have had an unintended consequence... The issue is currently fixed. I did some things to remove extended permissions and I also updated the docker since I noticed the option was available. Not sure what exactly fixed it, the update or my removing of extended permissions.

Looks like owner was changed. I have HomeAssistant running with no issues. That's the only other active one running.

These were correct. No luck with this. Still have the same errors in the log.

Not sure what this means exactly. How do I set these?

Here are the results.

Thanks for helping me troubleshoot this. Here is what I received.

I didn't change any settings. My docker.img is not full and there are no orphaned docker images. Should I have a directory /usr/share/zoneminder in mystem? If I am supposed to, I currently do not.

I deleted the docker and 'appdata/Zoneminder' folder and did another fresh installation. I'm getting the same errors in my log over and over. web_php 8492 ERR Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user /usr/share/zoneminder/www/index.php 159 web_php 8490 ERR disk_total_space returned false. Verify the web account user has access to events /usr/share/zoneminder/www/includes/functions.php 145

I haven't changed any settings. Those errors were generated from a default setting installation. I looked at (didn't change) my zm.conf file and saw these paths which match the errors I'm receiving. Are these correct? # Path to installed data directory, used mostly for finding DB upgrade scripts ZM_PATH_DATA=/usr/share/zoneminder # Path to ZoneMinder web files ZM_PATH_WEB=/usr/share/zoneminder/www

I deleted my old docker and did a fresh installation. I am getting these errors in my log upon startup. Any ideas? Should this path be /usr/share/appdata/zoneminder/www/? 2017-05-28 10:04:24.812157 web_php 8492 ERR Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user /usr/share/zoneminder/www/index.php 159 2017-05-28 10:00:22.938535 web_php 8490 ERR disk_total_space returned false. Verify the web account user has access to events /usr/share/zoneminder/www/includes/functions.php 145

Thank you for this! Very helpful. I have to reinstall the extpack every time my server restarts. Any idea how to prevent that?

Nevermind on the shares questions. I see now that I needed to enable them. I'm still curious why it reset all my settings but if it's not causing any issues I guess it's not a big deal. After the issues I had, if anyone wants to browse my syslog I posted previously and check for potential problems I would really appreciate it. Thanks!

So I was able to restore almost all of my files and re-organized them back into the shares they were in. Thanks for all the help. However, now I have upgraded to 4.5.6 and when I plugged my flash drive back in all of my settings were lost. The server name has gone back to "Tower" and I don't have the ability to create user shares. When I go to the Shares section, there is nothing but white space below the Export Settings box. The Main page looks like it did before (I had to go in and re-assign the drives like the readme instructed) and all my files are viewable in the disk folders. I just can't create shares... I attached my syslog in case that will be any help. syslog.txt

Yes, disk3 is still empty. I am not sure what is going on with this disk. When I started this whole mess, I added disk3 and disk4... disk3 was a 1TB drive originally (disk4 was a 1.5TB drive and works fine). I thought disk3 was a failed disk (appeared red), so I replaced it with a new, 1.5TB drive. It is still red. Maybe this means the cabling or port is defective? I think I have one more SATA port available on the motherboard, should I shut down and plug disk3 into another port? So you are saying I can move from a disk folder to a share folder, right (after I create my shares)? My question/concern here is that the disk folder is one hard drive, but the share folder may be multiple hard drives... Unraid will figure this part out?

Well it's looking like almost all of my files have been restored! Thanks for the advice! Hard to tell for sure at this point because so many are in random folders in the "lost+found" directory. I have a couple more questions now: First, I'm scared to touch anything... can I re-create my shares and begin to move files to where I want them? Currently I see 4 folders (disk1, disk2, disk3, & disk4). If I create a share, can I drag from the disk folders to the share folder? Second, I still have a disk that is red. It's disk3 but I still see disk3 when I am viewing my server in Windows Explorer. Should I figure out how to address this problem before I begin moving files around? What do you think I should do here? Thanks again!

You are correct. It's started now... It's definitely going to be a little while before I post an update. Thank you!

When I type this, I get this message: umount: /dev/md1: not found Thinking that the "umount: /dev/md1: not found" error might have meant is was already un-mounted (I don't know any better), I skipped to the next step. When I type this command, then type "Yes", I get this: Failed to open the device '/dev/md1' : No such file or directory It then goes back to where it started: root@matts-server :~# Any suggestions for this?

It is possible for me to put the exact same disks back to the last operational setup and I have not written anything to any drives since this happened. What benefit will I get from doing this? You mention that the parity will still be useless to recover what was on the drives... Luckily, the failed drive is one of the two new drives I was adding. In the screen shot, disk3 and disk4 were newly added. I don't want to turn it on to check at this point but I am guessing your right about the version. You're definitely right that it listed all drives as unformatted. I will definitely do this whether I recover my data or not. So, based on the very first thing you said... I can configure my system back to when it was working (2 data drives plus 1 parity drive). No new data has been written to the array since. What will this do for me? I couldn't tell from your response if it would lead to potential data recovery. Thanks for the response, Matt

Hey Everyone, I recently added two new disks to my Unraid array (giving me 5 total drives-4 plus parity). Upon starting the array, I believe I formatted all new disks by accident not realizing what I was doing. Shortly thereafter, I used the restore function which I understand has reset my parity drive (I think I hit it two separate times). Before I really understood what was happening, I thought my issues were due to a filed drive because 1 of the 2 drives I added was red. Therefore, I replaced one of them with a larger drive. So I added two drives, formatted, restored, and replaced one drive with a larger drive. My current state is that the same drive I replaced is still red, although it did recognize that I replaced it with a larger one. I found some useful information on the forums but I have some questions before I do anything: I want to follow the instructions posted by Joe L. here (http://lime-technology.com/forum/index.php?topic=6008.msg57379#msg57379), but within his post he is advising me to use the Trust-My-Parity process (http://lime-technology.com/wiki/index.php?title=Make_unRAID_Trust_the_Parity_Drive,_Avoid_Rebuilding_Parity_Unnecessarily). My issue with this is this statement: It should NEVER be used if you have a failed disk or are in the process of replacing a failed disk. It should NEVER be used if you are replacing a drive with one of a larger size. I feel that I fit into either one or both of those categories which means I don’t even know where to begin. Can anyone please offer some suggestions? I did e-mail Unraid support but have not heard anything back after a couple days so I thought I would post here. I attached a screen shot. Disk3 is the disk I replaced with a larger one, Disk4 is the other disk that was added.

Thanks! I decided to purchase that motherboard and my unRAID server is up and running. I had some trouble booting at first but the HP formatting tool fixed all my problems. Thanks again!

Hey everyone... First, I do know there is a hardware compatibility list but it seems a little outdated for purchasing a brand new motherboard right now. Most of the ones I am interested in are no longer available on Newegg and I would like something relatively new. Can someone recommend a motherboard for me that can run unRAID? Here is my current processor: Intel Celeron E3300 2.5GHz LGA 775 65W Dual-Core Processor. I have an Antec 1200 ATX Full Tower Case. So I need an ATX motherboard that can fit my Intel Celeron LGA 775 processor. Does anyone have any recommendations that are proven to work with unRAID? Any help is appreciated. Thanks! Matt