[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#576913: marked as done (Sata raid 1 errors)



Your message dated Mon, 12 Apr 2010 21:54:26 +0200
with message-id <20100412195425.GA10984@baikonur.stro.at>
and subject line Re: Bug#576913: further info on Sata raid 1 errors
has caused the Debian Bug report #576913,
regarding Sata raid 1 errors
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
576913: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576913
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: Debian 5.0
Kernel: Linux 2.6.26-2-686 on i686
Motherboard: ASUS P5QPL-AM
CPU: Intel(R) Core(TM)2 Quad CPU Q8300 @ 2.50GHz, 4 cores
Hard drives: 4 x ATA WDC WD5000AAKS-0 (2 in software raid 1 config from Debian setup)

2xharddrive on raid 1 MD with ext3 500gb partition using /
the other 2 as /home and another path as ext3

Hi
Whenever I move big files (>2gb) on the raid 1 I get these errors:

Apr  8 08:32:07 rauserver kernel: [150817.743370] ata1.01: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Apr  8 08:32:07 rauserver kernel: [150817.743370] ata1.01: BMDMA stat 0x65
Apr  8 08:32:07 rauserver kernel: [150817.743370] ata1.01: cmd c8/00:68:27:74:34/00:00:00:00:00/f4 tag 0 dma 53248 in
Apr  8 08:32:07 rauserver kernel: [150817.743370]          res 51/40:27:65:74:34/40:00:04:00:00/f4 Emask 0x9 (media error)
Apr  8 08:32:07 rauserver kernel: [150817.743370] ata1.01: status: { DRDY ERR }
Apr  8 08:32:07 rauserver kernel: [150817.743370] ata1.01: error: { UNC }
Apr  8 08:32:07 rauserver kernel: [150817.820854] ata1.00: configured for UDMA/133
Apr  8 08:32:07 rauserver kernel: [150817.838015] ata1.01: configured for UDMA/133
Apr  8 08:32:07 rauserver kernel: [150817.838045] ata1: EH complete
Apr  8 08:32:07 rauserver kernel: [150817.880854] sd 0:0:0:0: [sda] 976773168 512-byte hardware sectors (500108 MB)
Apr  8 08:32:07 rauserver kernel: [150817.925860] sd 0:0:0:0: [sda] Write Protect is off
Apr  8 08:32:07 rauserver kernel: [150817.925890] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Apr  8 08:32:07 rauserver kernel: [150817.935963] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr  8 08:32:07 rauserver kernel: [150817.968436] sd 0:0:1:0: [sdb] 976773168 512-byte hardware sectors (500108 MB)
Apr  8 08:32:07 rauserver kernel: [150817.982705] sd 0:0:1:0: [sdb] Write Protect is off
Apr  8 08:32:07 rauserver kernel: [150817.982735] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00
Apr  8 08:32:07 rauserver kernel: [150817.990878] sd 0:0:1:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA


This is quite repeatable and the bigger the files the more I get. If a really big file then the system freezes and needs to be hard reset.

This happens all the time with MySQL, mysqldump fails due to lockup on large files. Also MySql performance is not as fast as it should be.

I have rebuilt the machine back to windows 2008 and stress tested with these disks in software raid and no issues and the performance is exceptionally fast. Now rebuilt back to Debian and still the same issue arising.

Smart shows no issues with these disks also.

If I put the data on the non mirrored drives in Debian and try then no problems at all and data access is fast.

I have flashed the Mb to the latest version and replaced all the sata cables but no improvement.

This looks like a bug to me, anybody have any ideas?



Kind regards

--
..........................
Dave Edwards (G7RAU)
email:
dave@g7rau.co.uk
Web:
http://g7rau.demon.co.uk/
..........................




--- End Message ---
--- Begin Message ---
On Mon, Apr 12, 2010 at 08:14:58PM +0100, Dave Edwards wrote:
> Hi
> 
> Please cancel this bug. The disk has had a catastrophic failure so the 
> reports in the log were valid.
> 
> Sorry for any investigation work this has incurred.

thanks for feedback, closing.


--- End Message ---

Reply to: