Jomp

Firmware update: https://apps1.seagate.com/downloads/certificate.html?key=1200432356414 I'm swapping out my SMR archive 8tb parity in preparation for adding a second parity drive. I figure the extra RPM/cache should help with speed vs having two SMR drives as parity drives. Mine arrives tomorrow, it seems that some of them already ship with the new firmware, so I'll see what mine comes with!

Simple Control (formerly Roomie Remote) on iOS has been awesome for me over the last year. It ties together my lights, outlets, AV gear, HVAC, etc. I really like it because it allows me to use the best of x automation piece and not having to tie everything to a certain manufacturer or system.

I've been wondering about this for a while, so I figure I'll finally ask. While watching something on my media streamer (Dune Smart HD), the video will freeze/stop when a disk gets spun up. What I can't figure out is why it only happens when my Windows computer does the spinning up. If I spin disks up with the unraid web interface, no freezing, but when Windows spins up a drive, freezing. Thoughts on this behavior?

Has anybody tried with the update and iOS 9? https://www.reddit.com/r/sonos/comments/3r63rs/airsonos_has_been_updated_to_support_1011_and_ios9/

Went with the LSI, thanks

Is the SAS2LP-MV8 or 9211-8i the preferred 8x card these days for unraid? Something else? I've seen a few threads with SAS2LP issues, so I'm somewhat hesitant there now. I had a SASLP card ~4 years ago that worked fine, but I'm looking for an 8x card this time around. Thoughts?

Thank you so much! I spent hours trying to find this sneaky duplicate and had pretty much given up on it before I found this. It was found and deleted in 30 seconds with this script

Nice one, ordered! Thanks!

This is really great stuff! I'll be giving the verification part a go shortly.

Awesome! I use Corz to checksum everything on my computer before transferring to unraid (though I have it use .md5 not .hash,) BUT it takes a week++ to hash check everything over the network. The ability to have this hash check everything on unraid would dramaticly cut that time down -- sweet!

Mine are all about the same, 37C-40C in those front 8 slots when all are spinning idle. The 40C is that drive you circled and it's also my parity (8TB Seagate). They are 40C-45C when parity checking/parity resynching, 45C being the parity/circled drive. The caselabs drives all run ~5C cooler. Drives are in the low 30C's when only a few drives are spun up. They are 4TB Seagate NAS drives in the 3 bay, running between 36-40C when idle and also checking. Not much deviation from that. Keep in mind I replaced the fan in it with a quieter and thus lower cfm fan. Unfortunately I never used the stock fan in them, so I have no idea if it would cool them more. The drives don't have a whole lot of separation, so I doubt the difference is that big. *The server is in a closet, so airflow in there isn't great. Ambient temperature is 77F. I have to say, it's surprisingly quiet and it cools pretty well for the low speed fans that are in it!

Small upgrade! I think I'm out of places to put drives in this case now! -EverCool Dual 5.25 in. Drive Bay to Triple 3.5 in. HDD -Nexus 80mm Real Silent Case Fan - SP802512L-03 -IO Crest 2 Port SATA III PCI-Express x1 Card (SY-PEX40039)

Updating in case somebody has/searches for this problem. I replaced the RAM and everything seems to be running smoothly again. So even though it was ECC ram, it going bad was still was causing crashes.

Locked up hard again about ~30gb into a copy. So, it's happening more often now (only a few days of uptime this time). There is one more event in the supermicro log, but it's from yesterday, so not when it froze up. Event Log:14 event entries Event ID Time Stamp Sensor Name Sensor Type Description 1 2015/01/13 11:40:54 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 2 2015/01/13 11:40:55 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 3 2015/05/22 03:47:07 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 4 2015/05/22 03:47:07 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 5 2015/06/06 00:32:30 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 6 2015/06/06 00:32:30 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 7 2015/07/16 19:16:52 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 8 2015/07/16 19:16:52 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 9 2015/07/19 19:24:55 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 10 2015/07/19 19:24:55 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 11 2015/07/24 14:06:29 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 12 2015/07/24 14:06:29 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 13 2015/07/30 1:30:44 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 14 2015/07/30 1:30:44 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted I was running a tail in my browser and console, but it failed to capture anything unusual, I've attached it still, so I think that points to a hardware problem, correct? I'm at a complete loss of what to do. Basically since I've owned the server it's been 200 days uptime > freeze, 30 days uptime > freeze, 7 days uptime > freeze, and this last time 4 days uptime > freeze. So no issues until the last month and a half and since then it's really had issues. Ouch. Edit: I was just running memtest and another memory event appeared in the log. Does ECC ram generate errors in memtest? I also thought ECC ram was supposed to prevent crashes due to memory errors though?

