Mancubus

Thanks for the information. I tried the steps for "Rebuilding a drive onto itself" and it appears to be re-creating the parity. Thanks!

As the title says, my Parity drive stopped working suddenly without reason. When I stopped the array, the drive was missing. After a power down and a jiggling of the cables, I booted the system up and it sees the drive however unRaid says that Parity is disabled, even though the drive is selected. I was able to run a full SMART test with no errors reported, but the system does not want to use it. Any suggestions on how to resolve this? I'm concerned about losing data without protection in place. TIA!

Strange, I tried to run the scrub from a different browser (Edge) and I can access the GUI page of the cache drive without issues. Not sure why that flickering is happening with Chrome and only on the cache drive gui but oh well. I have the scrub running now. In the meantime, if it finds uncorrectable errors, what should my next steps be?

Thanks for the reply. I tried running the stats command on my cache pool and had the following results: Looks like I do certainly have some integrity issues. When I try to go to the GUI to run the scrub command, the page just keeps flashing and I can't click anything. Not sure if that's related to my current issue or if its a bug. No other drives do this. I suppose I could run the scrub command from the CLI, I'll see if I can find the proper commands so that I don't accidentally delete my file system.

Hi all, I seem to be having this issue where my log file keeps filling up to 100%. When I try to view the log file through the interface, it shows up blank. I downloaded my diagnostics file and have attached it here. If someone could help me shed some light as to what or why my log keeps filling up, it would be greatly appreciated. Thanks! tower-diagnostics-20221226-0150.zip

Thanks, I went out and purchased a new 4TB drive. Hopefully it works out.

My parity drive has suddenly disabled itself. When I run a SMART test, it says that there are no issues. I've tried removing the drive, rebooting and then adding it again. It went through the rebuild process which took about a day and a half. It worked again for about 3 days and then disabled itself again. I've also checked the cables and power. I've attached the diagnostics file, any help would be greatly appreciated. Thanks! tower-diagnostics-20200115-2247.zip

OK, thank you for clarifying. I'll manage things manually for now until a solution is found.

Thanks, after my last post I did some research and decided to test the 6.4 RC since downgrading seemed simple. True to form (at least as it seems for me) it broke many things including my dockers (they disappeared) and I could not longer access shares from some of the systems on my network. I spent a couple hours of getting things fixed up and I am now running the latest 6.4RC and I am able to assign IPs to the dockers independent of the unRaid host IP which is what I wanted to do. The only issue I have now is that its not receiving IPs from my DHCP server but is assigning the IP itself. I do have the ability to assign the IP manually from the GUI however I prefer to leverage my DHCP server and assign reserved IPs for cleaner management. Not sure if this behavior is by design or if there's something that I can do alter it so that it behaves the way that I'd like. I'll do a search however if you have any advice to give I'd gladly accept it. Thanks!

Ah, OK. I glossed over that. I figured I was on the latest since it was reporting that there were no updates. Short of installing a RC of version 6.4, is there anything that I can do to get this working in my current version? I am running a few mission critical services on my unRaid (one of them being a Security Cam DVR) and I'd rather not risk any instability that inherently comes from early release software.

Thanks for the reply. I must be an idiot because I don't see anywhere it can be easily changed in the GUI. I did search for the instructions before and after posting this question. Every single article that I found links back to the original instructions on this thread. Is there another article that shows how this is done through the GUI?

OK, so I found this thread because I need to set up my Home Automation gateway docker to use port 80 which means it will require its own IP address. Unfortunately I'm not getting anywhere. I tried entering the commands on the first post and my unRaid manages to accept them all except for when I enter the last line: homenet When I press enter I get the following message: "docker network create" requires exactly 1 argument(s). See 'docker network create -[-help'. Specifics: I am running version 6.3.5 I have 1 nic Network info: Unraid: 192.168.0.133 Subnet 192.168.0.0/24 GW: 192.168.0.1 I did make the changes to the commands so that they reflected my subnet and not that of the instructions. Other than that, I've copied everything to the letter. Any suggestions?

Thanks for pointing that out! I changed the cables and restarted the rebuild. It went further in 30 minutes than it did the 3+ days I had it running previously (about 70mb/s). I'm wondering if the original drive was reported as bad due to the cable issue... I'll hook it up after the rebuild is done and re-integrate it back into my array. Thanks again!

I had a 2TB drive fail and so I replaced it with at 3TB drive. I started the rebuild process about 2 days ago and it's only at ~4%. At this rate, it's estimating to be finished in about 90 days which is way too long. I've attached my diagnostics file in hopes someone can help me get to the bottom of this. Thanks. Edit, the file is too large to attach: https://www.dropbox.com/s/zjyssxee8nwn16i/diagnostics-20160120-2017.zip?dl=0

Looks like the file system corruption and xfs_repair fixed the issue. I've been stable for a few days now. Thank you all for your help!

Thank you for pointing that out. My unRaid box is headless however when I logged into IPMI the console displayed an error stating that there was file-system corruption on md7. I ran the command as indicated in the link you sent and it did in fact find corrupt files and was able to fix the file system. So far things are going well but I'll keep an eye on it for the next week or so to see if the issue re-occurs. Thanks again!

OK, so it just happened again. The drive contents disappear but the free space and used space still shows correctly in the GUI. All drives show up as green in the UI when the array is both running or stopped. I managed to grab a diagnostics file before rebooting the server which has fixed the problem for now. tower-diagnostics-20151107-1405.zip

Yes, by all accounts unRaid thinks the array is healthy as per the nightly health check that I have it do. All drives are green and I can access the drive, I just don't see anything on it until I reboot. It's very strange. The drive is still working so I'll wait until the next time it happens and run another diagnostics. In the meantime, is there anything else I should be checking? Thanks.

Thanks, should I do that now while everything is working or run the diagnostics when/if it fails? *edit* Instead of waiting for an answer, I've completed the diagnostics scan while things are running well. Please note that the disk I'm having this issue with is disk 7 in the array. All of the others do not have this problem. Also note that when this happens, the files that are associated with the shares that are on disk 7 also do not appear until the reboot. Thanks! tower-diagnostics-20151106-1119.zip

Hi all, I'm running the latest build of unRaid (6.1.3) and I've been experiencing strange problems over the last couple of days. One of my newer drives which also has the most recent data on it (movies mostly) keeps going 'dark'. By dark I mean, all of the contents and shares on the disk are not visible however the unRaid gui displays the proper free/used information but no folder or file structure. I'm able to get it working again by rebooting the array but then it randomly happens again. I've run a parity check and everything is fine as far as unRaid is concerned however this is obviously not true. Any suggestions on what the issue could be? Some additional info: The drive is 2TB and is formatted with xfs. It is 1 out of 11 drives. The others are formatted with reiser. I have the full unRaid license.