ptirmal

Do you think I should start a parity check or just wait for now and see if it stays up without issues? Can someone tell me if I am interpretting the results of fdisk -l showing my parity drive while the unRAID webgui shows it as "missing disk," to be more of a software issue as opposed to a hardware one, especially since rootfs was full for unknown reasons? My only guess is a recent update of one of my dockers caused something.

I was on 6.6.7 but I thought some of my issues might had been the upgrade, since it was running fine for months on 6.6.3 and not that long on 6.6.7, so I downgraded back to 6.6.3. Do you think I should do it right now or wait to see how stable it is? Current uptime 1 hr 17min. Seems it was fine for at least 5 hours yesterday before I went to sleep and when I woke up I saw the disk showing it was missing. SMART long was running and it made it to at least 40% when I last checked it but don't think it completed in time. Here is the current diagnostics file. Also, thanks all for your help! unraid6-diagnostics-20190311-1129.zip Edit: Updated to 6.6.7 on reboot (after 2 hours with no issues) - uploaded diagnostics after this reboot unraid6-diagnostics-20190311-1218.zip

I guess I deleted it in an edit, but it looks pretty much full of empty files because I guess there wasn't enough space to create it? I think the output of the commands is the most I have, and the log I copy pasted. So now in maintenance mode with no docker or VMs enabled, should I just wait and see how it behaves? Should I start a parity check? tower-diagnostics-20190311-0800.zip

Understood. So I'm booted into maintenance mode with no docker apps running or VM. When the parity disk went missing before dockers were running but no VM was running .I uninstalled preclear plugin which I thought I already had done... I am seeing this in the logs for warnings and errors: Does this looks like anything that needs to be addressed? Could the RAM filling up cause the parity disk to go "missing?" Since it looks like it was still showing up under fdisk?

Ok I rebooted. Here is the diagnostics zip. My flash drive doesn't look full to me after reboot: df -h results are also different...

lsscsi lspci lsusb free ps ifconfig Just saw your post johnnie: Not sure how to access it though since I can't connect over samba... Not sure what it means when it says no space left on device... will /boot survive a reboot? log 03.11.2019.txt

I've tried but once the disk goes missing it seems when I click download it doesn't do anything. Same as when I navigate to "main," it just hangs indefinitely. Is there a way to get some info via CL? I just uploaded the last diagnostics I ran. This was yesterday after the reboot. I'll see if I can run some of these commands and attach the results unraid6-diagnostics-20190310-1439.zip

It dropped out again after maybe 8 hours? Long SMART never finished. I ran an fdisk -l command and it shows up as dev/sdc Currently my drives are: 10TB parity 8TB 8TB 8TB 5TB 240GB - cache SSD 3TB - unassigned device drive I'm not too familiar with command line but the fdisk command looks like the 10TB drive is being recognized there as SDC, correct? It's just not showing up in the mapper? I just want to be sure it's a bad disk before I RMA it, or if it's something else. Edit: just ran df -h and it doesn't come up... does this mean the drive is not showing up at the hardware level?

I noticed the other day that my parity disk went missing according to unRAID. Under the dashboard it would say it's missing and no other info. The disk in question is a 10TB WD Easystore that I had used kapton tape on. I've been using this drive for about 4 months without issue. I couldn't stop the array so I had to issue a powerdown command to turn it off. I turned it back on and the drive was showing up fine. I did a SMART short test and it passed. I started a parity check and here is where it gets interesting. At about 30% or so I guess the disk disconnected, as I got a message that the parity sync finished (errors). It then starts back up and disconnects a few times. I was able to shut it down again and move the disk to a different bay so the SATA cable should be ruled out as an issue. I also downgraded the server from 6.6.7 to 6.6.3. This is a 10TB easystore (4 months old) that I had to tape the 3rd pin on to get it to show up in the system, tape looks fine not damaged. I am using a SYBA non raid card for additional SATA ports - I don't know exactly what drive is connected to what but it should be a mix up and I've had no other issues. Upon another parity check it made it a few hours before having an issue again, "disk missing." I shutdown and just retaped the pin on my drive, moved it to another bay and powered on my server. I uninstalled the dynamix plugins that it told me were not compatible (system stats and another one I don't remember exactly) even though they've been running for months without issue. I've also removed the preclear plugin. Not sure what else to check? It seems to show up fine after restarting and SMART indicators seem to show no problems. I couldn't post diagnostics as when the parity disk shows missing, it doesn't let me do much on the server, including downloading the log/diagnostics. Could the drive be bad?

