• Content Count

  • Joined

  • Last visited

Everything posted by Axl

  1. The Intel drive can't write faster than the ADATA drive can read....
  2. Interesting you're saying you prefer Samsung?
  3. I actually just realized that Multi-Level Cell could be anything higher than SLC. In common web jargon, it seems MLC is nearly synonymous with 2 bits per cell.
  4. "3bit MLC 3D V-NAND" Is that a polite way of saying TLC? Or is the implication that Samsung V-NAND is basically the same, no matter how many bits one is stuffing into a cell?
  5. Axl

    Storage Spaces vs unRAID

    Sorry to necro an old thread here, though not by too much. For future reference, never ship a system like you're describing assembled. Pull the drives and pack them individually first, and then box as needed. I've had indestructible things like power supplies and SSDs destroyed while shipping systems (in the past, lessons learned), and even crazy things like good Corsair fans falling off their motors. That either takes serious impact, or days of terrible vibration. Maybe plenty of both.
  6. Axl

    Advice on purchasing a NAS

    Spinning drives in an array (even just a mirrored pair) with proper controller (let's say ZFS) can perform like local SSDs if connected with 10Gb ethernet of your choice. I prefer DAC cables and Intel x520's to the more expensive x540's. Definitely nothing wrong with SolarFlare, Myricom, Emulex and others. In a couple of years, those choices will probably consolidate to Intel and Avago.
  7. Very nice pictures in this article, and a very nice write-up in the conclusion. Well done and very interesting!
  8. Supermicro platforms are rock-solid. I can't say exactly the same with confidence for ASRock (Rack) systems.
  9. New drives sometimes come with errors, sometimes develop errors during shipping, handling, and installation; and then there is this. Hundreds of "new" drives that for some reason needed "additional testing" before being sold at a discounted price. Too many unknowns and red flags, not worth the hassle to be hung up over one individual unit.
  10. Thanks, Adam and Brian. Much obliged.
  11. Great discussion of the new features of 6.2 here.
  12. Charts and doctors indicate that I have excellent vision, but I just couldn't make out any detail in the first two pictures. I went over to their site and found some click-to-enlarge. It's going to be a while before I get to use software that expensive.
  13. Great sneak-peek. Would it be too revealing of their IP to make the pictures clickable to a larger version, or a large format gallery link?
  14. You could boot Gparted or PartedMagic (from 8/2013 or earlier) and check their SMART readings versus SeaTools. Still doesn't help with getting SeaTools to report a problem, which you'll likely need for RMA. Good luck, I gave away a Seagate SSD 600 which was faulty from day one but would not throw a Seatools error, so no RMA. You could watch the disk errors climb by the millions during a benchmark run.
  15. I know this thread is dated at this point, but for future reference, it appears that the LSI 9265 is the same as the 9266 just with different SFF-8087 port placement.
  16. And in this attached shot, you can see that CDI is also vulnerable to "misreading" SMART values. Note in the Kingston utility, that the drive has read 2679477 sectors with 0 errors. Look at how CrystalDiskInfo reports that. Same further down the SMART attribute list, at the ECC entries. Different drives report differently, and different utilities interpret differently. You gotta use a bunch and figure it out which ones work best and where But HD Tune can be let go.
  17. Weirdest trick for getting into LSI BIOS on a consumer motherboard - set the board to boot from CD first, even if there is no CD drive. Then Ctrl-H might actually work. So simple and seems pointless, but it has saved me hours since finding the trick recently. Also it seems like you have to jackhammer keys when trying to access BIOSes these days. Lock one hand down on Control and hammer the H with the other hand! My guess is the card BIOS needs you to confirm the order of the arrays it is re-importing, and hopefully then you will be able to see them again. Your OS may need them reimported as well, as it may have marked the disks offline.
  18. There is one other way. Don't do this outside of a testing environment, and only if your system supports IOMMU / vT-D. If you have a Windows (Pro or Server) guest VM, and no other running VMs using storage attached to the LSI, then you could enable PCI pass-through on the ESXi host and pass the LSI controller on to your Windows VM. Then normal LSI Windows utiltities will work - sometimes this is much faster than trying to get into the LSI card BIOS during reboots to set up arrays. In ESXi, it's under Configuration - > Hardware -> Advanced Setiings - > Configure Passthrough. While perfectly fine in testing, please don't do this outside a testing environment.
  19. This may or may not help in your situation. 1) Some Seagate drives don't report SMART data correctly. Personally I've only seen it on their short-lived SSD line, but I suppose it could happen on a spinner also. 2) Some drive monitoring programs simply pull the SMART data wrong, or report it wrong. Some SSDs have SMART values that do not exist on spinning drives, such as for TB read and written from host, and some have it also for TB read and written to NAND. I've seen GPartEd / PartedMagic tell me that a perfectly good SSD was failing because the apps skipped an entry for TB read and written, causing the app to display 3 trillion CRC errors rather than 3 trillion bytes read. Said differently, those lines reported in the SMART reporting utilities differ considerably from app to app and drive to drive. 3) HD Tune is useless. Sorry but true. CrystalDiskInfo is much more accurate, most of the time. Be sure to go to Function -> Advanced Feature -> Raw Values and report them in 10(Dec). Now its starts to make sense. 4) My experience only, but SeaTools is absolutely useless. The ONLY thing it's useful for is getting Seagate to take a failing drive back. 5) You probably know, but be aware that only a few SMART values mean anything to the consumer. And see this attached pic for what I mean about entries specific to SSDs (at the bottom).
  20. And two years later I believe Seagate can already be removed from this list. This from the user of a Seagate SSD 600 (that has nice write speeds and horrendous read speeds). They can be added again if they ever do anything with SandForce.
  21. I felt like I had a lot to add when we were discussing MegaRAIDs and Quantum Atlas 10k II's back in what...1999, and I quickly embraced the early 40, 60, and 90GB SSD's along with virtualization, and I certainly enjoy reading about the datacenter storage evolution, but personally I don't have much to add to today's threads. I have virtually no storage experience beyond the modern-day equivalents of the things I just mentioned. I always hoped for more RAID controller and array coverage way back then so I'm not at all displeased with today's articles and threads.
  22. I am not an LSI RAID controller expert, but I am a longtime LSI (and all the others) RAID controller user, and I believe that you do have to wait for the background initialization to finish before performing any FS operations. Recently I created two mirrored sets on a 9266-4i. One set was two Intel 530 SSDs and the other set was two 1 TB WD VelociRaptors. Keep in mind these were just mirrors, but both background initializations finished instantaneously. This may be different with a large RAID 60 on 7200rpm SATA SAS drives - it may not be instantaneous. I would try this first - wait for BI to finish and report back. I hope and I read your question right, and i hope this is of some help.
  23. Axl

    LSI 9211-8i HBA not working?

    First thought, you could try going into the Asus board's BIOS (UEFI?) and changing the value of the setting called something like "Force Option ROM BIOS", probably from Auto/Quickboot to Enabled/Force. p.s. just saw your other post, glad you found a method that worked.
  24. Speaking of PCI Express incompatibilities, have you tried your 9260-8i in a PCIE 2.0 slot rather than a 3.0 slot? I've heard of some LSI cards and certain motherboards not getting along when used in PCIE slots they aren't explicitly rated for. I know, there should be backward-compatibility, but apparently there ARE issues in certain cases. I have a 9266-4i which has not gone into service yet. I would be willing to hook up an SSD (Kingston HyperX 3K 120GB is available) and run some tests. I downloaded your IOMeter settings and I'll give that a try in the next couple days. The 9266 compared to 9260 bumps up the LSISAS2108 to a LSISAS2208 and bumps the 512MB of DDR-2 to 1GB of DDR3. But it's still PCIE 2.0. I chose this on purpose, as all I have are AMD systems with no PCIE 3.0, and I didn't want to risk the compatibility issues I've read about when mixing PCIE generations (only applicable to LSI, as far as I've read).
  25. As someone who manages a very small (non-tech) business but has a networking background, all I can say is wow! What an awesome collection of equipment and what generous donors! Thank you SR for the peek into the rack. Always appreciated.