July 29, 20241 yr Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450152 Jul 27 01:31:26 185409 kernel: I/O error, dev sdb, sector 4121449968 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121449904 Jul 27 01:31:26 185409 kernel: I/O error, dev sdb, sector 4121450304 op 0x0:(READ) flags 0x0 phys_seg 32 prio class 2 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450240 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450248 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450256 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450264 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450272 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450280 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450288 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450296 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450304 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450312 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450320 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450328 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450336 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450344 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450352 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450360 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450368 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450376 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450384 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450392 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450400 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450408 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450416 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450424 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450432 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450440 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450448 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450456 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450464 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450472 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450480 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121450488 Jul 27 01:31:26 185409 kernel: I/O error, dev sdb, sector 4121207624 op 0x0:(READ) flags 0x0 phys_seg 21 prio class 2 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207560 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207568 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207576 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207584 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207592 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207600 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207608 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207616 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207624 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207632 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207640 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207648 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207656 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207664 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207672 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207680 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207688 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207696 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207704 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207712 Jul 27 01:31:26 185409 kernel: md: disk3 read error, sector=4121207720 Watching tv shows on my emby one night, the video stuck and the app crushed, I opened the emby again didn't think much. The next day I found these errors in log run a smart extend test came back with nothing wrong, should I be worried? Edited July 29, 20241 yr by xyzeratul
July 29, 20241 yr Author 23 minutes ago, JorgeB said: Please post the diagnostics. Thanks, attached below, also the disk3 smart test 185409-diagnostics-20240729-1829.zip 185409-smart-20240729-1829.zip
July 29, 20241 yr Community Expert Solution It's not logged as a disk problem, could be a power/connection issue or spin down related, some SAS disks don't always behave correctly while spinning up.
July 29, 20241 yr Author 1 hour ago, JorgeB said: It's not logged as a disk problem, could be a power/connection issue or spin down related, some SAS disks don't always behave correctly while spinning up. Yea, it's one of SAS drive my friend give me, since my board and case support SAS, I have been using these SAS drive for a bit over a year now. So should I keep using it, or it's time looking for a replacement? PS: shutdown and clean some dust today, restart and unraid told me the disk turns good? Edited July 29, 20241 yr by xyzeratul
July 29, 20241 yr Community Expert 41 minutes ago, xyzeratul said: or it's time looking for a replacement? Like mentioned, doesn't look like a disk problem.
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.