Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About fysmd

  • Rank
    Advanced Member


  • Gender
  • Location
  • AIM
  • YIM
  • MSN Messenger
  1. Hi all, Well, a week later, a full rebuild and much frustration later I think I can confirm that the SATA power cable with capacitor was my issue. No issues reported since! Thanks for the help and advise all!
  2. So, after more investigation I found the only component common to the misbehaving drives was one of these puppies: https://www.scan.co.uk/products/silverstone-cp06-1-to-4-sata-power-adaptor-cable-with-capacitor Removed and now over three hours into rebuild with no faults so far (everything's crossed).
  3. During rebuild two otherwise happy drives now report a >>LOT<< of read errors. I'm replacing the PSU which supplies all so far affcted drives, is there anything lurking in the logs I dont see? server-diagnostics-20190224-0822.zip
  4. the drives are split over two 550W PSUs but will tot up how many / which on each.
  5. machine reboot rather than stop and restart array? - damn, in the middle of preclears
  6. Just had another drive go, disk2 now, diag attached server-diagnostics-20190223-1439.zip
  7. Sorry, that's not what I meant - I now have four drives which i removed from the array, likely cable related. is there any reason to suspect them faulty? One back at full strength I may run preclear a few times on them to test them but is there anything else?
  8. thanks, I noticed disk18 and have a replacement now - preclearing. While starting a pre-clear, disk2 just went offline!! It does seem that all these drives were on the same cable. Bi of rearrangement and that cable's out of play now. REALLY glad I added two parity now! Other than drive18 with errors, would I be right thinking that they're likely OK?
  9. So I've just had my third drive in a fortnight go bad. Last week I took the precaution of adding a 2nd parity but had another go unmountable since then. Now the drives failing have been old but I'm wondering if there is something going on here which I'm not noticing. Posted diag from today and one from a v poory state last week. Any advise / comments much appreciated.. [off to buy another couple of drives!] server-diagnostics-20190223-0956.zip server-diagnostics-20190216-1045.zip
  10. O-M-G!! I feel like a muppet. Off to get proper cables now. Thanks again!
  11. I want to say a big thank you, especially to johnnie.black for all the help with my recent issues (not only in this thread!) I worked out the source of my troubles I think and it was mainly -- >>ME<< I'm embarrassed to say that I had a compound issue: 1. Two of the five cables I bought seem incompatible, drives connected after one of these cables were not detected! 2. I'm a dick - I had knocked power off for a large number of by drives (2nd PSU!) - THINGS WORK BETTER WHEN PLUGGED IN! Now I'm over my brain fart I can start to fix properly, the cables I bought (same supplier) are: https://www.scan.co.uk/products/1m-broadcom-sff-8643-to-x4-sata-cable-mini-sas-hd-to-sata-data-port (works) and https://www.scan.co.uk/products/60cm-silverstone-12gb-minisas-hd-sff-8643-to-sata-7pinplussideband-cable (don't work) What should I be looking for vs avoid in these cables, I'm not seeing the difference
  12. I dont know what forward vs reverse breakout means.... Tried the HBA in two identical machines, same result and have now replaced the card, same result Same cables and drives though I've upgraded the firmware on the HBA, same results, no BIOS update available for MB. Could this be MB or Drive compatibility?
  13. Oh I hope not, servers been down for days already Would be just my luck though! Anybody know if there's any config I need to do to enable all ports for sata drives or anything similar?
  14. Hi all, I'm new to this card and just installed it. It seems to only detect drives connected to the first port. All four connected drives are detected but moving the same cable to other ports on the card leaves them undetected. If I run the setup tool at boot time (ctrl-c) I see the same thing, just four drives. Any tips?
  15. OK, well my new toy will be with me tomorrow so I'll take it from there. Can I just check the approach when I get the new controller, after reconnecting everything should I expect the one disabled drive to still be disabled? is there a way to force it back into life or is it safer (better) to just all it to allow the array to rebuild on the same disk again?