4
1
I recently received a Linux box having problems with Samba share - first off, couldn't connect, second ls -la
showed some I/O error
(close to what can be seen below) with no listing.
Now, I've fully updated the box, and after the update, the RAID is OK, all the data accessible and Samba worked like a charm. Apparently, I didn't save the previous logs.
Now, even if everything works, from time to time this pops up in my journalctl
:
kernel: ata4: EH complete
kernel: end_request: I/O error, dev sdc, sector 2839546656
kernel: cdb[0]=0x28: 28 00 a9 40 0b 20 00 00 f0 00
kernel: sd 3:0:0:0: [sdc] CDB:
kernel: ASC=0x47 ASCQ=0x0
kernel: sd 3:0:0:0: [sdc]
kernel: a9 40 0b a0
kernel: 72 0b 47 00 00 00 00 0c 00 0a 80 00 00 00 00 00
kernel: Descriptor sense data with sense descriptors (in hex):
kernel: Sense Key : 0xb [current] [descriptor]
kernel: sd 3:0:0:0: [sdc]
kernel: Result: hostbyte=0x00 driverbyte=0x08
kernel: sd 3:0:0:0: [sdc]
kernel: ata4.00: configured for UDMA/133
kernel: ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 330)
kernel: ata4: hard resetting link
kernel: ata4.00: error: { ICRC ABRT }
kernel: ata4.00: status: { DRDY ERR }
kernel: [145B blob data]
kernel: ata4.00: failed command: READ DMA EXT
kernel: ata4: SError: { UnrecovData 10B8B BadCRC }
kernel: ata4.00: BMDMA stat 0x26
kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6
smartctl -t extended
(S.M.A.R.T. long (maximum) scan) says nothing three times already.
By "everything works", I mean:
// Read from drive, write to drive.
find > files.txt
// Another read->write.
du -bc > sizes.txt
// 100 GB random writer
dd if=/dev/urandom of=fillerd bs=512 count=209715200
The files end up uncorrupt, fully readable.
What does the error depict? Should I be worried? How do I fix it?
This appeared to be the real issue. Something wrong with the connectors, because after some messing around with hardware, the errors stopped. – joltmode – 2013-09-16T06:59:14.763