Jump to content

Whaler_99

Members
  • Content Count

    532
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Whaler_99

  • Rank
    Advanced Member

Converted

  • Gender
    Male
  • Location
    Northern Ontario, Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. If you do decide you want to part with the chassis, let me know. I'm not super local, but would be willing to drive out to pick it up.
  2. Are you willing to sell just the case from "server 1"? If so, cost?
  3. Thanks very much! That was exactly the issue. Just taped off pin 3 and sure enough, the drive powered up right away. Least I know what we are dealing with now.
  4. So, would this be an issue with the Norco 3x5 cage no processing this properly to the drive? I tried different power cables and connectors on the PSU (modular). I am also bringing in a different power supply tomorrow, just in case.
  5. Think we have isolated the issue, but no clue why. The 3TB drives are 5V .7A and 12V .66A. These new 6TB are 5V .85A and 12V .99A. After a few minutes of the system being powered up, we pulled the drive and sure enough, it's not even powered on. So, it looks like these Norco cages that run off two Molex power plugs cannot deliver enough power. I'm wondering if I should now try a different 3x5 cage...
  6. You'd think. I cannot connect direct to the controller. It has min SAS connectors to fan out cables for connecting to the drive cages. I'm bringing in another motherboard tomorrow to test. I checked the website on it, a TA870U3 and the highest size drive they show support for is 4TB... weird.
  7. So, something else is going on. This server is normally run headless, so we yanked it out and attached it to a KVM. Got into the SAS controller config util, and it doesn't even see the 6TB drive, so it isn't an issue with unRaid but either both drives or the 5x3 cage. Would an older system have anything to do with it perhaps?
  8. Having some issues with some drive upgrades. I have 8 SAS drives currently installed, mixed 2TB and 3TB WD drives. I need to start some upgrades so wanted to replaced my 3TB Parity drive with a brand new 6TB Seagate SAS drive I have. Trouble shooting: Unit originally used two Super Micro AOC-SAS2LP-MV8 cards (4 drives per). I have also tested with a LSI SAS 9300-8i. No luck. The cards see all the 2 and 3 TB drives but not the 6. I have also tested with another brand new Seagate 6TB drive I have, same result, not detected. Using unRaid 6.5.1 Using Norco 5x3 cages, but doubt that is an issue. Any help on where to go from here be appreciated.
  9. Do you have any cables to include with the card(s)?
  10. Almost all the 5 bay units have 80mm fans. A few have 90mm. You cannot fit a 120mm fan in a 5 bay hot swap along with all the connections needed. From various testing and real world use they almost all perform fine. I have even added LNA's to some to slow them down and make them a bit quieter. I occasional get temp warning on a drive in summer during a parity check or 45-49 C but that typically clears up pretty quick.
  11. Thanks for this, was having this exact issue on a new ASRock board, core i5 6400.... adding that line into my GO file fixed it up.
  12. In another review I did I also commented on the trayless ones seeming to be a bit flimsy one the drive is installed (not very secure) and using a thinner 3.5" would cause issues especially depending on the orientation of the cage. Conclusion, although a pain, almost any of the cages that require you to screw the drives into the tray are going to give you a better, more consistent experience, especially if you are removing and inserting drives a lot for some reason. Just a more secure design overall.
  13. I'm not specifically sure, as it doesn't explicitly state one way or the other, but I assume it does. Most of these 3x5 units, the backplane is pretty dumb and just passing through signals, so will support SATA I/II/III just fine. I know a couple models state support for I and II and but not III specifically, so maybe there you might have an issue.