On Mon, Aug 27, 2012 at 7:34 PM, Camaleón <noela...@gmail.com> wrote: > On Mon, 27 Aug 2012 16:21:41 +0500, Muhammad Yousuf Khan wrote: > >> On Mon, Aug 27, 2012 at 3:28 PM, Sthu Deus <sthu.d...@gmail.com> wrote: >>> Good time of the day, Muhammad. >>> >>> >>> You wrote: >>> >>>> i am using RAID 1 on 2x500GB harddrives. and one of my drive shows >>>> Current_Pending_Sector 154. how can i fix that. > > You can't. Modern hard disks handle this by themselves in a process that > is transparent for the user (they "mark" the bad sectors so they are not > used again). You have to worry though if this value > (Current_Pending_Sector) starts increasing very quickly. > > After all, as you are using "raid 1" you are covered by this (i.e., a > hard disk failure), right? ;-P > >>> I also did not have such a problem. But I think, that You have not to >>> worry about this unless huge amount of sectors will become bad in short >>> period of time. - The HDD will relocate it itself, marking the primary >>> ones as bad and that's it. > > Exactly. > >> but my /var/log/syslog showing this >> >> >> Aug 27 12:11:37 lion kernel: [ 6.347932] ata1.00: status: { DRDY ERR } >> Aug 27 12:11:37 lion kernel: [ 6.348008] ata1.00: error: { UNC } >> Aug 27 12:11:37 lion kernel: [ 6.372478] ata1.00: configured for UDMA/133 >> Aug 27 12:11:37 lion kernel: [ 6.372487] ata1: EH complete >> Aug 27 12:11:37 lion kernel: [ 9.059325] ata1.00: exception Emask 0x0 >> SAct 0x0 SErr 0x0 action 0x0 >> Aug 27 12:11:37 lion kernel: [ 9.059413] ata1.00: BMDMA stat 0x4 >> Aug 27 12:11:37 lion kernel: [ 9.059514] ata1.00: failed command: READ DMA >> Aug 27 12:11:37 lion kernel: [ 9.059620] ata1.00: cmd >> c8/00:08:08:78:1b/00:00:00:00:00/e2 tag 0 dma 4096 in >> Aug 27 12:11:37 lion kernel: [ 9.059621] res >> 51/40:00:0a:78:1b/00:00:00:00:00/e2 Emask 0x9 (media error) >> >> >> do i have to worry about this? > > Sure you do. What's connected to ata1.00? (dmesg | grep -i ata1.00) > > These errors are usually derived not from "bad sectors" but a hardware issue > (e.g., bad/loosey cabling). Just to be sure, you can run a full SMART test to > diagnose any problem from the disk and better if you use the hdd > manufacturer's > test disk tools which are usually run from a small live-cd iso. > > Greetings, > > -- > Camaleón > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > Archive: http://lists.debian.org/k1g0ig$9nj$1...@ger.gmane.org >
here you go. [ 2.920604] ata1.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 2.955968] ata1.00: ATA-8: WDC WD5000AVVS-63M8B0, 01.00A01, max UDMA/133 [ 2.955972] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 0/32) [ 2.961570] ata1.00: configured for UDMA/133 would you please tell me one more thing. i am using rsyslog server but i can not see this critical error on that rsyslog server. i am using this in /etc/rsyslog.conf *.* @@MySyslogServer which is working fine however it suppose to show this msg also. any experience person would like to throw some light on that plz. Thanks, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cagwvfmk1ojoopt_+lxxo457ffnyqawqohuvkth7runmx1wp...@mail.gmail.com