Lots of con-current I/O = resets SATA link? (2.6.25.10) - Kernel

This is a discussion on Lots of con-current I/O = resets SATA link? (2.6.25.10) - Kernel ; I've read the best way to 'deal' with this issue is to turn off apic/acpi etc, is there any downside to turning them off? Particularly APIC for IRQ routing? This happens on drives on both the Intel 965 chipset motherboard ...

+ Reply to Thread
Results 1 to 15 of 15

Thread: Lots of con-current I/O = resets SATA link? (2.6.25.10)

  1. Lots of con-current I/O = resets SATA link? (2.6.25.10)

    I've read the best way to 'deal' with this issue is to turn off apic/acpi
    etc, is there any downside to turning them off? Particularly APIC for IRQ
    routing?

    This happens on drives on both the Intel 965 chipset motherboard ports and
    PCI-e x1 cards, and the cables are not the issue (the cables with 12 other
    150 raptors have no issues) (same cables I used with them)).

    With NCQ on or OFF it occurs.

    $ ls
    0/ 10/ 12/ 14/ 16/ 18/ 2/ 3/ 5/ 7/ 9/ runtest.sh*
    1/ 11/ 13/ 15/ 17/ 19/ 20/ 4/ 6/ 8/ linux-2.6.25.10.tar

    $ cat runtest.sh
    #!/bin/bash

    for i in `seq 0 20`
    do
    cd $i
    tar xf ../linux-2.6.25.10.tar &
    cd ..
    done

    With NCQ off (earlier) (from just heavy I/O on the raid5):
    Jul 5 11:50:06 p34 kernel: [112161.433913] ata6.00: exception Emask 0x0 SAct
    0x0 SErr 0x0 action 0x2 frozen
    Jul 5 11:50:06 p34 kernel: [112161.433923] ata6.00: cmd
    b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
    Jul 5 11:50:06 p34 kernel: [112161.433924] res
    40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    Jul 5 11:50:06 p34 kernel: [112161.433927] ata6.00: status: { DRDY }
    Jul 5 11:50:06 p34 kernel: [112161.736858] ata6: soft resetting link
    Jul 5 11:50:07 p34 kernel: [112161.889840] ata6: SATA link up 3.0 Gbps (SStatus
    123 SControl 300)
    Jul 5 11:50:07 p34 kernel: [112161.911418] ata6.00: configured for UDMA/133
    Jul 5 11:50:07 p34 kernel: [112161.656792] sd 5:0:0:0: [sdf] Write Protect is
    off
    Jul 5 11:50:07 p34 kernel: [112161.656797] sd 5:0:0:0: [sdf] Mode Sense: 00 3a
    00 00
    Jul 5 11:50:07 p34 kernel: [112161.659296] sd 5:0:0:0: [sdf] Write cache:
    enabled, read cache: enabled, doesn't support DPO or FUA

    With NCQ on (with the test shown above):
    [115786.990237] ata6.00: exception Emask 0x0 SAct 0x3ffff SErr 0x0 action 0x2 frozen
    [115786.990247] ata6.00: cmd 60/80:00:bf:07:94/00:00:10:00:00/40 tag 0 ncq 65536 in
    [115786.990249] res 40/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout)
    [115786.990254] ata6.00: status: { DRDY }
    [115786.990259] ata6.00: cmd 60/88:08:b7:ee:c1/01:00:1d:00:00/40 tag 1 ncq 200704 in
    [115786.990261] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990265] ata6.00: status: { DRDY }
    [115786.990270] ata6.00: cmd 60/f8:10:bf:eb:c1/02:00:1d:00:00/40 tag 2 ncq 389120 in
    [115786.990271] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990275] ata6.00: status: { DRDY }
    [115786.990280] ata6.00: cmd 60/c0:18:3f:e8:c1/01:00:1d:00:00/40 tag 3 ncq 229376 in
    [115786.990282] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990286] ata6.00: status: { DRDY }
    [115786.990291] ata6.00: cmd 60/c0:20:ff:e9:c1/01:00:1d:00:00/40 tag 4 ncq 229376 in
    [115786.990293] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990297] ata6.00: status: { DRDY }
    [115786.990302] ata6.00: cmd 61/08:28:0f:c6:b6/00:00:1f:00:00/40 tag 5 ncq 4096 out
    [115786.990303] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990307] ata6.00: status: { DRDY }
    [115786.990312] ata6.00: cmd 61/10:30:df:b0:17/00:00:01:00:00/40 tag 6 ncq 8192 out
    [115786.990313] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990318] ata6.00: status: { DRDY }
    [115786.990323] ata6.00: cmd 61/10:38:4f:88:79/00:00:03:00:00/40 tag 7 ncq 8192 out
    [115786.990324] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990328] ata6.00: status: { DRDY }
    [115786.990333] ata6.00: cmd 61/10:40:3f:18:95/00:00:05:00:00/40 tag 8 ncq 8192 out
    [115786.990335] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990339] ata6.00: status: { DRDY }
    [115786.990344] ata6.00: cmd 61/08:48:d7:f6:a9/00:00:06:00:00/40 tag 9 ncq 4096 out
    [115786.990345] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990350] ata6.00: status: { DRDY }
    [115786.990355] ata6.00: cmd 61/08:50:9f:37:b7/00:00:07:00:00/40 tag 10 ncq 4096 out
    [115786.990356] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990360] ata6.00: status: { DRDY }
    [115786.990365] ata6.00: cmd 61/08:58:27:7c:d1/00:00:08:00:00/40 tag 11 ncq 4096 out
    [115786.990367] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990371] ata6.00: status: { DRDY }
    [115786.990376] ata6.00: cmd 61/08:60:97:48:46/00:00:0d:00:00/40 tag 12 ncq 4096 out
    [115786.990377] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990381] ata6.00: status: { DRDY }
    [115786.990386] ata6.00: cmd 61/08:68:cf:b4:68/00:00:0e:00:00/40 tag 13 ncq 4096 out
    [115786.990388] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990392] ata6.00: status: { DRDY }
    [115786.990397] ata6.00: cmd 61/80:70:3f:06:94/01:00:10:00:00/40 tag 14 ncq 196608 out
    [115786.990398] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990402] ata6.00: status: { DRDY }
    [115786.990408] ata6.00: cmd 61/08:78:7f:a4:88/00:00:11:00:00/40 tag 15 ncq 4096 out
    [115786.990409] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990413] ata6.00: status: { DRDY }
    [115786.990418] ata6.00: cmd 61/08:80:37:b8:d5/00:00:13:00:00/40 tag 16 ncq 4096 out
    [115786.990419] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990423] ata6.00: status: { DRDY }
    [115786.990428] ata6.00: cmd 61/08:88:c7:a4:8b/00:00:1d:00:00/40 tag 17 ncq 4096 out
    [115786.990430] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    [115786.990454] ata6.00: status: { DRDY }
    [115787.293177] ata6: soft resetting link
    [115787.446158] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    [115788.133592] ata6.00: configured for UDMA/133
    [115788.133628] ata6: EH complete
    [115787.877547] sd 5:0:0:0: [sdf] 586072368 512-byte hardware sectors (300069 MB)
    [115787.877689] sd 5:0:0:0: [sdf] Write Protect is off
    [115787.877692] sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00
    [115787.878746] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

    What is the true cause of this, is there anyway to get more information?

    I will test soon with apic/acpi=off.

    Justin.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  2. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)

    Try booting with:

    nolapic

    That largely fixed my problems on my motherboard (2.6.18+, EPoX MF-570SLI).
    I hope to try 2.6.25+ soon.

    --
    Jon
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  3. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)

    Try booting with:

    nolapic

    That largely fixed my problems on my motherboard (2.6.18+, EPoX MF-570SLI).
    I hope to try 2.6.25+ soon.
    --
    Jon
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  4. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)

    Hello!

    I'm having a similar problem with a brand new Hardware under Fedora 9 x64
    8GB RAM
    Motherboard: ASUS M3N-H/HDMI
    Chipset: NForce 8300/Nvidia 750a
    CPU: AMD AM2 5600+, 2.9GHz, Brisbane Dual Core
    Kernel: 2.6.25.9-76.fc9.x86_64
    Smartmontools: smartmontools-5.38-2.fc9.x86_64
    BIOS AHCI mode
    Power cables for ata3 and ata4 are on the same cable from an Enermax
    power supply.

    ata1.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    ata2.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    ata3.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    ata4.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    ata5.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    ata6.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
    scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
    scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
    scsi 3:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
    scsi 4:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
    scsi 5:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5

    Problem occours only on ata3, I've changed the disk Port 3 the third time
    (new disks) and changed the SATA cable, too. Problem still exists.

    Sometimes a RAID rebuild doesn't work at all.

    To get the drive to live I've to power down the system.

    Logs are attached.

    Can it be a bug on concurrent access of smartctl/smartd?

    Any ideas?

    Ciao,
    Gerhard

    --
    http://www.wiesinger.com/


    On Sat, 5 Jul 2008, Justin Piszcz wrote:

    > I've read the best way to 'deal' with this issue is to turn off apic/acpi
    > etc, is there any downside to turning them off? Particularly APIC for IRQ
    > routing?
    >
    > This happens on drives on both the Intel 965 chipset motherboard ports and
    > PCI-e x1 cards, and the cables are not the issue (the cables with 12 other
    > 150 raptors have no issues) (same cables I used with them)).
    >
    > With NCQ on or OFF it occurs.
    >
    > $ ls
    > 0/ 10/ 12/ 14/ 16/ 18/ 2/ 3/ 5/ 7/ 9/ runtest.sh*
    > 1/ 11/ 13/ 15/ 17/ 19/ 20/ 4/ 6/ 8/ linux-2.6.25.10.tar
    >
    > $ cat runtest.sh
    > #!/bin/bash
    >
    > for i in `seq 0 20`
    > do
    > cd $i
    > tar xf ../linux-2.6.25.10.tar &
    > cd ..
    > done
    >
    > With NCQ off (earlier) (from just heavy I/O on the raid5):
    > Jul 5 11:50:06 p34 kernel: [112161.433913] ata6.00: exception Emask 0x0 SAct
    > 0x0 SErr 0x0 action 0x2 frozen
    > Jul 5 11:50:06 p34 kernel: [112161.433923] ata6.00: cmd
    > b0/d8:00:00:4f:c2/00:00:00:00:00/00 tag 0
    > Jul 5 11:50:06 p34 kernel: [112161.433924] res
    > 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
    > Jul 5 11:50:06 p34 kernel: [112161.433927] ata6.00: status: { DRDY }
    > Jul 5 11:50:06 p34 kernel: [112161.736858] ata6: soft resetting link
    > Jul 5 11:50:07 p34 kernel: [112161.889840] ata6: SATA link up 3.0 Gbps
    > (SStatus
    > 123 SControl 300)
    > Jul 5 11:50:07 p34 kernel: [112161.911418] ata6.00: configured for UDMA/133
    > Jul 5 11:50:07 p34 kernel: [112161.656792] sd 5:0:0:0: [sdf] Write Protect
    > is
    > off
    > Jul 5 11:50:07 p34 kernel: [112161.656797] sd 5:0:0:0: [sdf] Mode Sense: 00
    > 3a
    > 00 00
    > Jul 5 11:50:07 p34 kernel: [112161.659296] sd 5:0:0:0: [sdf] Write cache:
    > enabled, read cache: enabled, doesn't support DPO or FUA
    >
    > With NCQ on (with the test shown above):
    > [115786.990237] ata6.00: exception Emask 0x0 SAct 0x3ffff SErr 0x0 action 0x2
    > frozen
    > [115786.990247] ata6.00: cmd 60/80:00:bf:07:94/00:00:10:00:00/40 tag 0 ncq
    > 65536 in
    > [115786.990249] res 40/00:00:00:00:00/00:00:00:00:00/a0 Emask 0x4
    > (timeout)
    > [115786.990254] ata6.00: status: { DRDY }
    > [115786.990259] ata6.00: cmd 60/88:08:b7:ee:c1/01:00:1d:00:00/40 tag 1 ncq
    > 200704 in
    > [115786.990261] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990265] ata6.00: status: { DRDY }
    > [115786.990270] ata6.00: cmd 60/f8:10:bf:eb:c1/02:00:1d:00:00/40 tag 2 ncq
    > 389120 in
    > [115786.990271] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990275] ata6.00: status: { DRDY }
    > [115786.990280] ata6.00: cmd 60/c0:18:3f:e8:c1/01:00:1d:00:00/40 tag 3 ncq
    > 229376 in
    > [115786.990282] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990286] ata6.00: status: { DRDY }
    > [115786.990291] ata6.00: cmd 60/c0:20:ff:e9:c1/01:00:1d:00:00/40 tag 4 ncq
    > 229376 in
    > [115786.990293] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990297] ata6.00: status: { DRDY }
    > [115786.990302] ata6.00: cmd 61/08:28:0f:c6:b6/00:00:1f:00:00/40 tag 5 ncq
    > 4096 out
    > [115786.990303] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990307] ata6.00: status: { DRDY }
    > [115786.990312] ata6.00: cmd 61/10:30:df:b0:17/00:00:01:00:00/40 tag 6 ncq
    > 8192 out
    > [115786.990313] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990318] ata6.00: status: { DRDY }
    > [115786.990323] ata6.00: cmd 61/10:38:4f:88:79/00:00:03:00:00/40 tag 7 ncq
    > 8192 out
    > [115786.990324] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990328] ata6.00: status: { DRDY }
    > [115786.990333] ata6.00: cmd 61/10:40:3f:18:95/00:00:05:00:00/40 tag 8 ncq
    > 8192 out
    > [115786.990335] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990339] ata6.00: status: { DRDY }
    > [115786.990344] ata6.00: cmd 61/08:48:d7:f6:a9/00:00:06:00:00/40 tag 9 ncq
    > 4096 out
    > [115786.990345] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990350] ata6.00: status: { DRDY }
    > [115786.990355] ata6.00: cmd 61/08:50:9f:37:b7/00:00:07:00:00/40 tag 10 ncq
    > 4096 out
    > [115786.990356] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990360] ata6.00: status: { DRDY }
    > [115786.990365] ata6.00: cmd 61/08:58:27:7c:d1/00:00:08:00:00/40 tag 11 ncq
    > 4096 out
    > [115786.990367] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990371] ata6.00: status: { DRDY }
    > [115786.990376] ata6.00: cmd 61/08:60:97:48:46/00:00:0d:00:00/40 tag 12 ncq
    > 4096 out
    > [115786.990377] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990381] ata6.00: status: { DRDY }
    > [115786.990386] ata6.00: cmd 61/08:68:cf:b4:68/00:00:0e:00:00/40 tag 13 ncq
    > 4096 out
    > [115786.990388] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990392] ata6.00: status: { DRDY }
    > [115786.990397] ata6.00: cmd 61/80:70:3f:06:94/01:00:10:00:00/40 tag 14 ncq
    > 196608 out
    > [115786.990398] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990402] ata6.00: status: { DRDY }
    > [115786.990408] ata6.00: cmd 61/08:78:7f:a4:88/00:00:11:00:00/40 tag 15 ncq
    > 4096 out
    > [115786.990409] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990413] ata6.00: status: { DRDY }
    > [115786.990418] ata6.00: cmd 61/08:80:37:b8:d5/00:00:13:00:00/40 tag 16 ncq
    > 4096 out
    > [115786.990419] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990423] ata6.00: status: { DRDY }
    > [115786.990428] ata6.00: cmd 61/08:88:c7:a4:8b/00:00:1d:00:00/40 tag 17 ncq
    > 4096 out
    > [115786.990430] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4
    > (timeout)
    > [115786.990454] ata6.00: status: { DRDY }
    > [115787.293177] ata6: soft resetting link
    > [115787.446158] ata6: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    > [115788.133592] ata6.00: configured for UDMA/133
    > [115788.133628] ata6: EH complete
    > [115787.877547] sd 5:0:0:0: [sdf] 586072368 512-byte hardware sectors (300069
    > MB)
    > [115787.877689] sd 5:0:0:0: [sdf] Write Protect is off
    > [115787.877692] sd 5:0:0:0: [sdf] Mode Sense: 00 3a 00 00
    > [115787.878746] sd 5:0:0:0: [sdf] Write cache: enabled, read cache: enabled,
    > doesn't support DPO or FUA
    >
    > What is the true cause of this, is there anyway to get more information?
    >
    > I will test soon with apic/acpi=off.
    >
    > Justin.
    > --
    > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    > the body of a message to majordomo@vger.kernel.org
    > More majordomo info at http://vger.kernel.org/majordomo-info.html
    > Please read the FAQ at http://www.tux.org/lkml/
    >

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  5. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)



    On Mon, 7 Jul 2008, Gerhard Wiesinger wrote:

    > Hello!
    >
    > Missing logs attached ...
    >
    > Ciao,
    > Gerhard



    Hello!

    I'm having a similar problem with a brand new Hardware under Fedora 9 x64
    8GB RAM
    Motherboard: ASUS M3N-H/HDMI
    Chipset: NForce 8300/Nvidia 750a
    CPU: AMD AM2 5600+, 2.9GHz, Brisbane Dual Core
    Kernel: 2.6.25.9-76.fc9.x86_64
    Smartmontools: smartmontools-5.38-2.fc9.x86_64
    BIOS AHCI mode
    Power cables for ata3 and ata4 are on the same cable from an Enermax power
    supply.

    ata1.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    ata2.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    ata3.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    ata4.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    ata5.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    ata6.00: ATA-7: SAMSUNG HD103UJ, 1AA01109, max UDMA7
    scsi 0:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
    scsi 1:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
    scsi 2:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
    scsi 3:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
    scsi 4:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5
    scsi 5:0:0:0: Direct-Access ATA SAMSUNG HD103UJ 1AA0 PQ: 0 ANSI: 5

    Problem occours only on ata3, I've changed the disk Port 3 the third time (new
    disks) and changed the SATA cable, too. Problem still exists.

    Sometimes a RAID rebuild doesn't work at all.

    To get the drive to live I've to power down the system.

    Logs are attached.

    Can it be a bug on concurrent access of smartctl/smartd?

    Any ideas?

    Ciao,
    Gerhard

    --

    Hi Gerhard,

    It /could/ be the port itself if you have changed the cable and disk..

    Have you tried loading the disk with dd and seeing if you can reproduce
    the problem? You are getting the same error I get generally, I can
    recommend turning OFF NCQ first and see if the problem goes away.

    # Define DISKS.
    cd /sys/block
    DISKS=$(/bin/ls -1d sd[a-z])

    # Disable NCQ on all disks.
    echo "Disabling NCQ on all disks..."
    for i in $DISKS
    do
    echo "Disabling NCQ on $i"
    echo 1 > /sys/block/"$i"/device/queue_depth
    done


    Justin.

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  6. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)

    On Mon, 7 Jul 2008, Justin Piszcz wrote:

    > Hi Gerhard,
    >
    > It /could/ be the port itself if you have changed the cable and disk..
    >


    Yes, but it is very unlikely. I have written TB of data there without any
    problems. Anyway this is my 3rd exchanged SAMSUNG disk ...


    > Have you tried loading the disk with dd and seeing if you can reproduce the
    > problem? You are getting the same error I get generally, I can recommend
    > turning OFF NCQ first and see if the problem goes away.
    >
    > # Define DISKS.
    > cd /sys/block
    > DISKS=$(/bin/ls -1d sd[a-z])
    >
    > # Disable NCQ on all disks.
    > echo "Disabling NCQ on all disks..."
    > for i in $DISKS
    > do
    > echo "Disabling NCQ on $i"
    > echo 1 > /sys/block/"$i"/device/queue_depth
    > done
    >


    I tried to disable NCQ on all disks and tried to rebuild the raid, but it
    still failed to rebuild with the same error message.

    I also tried the nolapic kernel parameter without success.

    /dev/sda: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
    /dev/sdb: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
    /dev/sdc: 5 Reallocated_Sector_Ct 0x0033 091 091 010 Pre-fail Always - 413
    /dev/sdd: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
    /dev/sde: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0
    /dev/sdf: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0

    The only thing is that the Reallocated_Sector_Ct is still >0 on /dev/sdc
    (keep in mind this is my 3rd new Samsung disk on /dev/sdc and I had up to
    3000 Reallocated_Sector_Ct on previous disks in < 1 day !!!).

    Should I replace the disk a fourth time?

    When you search in google you find a lot of threads with the timeout
    problem. Might this be a software issue?

    Any ideas?

    Thnx.

    Ciao,
    Gerhard

    --
    http://www.wiesinger.com/
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  7. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)

    Hello!

    BTW:
    The error in syslog also accoured when Reallocated_Sector_Ct didn't go up.

    Ciao,
    Gerhard

    --
    http://www.wiesinger.com/


    On Tue, 8 Jul 2008, Gerhard Wiesinger wrote:

    > On Mon, 7 Jul 2008, Justin Piszcz wrote:
    >
    >> Hi Gerhard,
    >>
    >> It /could/ be the port itself if you have changed the cable and disk..
    >>

    >
    > Yes, but it is very unlikely. I have written TB of data there without any
    > problems. Anyway this is my 3rd exchanged SAMSUNG disk ...
    >
    >
    >> Have you tried loading the disk with dd and seeing if you can reproduce the
    >> problem? You are getting the same error I get generally, I can recommend
    >> turning OFF NCQ first and see if the problem goes away.
    >>
    >> # Define DISKS.
    >> cd /sys/block
    >> DISKS=$(/bin/ls -1d sd[a-z])
    >>
    >> # Disable NCQ on all disks.
    >> echo "Disabling NCQ on all disks..."
    >> for i in $DISKS
    >> do
    >> echo "Disabling NCQ on $i"
    >> echo 1 > /sys/block/"$i"/device/queue_depth
    >> done
    >>

    >
    > I tried to disable NCQ on all disks and tried to rebuild the raid, but it
    > still failed to rebuild with the same error message.
    >
    > I also tried the nolapic kernel parameter without success.
    >
    > /dev/sda: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    > Always - 0
    > /dev/sdb: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    > Always - 0
    > /dev/sdc: 5 Reallocated_Sector_Ct 0x0033 091 091 010 Pre-fail
    > Always - 413
    > /dev/sdd: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    > Always - 0
    > /dev/sde: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    > Always - 0
    > /dev/sdf: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    > Always - 0
    >
    > The only thing is that the Reallocated_Sector_Ct is still >0 on /dev/sdc
    > (keep in mind this is my 3rd new Samsung disk on /dev/sdc and I had up to
    > 3000 Reallocated_Sector_Ct on previous disks in < 1 day !!!).
    >
    > Should I replace the disk a fourth time?
    >
    > When you search in google you find a lot of threads with the timeout problem.
    > Might this be a software issue?
    >

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  8. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)



    On Tue, 8 Jul 2008, Gerhard Wiesinger wrote:

    > Hello!
    >
    > BTW:
    > The error in syslog also accoured when Reallocated_Sector_Ct didn't go up.
    >


    Yes, I have seen the same thing on drives going bad as well.

    What type of PSU are you using (per the other thread) and how are you
    splitting the power connectors/etc?

    Justin.

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  9. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)



    On Tue, 8 Jul 2008, Gerhard Wiesinger wrote:

    > On Mon, 7 Jul 2008, Justin Piszcz wrote:
    >
    >> Hi Gerhard,
    >>
    >> It /could/ be the port itself if you have changed the cable and disk..
    >>

    >
    > Yes, but it is very unlikely. I have written TB of data there without any
    > problems. Anyway this is my 3rd exchanged SAMSUNG disk ...
    >
    >
    >> Have you tried loading the disk with dd and seeing if you can reproduce the
    >> problem? You are getting the same error I get generally, I can recommend
    >> turning OFF NCQ first and see if the problem goes away.
    >>
    >> # Define DISKS.
    >> cd /sys/block
    >> DISKS=$(/bin/ls -1d sd[a-z])
    >>
    >> # Disable NCQ on all disks.
    >> echo "Disabling NCQ on all disks..."
    >> for i in $DISKS
    >> do
    >> echo "Disabling NCQ on $i"
    >> echo 1 > /sys/block/"$i"/device/queue_depth
    >> done
    >>

    >
    > I tried to disable NCQ on all disks and tried to rebuild the raid, but it
    > still failed to rebuild with the same error message.
    >
    > I also tried the nolapic kernel parameter without success.
    >
    > /dev/sda: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    > Always - 0
    > /dev/sdb: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    > Always - 0
    > /dev/sdc: 5 Reallocated_Sector_Ct 0x0033 091 091 010 Pre-fail
    > Always - 413
    > /dev/sdd: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    > Always - 0
    > /dev/sde: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    > Always - 0
    > /dev/sdf: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    > Always - 0
    >
    > The only thing is that the Reallocated_Sector_Ct is still >0 on /dev/sdc
    > (keep in mind this is my 3rd new Samsung disk on /dev/sdc and I had up to
    > 3000 Reallocated_Sector_Ct on previous disks in < 1 day !!!).
    >
    > Should I replace the disk a fourth time?
    >
    > When you search in google you find a lot of threads with the timeout problem.
    > Might this be a software issue?
    >
    > Any ideas?


    Please run:

    smartctl -t short /dev/sdc
    sleep 300
    smartctl -t long /dev/sdc

    Wait 2-3 hours or more and:

    smartctl -a /dev/sdc

    Justin.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  10. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)

    On Tue, 8 Jul 2008, Justin Piszcz wrote:

    >> BTW:
    >> The error in syslog also accoured when Reallocated_Sector_Ct didn't go up.
    >>

    >
    > Yes, I have seen the same thing on drives going bad as well.
    >
    > What type of PSU are you using (per the other thread) and how are you
    > splitting the power connectors/etc?
    >


    I'm using an Enermax Power Supply (ATX 385 Watt, ENERMAX PRO82+) for 6
    harddisks using a connector with 2 connectors, and I think also 2 more
    with 2 connectors. But I'm currently not at the computer.

    Ciao,
    Gerhard

    --
    http://www.wiesinger.com/

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  11. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)

    On Tue, 8 Jul 2008, Justin Piszcz wrote:

    >
    >
    > On Tue, 8 Jul 2008, Gerhard Wiesinger wrote:
    >
    >> On Mon, 7 Jul 2008, Justin Piszcz wrote:
    >>
    >>> Hi Gerhard,
    >>>
    >>> It /could/ be the port itself if you have changed the cable and disk..
    >>>

    >>
    >> Yes, but it is very unlikely. I have written TB of data there without any
    >> problems. Anyway this is my 3rd exchanged SAMSUNG disk ...
    >>
    >>
    >>> Have you tried loading the disk with dd and seeing if you can reproduce
    >>> the problem? You are getting the same error I get generally, I can
    >>> recommend turning OFF NCQ first and see if the problem goes away.
    >>>
    >>> # Define DISKS.
    >>> cd /sys/block
    >>> DISKS=$(/bin/ls -1d sd[a-z])
    >>>
    >>> # Disable NCQ on all disks.
    >>> echo "Disabling NCQ on all disks..."
    >>> for i in $DISKS
    >>> do
    >>> echo "Disabling NCQ on $i"
    >>> echo 1 > /sys/block/"$i"/device/queue_depth
    >>> done
    >>>

    >>
    >> I tried to disable NCQ on all disks and tried to rebuild the raid, but it
    >> still failed to rebuild with the same error message.
    >>
    >> I also tried the nolapic kernel parameter without success.
    >>
    >> /dev/sda: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    >> Always - 0
    >> /dev/sdb: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    >> Always - 0
    >> /dev/sdc: 5 Reallocated_Sector_Ct 0x0033 091 091 010 Pre-fail
    >> Always - 413
    >> /dev/sdd: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    >> Always - 0
    >> /dev/sde: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    >> Always - 0
    >> /dev/sdf: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail
    >> Always - 0
    >>
    >> The only thing is that the Reallocated_Sector_Ct is still >0 on /dev/sdc
    >> (keep in mind this is my 3rd new Samsung disk on /dev/sdc and I had up to
    >> 3000 Reallocated_Sector_Ct on previous disks in < 1 day !!!).
    >>
    >> Should I replace the disk a fourth time?
    >>
    >> When you search in google you find a lot of threads with the timeout
    >> problem. Might this be a software issue?
    >>
    >> Any ideas?

    >
    > Please run:
    >
    > smartctl -t short /dev/sdc
    > sleep 300
    > smartctl -t long /dev/sdc
    >
    > Wait 2-3 hours or more and:
    >
    > smartctl -a /dev/sdc



    I'm changing the disk one more time ...

    Ciao,
    Gerhard

    --
    http://www.wiesinger.com/

    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  12. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)



    On Tue, 8 Jul 2008, Gerhard Wiesinger wrote:

    > On Tue, 8 Jul 2008, Justin Piszcz wrote:
    >
    >>
    >>
    >> On Tue, 8 Jul 2008, Gerhard Wiesinger wrote:
    >>
    >>> On Mon, 7 Jul 2008, Justin Piszcz wrote:
    >>>
    >>>> Hi Gerhard,

    >>
    >> Please run:
    >>
    >> smartctl -t short /dev/sdc
    >> sleep 300
    >> smartctl -t long /dev/sdc
    >>
    >> Wait 2-3 hours or more and:
    >>
    >> smartctl -a /dev/sdc

    >
    >
    > I'm changing the disk one more time ...


    Once you replace the disk please re-run the tests shown above and show us
    the output please.

    How many SAMSUNG disks have you gone through, do they really fail that
    often?

    Justin.
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  13. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)

    On Tue, 8 Jul 2008, Justin Piszcz wrote:

    >>>>> Hi Gerhard,
    >>>
    >>> Please run:
    >>>
    >>> smartctl -t short /dev/sdc
    >>> sleep 300
    >>> smartctl -t long /dev/sdc
    >>>
    >>> Wait 2-3 hours or more and:
    >>>
    >>> smartctl -a /dev/sdc

    >>
    >>
    >> I'm changing the disk one more time ...

    >
    > Once you replace the disk please re-run the tests shown above and show us the
    > output please.
    >
    > How many SAMSUNG disks have you gone through, do they really fail that often?
    >


    Hello Justin!

    Setup Power suppply:
    sda-sdd are on the same power supply cable, sde, sdf are on a second one.

    I changed the disk to a new SAMSUNG disk and the first raid resync did NOT
    work and I had 1 reallocated sector ...

    Also the RMA guy at our very good computer store (http://www.ditech.at/)
    were helpfull in changing the disks and he hates the SAMSUNG disks
    because of high RMA rates ...

    But:
    smart checks were ok (details see below). The smart checks are shown as
    aborted, but before running the next tests they were at "Completed without
    error" (strange).

    Now sdc has it's own power cable and I'm running a raid resync now.

    Power supply is:
    ATX 385 Watt, ENERMAX PRO82+

    Load on power supply measured on 220V side with a true RMS Wattmeter:
    Power off: 6,5W
    Max seen at power up: 196W
    BIOS: 114,1W
    Linux idle: 92,0W
    100% Disk I/O, 100% CPU load: 149,6W
    => Everything fine and as expected.

    I'll keep you up to date ...

    Ciao,
    Gerhard

    --
    http://www.wiesinger.com/


    ================================================== ============================================
    smartctl -a /dev/sdc
    smartctl version 5.38 [x86_64-redhat-linux-gnu] Copyright (C) 2002-8 Bruce Allen
    Home page is http://smartmontools.sourceforge.net/

    === START OF INFORMATION SECTION ===
    Device Model: SAMSUNG HD103UJ
    Serial Number: XXXXXXXXXXXXX
    Firmware Version: 1AA01109
    User Capacity: 1,000,204,886,016 bytes
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 8
    ATA Standard is: ATA-8-ACS revision 3b
    Local Time is: Wed Jul 9 07:03:39 2008 CEST

    ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for
    details.

    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled

    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED

    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection:
    Disabled.
    Self-test execution status: ( 0) The previous self-test routine
    completed
    without error or no self-test has
    ever
    been run.
    Total time to complete Offline
    data collection: (11927) seconds.
    Offline data collection
    capabilities: (0x7b) SMART execute Offline immediate.
    Auto Offline data collection
    on/off support.
    Suspend Offline collection upon
    new
    command.
    Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 2) minutes.
    Extended self-test routine
    recommended polling time: ( 200) minutes.
    Conveyance self-test routine
    recommended polling time: ( 21) minutes.
    SCT capabilities: (0x003f) SCT Status supported.
    SCT Feature Control supported.
    SCT Data Table supported.

    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED
    WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0
    3 Spin_Up_Time 0x0007 091 091 011 Pre-fail Always - 3560
    4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 5
    5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 1
    7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0
    8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 13955
    9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 11
    10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0
    11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 5
    13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 0
    183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
    184 Unknown_Attribute 0x0033 100 100 099 Pre-fail Always - 0
    187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0
    188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0
    190 Airflow_Temperature_Cel 0x0022 075 066 000 Old_age Always - 25 (Lifetime Min/Max 25/34)
    194 Temperature_Celsius 0x0022 074 064 000 Old_age Always - 26 (Lifetime Min/Max 25/36)
    195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 2077
    196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x003e 100 100 000 Old_age Always - 0
    200 Multi_Zone_Error_Rate 0x000a 253 253 000 Old_age Always - 0
    201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0

    SMART Error Log Version: 1
    No Errors Logged

    SMART Self-test log structure revision number 0
    Warning: ATA Specification requires self-test log structure revision
    number = 1
    Num Test_Description Status Remaining
    LifeTime(hours) LBA_of_first_error
    # 1 Extended offline Completed without error 00% 4 -
    # 2 Conveyance offline Aborted by host 00% 1 -
    # 3 Short offline Aborted by host 00% 0 -
    # 4 Conveyance offline Aborted by host 00% 0 -

    SMART Selective Self-Test Log Data Structure Revision Number (0) should be
    1
    SMART Selective self-test log data structure revision number 0
    Warning: ATA Specification requires selective self-test log data structure
    revision number = 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute
    delay.
    ================================================== ============================================
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  14. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)

    On Wed, 09 Jul 2008, Gerhard Wiesinger wrote:
    > Load on power supply measured on 220V side with a true RMS Wattmeter:


    That won't help for the failure mode you're looking for.

    Hook an osciloscope to the power lines on the HD's power feed, and try to
    get it to trigger on any "big" variations.

    --
    "One disk to rule them all, One disk to find them. One disk to bring
    them all and in the darkness grind them. In the Land of Redmond
    where the shadows lie." -- The Silicon Valley Tarot
    Henrique Holschuh
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  15. Re: Lots of con-current I/O = resets SATA link? (2.6.25.10)



    On Wed, 9 Jul 2008, Gerhard Wiesinger wrote:

    > On Tue, 8 Jul 2008, Justin Piszcz wrote:
    >
    >>>>>> Hi Gerhard,
    >>>>
    >>>> Please run:
    >>>>
    >>>> smartctl -t short /dev/sdc
    >>>> sleep 300
    >>>> smartctl -t long /dev/sdc
    >>>>
    >>>> Wait 2-3 hours or more and:
    >>>>
    >>>> smartctl -a /dev/sdc
    >>>
    >>>
    >>> I'm changing the disk one more time ...

    >>
    >> Once you replace the disk please re-run the tests shown above and show us
    >> the output please.
    >>
    >> How many SAMSUNG disks have you gone through, do they really fail that
    >> often?
    >>

    >
    > Hello Justin!
    >
    > Setup Power suppply:
    > sda-sdd are on the same power supply cable, sde, sdf are on a second one.
    >
    > I changed the disk to a new SAMSUNG disk and the first raid resync did NOT
    > work and I had 1 reallocated sector ...
    >
    > Also the RMA guy at our very good computer store (http://www.ditech.at/) were
    > helpfull in changing the disks and he hates the SAMSUNG disks because of high
    > RMA rates ...
    >
    > But:
    > smart checks were ok (details see below). The smart checks are shown as
    > aborted, but before running the next tests they were at "Completed without
    > error" (strange).
    >
    > Now sdc has it's own power cable and I'm running a raid resync now.
    >
    > Power supply is:
    > ATX 385 Watt, ENERMAX PRO82+
    >
    > Load on power supply measured on 220V side with a true RMS Wattmeter:
    > Power off: 6,5W
    > Max seen at power up: 196W
    > BIOS: 114,1W
    > Linux idle: 92,0W
    > 100% Disk I/O, 100% CPU load: 149,6W
    > => Everything fine and as expected.
    >
    > I'll keep you up to date ...
    >


    Hello!

    It looks like it works now without any problems:
    *) Serveral RAID checks (once a day)
    *) smartctl checks were fine
    *) Only one reallocated sector
    *) Writing the disk full with random data

    So the possibilities for the fault are:
    *) SATA power connector (most likely I would guess)
    *) 4th disk is now ok
    *) Other 220V power cable connector through the Wattmeter

    Ciao,
    Gerhard

    --
    http://www.wiesinger.com/
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

+ Reply to Thread