Hi All,
I have a 9260-16i that I had hooked up to 5 wdc30ezrs 3tb and 4 st3000DM001 drives - I've had the wdc drive up and running on a different setup for a while and all seemed well with them, but only very recently acquired the Seagate drives.
I know one of the seagates is faulty cause it's making a racket - sounds like the drive is full of grit..
I set up a virtual drive using megaraid with the rest of the drives and got a LOAD of beeping.. apparently the other 3 seagate drives are faulty too..
I deleted the virtual drive - and plugged each drive into the mb sata connectors, and prepared to do some testing. *sigh*
In the meantime I set up a raid 5 of my remaining wdc drives - at least I knew they'd be alright...wrong..
About 10mins after creating the virtual drive I was once more harassed by beeping hell, allegedly now one of my wdcs had failed, more testing..
Here's the thing..
The noisy one is dead - doesn't even "detect" any more, so I'll focus on the rest.
Using the windows7 drive manager;
All drives initialize correctly (gpt)
All drives format correctly (Full format)
All drives surface scan correctly (NO bad block)
however using seatools;
No drives pass ANY test
Not the short ones OR the long ones
Sadly I can only use the version that runs under windows as it would appear the fdos based ISO available from Seagate doesn't function with my sata controllers.
I've just started DLGDIAG for windows - and this far seagate number is passing all tests..apparently I still have 4hours left on the surface test (*yawn!*)
What is the story here- is the LSI controller just being mega picky, or what is going on? Have I missed some feature/bug/incompatibility with my drives?
Any help, thoughts, comments appreciated..
I have a 9260-16i that I had hooked up to 5 wdc30ezrs 3tb and 4 st3000DM001 drives - I've had the wdc drive up and running on a different setup for a while and all seemed well with them, but only very recently acquired the Seagate drives.
I know one of the seagates is faulty cause it's making a racket - sounds like the drive is full of grit..
I set up a virtual drive using megaraid with the rest of the drives and got a LOAD of beeping.. apparently the other 3 seagate drives are faulty too..
I deleted the virtual drive - and plugged each drive into the mb sata connectors, and prepared to do some testing. *sigh*
In the meantime I set up a raid 5 of my remaining wdc drives - at least I knew they'd be alright...wrong..
About 10mins after creating the virtual drive I was once more harassed by beeping hell, allegedly now one of my wdcs had failed, more testing..
Here's the thing..
The noisy one is dead - doesn't even "detect" any more, so I'll focus on the rest.
Using the windows7 drive manager;
All drives initialize correctly (gpt)
All drives format correctly (Full format)
All drives surface scan correctly (NO bad block)
however using seatools;
No drives pass ANY test
Not the short ones OR the long ones
Sadly I can only use the version that runs under windows as it would appear the fdos based ISO available from Seagate doesn't function with my sata controllers.
I've just started DLGDIAG for windows - and this far seagate number is passing all tests..apparently I still have 4hours left on the surface test (*yawn!*)
What is the story here- is the LSI controller just being mega picky, or what is going on? Have I missed some feature/bug/incompatibility with my drives?
Any help, thoughts, comments appreciated..