Here is a first hand(I saw this personally) dmesg report of an error:

ata1.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0
ata1.00: irq_stat 0x40000008
ata1.00: failed command: READ FPDMA QUEUED
ata1.00: cmd 60/20:00:80:13:06/00:00:05:00:00/40 tag 0 ncq 16384 in
res 41/40:20:96:13:06/00:00:05:00:00/00 Emask 0x409 (media error) <F>
ata1.00: status: { DRDY ERR }
ata1.00: error: { UNC }
ata1.00: configured for UDMA/133
sd 0:0:0:0: [sda] Unhandled sense code
sd 0:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda]
Sense Key : 0x3 [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
05 06 13 96
sd 0:0:0:0: [sda]
ASC=0x11 ASCQ=0x4
sd 0:0:0:0: [sda] CDB:
cdb[0]=0x28: 28 00 05 06 13 80 00 00 20 00
end_request: I/O error, dev sda, sector 84284310
Buffer I/O error on device sda, logical block 10535538
Buffer I/O error on device sda, logical block 10535539
ata1: EH complete

The bad sector was indeed LBA 84284310, the drive did not go offline and I believe it would have been error 23 in windows (will double check if possible).