Hello, Please can I share my puzzlement here in the hope a problem shared is a
problem halved...
Sdb on this system has smart errors and a replacement disk is on order.
However, I notice that sda is also mentioned.
Sadly I can find nothing wrong with sda, smart and tests are all clean. I am wondering if sda is actually good and it is
just suffering a consequence of the problems with sdb .. see last log line:-
Oct 29 01:42:03 sv24 kernel: [1529665.357951] ata2: EH in SWNCQ
mode,QC:qc_active 0x1 sactive 0x1
Oct 29 01:42:03 sv24 kernel: [1529665.357987] ata2: SWNCQ:qc_active 0x1
defer_bits 0x0 last_issue_tag 0x0
Oct 29 01:42:03 sv24 kernel: [1529665.357988] dhfis 0x1 dmafis 0x1 sdbfis 0x0
Oct 29 01:42:03 sv24 kernel: [1529665.358047] ata2: ATA_REG 0x41 ERR_REG 0x40
Oct 29 01:42:03 sv24 kernel: [1529665.358074] ata2: tag : dhfis dmafis sdbfis
sacitve
Oct 29 01:42:03 sv24 kernel: [1529665.358103] ata2: tag 0x0: 1 1 0 1
Oct 29 01:42:03 sv24 kernel: [1529665.358134] ata2.00: exception Emask 0x1 SAct
0x1 SErr 0x0 action 0x6 frozen
Oct 29 01:42:03 sv24 kernel: [1529665.358185] ata2.00: Ata error. fis:0x21
Oct 29 01:42:03 sv24 kernel: [1529665.358213] ata2.00: failed command: READ
FPDMA QUEUED
Oct 29 01:42:03 sv24 kernel: [1529665.358248] ata2.00: cmd
60/08:00:9f:80:01/00:00:00:00:00/40 tag 0 ncq 4096 in
Oct 29 01:42:03 sv24 kernel: [1529665.358249] res
41/40:00:9f:80:01/40:00:00:00:00/40 Emask 0x9 (media error)
Oct 29 01:42:03 sv24 kernel: [1529665.358347] ata2.00: status: { DRDY ERR }
Oct 29 01:42:03 sv24 kernel: [1529665.358374] ata2.00: error: { UNC }
Oct 29 01:42:03 sv24 kernel: [1529665.358403] ata2: hard resetting link
Oct 29 01:42:03 sv24 kernel: [1529665.358405] ata2: nv: skipping hardreset on
occupied port
Oct 29 01:42:03 sv24 kernel: [1529665.824025] ata2: SATA link up 3.0 Gbps
(SStatus 123 SControl 300)
Oct 29 01:42:03 sv24 kernel: [1529665.848473] ata2.00: configured for UDMA/133
Oct 29 01:42:03 sv24 kernel: [1529665.848490] sd 1:0:0:0: [sdb] Unhandled sense
code
Oct 29 01:42:03 sv24 kernel: [1529665.848493] sd 1:0:0:0: [sdb] Result:
hostbyte=DID_OK driverbyte=DRIVER_SENSE
Oct 29 01:42:03 sv24 kernel: [1529665.848496] sd 1:0:0:0: [sdb] Sense Key :
Medium Error [current] [descriptor]
Oct 29 01:42:03 sv24 kernel: [1529665.848499] Descriptor sense data with sense
descriptors (in hex):
Oct 29 01:42:03 sv24 kernel: [1529665.848501] 72 03 11 04 00 00 00 0c
00 0a 80 00 00 00 00 00
Oct 29 01:42:03 sv24 kernel: [1529665.848532] 00 01 80 9f
Oct 29 01:42:03 sv24 kernel: [1529665.848541] sd 1:0:0:0: [sdb] Add. Sense:
Unrecovered read error - auto reallocate failed
Oct 29 01:42:03 sv24 kernel: [1529665.848548] sd 1:0:0:0: [sdb] CDB: Read(10):
28 00 00 01 80 9f 00 00 08 00
Oct 29 01:42:03 sv24 kernel: [1529665.848567] end_request: I/O error, dev sdb,
sector 98463
Oct 29 01:42:03 sv24 kernel: [1529665.848618] ata2: EH complete
Oct 29 01:42:03 sv24 kernel: [1529665.849447] raid1:md125: read error corrected
(8 sectors at 98400 on sdb1)
Oct 29 01:42:03 sv24 kernel: [1529665.849456] raid1: sda1: redirecting sector
98344 to another mirror
After this time the logs have nothing else to say about these disks. I also wonder if that redirection is permanent ..
or does it get fixed in the next mdadm resync?
Some more info about this machine:
elbournb@sv24:/var/log$ df -h
FilesystemSize Used Avail Use% Mounted on
/dev/md125 19G 6.2G 12G 36% /
tmpfs 4.0G 12K 4.0G 1% /lib/init/rw
udev 4.0G 196K 4.0G 1% /dev
tmpfs 4.0G 0 4.0G 0% /dev/shm
/dev/md2 422G 152G 249G 38% /home
elbournb@sv24:/var/log$ cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sdb6[0] sda6[2] sdc6[1]
449313856 blocks [3/3] [UUU]
md1 : active raid1 sdb5[0] sda5[2] sdc5[1]
19534912 blocks [3/3] [UUU]
md125 : active raid1 sdb1[0] sda1[2] sdc1[1]
19534912 blocks [3/3] [UUU]
unused devices: none
--
Confidence is what you have before you understand a problem - Woody Allen
--
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/509b8ee3.10...@gmail.com