I'm still trying to figure out how I want it setup, still in the planning stage. I only have one camera hooked up right now as "laundry room," when I go to events I see two folders: "1" and "Laundry room," both have the same events - is this normal? Sorry if this is a Zoneminder question, I am doing my best to search through the documentation. Edit: Sorry I think it was because I created a zone "1" and it was saving those specific motion detection events in addition to the base ones. Was it actually saving those files twice or were the just symlinked?

Thanks for maintaining this docker dlandon! I plan to get two 720p cameras going initially and then add another 2 higher resolution ones later. I am still doing some testing and I think I much prefer this to running Blue Iris in a VM. I had a question about saving recordings. My plan is to run my cameras off an unassigned device drive (3TB) with mocord, I don't see how I can separate motion detected videos, is this possible? My plan was to have a script run every X hours that will rsync the "motion detected" directory to another location. I don't want to sync the entire folder if I am running it in mocord, and I think I would prefer mocord to modetect. Thoughts?

I currently have my computer running weekly incremental and monthly full disk image backs to my unraid server to a public share, the majority of my shares are secure and if I need to add or move files into them I change the share permission. I'm wondering what the best way to automate moving my backups to my secured share. Is it simply using cron to run rsync? Is there anything with a gui I could use that might be helpful?

Not sure when I can schedule a downtime of 24 hours! It was a clean shutdown, the UPS initiated it. I was trying to update the Dockers, I started with duplicati and then did Ombi and Plex next, before duplicati finished. They all just hung, I think the log showed they couldn't be stopped, then they were inaccessible. They also locked my ability to stop the array.

After this call trace I attempted updating Dockers, it wouldn't let me stop them and I was forced to hard reset my server. I started it up and parity check came out fine. I did have an issue about 2-3 months ago, the system was unresponsive, couldn't access anything via web gui, no IP address, nothing, also had to hard reset then. My initial thought were this is a docker/software issue not a hardware one, the hardware has been running 24/7 for 4+ years, I did add more RAM about a year ago and I added a sata controller maybe 6-9 months ago. Is there anything I should watch out for to diagnose it further? Is a memtest a good idea? Edit: Also, my apartment has been having power issues and my server has been getting on battery more often. The last time was probably 30 days ago when it shut itself off. The issue should have been fixed then though (electrician was there and did some work).

Anybody?

Had this message pop up on my server: Your server has issued one or more call traces. This could be caused by a Kernel Issue, Bad Memory, etc. You should post your diagnostics and ask for assistance on the unRaid forums Can someone take a look at this for me? unraid6-diagnostics-20180218-1922.zip

Thanks. Installed and made the changes, will post back if errors continue.

8GB on my server running a bunch of dockers. Plex, Ombi, PlexPy, Cadvisor, Sabnzbd, Crashplan (only backing up 170GB), Radarr and Sonarr. The last two being the more memory hungry ones, mostly Radarr and mono from what I can tell. I received an out of memory error and a process killed. When I look at the memory graph it looks like there was still 215MB free with 890MB cached. Do I really need 16GB? Attached my log. syslog.txt

Yes I do. I currently have them notify me via Pushbullet. I also check in on it pretty regularly.

Yea it sucks but that's what backups are for right? I had unbalance on the default settings so I don't know if notifications are enabled by default. I did notice when it was complete it wasn't let me click validate or anything else. I should have looked into it further but I figured it transferred it all since unraid was showing what looked like the correct percentage increase. Oh well, live and learn, could have been worse. And it looks like I'm restoring from my backup so whatever I deemed important survives.

I'm trying to restore from a backup that's stored on another computer on my network. The problem is it's telling me that "there is not enough space available to restore". I haven't changed any settings to the share, but files were removed from the share which is why I want to restore from it. What can be the issue? Plenty of space available. Edit: Think I figured it out, was trying to restore to root. Changed that and looks to be starting the restore.

Those disks were already formatted... I assumed (incorrectly) that the disks had moved the files because it said it was complete. I'm having a separate issue restoring from my crashplan backup.

So I'm not quite sure what's going on. I ran docker safe permissions, nothing changed. Crashplan shows missing files same as when I access via samba or console so I'm guessing they didn't move before the format? . I couldn't see anything that looks like it didn't copy, and unraid is showing the capacity was used. However, it appears Crashplan is not showing the data is there, but it's telling me there isn't enough space to restore (attached) which makes it seem permission related. Backup is the share with most of the stuff that's missing. Thoughts?

Thanks, I'll check when I get back. At the time I thought maybe the parity disk wasn't updating during the transfer.

Same, set to default, nothing is excluded. Just want to reiterate that I'm pretty sure the data has been copied correctly, because the drive usage percentage increased respective to the data I moved (which was copied) prior to formatting (which then went back to where it was before any file moving). Edit: So, looking at this thread: I think this is a samba issue. I'll have to check when I get home to be certain. I've never had to fix permissions before, is there a way I can go about doing that?