Le vendredi 28 juin 2013 à 02:31 +0100, Ben Hutchings a écrit : > > [...]
> I still suspect a hardware problem, just because ext4 is the default
> filesystem for 'wheezy' and no-one else reported this yet.
That sounds like a reasonable assumption, yeah.
> [...]
> So maybe the second controller (or its driver) is faulty. Can you try
> using the RAID-1 disks connected to the first controller, with nothing
> connected to the second controller? [...]
So as planned I unplugged the working non RAID1 disk from their
controller, and connect the ext4 RAID1 and the ext3 RAID1 disk to it
(yeah these are 2 powerful RAID1 with 1 device only ;) for testing
purposes).
I also tried to re-plug each PCI card, and connect the video card fan
that was not connected (yeah it was a bad idea to limit the noise level
few years ago).
I did all the tests I could to try to overheat the system (same as
yesterday):
* 4 running dd if=/dev/urandom | gzip >/dev/null for the cpu
* massive copy from one disk to the other
* delete of duplicates between two directories (with many duplicates)
All that in parallel. Everything seems to work fine. No corruption nor
CPU overheating message (yesterday I still had some even after remove
the overclock of the CPU).
However, I now still have two disk and a controller that I would love to
use. How can we go further on this issue?
It seems there's a relation between the PCI card and the CPU messages
(but the video card FAN could be related too)...
for the record, the PCI card is supposed (and was) faster than the
working one (SATA-II). Could there be too much traffic on the PCI bus?
or maybe the card is doing something not expected by the driver?
Here's the lspci -vvvv for this card (if I'm not wrong):
02:09.0 SATA controller: Initio Corporation INI-1623 PCI
SATA-II Controller (rev 02) (prog-if 00 [Vendor
specific])
Subsystem: Initio Corporation Device 1626
Control: I/O+ Mem+ BusMaster+ SpecCycle-
MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr-
DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
INTx-
Latency: 32, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 17
Region 0: I/O ports at 9000 [size=256]
Region 1: Memory at ef022000 (32-bit,
non-prefetchable) [size=4K]
[virtual] Expansion ROM at 80000000 [disabled]
[size=128K]
Capabilities: [dc] Power Management version 2
Flags: PMEClk+ DSI- D1+ D2+
AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0
DScale=0 PME-
Kernel driver in use: sata_inic162x
(and the website is: http://www.initio.com/Html/INIC-1623TA2.asp)
It was a cheap one, I have to admit it.
the working card one is:
02:0b.0 Mass storage controller: Promise Technology,
Inc. PDC40718 (SATA 300 TX4) (rev 02)
Subsystem: Promise Technology, Inc. PDC40718
(SATA 300 TX4)
Control: I/O+ Mem+ BusMaster+ SpecCycle-
MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
DisINTx-
Status: Cap+ 66MHz+ UDF- FastB2B- ParErr-
DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
INTx-
Latency: 88 (1000ns min, 4500ns max), Cache Line
Size: 4 bytes
Interrupt: pin A routed to IRQ 19
Region 0: I/O ports at 9c00 [size=128]
Region 2: I/O ports at a000 [size=256]
Region 3: Memory at ef021000 (32-bit,
non-prefetchable) [size=4K]
Region 4: Memory at ef000000 (32-bit,
non-prefetchable) [size=128K]
[virtual] Expansion ROM at 80040000 [disabled]
[size=32K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2-
AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0
DScale=0 PME-
Kernel driver in use: sata_promise
How can I help going further?
Martin.
--
Martin Braure de Calignon
signature.asc
Description: This is a digitally signed message part
