September 10, 20241 yr I have two cache drives set as RAID1 via BTRFS. Today I misclicked on the icon and i accidentally opened the logs of one of them. I see extremely worring strings like: Sep 10 12:54:05 Server kernel: I/O error, dev sdb, sector 541844120 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 2 Sep 10 12:54:05 Server kernel: ata1: EH complete Sep 10 12:54:05 Server kernel: BTRFS info (device sdb1): read error corrected: ino 4610 off 0 (dev /dev/sdb1 sector 490758712) Sep 10 12:54:05 Server kernel: BTRFS info (device sdb1): read error corrected: ino 7426 off 17612800 (dev /dev/sdb1 sector 54751520) Sep 10 12:54:05 Server kernel: BTRFS info (device sdb1): read error corrected: ino 7426 off 17616896 (dev /dev/sdb1 sector 54751528) Sep 10 12:54:05 Server kernel: BTRFS info (device sdb1): read error corrected: ino 7426 off 17625088 (dev /dev/sdb1 sector 54751544) Sep 10 12:54:05 Server kernel: BTRFS info (device sdb1): read error corrected: ino 7426 off 17620992 (dev /dev/sdb1 sector 54751536) Sep 10 12:54:05 Server kernel: BTRFS info (device sdb1): read error corrected: ino 7426 off 17629184 (dev /dev/sdb1 sector 54751552) Sep 10 12:54:05 Server kernel: BTRFS info (device sdb1): read error corrected: ino 7426 off 17633280 (dev /dev/sdb1 sector 54751560) Sep 10 12:54:05 Server kernel: BTRFS info (device sdb1): read error corrected: ino 4610 off 4096 (dev /dev/sdb1 sector 490758720) Sep 10 12:54:05 Server kernel: BTRFS info (device sdb1): read error corrected: ino 7426 off 17637376 (dev /dev/sdb1 sector 54751568) Sep 10 12:54:05 Server kernel: BTRFS info (device sdb1): read error corrected: ino 7426 off 17641472 (dev /dev/sdb1 sector 54751576) Sep 10 12:54:06 Server kernel: ata1.00: exception Emask 0x11 SAct 0x6002140 SErr 0x680100 action 0x6 frozen Sep 10 12:54:06 Server kernel: ata1.00: irq_stat 0x48000008, interface fatal error Sep 10 12:54:06 Server kernel: ata1: SError: { UnrecovData 10B8B BadCRC Handshk } Sep 10 12:54:06 Server kernel: ata1.00: failed command: READ FPDMA QUEUED But unraid didn't warn me at all about this problem. Should i replace this drive immediately?
September 10, 20241 yr Author I see a lot of unnecessary (shares configs, docker, qemu VMs) PII in the diagnostics, here are the relevant parts: syslog.txt TEAM_T2532TB_TPBFxxx-2024-04-03 ssd2 (sdb).txt btrfs-usage.txt
September 10, 20241 yr Community Expert Solution Looks more like a power/connection issues, check/replace cables and then scrub the pool to confirm all is well.
September 10, 20241 yr Author ok i hope in the weekend i have time to take it out and see what happens if i switch the sata cables (of course i installed the server in the most inconvenient place of the house where i need to disassemble everything to take it out)
October 9, 20241 yr Author One month later I finally had the time to open the server and use this as an excuse to change the sata SSD with a more expensive but faster nvme one. I did a full surface scan with hd sentinel but it looks like the drive was working perfectly 😅 as you said probably it was a temporary cable/connection issue that went away the moment I plugged a different one
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.