postersyndrome Posted May 28, 2022 Share Posted May 28, 2022 I am running UnRAID 6.9.2. I was planning on upgrading this weekend, but my monthly disk check reported read errors on my parity drive. My SMART report does not appear to show any errors. I have not shut down, the only thing I did was run another parity check, which passed with no errors. Any help would be greatly appreciated. Thanks in advance. plexraid-diagnostics-20220528-1337.zip Quote Link to comment
Solution Squid Posted May 28, 2022 Solution Share Posted May 28, 2022 Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 28 00 00 00 01 80 12 b6 88 40 00 43d+11:57:14.120 READ FPDMA QUEUED ea 00 00 00 00 00 00 00 00 00 00 00 00 43d+11:57:13.644 FLUSH CACHE EXT 61 01 20 00 20 00 02 04 77 dc c0 40 00 43d+11:57:04.705 WRITE FPDMA QUEUED 61 04 00 00 18 00 02 04 77 d8 c0 40 00 43d+11:57:04.705 WRITE FPDMA QUEUED 61 04 00 00 10 00 02 04 77 d4 c0 40 00 43d+11:57:04.705 WRITE FPDMA QUEUED Error 2 [1] occurred at disk power-on lifetime: 17515 hours (729 days + 19 hours) Reseat the cabling. Also, trimming every hour is going to decrease the lifetime of the SSD. Once a week is more than sufficient. Quote Link to comment
postersyndrome Posted May 28, 2022 Author Share Posted May 28, 2022 6 minutes ago, Squid said: Commands leading to the command that caused the error were: CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/Feature_Name -- == -- == -- == == == -- -- -- -- -- --------------- -------------------- 60 00 28 00 00 00 01 80 12 b6 88 40 00 43d+11:57:14.120 READ FPDMA QUEUED ea 00 00 00 00 00 00 00 00 00 00 00 00 43d+11:57:13.644 FLUSH CACHE EXT 61 01 20 00 20 00 02 04 77 dc c0 40 00 43d+11:57:04.705 WRITE FPDMA QUEUED 61 04 00 00 18 00 02 04 77 d8 c0 40 00 43d+11:57:04.705 WRITE FPDMA QUEUED 61 04 00 00 10 00 02 04 77 d4 c0 40 00 43d+11:57:04.705 WRITE FPDMA QUEUED Error 2 [1] occurred at disk power-on lifetime: 17515 hours (729 days + 19 hours) Reseat the cabling. Also, trimming every hour is going to decrease the lifetime of the SSD. Once a week is more than sufficient. Thanks for the fast response. Since you said more than sufficient, I have set the trim to once a month. If I should move it to once a week, I'm ok with that too. I am currently in the process of running an extended test. As soon as that finishes, I will power down and reseat the cables on the device. Again, thank you for responding so fast. Quote Link to comment
postersyndrome Posted May 31, 2022 Author Share Posted May 31, 2022 My Extended test finished. There were no errors found. This morning, I powered off the server and reseated the cables on the drive indicated. I did notice that the power connector right next to the one connected to the drive with issues has a 4-pin molex adapter for a fan controller. I'm not sure if that is the cause or not, but if it happens again, I will start looking for an alternative there. After the server came up and I was able to ensure that the issue was resolved at least for the time being, I backed up my flash drive and upgraded to the newest version of unRAID. This was the plan before I started getting the errors. So far, so good. Thanks for the assistance, @Squid! 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.