February 9, 20242 yr I've rebuilt this disk multiple times at this point but I eventually end up getting these errors that bring the device offline: Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1151 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1151 Sense Key : 0x2 [current] Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1151 ASC=0x4 ASCQ=0x0 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1151 CDB: opcode=0x88 88 00 00 00 00 00 b3 90 36 a0 00 00 00 30 00 00 Feb 9 00:06:59 Pluto kernel: I/O error, dev sdi, sector 3012572832 op 0x0:(READ) flags 0x0 phys_seg 6 prio class 2 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1088 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1088 Sense Key : 0x2 [current] Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1088 ASC=0x4 ASCQ=0x0 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1088 CDB: opcode=0x8a 8a 00 00 00 00 00 9e 85 48 b8 00 00 00 50 00 00 Feb 9 00:06:59 Pluto kernel: I/O error, dev sdi, sector 2659535032 op 0x1:(WRITE) flags 0x0 phys_seg 10 prio class 2 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1089 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1089 Sense Key : 0x2 [current] Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1089 ASC=0x4 ASCQ=0x0 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1089 CDB: opcode=0x88 88 00 00 00 00 00 b3 90 36 48 00 00 00 30 00 00 Feb 9 00:06:59 Pluto kernel: I/O error, dev sdi, sector 3012572744 op 0x0:(READ) flags 0x0 phys_seg 6 prio class 2 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1090 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=4s Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1090 Sense Key : 0x2 [current] Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1090 ASC=0x4 ASCQ=0x0 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1090 CDB: opcode=0x88 88 00 00 00 00 00 b3 90 36 78 00 00 00 28 00 00 Feb 9 00:06:59 Pluto kernel: I/O error, dev sdi, sector 3012572792 op 0x0:(READ) flags 0x0 phys_seg 5 prio class 2 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1091 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1091 Sense Key : 0x2 [current] Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1091 ASC=0x4 ASCQ=0x0 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1091 CDB: opcode=0x88 88 00 00 00 00 00 b3 90 36 d0 00 00 00 08 00 00 Feb 9 00:06:59 Pluto kernel: I/O error, dev sdi, sector 3012572880 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1092 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1092 Sense Key : 0x2 [current] Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1092 ASC=0x4 ASCQ=0x0 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1092 CDB: opcode=0x8a 8a 00 00 00 00 00 9e 85 49 08 00 00 00 10 00 00 Feb 9 00:06:59 Pluto kernel: I/O error, dev sdi, sector 2659535112 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 2 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1093 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1093 Sense Key : 0x2 [current] Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1093 ASC=0x4 ASCQ=0x0 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1093 CDB: opcode=0x88 88 00 00 00 00 00 b3 90 36 d8 00 00 00 08 00 00 Feb 9 00:06:59 Pluto kernel: I/O error, dev sdi, sector 3012572888 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1094 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1094 Sense Key : 0x2 [current] Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1094 ASC=0x4 ASCQ=0x0 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1094 CDB: opcode=0x8a 8a 00 00 00 00 00 9e 85 49 18 00 00 00 08 00 00 Feb 9 00:06:59 Pluto kernel: I/O error, dev sdi, sector 2659535128 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1095 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1095 Sense Key : 0x2 [current] Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1095 ASC=0x4 ASCQ=0x0 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1095 CDB: opcode=0x88 88 00 00 00 00 00 b3 90 36 e0 00 00 00 08 00 00 Feb 9 00:06:59 Pluto kernel: I/O error, dev sdi, sector 3012572896 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 2 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1096 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=0s Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1096 Sense Key : 0x2 [current] Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1096 ASC=0x4 ASCQ=0x0 Feb 9 00:06:59 Pluto kernel: sd 1:0:3:0: [sdi] tag#1096 CDB: opcode=0x8a 8a 00 00 00 00 00 9e 85 49 20 00 00 00 10 00 00 Feb 9 00:06:59 Pluto kernel: I/O error, dev sdi, sector 2659535136 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 2 I have tried different cables to the controller and different power cables but nothing seems to make a difference. The drive isn't that old (1yr power on time) and the SMART info looks OK?1
February 9, 20242 yr Community Expert It's not logged as a device problem and SMART looks fine, it may be worth connecting it to the onboard SATA controller instead, if the same and if you have already replaced both cables, it could still be a device issue.
February 9, 20242 yr Author Cheers. I'll try the onboard SATA tonight and see how I get on. I assume I'm right in saying I have to rebuild after the reconnection? That's been my usual approach
February 9, 20242 yr Community Expert The errors you posted are form a cache device, smallcache, not the disk that got disabled, that disk also looks OK, but there are a lot of UDMA CRC errors, make sure that is not increasing, it could be a SATA cable, if the emulated disk is mounting you can rebuild.
February 9, 20242 yr Author In the original post? That's directly from the disk log on the HDD attached at sdi (8TB WD). I've stopped using smallcache because it drops offline occasionally, I intend to remove it completely. The 8TB disk on the otherhand is problematic but I'll try the onboard raid controller to see if that makes a difference.
February 9, 20242 yr Community Expert 16 minutes ago, jjbrunton said: In the original post? That's directly from the disk log on the HDD attached at sdi (8TB WD). Did you reboot after the errors? sdi in the diags is a SanDisk X300 2.5 7MM 256GB
February 9, 20242 yr Author 2 hours ago, JorgeB said: Did you reboot after the errors? sdi in the diags is a SanDisk X300 2.5 7MM 256GB Ah that'd be it. Here's the recent runtime. pluto-diagnostics-20240209-1143.zip
February 9, 20242 yr Community Expert Looks more like a power/connection issue, replace the SATA cable one more time and rebuild, and if it happens again post new diags in this thread, this way we can compare the CRC errors with the previous diags. P.S. there are mcvlan call traces logged, those can crash the server, you should change docker network to ipvlan. P.P.S unless you are troubleshooting a mover issue, recommend disabling the mover logging, or it will spam the log.
February 12, 20242 yr Author I've switched it to the onboard controller with a new SATA cable and so far so good. Thanks for the other tips.
February 12, 20242 yr Author On 2/9/2024 at 5:42 PM, JorgeB said: Looks more like a power/connection issue, replace the SATA cable one more time and rebuild, and if it happens again post new diags in this thread, this way we can compare the CRC errors with the previous diags. P.S. there are mcvlan call traces logged, those can crash the server, you should change docker network to ipvlan. P.P.S unless you are troubleshooting a mover issue, recommend disabling the mover logging, or it will spam the log. Actually just to follow up on this, my Docker is set to IPVlan: Are there further settings required?
February 12, 20242 yr Community Expert They could be old errors, did you reboot after changing to ipvlan?
February 12, 20242 yr Author 1 hour ago, JorgeB said: They could be old errors, did you reboot after changing to ipvlan? I have rebooted multiple times but I can't actually remember selecting VLAN. The fix common problems still shows: "Macvlan and bridging has been found. This might cause issues with stability on your server."
February 12, 20242 yr Author In the docker settings? I've tried rebooting since the earlier post and that still shows as problem in Fix common problems.. Is there anything else that needs to be changed in the network settings?
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.