On 07/11/2018 04.48, Felix Miata wrote:
# journalctl -b -e ... Nov 06 19:54:55 00srv smartd[937]: Device: /dev/sdc [SAT], 8 Currently unreadable (pending) sectors Nov 06 20:24:56 00srv smartd[937]: Device: /dev/sdc [SAT], 8 Currently unreadable (pending) sectors Nov 06 20:54:56 00srv smartd[937]: Device: /dev/sdc [SAT], 8 Currently unreadable (pending) sectors Nov 06 21:24:56 00srv smartd[937]: Device: /dev/sdc [SAT], 8 Currently unreadable (pending) sectors Nov 06 21:54:55 00srv smartd[937]: Device: /dev/sdc [SAT], 8 Currently unreadable (pending) sectors # fdisk -l /dev/sdc; smartctl -x /dev/sdc http://fm.no-ip.com/Tmp/Hardware/Disk/smartctlx-msi85-hgst1000.txt shows Current_Pending_Sector raw value is 8 after only 1660 power on hours. :-(
Earlier: 81 hours.
How can I find out which device(s) have the bad sectors before replacing the disk?
Well, it is clearly sdc, and your fdisk output gives you the serial number of the disk. If you do not know which one it is, remove them all, boot a rescue media, connect a single one, read the identifiers (hdparm -i /dev/sda), and put a sticker with the "model=" string somewhere you can read. Hopefully the serial is already printed in the manufacturer label, so no need to boot.
Are these likely fixable short of replacing the disk?
Sometimes.
If so, how?
Read the recent thread "[opensuse] Login weirdness". Basically, your disk fails consistently on LBA 142446713, read error. You have to find out what is there and rewrite that sector.
Can an extended offline test force them to be rewritten and reallocated?
No. A read doesn't remap the sector, only a write.
Could this be some kind of false alarm on so young a disk?
No. However, an error doesn't need to be fatal, most disks have errors you do not see. Disks have an area to remap those bad sectors out of sight and use, and continue working. The problem is if they continue to develop more errors. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)