Kismet

The diagnostics I included with the screenshot was taken after the write finished and I stopped the array, no rebooting. After that I started the array and let it run, and here is the diagnostics from after I got back to the server and the second data rebuild was complete. After this report (polaris-diagnostics-20171230-0719) I stopped the array and now the UI is telling me everything is normal, no unexpected disk. If it's the USB then great, finally something I can pinpoint, but this time I did absolutely nothing different and haven't rebooted since before the first rebuild and somehow it's just working after the second rebuild. polaris-diagnostics-20171230-0719.zip

So now I have a whole new problem. The data rebuild on my new drive just completed so I stopped the array so I could power down the system and replace the next drive since I'm replacing them all. Except when I powered down the array the UI now shows the array wants to see the old data drive instead of the new one which just got rebuilt and appears as if it won't let me start the array without kicking off another rebuild. polaris-diagnostics-20171229-1832.zip Edit: Glorious, just glorious. I figured I should be able to just restart the array and do the data rebuild. After all, the data rebuild completed successfully according to the UI and syslog, therefore it should be able to quickly validate that the data is there and not need to copy it all over again. No, no check at all, it's redoing the whole write all over again. At least when I was doing the parity swap you could say I executed the procedure from the manual incorrectly because I didn't complete the data rebuild on the old parity drive which is in the process. Here I followed everything step by step with no errors anywhere and I'm still having to repeat the process and hope it just works the second time. See you another 8 hours.

That's why I rebooted to install a new drive instead of doing a data rebuild on the old parity drive. So the second copy finished a few minutes ago. I pulled a diagnostic package and then, because I'm a glutton for punishment and I wanted to check and see if I was right, I started the array in maintenance mode then shutdown, inserted the new disk, and everything is working as expected. The new parity disk was recognized as my array's parity disk and the system is currently doing a data rebuild on the new data disk. Which is itself extremely frustrating, a little warning or notice that the UI is lying to you and you have to start the array to finalize the configuration would have been nice. Even when you start the copy event the text describe what you're doing just says you "may" start the array afterwards like it doesn't matter if you do or not. I know all it cost me was a little bit of wear and an extra 9 hours, but the level of frustration and amount of expletives I want to actually put in this post over a lack of such a simple and basic UI tweak is seriously making me consider whether I want to continue using Unraid. polaris-diagnostics-20171229-0952.zip

Unless there is a archive somewhere I can't find, I don't have those. The diagnostics tool only gives me the syslog records back to the last startup. Edit: Since the day is over for me I'm just going to kick off a copy again and see what happens in the morning. polaris-diagnostics-20171228-2353.zip

I have rebooted, although I can still give you the diagnostics if you'd like, just tell me what configuration of drives you'd like me to show. I don't think they'll tell you anything though, I can read and mount all the drives just fine, and they show up in the Unraid GUI without any problem. It's just after the reboot the array wants to see the old drive as the parity disk and not the new one.

I just completed a successful parity copy from my old disk to the new one. Then I shutdown the server and replaced the former parity disk with a new drive to do a data restore. However when I did that the array was looking for the old parity drive in the array and considered the new parity drive invalid (still recognizes the drive as a valid XFS disk with data, just not at as the parity disk). The only reason I can see for this is that it seems like I have to put the old parity drive in, start the array (assuming I don't have to do another copy), let the system do a data rebuild on the former parity disk, then remove the parity disk and put in the new drive to do a new data rebuild. Is that really the case or is there some other reason my new parity disk wouldn't be recognized? Edit: So I went in and set everything back to as it was when I completed the parity copy, and now Unraid still won't recognize my new disk as a partiy disk and wants me to do another 9 hour copy all over again. Second edit: This is an edit born of frustration because it really looks like the system completed the copy and the array, as listed in the UI, was showing the properly configured array (post copy) but Unraid didn't actually save the new configuration while leaving me with every indication that it had done so. And now because the configuration on the USB stick wasn't updated I've got the redo the whole process over just so I can force the UI to save the new configuration by hitting the start array button, despite no indication that would be necessary. Hypothetically I could just rebuild the array but if I do that then I lose the parity information and because I'm replacing a data disk that went bad, I'd lose the ability to restore it if I rebuild the array.

One of my drives is starting to give consistent read/write errors and I need to replace it. Since all of my drives are about the same age and I recently swapped out all the other hardware when I started using unraid, I thought I'd just replace them all. Right now I've got two 3TB drives and two 2TB drives, although I'm only using 3TB total at the moment. My plan is to replace all of them with three new 3TB drives. My plan is to do the following: 1) Copy all data from one 2TB drive to the other (there is space for this), remove the 2TB drive I copied from and rebuild parity. 2) When new drives come in, replace 3TB data drive with a new drive and then have the array rebuild it. 3) Replace remaining 2TB with a new drive, and rebuild it. 4) Replace parity drive. Just wanted to make sure I'm not missing anything important or if there is a better way to go about it?

I've got a weird problem where Sonarr is trying to update my library but it's failing and causing some sort of loop that consumes 100% of a core on my CPU. I can't find any log that shows a problem or irregularity, the only hint that anything is wrong is the "Update Library" button on the main page is greyed out and rotating as if it's processing, and the logs will show a refreshseries command was queued for the first series in my list and it was completed, but then it doesn't move on to the next series.

That turned out to be the problem, I had an invalid special character.

Use a docker that includes ffmpeg and python to your application of choice. For example, here is an NZBGet docker with the needed components to run MP4 Automator: https://hub.docker.com/r/bbsan/ts-nzbget/

I'm just trying out unRAID for the first time and when I went to change the root password via the web GUI the system immediately asked for a username and password after hitting apply. Neither the new root password, root with no password, nor my personal user account I created work. Edit: I've tried restarting the server and I have access to the console where I can log in with the new root password.