lishpy

Has anyone been able to get fan control working with this board through unRaid and NOT IPMI (for those of us who have the non Ipmi boards)? I'm not pleased with the drive temps I'm seeing and want to ramp up my fans a bit.

The copy completed and now I was given the ability to start the data rebuild. The SOP should be updated to reflect the reboot in step 5 being an issue if that's truly the cause. Since it's before the copy procedure is initiated it's still not clear that's the issue. Otherwise there's a bug here considering the two threads that followed the SOP to a T and failed in the same way only to be successful on the redo.

Exactly, the only time I shut down was before I initiated the copy procedure. Plus if you see above the logs say the copy succeeded, but then seemed to not work correctly.

I just kicked off a new copy so we'll see, I'll report back. I did power down at Step 5 because I pulled the data drive I'm replacing and put the new parity in it's drive bay.

Interestingly enough, I just posted a thread with exact same results because I'm going through the same process.

I initiated a parity swap yesterday following this procedure: https://docs.unraid.net/legacy/FAQ/parity-swap-procedure/ I checked on the progress this morning and it was at 96% for the copy procedure, so I expected things to be done shortly there after and initiate the disk rebuild. I just checked progress in the array again, and the array operation page is now back to where I started, saying I can initiate the copy again. According to the documentation, that COPY button should be a START button to start the array and initialize the data rebuild. What's even more confusing, checking my server notifications, about the time I expected the copy function to complete, I have a notification saying the following: "Disk 4, is being reconstructed and is available for normal operation" Disk 4 is the old parity drive that is being turned into a data disk. I can't see any indication that disk 4 is actually being reconstructed though, I have no ability to start the array, and the array devices page shows the new parity drive and new disk as new devices. Did this somehow not complete successfully and I need to run the copy again? I don't see any indication of any failures and the notification message this morning makes me think it completed successfully, but now I don't know what state the array is in. I don't see anything in the logs out of the ordinary right now, the disks are spun down. Log says the copy completed successfully, but below says slot 0 is wrong import. Sep 24 12:29:29 Tower emhttpd: copy: disk4 to disk0 completed Sep 24 12:29:55 Tower kernel: md: unRAID driver removed Sep 24 12:29:55 Tower emhttpd: shcmd (39876): /sbin/modprobe md-mod super=/boot/config/super.dat Sep 24 12:29:55 Tower kernel: md: unRAID driver 2.9.27 installed Sep 24 12:29:55 Tower kernel: mdcmd (1): import 0 sdf 64 13672382412 0 WDC_WUH721414ALE6L1_Y6G3NGSC Sep 24 12:29:55 Tower kernel: md: import disk0: (sdf) WDC_WUH721414ALE6L1_Y6G3NGSC size: 13672382412 Sep 24 12:29:55 Tower kernel: md: import_slot: 0 wrong Sep 24 12:29:55 Tower kernel: mdcmd (2): import 1 sdd 64 7814026532 0 WDC_WD80EDAZ-11TA3A0_VGGYLR9G Sep 24 12:29:55 Tower kernel: md: import disk1: (sdd) WDC_WD80EDAZ-11TA3A0_VGGYLR9G size: 7814026532 Sep 24 12:29:55 Tower kernel: mdcmd (3): import 2 sdc 64 7814026532 0 WDC_WD80EFAX-68LHPN0_7SGLHX6C Sep 24 12:29:55 Tower kernel: md: import disk2: (sdc) WDC_WD80EFAX-68LHPN0_7SGLHX6C size: 7814026532 Sep 24 12:29:55 Tower kernel: mdcmd (4): import 3 sdh 64 3907018532 0 ST4000DM000-1F2168_Z304H4Z2 Sep 24 12:29:55 Tower kernel: md: import disk3: (sdh) ST4000DM000-1F2168_Z304H4Z2 size: 3907018532 Sep 24 12:30:05 Tower kernel: mdcmd (5): import 4 sdg 64 7814026532 0 WDC_WD80EFAX-68LHPN0_7SGLWD9C Sep 24 12:30:05 Tower kernel: md: import disk4: (sdg) WDC_WD80EFAX-68LHPN0_7SGLWD9C size: 7814026532 Sep 24 12:30:05 Tower kernel: md: import_slot: 4 replaced Also probably unrelated, but if you hover over the orange triangle on the array operation page, it says "Started, array unprotected" but on the dashboard I see all disks as offline. Looking for next steps to help troubleshoot. Array operation: https://imgur.com/id9jLUc Array disks: https://imgur.com/hukGTbI

