kenoka

Members
  • Posts

    451
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

kenoka's Achievements

Enthusiast

Enthusiast (6/14)

0

Reputation

  1. When I restarted the array, the two drive cache pool shows as unmountable. I'm sorry, I don't know where the cache page is. Edit: Never mind, I just had to stop and start again. Thanks very much! It seems to be re-balancing now.
  2. I had a cache pool of three drives. A couple of days ago, one of the drives dropped out of the pool, and I had to rebuild my dockers. I tested the suspect drive, and it seemed fine, but I had been using it in an external eSATA dock before putting it into my case, and it seems like that dock has failed. So I put the drive into the case, and started up. The drive showed up again, and shows as part of the cache pool, but the cache capacity remains at 480 GB, rather than ~720 GB (two 480 GB drives and one 500 GB). The third cache drive will also show as spun down after some time, and there is essentially no read or write activity on it. When I originally added it, it was quite busy, and I expected this to happen again. SMART reports attached. mediaserver-smart-20161017-0737.zip mediaserver-smart-20161017-0737_long.zip
  3. I have a pretty newly installed Windows 10 VM, which will be my gaming system. Everything appears to have gone well in setup, and I have been slowly installing software and testing the system. Recently, it has started crashing, and the unraid array has stopped along with it. I can only assume it's crashing at the kernel level, and I'm a bit flummoxed by this behavior. Let me know what information to upload to help diagnose this.
  4. Well, after seeing this thread, I too have pulled the trigger: 1x Xeon E5-2670, Supermicro X9SRL-F, and 32GB ECC RAM. I have been running the same server hardware for five or six years, and it has happily been chugging along on my old Phenom II X3 720. UnRAID 6 has changed my entire outlook, and now I'm looking to be able to task my server with a lot more. This chip is an unbelievably good deal, even with the expensive motherboard. Going from a Passmark of 2704 to over 12,000 is very exciting, especially for the possibility of a Windows gaming VM to replace my also sadly aged gaming rig. Many thanks to all who have provided lots of information and feedback on this deal.
  5. Hmm, I keep vacillating on those. It's difficult for me to justify the cost, given that I need to upgrade the guts of the server. I have some Cooler Master 4 in 3 trays (no hot swap), and they have served me well. I'm probably going to hold out for a Norco, given that the cost of 3 trays adds up to nearly the same. Version 6 has really turned my world upside down. Suddenly I'm getting ambitious thoughts of incorporating my gaming rig as a VM. And since that needs an upgrade as well, it seems a prime time to build a really high end machine. So the convenience of hot swappable trays will probably have to drop down the "want" list for quite a while.
  6. My mistake, for some reason I assumed it was a 3770k, and Sandy/Ivy Bridge K models don't support VT-d. Color me interested again.
  7. I may be interested. How much do you want for the CPU and mobo? Actually, never mind. Looks like that generation of CPU doesn't support VT-d. Bummer. I may still be interested in the cages though. I will check back.
  8. SATA III totally doesn't matter, since platter based drives don't even saturate SATA II.
  9. AHCI will allow your SATA drives to operate at full speed, and with all SATA features.
  10. I would run a SMART test on that drive and report back.
  11. You should be able to see if HPA is at work. First of all, you can see if it's enabled in the BIOS settings. Secondly, if it's active, one or more of your disks would be reporting a different size than it should, due to the HPA file. But it sounds like you've already ordered another board, so it's probably moot at this point.
  12. A drive could fail at any time. It could be entirely coincidental. However, I would try switching data cables prior to the next rebuild. If it still shows as failed, switch power cables. If it fails again, switch data ports. This is all assuming the disk passes a long preclear run and SMART test.
  13. No, you need to capture the current syslog prior to shutdown. It restarts with every boot.
  14. Your syslog doesn't seem to say a whole lot. It looks like a report taken just after your most recent reboot. What we'd need to see is the syslog from when the failure occurred. Whenever a drive is questionable, you should probably run a SMART check. Run that and post the results please. On your preclear run, there are a couple of worrying items. "Program_Fail_Cnt_Total" has a crazy high number: 16937351. After some internet snooping, it looks like a common complaint for this drive. I'm not sure how much of a worry it actually is. The second is "G-Sense Error Rate", which should probably not be showing up at all in a desktop machine, except in an earthquake. However there are no reallocated sectors, or pending sectors, or UDMA CRC errors.
  15. I don't think so. It's still a good test. But now we have data to suggest that it's not 100% valid in all cases. So we'll need to remember that a flaky system that has passed memtest should be checked with Prime95.