* Re: And again help on deciphering an error (continued) [not found] ` <491DDA43.4030600@sauce.co.nz> @ 2008-11-14 20:06 ` Justin Piszcz 2008-11-14 20:12 ` Justin Piszcz 0 siblings, 1 reply; 5+ messages in thread From: Justin Piszcz @ 2008-11-14 20:06 UTC (permalink / raw) To: Richard Scobie; +Cc: Peter Rabbitson, linux-raid, linux-ide On Sat, 15 Nov 2008, Richard Scobie wrote: > Justin Piszcz wrote: >> >> >> On Fri, 14 Nov 2008, Peter Rabbitson wrote: >> >>> Peter Rabbitson wrote: >>> >>>> Hello, >>>> >>>> I need help with understanding what is going on here >>>> (full log): > > These posts might be worth sending to linux-ide. > > Regards, > > Richard > I have a whole bunch, but here is the last one: [64894.610696] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 [64894.610703] ata9.00: irq_stat 0x00020002, device error via D2H FIS [64894.610708] ata9.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 [64894.610709] res 51/04:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x1 (devic e error) [64894.610714] ata9.00: status: { DRDY ERR } [64894.610718] ata9.00: error: { ABRT } [64894.626437] ata9.00: configured for UDMA/100 [64894.626449] ata9: EH complete [64894.626654] sd 8:0:0:0: [sdh] 586072368 512-byte hardware sectors (300069 MB) [64894.637744] end_request: I/O error, dev sdh, sector 586067135 [64894.637759] md: super_written gets error=-5, uptodate=0 [64894.637762] raid5: Disk failure on sdh1, disabling device. [64894.637763] raid5: Operation continuing on 9 devices. [64894.638129] sd 8:0:0:0: [sdh] Write Protect is off [64894.638131] sd 8:0:0:0: [sdh] Mode Sense: 00 3a 00 00 [64894.638148] sd 8:0:0:0: [sdh] Write cache: enabled, read cache: enabled, does n't support DPO or FUA Justin. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: And again help on deciphering an error (continued) 2008-11-14 20:06 ` And again help on deciphering an error (continued) Justin Piszcz @ 2008-11-14 20:12 ` Justin Piszcz 2008-11-15 3:53 ` Robert Hancock 0 siblings, 1 reply; 5+ messages in thread From: Justin Piszcz @ 2008-11-14 20:12 UTC (permalink / raw) To: Richard Scobie; +Cc: Peter Rabbitson, linux-raid, linux-ide On Fri, 14 Nov 2008, Justin Piszcz wrote: > > > On Sat, 15 Nov 2008, Richard Scobie wrote: > >> Justin Piszcz wrote: >>> >>> >>> On Fri, 14 Nov 2008, Peter Rabbitson wrote: >>> >>>> Peter Rabbitson wrote: >>>> >>>>> Hello, >>>>> >>>>> I need help with understanding what is going on here >>>>> (full log): >> >> These posts might be worth sending to linux-ide. >> >> Regards, >> >> Richard >> > > I have a whole bunch, but here is the last one: Here are some more: Jul 14 05:54:55 p34 kernel: [478107.751877] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Jul 14 05:54:55 p34 kernel: [478107.751883] ata4.00: irq_stat 0x40000001 Jul 14 05:54:55 p34 kernel: [478107.751889] ata4.00: cmd 25/00:f8:08:b0:ee/00:00:22:00:00/e0 tag 0 dma 126976 in Jul 14 05:54:55 p34 kernel: [478107.751890] res 51/40:f8:47:b0:ee/00:00:22:00:00/e0 Emask 0x9 (media error) Jul 14 05:54:55 p34 kernel: [478107.751895] ata4.00: status: { DRDY ERR } Jul 14 05:54:55 p34 kernel: [478107.751898] ata4.00: error: { UNC } Jul 14 05:54:55 p34 kernel: [478107.773836] ata4.00: configured for UDMA/133 Jul 14 05:54:55 p34 kernel: [478107.773845] ata4: EH complete Jul 14 05:54:55 p34 kernel: [478107.844912] sd 3:0:0:0: [sdd] 586072368 512-byte hardware sectors (300069 MB) Jul 14 05:54:55 p34 kernel: [478107.846321] sd 3:0:0:0: [sdd] Write Protect is off Jul 14 05:54:55 p34 kernel: [478107.846325] sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00 Jul 14 05:54:55 p34 kernel: [478107.849297] sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Oct 12 09:25:22 p34 kernel: [1434196.959129] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Oct 12 09:25:30 p34 kernel: [1434196.959137] ata6.00: irq_stat 0x40000001 Oct 12 09:25:30 p34 kernel: [1434196.959142] ata6.00: cmd 25/00:00:00:af:ee/00:02:22:00:00/e0 tag 0 dma 262144 in Oct 12 09:25:30 p34 kernel: [1434196.959144] res 51/40:00:4f:b0:ee/00:02:22:00:00/e0 Emask 0x9 (media error) Oct 12 09:25:30 p34 kernel: [1434196.959149] ata6.00: status: { DRDY ERR } Oct 12 09:25:30 p34 kernel: [1434196.959152] ata6.00: error: { UNC } Oct 12 09:25:30 p34 kernel: [1434196.999110] ata6.00: configured for UDMA/133 Oct 12 09:25:30 p34 kernel: [1434196.999144] ata6: EH complete Oct 12 09:25:30 p34 kernel: [1434203.096157] ata6.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Oct 12 09:25:30 p34 kernel: [1434203.096165] ata6.00: irq_stat 0x40000001 Oct 12 09:25:30 p34 kernel: [1434203.096171] ata6.00: cmd 25/00:00:00:af:ee/00:02:22:00:00/e0 tag 0 dma 262144 in Oct 12 09:25:30 p34 kernel: [1434203.096172] res 51/40:00:4f:b0:ee/00:02:22:00:00/e0 Emask 0x9 (media error) Oct 12 09:25:30 p34 kernel: [1434203.096177] ata6.00: status: { DRDY ERR } Oct 12 09:25:30 p34 kernel: [1434203.096181] ata6.00: error: { UNC } Oct 12 09:25:30 p34 kernel: [1434203.104811] ata6.00: configured for UDMA/133 Oct 12 09:25:30 p34 kernel: [1434203.104819] ata6: EH complete Nov 9 09:25:19 p34 kernel: [ 3686.460568] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 9 09:25:19 p34 kernel: [ 3686.460574] ata4.00: irq_stat 0x40000001 Nov 9 09:25:19 p34 kernel: [ 3686.460579] ata4.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 Nov 9 09:25:19 p34 kernel: [ 3686.460580] res 51/10:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x81 (invalid argument) Nov 9 09:25:19 p34 kernel: [ 3686.460585] ata4.00: status: { DRDY ERR } Nov 9 09:25:19 p34 kernel: [ 3686.460589] ata4.00: error: { IDNF } Nov 9 09:25:24 p34 kernel: [ 3691.461173] ata4.00: qc timeout (cmd 0xec) Nov 9 09:25:24 p34 kernel: [ 3691.461183] ata4.00: failed to IDENTIFY (I/O error, err_mask=0x5) Nov 9 09:25:24 p34 kernel: [ 3691.461187] ata4.00: revalidation failed (errno=-5) Nov 9 09:25:24 p34 kernel: [ 3691.461192] ata4: hard resetting link Nov 9 09:25:24 p34 kernel: [ 3691.766178] ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) Nov 9 09:25:24 p34 kernel: [ 3691.803834] ata4.00: configured for UDMA/133 Nov 9 09:25:24 p34 kernel: [ 3691.803846] end_request: I/O error, dev sdd, sector 586067135 Nov 9 09:25:24 p34 kernel: [ 3691.803849] md: super_written gets error=-5, uptodate=0 Nov 9 09:25:24 p34 kernel: [ 3691.803853] raid5: Disk failure on sdd1, disabling device. Nov 9 09:25:24 p34 kernel: [ 3691.803854] raid5: Operation continuing on 8 devices. Nov 12 01:22:28 p34 kernel: [64894.610696] ata9.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Nov 12 01:22:28 p34 kernel: [64894.610703] ata9.00: irq_stat 0x00020002, device error via D2H FIS Nov 12 01:22:28 p34 kernel: [64894.610708] ata9.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 Nov 12 01:22:28 p34 kernel: [64894.610709] res 51/04:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x1 (device error) Nov 12 01:22:28 p34 kernel: [64894.610714] ata9.00: status: { DRDY ERR } Nov 12 01:22:28 p34 kernel: [64894.610718] ata9.00: error: { ABRT } Nov 12 01:22:28 p34 kernel: [64894.626437] ata9.00: configured for UDMA/100 Nov 12 01:22:28 p34 kernel: [64894.626449] ata9: EH complete Nov 12 01:22:28 p34 kernel: [64894.626654] sd 8:0:0:0: [sdh] 586072368 512-byte hardware sectors (300069 MB) Nov 12 01:22:28 p34 kernel: [64894.637744] end_request: I/O error, dev sdh, sector 586067135 Nov 12 01:22:28 p34 kernel: [64894.637759] md: super_written gets error=-5, uptodate=0 Nov 12 01:22:28 p34 kernel: [64894.637762] raid5: Disk failure on sdh1, disabling device. Nov 12 01:22:28 p34 kernel: [64894.637763] raid5: Operation continuing on 9 devices. Nov 12 01:22:28 p34 kernel: [64894.638129] sd 8:0:0:0: [sdh] Write Protect is off Nov 12 01:22:28 p34 kernel: [64894.638131] sd 8:0:0:0: [sdh] Mode Sense: 00 3a 00 00 Nov 12 01:22:28 p34 kernel: [64894.638148] sd 8:0:0:0: [sdh] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: And again help on deciphering an error (continued) 2008-11-14 20:12 ` Justin Piszcz @ 2008-11-15 3:53 ` Robert Hancock 2008-11-15 8:37 ` Peter Rabbitson 0 siblings, 1 reply; 5+ messages in thread From: Robert Hancock @ 2008-11-15 3:53 UTC (permalink / raw) To: linux-raid; +Cc: linux-ide Justin Piszcz wrote: > Here are some more: > > Jul 14 05:54:55 p34 kernel: [478107.751877] ata4.00: exception Emask 0x0 > SAct 0x0 SErr 0x0 action 0x0 > Jul 14 05:54:55 p34 kernel: [478107.751883] ata4.00: irq_stat 0x40000001 > Jul 14 05:54:55 p34 kernel: [478107.751889] ata4.00: cmd > 25/00:f8:08:b0:ee/00:00:22:00:00/e0 tag 0 dma 126976 in > Jul 14 05:54:55 p34 kernel: [478107.751890] res > 51/40:f8:47:b0:ee/00:00:22:00:00/e0 Emask 0x9 (media error) > Jul 14 05:54:55 p34 kernel: [478107.751895] ata4.00: status: { DRDY ERR } > Jul 14 05:54:55 p34 kernel: [478107.751898] ata4.00: error: { UNC } Drive reporting an uncorrectable error on a read command. > Nov 9 09:25:19 p34 kernel: [ 3686.460568] ata4.00: exception Emask 0x0 > SAct 0x0 SErr 0x0 action 0x0 > Nov 9 09:25:19 p34 kernel: [ 3686.460574] ata4.00: irq_stat 0x40000001 > Nov 9 09:25:19 p34 kernel: [ 3686.460579] ata4.00: cmd > ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 > Nov 9 09:25:19 p34 kernel: [ 3686.460580] res > 51/10:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x81 (invalid argument) > Nov 9 09:25:19 p34 kernel: [ 3686.460585] ata4.00: status: { DRDY ERR } > Nov 9 09:25:19 p34 kernel: [ 3686.460589] ata4.00: error: { IDNF } Flush cache returned ID not found (drive couldn't find a sector) > Nov 9 09:25:24 p34 kernel: [ 3691.461173] ata4.00: qc timeout (cmd 0xec) > Nov 9 09:25:24 p34 kernel: [ 3691.461183] ata4.00: failed to IDENTIFY > (I/O error, err_mask=0x5) > Nov 9 09:25:24 p34 kernel: [ 3691.461187] ata4.00: revalidation failed > (errno=-5) > Nov 9 09:25:24 p34 kernel: [ 3691.461192] ata4: hard resetting link > Nov 9 09:25:24 p34 kernel: [ 3691.766178] ata4: SATA link up 3.0 Gbps > (SStatus 123 SControl 300) > Nov 9 09:25:24 p34 kernel: [ 3691.803834] ata4.00: configured for UDMA/133 > Nov 9 09:25:24 p34 kernel: [ 3691.803846] end_request: I/O error, dev > sdd, sector 586067135 > Nov 9 09:25:24 p34 kernel: [ 3691.803849] md: super_written gets > error=-5, uptodate=0 > Nov 9 09:25:24 p34 kernel: [ 3691.803853] raid5: Disk failure on sdd1, > disabling device. > Nov 9 09:25:24 p34 kernel: [ 3691.803854] raid5: Operation continuing > on 8 devices. > > Nov 12 01:22:28 p34 kernel: [64894.610696] ata9.00: exception Emask 0x0 > SAct 0x0 SErr 0x0 action 0x0 > Nov 12 01:22:28 p34 kernel: [64894.610703] ata9.00: irq_stat 0x00020002, > device error via D2H FIS > Nov 12 01:22:28 p34 kernel: [64894.610708] ata9.00: cmd > ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 > Nov 12 01:22:28 p34 kernel: [64894.610709] res > 51/04:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x1 (device error) > Nov 12 01:22:28 p34 kernel: [64894.610714] ata9.00: status: { DRDY ERR } > Nov 12 01:22:28 p34 kernel: [64894.610718] ata9.00: error: { ABRT } Flush cache returned command aborted, presumably because the write to media failed. Looks like some sick drives, or some other more global problem (power, temperature, etc.) to me.. ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: And again help on deciphering an error (continued) 2008-11-15 3:53 ` Robert Hancock @ 2008-11-15 8:37 ` Peter Rabbitson 0 siblings, 0 replies; 5+ messages in thread From: Peter Rabbitson @ 2008-11-15 8:37 UTC (permalink / raw) To: Robert Hancock; +Cc: linux-raid, linux-ide Robert Hancock wrote: > Justin Piszcz wrote: >> Here are some more: >> >> Jul 14 05:54:55 p34 kernel: [478107.751877] ata4.00: exception Emask >> 0x0 SAct 0x0 SErr 0x0 action 0x0 >> Jul 14 05:54:55 p34 kernel: [478107.751883] ata4.00: irq_stat 0x40000001 >> Jul 14 05:54:55 p34 kernel: [478107.751889] ata4.00: cmd >> 25/00:f8:08:b0:ee/00:00:22:00:00/e0 tag 0 dma 126976 in >> Jul 14 05:54:55 p34 kernel: [478107.751890] res >> 51/40:f8:47:b0:ee/00:00:22:00:00/e0 Emask 0x9 (media error) >> Jul 14 05:54:55 p34 kernel: [478107.751895] ata4.00: status: { DRDY ERR } >> Jul 14 05:54:55 p34 kernel: [478107.751898] ata4.00: error: { UNC } > > Drive reporting an uncorrectable error on a read command. > >> Nov 9 09:25:19 p34 kernel: [ 3686.460568] ata4.00: exception Emask >> 0x0 SAct 0x0 SErr 0x0 action 0x0 >> Nov 9 09:25:19 p34 kernel: [ 3686.460574] ata4.00: irq_stat 0x40000001 >> Nov 9 09:25:19 p34 kernel: [ 3686.460579] ata4.00: cmd >> ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 >> Nov 9 09:25:19 p34 kernel: [ 3686.460580] res >> 51/10:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x81 (invalid argument) >> Nov 9 09:25:19 p34 kernel: [ 3686.460585] ata4.00: status: { DRDY ERR } >> Nov 9 09:25:19 p34 kernel: [ 3686.460589] ata4.00: error: { IDNF } > > Flush cache returned ID not found (drive couldn't find a sector) > >> Nov 9 09:25:24 p34 kernel: [ 3691.461173] ata4.00: qc timeout (cmd 0xec) >> Nov 9 09:25:24 p34 kernel: [ 3691.461183] ata4.00: failed to IDENTIFY >> (I/O error, err_mask=0x5) >> Nov 9 09:25:24 p34 kernel: [ 3691.461187] ata4.00: revalidation >> failed (errno=-5) >> Nov 9 09:25:24 p34 kernel: [ 3691.461192] ata4: hard resetting link >> Nov 9 09:25:24 p34 kernel: [ 3691.766178] ata4: SATA link up 3.0 Gbps >> (SStatus 123 SControl 300) >> Nov 9 09:25:24 p34 kernel: [ 3691.803834] ata4.00: configured for >> UDMA/133 >> Nov 9 09:25:24 p34 kernel: [ 3691.803846] end_request: I/O error, dev >> sdd, sector 586067135 >> Nov 9 09:25:24 p34 kernel: [ 3691.803849] md: super_written gets >> error=-5, uptodate=0 >> Nov 9 09:25:24 p34 kernel: [ 3691.803853] raid5: Disk failure on >> sdd1, disabling device. >> Nov 9 09:25:24 p34 kernel: [ 3691.803854] raid5: Operation continuing >> on 8 devices. >> >> Nov 12 01:22:28 p34 kernel: [64894.610696] ata9.00: exception Emask >> 0x0 SAct 0x0 SErr 0x0 action 0x0 >> Nov 12 01:22:28 p34 kernel: [64894.610703] ata9.00: irq_stat >> 0x00020002, device error via D2H FIS >> Nov 12 01:22:28 p34 kernel: [64894.610708] ata9.00: cmd >> ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 >> Nov 12 01:22:28 p34 kernel: [64894.610709] res >> 51/04:00:34:cf:f3/00:00:00:f3:40/a3 Emask 0x1 (device error) >> Nov 12 01:22:28 p34 kernel: [64894.610714] ata9.00: status: { DRDY ERR } >> Nov 12 01:22:28 p34 kernel: [64894.610718] ata9.00: error: { ABRT } > > Flush cache returned command aborted, presumably because the write to > media failed. > > Looks like some sick drives, or some other more global problem (power, > temperature, etc.) to me.. > But an _identical_ sector number? Looks too unlikely... I might try to crank open hexedit and write repeatedly to this place. Sectors are still 512 bytes right? Peter ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: And again help on deciphering an error (continued) [not found] ` <alpine.DEB.1.10.0811141456550.22161@p34.internal.lan> [not found] ` <491DDA43.4030600@sauce.co.nz> @ 2008-11-14 21:33 ` Peter Rabbitson 1 sibling, 0 replies; 5+ messages in thread From: Peter Rabbitson @ 2008-11-14 21:33 UTC (permalink / raw) To: Justin Piszcz; +Cc: linux-raid, linux-ide Justin Piszcz wrote: > > > On Fri, 14 Nov 2008, Peter Rabbitson wrote: > >> Peter Rabbitson wrote: >>> Hello, >>> >>> I need help with understanding what is going on here >>> (full log): >>> >>> >>> Oct 27 11:33:41 Arzamas kernel: ata6.00: exception Emask 0x10 SAct 0x0 >>> SErr 0x80000 action 0xe frozen >>> Oct 27 11:33:41 Arzamas kernel: ata6.00: irq_stat 0x01100010, PHY RDY >>> changed >>> Oct 27 11:33:41 Arzamas kernel: ata6: SError: { 10B8B } >>> Oct 27 11:33:41 Arzamas kernel: ata6.00: cmd >>> ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0 >>> Oct 27 11:33:41 Arzamas kernel: res 06/37:00:00:00:00/00:00:00:00:06/00 >>> Emask 0x12 (ATA bus error) >>> Oct 27 11:33:41 Arzamas kernel: ata6.00: error: { IDNF ABRT } >>> Oct 27 11:33:41 Arzamas kernel: ata6: hard resetting link >>> Oct 27 11:33:46 Arzamas kernel: ata6: SATA link up 3.0 Gbps (SStatus 123 >>> SControl 0) >>> Oct 27 11:33:46 Arzamas kernel: ata6.00: configured for UDMA/100 >>> Oct 27 11:33:46 Arzamas kernel: ata6: EH complete >>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] 488397168 512-byte >>> hardware sectors (250059 MB) >>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Write Protect is off >>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Mode Sense: 00 3a >>> 00 00 >>> Oct 27 11:33:46 Arzamas kernel: sd 6:0:0:0: [sde] Write cache: enabled, >>> read cache: enabled, doesn't support DPO or FUA >>> Oct 27 11:33:46 Arzamas kernel: end_request: I/O error, dev sde, sector >>> 488166955 >> >> The saga continues. After replacing the drive (and I didn't make a >> mistake as the serial numbers don't match) I got _exaclty_ the same >> error a week later. I have replaced the cable for the drive in question, >> will see what happens. The controller is: >> >> 02:03.0 Mass storage controller: Silicon Image, Inc. SiI 3124 PCI-X >> Serial ATA Controller (rev 02) >> Subsystem: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller >> 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: 64, Cache Line Size: 64 bytes >> Interrupt: pin A routed to IRQ 25 >> Region 0: Memory at fc5fd800 (64-bit, non-prefetchable) [size=128] >> Region 2: Memory at fc5f0000 (64-bit, non-prefetchable) [size=32K] >> Region 4: I/O ports at b000 [size=16] >> Expansion ROM at fc480000 [disabled] [size=512K] >> Capabilities: [64] Power Management version 2 >> Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA >> PME(D0-,D1-,D2-,D3hot-,D3cold-) >> Status: D0 PME-Enable- DSel=0 DScale=1 PME- >> Capabilities: [40] PCI-X non-bridge device >> Command: DPERE- ERO+ RBC=512 OST=12 >> Status: Dev=ff:1f.0 64bit+ 133MHz+ SCD- USC- DC=simple >> DMMRBC=2048 >> DMOST=12 DMCRS=128 RSCEM- 266MHz- 533MHz- >> Capabilities: [54] Message Signalled Interrupts: Mask- 64bit+ >> Queue=0/0 >> Enable- >> Address: 0000000000000000 Data: 0000 >> Kernel driver in use: sata_sil24 >> >> >> Anyone has any bright ideas? > > Hm, someone else also has similar problems, maybe we ought to buy new hw or > something, I have the same/similar issue as you. > > BTW, after that error, if you re-run a short/long test, do they succeed or > hang (never complete)? > They succeed with flying colors. Moreover I had badblocks -svw running at the same time (so the drive was really loaded). And I did this repeatedly with the first one - no issues. Peter ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2008-11-15 8:37 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <4907A5FA.7050903@rabbit.us>
[not found] ` <491DC218.9010301@rabbit.us>
[not found] ` <alpine.DEB.1.10.0811141456550.22161@p34.internal.lan>
[not found] ` <491DDA43.4030600@sauce.co.nz>
2008-11-14 20:06 ` And again help on deciphering an error (continued) Justin Piszcz
2008-11-14 20:12 ` Justin Piszcz
2008-11-15 3:53 ` Robert Hancock
2008-11-15 8:37 ` Peter Rabbitson
2008-11-14 21:33 ` Peter Rabbitson
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).