Appreciate the follow up everyone. Regardless of what it's called, if I run 5.7.x ("unstable" or stable) branch, when 5.8.X drops here shortly as the full stable branch as Ubiquiti is calling it, is that line going to update to 5.8.X or am I going to have to make more changes to the Docker setup and pulling from a different track every time Ubiquiti marks a release as stable? My point was more so of how this line is going to progress going forward. Unifi's listing here: UniFi Controller 5.9 (Testing) We recently shared a testing release of the 5.9 line. This version is still under development. Our main goal is to give you a better overview of your Wi-Fi setup. UniFi Controller 5.8 (Stable Candidate) We added couple new features to the 5.8 line: UniFi Controller 5.7 (Stable) Amongst many performance and stability improvements we also added these features to the 5.7 line: UniFi Controller 5.6 (LTS) Long-Term Support (LTS) release with security updates and critical bug fixes. I'm running AP's which in the next firmware version will absolutely require the 5.7.X controller line, which is why I asked. I'm not asking for beta support here or even running the betas/RCs, just an outline of how this plans to progress going forward. Thanks for your time, I didn't mean to come off as harsh if that was taken as that.

Is there a way to update this container without having to wait for the maintainer to do so? Can I just update the controller via the webUI with the Unifi firmware? This is still sitting on the 5.6 branch which is the older stable version. The stable 5.7.X has been out for months (which you are having us mark as "unstable" if we want to run it), and release candidates of 5.8 have been out for months as well, which means this is going to be two .X releases behind once 5.8 drops here. They've even had 5.9.X betas out for a while as well. I do appreciate a way to run Unifi on my unRAID server but I wish there were more options for those who don't want to run old stable versions. Options to run the 5.7 track while not as "unstable" would be great, along with ways to run the betas.

The server is not set to power back on post utility coming back on so that's a non issue. I'd rather have the server running on battery if I'm using it then shut down after 10 minutes expecting it to go back out again. It's rare that the power goes out and I need the server online immediately anyway.

That's odd, the webUI is showing the system as unRAID Pro. I just confirmed as well, the Pro.key file is located under /flash/config. There isn't anything named ._Pro.key.

Hi all, Running 6.4.1, last weekend the power went out at my house and my UPS shut down the server after about an hour (a clean shutdown). I powered it back on earlier this week, but didn't have a chance to look at it today. I started the array just now (since I have autostart disabled) and all of my user shares are missing. I can access the individual disks, but SMB folders are all gone. Did I miss something here with upgrading in the past releases? I'd appreciate any assistance here. I've attached my diagnostics. Thanks! tower-diagnostics-20180309-1235.zip

I also just had an 8TB WD Red get stuck on cycle 2's post read at 95%, pegging a CPU core at 100%. I used gfjardim-0.8.9-beta. Is there no known fix for this? A little frustrating to see all these posts go back months but no definitive script updates or answers. Thanks everyone for the help.

Holy shit this is awesome. So much faster to list everything, it's like a time warp back to unRAID 4. Thanks!

Well, ended up having to remove 2 sticks of RAM. I narrowed down to having two sticks not erring, one I knew for sure was (100000+ by this morning) and the last one I put back in ended up having 8 errors detected after an hour or so. I can live with only having 16GB of RAM now. I can't recall where I got this RAM so no idea where to warranty it. It's got Crucial stickers on it but they're covered with some other warranty stickers that aren't coming up on the Crucial site, so it seems I bought them from some reseller or something. Anyway, the server is back online and the webGUI loads just fine now. Thanks for the assistance everyone.

They're all secured I made sure. 15 minutes into the Memtest there were 3500 errors.