17 passes, no errors. I think the next time it freezes I'll look in the log and see if there was an event. And so we wait, unless you guys can think of something else to do ..

Saw this in my Supermicro event log, perhaps the freezing is a RAM issue after all? Event Log:12 event entries Event ID Time Stamp Sensor Name Sensor Type Description 1 2015/01/13 11:40:54 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 2 2015/01/13 11:40:55 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 3 2015/05/22 03:47:07 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 4 2015/05/22 03:47:07 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 5 2015/06/06 00:32:30 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 6 2015/06/06 00:32:30 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 7 2015/07/16 19:16:52 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 8 2015/07/16 19:16:52 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 9 2015/07/19 19:24:55 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 10 2015/07/19 19:24:55 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted 11 2015/07/24 14:06:29 OEM Memory Correctable Memory ECC @ DIMMA1(CPU1) - Asserted 12 2015/07/24 14:06:29 OEM Memory Uncorrectable Memory ECC @ DIMMA1(CPU1) - Asserted

Unraid has a fixed IP, as does IPMI and they share the same port/cable. I'm able to connect to IPMI when the server freezes, so I don't think it's a network thing. The server runs headless, but I'm able to see Unraid's screen using the java console redirect and it's frozen, my keyboard and the virtual keyboard don't do anything. Syslog attachment is incoming, but it obviously doesn't show what happened before the forced reboot.

Some backstory, I was running 5.0.5 and had about 200 days of uptime when I noticed my server had dropped off the network during a file write. Telnet, http, all not working. I IPMI'd in and the screen was showing the typical Unraid login, but was totally unresponsive. I rebooted, ran a parity sync that showed no sync mismatches, ran a md5 check of all my files and a week later it showed that everything hashed correctly. I figured it was an anomaly. I went ahead and upgraded to 6.0.0 since the final had just come out. Everything was going good and at about 30 days of uptime I decided to start converting drives from reiserfs to xfs since reiserfs was doing the annoying "drives are almost full so I don't want to write large files to fill them totally up" thing. About half way through converting my disks, again during a write, unraid went unresponsive. Telnet, http, all not working. I IPMI'd in and the screen was again showing the typical Unraid login, but was totally unresponsive. I rebooted, ran a parity sync, got a bunch of sync errors and now it's going to take another week to md5 hash everything. Annoying. This is obviously becoming a worrisome trend. I ran memtest and everything was ok there. I run unraid without any plugins or virtualization, totally stock. I'm currently running tail -f /var/log/syslog and waiting. All I can do wait for another freeze? Every crash takes a solid week to hash check everything, so I'd love some ideas to be a little bit more, uh, proactive. The common thread seems to be freezes during writes to the array. Any ideas? Thanks so much! Specs: CPU: Intel G3220 Motherboard: Supermicro X10SL7-F Ram: 4GB ECC Power Supply: Corsair RM650

Now we just need pics

http://www.corsair.com/en-us/type-3-flat-black-sata-cable-with-4-connectors

If you want to change a drive, you do have to unscrew it and take it completely out. Needless to say, it's no hot-swap, lol! Those drives are certainly going to be the last to be upgraded, and will stay there unless one fails. The cage does take up an awkward part of the case. The X10SL7's 14 SATA ports are right behind it and are in the way enough that I had to space the cage out a bit and screwed it into the metal fan grill holes and not the original fan holes, if that makes any sense. It's still really solid and not going anywhere. I can see how many cards would not allow you to use it. I look forward to seeing what you come up with, have fun

I went with the Caselabs option, I think it's the slickest expansion solution for the R4..

What a beautiful statement, exciting times!

I really like the X10SL7-F board. Also, since you're going with a server caliber motherboard, you might as well get ECC ram. Check mine out, since it hits many of your requirements/parts list: http://lime-technology.com/forum/index.php?topic=35249.0

I don't use them (I use WD SE drives), but I see no reason why it won't, and I'd be shocked if there would be an issue specific to those drives. That being said, if you plan to boot off a drive that's on the LSI controller (and not, e.g., from a USB drive as in barebones unRAID) you DO want to install the version 19 of the LSI firmware (off the Supermicro web site). It is a result of a ticket I opened (and fought for for several months), which has to do with boot order issues. Great stuff, daron. Thanks for your reply. I did email SM about drive compatibility, they just told me to do a search on their website (thanks). the seagate 3tb nas wasn't on the list but i'll give it a shot anyway. Seagate NAS drives work fine, I've got 12 of them on my X10SL7-F: http://lime-technology.com/forum/index.php?topic=35249.0 I did flash to IT mode, never tried the default mode..