Laov Posted February 15, 2022 Share Posted February 15, 2022 Hello, I've noticed my unraid disk log fill up with these messages that report sata link speed change: Feb 14 23:55:31 DataServer kernel: ata2.00: configured for UDMA/133 Feb 14 23:56:20 DataServer kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 14 23:56:20 DataServer kernel: ata2.00: configured for UDMA/133 Feb 14 23:57:56 DataServer kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Feb 14 23:57:56 DataServer kernel: ata2.00: configured for UDMA/133 Feb 14 23:58:10 DataServer kernel: ata2: limiting SATA link speed to 3.0 Gbps Feb 14 23:58:11 DataServer kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 14 23:58:11 DataServer kernel: ata2.00: configured for UDMA/133 Feb 15 00:04:56 DataServer kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 15 00:04:56 DataServer kernel: ata2.00: configured for UDMA/133 Is this something to be concerned about? These messages seem to have appeared right after I changed my hardware. Current specs: Model: Custom M/B: Gigabyte Technology Co., Ltd. Z87X-D3H-CF Version To be filled by O.E.M. - s/n: To be filled by O.E.M. BIOS: American Megatrends Inc. Version F8. Dated: 01/17/2014 CPU: Intel® Core™ i7-4770K CPU @ 3.50GHz HVM: Enabled IOMMU: Disabled Cache: 256 KiB, 1 MB, 8 MB Memory: 16 GiB DDR3 (max. installable capacity 32 GiB) I ran unraid for ~1 month previously on an older AMD phenom II x4 965 with GA-78LMT-USB3 (rev. 4.1) mobo and the log was nice and clean compared to a spam of these ata messages on the current system... Quote Link to comment
ChatNoir Posted February 16, 2022 Share Posted February 16, 2022 Please provide your full diagnostics in your next post. Quote Link to comment
Laov Posted February 16, 2022 Author Share Posted February 16, 2022 7 hours ago, ChatNoir said: Please provide your full diagnostics in your next post. Provided. dataserver-diagnostics-20220216-1743.zip Quote Link to comment
JorgeB Posted February 16, 2022 Share Posted February 16, 2022 Since it's happening with all the disks connected to the Intel SATA controller there could be a power/connection problem, or the board/controller is going bad, the former is much more likely. Quote Link to comment
Laov Posted February 16, 2022 Author Share Posted February 16, 2022 (edited) Feb 16 01:19:02 DataServer emhttpd: read SMART /dev/sdb Feb 16 02:11:09 DataServer kernel: ata1.00: exception Emask 0x50 SAct 0x60 SErr 0x4890800 action 0xe frozen Feb 16 02:11:09 DataServer kernel: ata1.00: irq_stat 0x0c400040, interface fatal error, connection status changed Feb 16 02:11:09 DataServer kernel: ata1: SError: { HostInt PHYRdyChg 10B8B LinkSeq DevExch } Feb 16 02:11:09 DataServer kernel: ata1.00: failed command: READ FPDMA QUEUED Feb 16 02:11:09 DataServer kernel: ata1.00: cmd 60/40:28:50:2f:2d/05:00:2e:00:00/40 tag 5 ncq dma 688128 in Feb 16 02:11:09 DataServer kernel: ata1.00: status: { DRDY } Feb 16 02:11:09 DataServer kernel: ata1.00: failed command: READ FPDMA QUEUED Feb 16 02:11:09 DataServer kernel: ata1.00: cmd 60/e8:30:90:34:2d/01:00:2e:00:00/40 tag 6 ncq dma 249856 in Feb 16 02:11:09 DataServer kernel: ata1.00: status: { DRDY } Feb 16 02:11:09 DataServer kernel: ata1: hard resetting link Feb 16 02:11:09 DataServer kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320) Feb 16 02:11:09 DataServer kernel: ata1.00: configured for UDMA/133 Feb 16 02:11:09 DataServer kernel: ata1: EH complete Some more errors this time in red... Is this something that needs immediate action? I was doing a parity check when these new ones appeared. I'd have more time to play around with the controller on weekend... Parity check returned 0 errors. Edited February 16, 2022 by Laov Quote Link to comment
Laov Posted February 22, 2022 Author Share Posted February 22, 2022 I changed my SATA controller mode from AHCI to IDE in mobo BIOS and so far the 2 main drives are stable without any weird messages. Speed for the parity check is identical so I will probably keep it this way. However I found some weird warnings in my smaller 1 TB hdd: Feb 20 02:19:41 DataServer emhttpd: spinning down /dev/sdd Feb 21 23:00:46 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 21 23:00:47 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 21 23:00:49 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 21 23:00:51 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 21 23:19:05 DataServer emhttpd: read SMART /dev/sdd Feb 22 00:38:34 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 00:38:34 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 00:38:35 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 00:38:35 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 00:38:36 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 00:38:38 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 00:38:40 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:12:15 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:12:17 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:12:19 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:12:21 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:22:13 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:22:13 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:22:13 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:22:14 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:22:15 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:22:16 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:22:18 DataServer wsdd[10966]: udp_send: Failed to send udp packet with Network is unreachable Feb 22 02:28:26 DataServer emhttpd: spinning down /dev/sdd What are UDP packet messages appearing on one of my drives? Quote Link to comment
JorgeB Posted February 22, 2022 Share Posted February 22, 2022 55 minutes ago, Laov said: What are UDP packet messages appearing on one of my drives? Those have nothing to do with drives, and if not needed you can disable WSD (settings -> SMB) to fix that. Quote Link to comment
Laov Posted February 22, 2022 Author Share Posted February 22, 2022 5 minutes ago, JorgeB said: Those have nothing to do with drives, and if not needed you can disable WSD (settings -> SMB) to fix that. I'm more curious to the cause for this. Why did the messages appear on only one of my drives log? SMB settings seem to be global for my entire server... What makes this drive special? Quote Link to comment
Solution JorgeB Posted February 22, 2022 Solution Share Posted February 22, 2022 6 minutes ago, Laov said: Why did the messages appear on only one of my drives log? Because wsdd contains sdd, same as the drive it's filtering. Quote Link to comment
Laov Posted February 22, 2022 Author Share Posted February 22, 2022 35 minutes ago, JorgeB said: Because wsdd contains sdd, same as the drive it's filtering. So if I connect my drive to 5th sata port instead of the 4th these messages will go away? Wow that some interesting behavior... Quote Link to comment
JonathanM Posted February 22, 2022 Share Posted February 22, 2022 2 minutes ago, Laov said: So if I connect my drive to 5th sata port instead of the 4th these messages will go away? Wow that some interesting behavior... Probably not, the messages will just show up in whichever drive gets assigned to the sdd device. Unraid assigns drives based on when in the boot process they are detected, so the sd? can change randomly. That's why all drive identification for array slots is based on serial numbers. I think you are missing the point though, the messages are simply a list of the lines in the syslog that reference a specific sd? designation, and because wsdd contains the letters sdd in order, it's being added to the list for that device. Quote Link to comment
Recommended Posts
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.