uzos5ixi Posted August 12, 2022 Share Posted August 12, 2022 Was hoping to get a hand with an error I'm continously seeing. I added a WDC DS520 to my server. I am receiving the following error. Steps I've taken to troubleshoot: 1. Remove WDC drive from the array (Error Stays) 2. Recable WDC drive along with replace cables (Error Stays) 3. Recable all SATA and Power Connecctors (No Joy) Diags are attached. Thanks for the help in advancee. [ 193.688205] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x50000 action 0x6 frozen [ 193.688211] ata1: SError: { PHYRdyChg CommWake } [ 193.688215] ata1.00: failed command: FLUSH CACHE EXT [ 193.688216] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 6 res 40/00:01:e0:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) [ 193.688219] ata1.00: status: { DRDY } [ 193.688222] ata1: hard resetting link [ 193.993393] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 194.017718] ata1.00: configured for UDMA/133 [ 194.017721] ata1.00: retrying FLUSH 0xea Emask 0x4 [ 194.023159] ata1: EH complete [ 194.407228] ata1.00: exception Emask 0x10 SAct 0x80 SErr 0x840000 action 0x6 frozen [ 194.407232] ata1.00: irq_stat 0x08000000, interface fatal error [ 194.407232] ata1: SError: { CommWake LinkSeq } [ 194.407235] ata1.00: failed command: WRITE FPDMA QUEUED [ 194.407235] ata1.00: cmd 61/08:38:a8:49:1f/00:00:00:01:00/40 tag 7 ncq dma 4096 out res 50/00:00:00:00:00/00:00:00:00:00/00 Emask 0x10 (ATA bus error) [ 194.407238] ata1.00: status: { DRDY } [ 194.407240] ata1: hard resetting link [ 194.712463] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [ 194.736586] ata1.00: configured for UDMA/133 [ 194.741309] ata1: EH complete [ 212.870225] ata1: limiting SATA link speed to 3.0 Gbps [ 213.176315] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 320) [ 213.200621] ata1.00: configured for UDMA/133 tower-diagnostics-20220811-2303.zip Quote Link to comment
JorgeB Posted August 12, 2022 Share Posted August 12, 2022 Try that device with a different controller if available. Quote Link to comment
MAM59 Posted August 12, 2022 Share Posted August 12, 2022 get rid of powertop if in use Quote Link to comment
uzos5ixi Posted August 12, 2022 Author Share Posted August 12, 2022 6 hours ago, JorgeB said: Try that device with a different controller if available. Not an option. I will buy an IT Mode HBA if I fail to find an alternative path. Quote Link to comment
uzos5ixi Posted August 12, 2022 Author Share Posted August 12, 2022 6 hours ago, MAM59 said: get rid of powertop if in use I do and will remove it after a parity resync. I'm becoming careless with the data and need to make sure it's properly protected. Why the concern with powertop? Quote Link to comment
Solution MAM59 Posted August 12, 2022 Solution Share Posted August 12, 2022 7 minutes ago, uzos5ixi said: Why the concern with powertop? depending on the used version and your hardware, it might seriously kill your sata connections now and then. It programs the SATA port to "auto" power saving which does not really work reliable on many controllers. Symptoms are loss of contact, unstable data transmission, degregation in link speed (like you are currently suffering from). It saves little, but can cause a lot of grief. 1 Quote Link to comment
uzos5ixi Posted August 12, 2022 Author Share Posted August 12, 2022 @mam59 Thanks you...you were spot on. 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.