On 3/2/16, m.r...@5-cent.us wrote:
> Sorry, we don't seem to have any Supermicros with that m/b, but with the
> ones we have (all X9* m/bs), as well as our many Dells, old Penguins
> (rebranded Supermicro), and HPs, we've had no trouble at all with them,
> other than the
On 3/2/16, John R Pierce wrote:
> any chance your SATA cables aren't up to SATA3 (6gbps) performance levels ?
The cables came with the SuperMicro board so I certainly hope they
haven't started cheapening out on those :D
In any case, the cables shouldn't be the problem
any chance your SATA cables aren't up to SATA3 (6gbps) performance
levels ?
In my experience, that's the most likely cause.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
I discovered, amidst great initial pain, that most, if not all, of the
problems I had with SATA disks were caused by SATA cables and not by
the disks themselves. Intermittent problems, such as disks randomly
not showing up in RAID groups, were solved when I replaced the cables
with proper
However, the latest C7 server I built, ran into problems with them on
on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error
write fpdma queued". Googling on it threw up old suggestions to limit
SATA link speed to 1.5Gbps using libata.force boot options and/or
noncq. Lowering the
On 3/1/2016 9:53 AM, Emmanuel Noobadmin wrote:
However, the latest C7 server I built, ran into problems with them on
on a Intel C236 board (SuperMicro X11SSH) with tons of "ata bus error
write fpdma queued". Googling on it threw up old suggestions to limit
SATA link speed to 1.5Gbps using
On Wed, Mar 02, 2016 at 01:53:54AM +0800, Emmanuel Noobadmin wrote:
> Might be slightly OT as it isn't necessarily a CentOS related issue.
>
> I've been using WD Reds as mdraid components which worked pretty well
> for non-IOPS intensive workloads.
>
> However, the latest C7 server I built, ran
Emmanuel Noobadmin wrote:
> Might be slightly OT as it isn't necessarily a CentOS related issue.
>
> I've been using WD Reds as mdraid components which worked pretty well
> for non-IOPS intensive workloads.
>
> However, the latest C7 server I built, ran into problems with them on
> on a Intel C236
On 3/2/16, Alice Wonder wrote:
> Is it possible to build a vanilla kernel to boot from and test if same
> issue exists?
Unfortunately no, had to get the server out ASAP so already swapped
the Reds with the vendor for HGSTs.
___
On 03/01/2016 09:53 AM, Emmanuel Noobadmin wrote:
Since I'm likely to use Reds again, it is a bit of a concern. So
wondering if I just happen to get an unlucky batch, or is there some
incompatibility between the Reds and the Intel C236 chipset, or
between Red / C236 / Centos 7 combo or the
Might be slightly OT as it isn't necessarily a CentOS related issue.
I've been using WD Reds as mdraid components which worked pretty well
for non-IOPS intensive workloads.
However, the latest C7 server I built, ran into problems with them on
on a Intel C236 board (SuperMicro X11SSH) with tons
11 matches
Mail list logo