February 6Feb 6 This week a parity check was running on my Unraid server and during this suddenly an error was show that the array had read errors. But when I checked the syslog I see it logs that error for a non-existing disk.Feb 5 21:45:57 Firefly kernel: md: disk29 read error, sector=29157647288Feb 5 21:45:57 Firefly kernel: md: disk29 read error, sector=29157647296Feb 5 21:45:57 Firefly kernel: md: disk29 read error, sector=29157647304Feb 5 21:45:57 Firefly kernel: md: disk29 read error, sector=29157647312Is this an error someone has seen before especially with a disk which doesn't exist in my system? Could this due to my HBA going a bit crazy at some time during the parity check? Or maybe some other explanation why this is logged for a disk number not in my system. Edited February 11Feb 11 by Stiibun Issue is solved
February 6Feb 6 Community Expert That will be parity2.You are likely to get better informed feedback if you attach your system’s diagnostics (with everything in the one zip file) to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.
February 6Feb 6 Author Yes it was indeed Parity 2 (/dev/sdh) how gave the error/warning. Seems in the SMART reported it has an elevated value for "Number of Reported Uncorrectable Errors". Hope this disk isn't going bad.First thought it was the Seagate Ironwolf disk (/dev/sdc) as it has some command timeout issues, but these have not gone up for good amount of time.Diagnostics attached here.firefly-diagnostics-20260206-2042.zip Edited February 7Feb 7 by Stiibun fortgot 'not' in '"but these have not gone up for good amount of time."
February 7Feb 7 Author Currently running a SMART extended self-test on that Parity 2 disk, it's at 40% so will take a while to complete.
February 7Feb 7 Community Expert It's logged as a disk problem on the syslog; let the SMART test complete.
February 8Feb 8 Author New diagnostics and SMART report for the disk in question. The "Read Recovery Attempts" didn't raise since last check, but the "Number of Hardware Resets" raise with 1 from 16 to 17 since Friday, should I be concerned about this and what could cause this?firefly-smart-20260208-1556.zipfirefly-diagnostics-20260208-1556.zip
February 9Feb 9 Author Yes it did show as completed and the server went to sleep last night which it did not the previous night when the SMART test was still running.
February 9Feb 9 Community Expert SInce there are no results logged, you can run a parity check instead to confirm if the disk is good.
February 9Feb 9 Author Thanks @JorgeB , just started another parity check now. Will take its sweet time, last 3 days. I'll revisit this thread with the results when it's done.Should I worry about the "Number of Hardware Resets" numbers in the SMART report?
February 9Feb 9 Community Expert 2 hours ago, Stiibun said:Should I worry about the "Number of Hardware Resets" numbers in the SMART report?Not really, not very important.
February 11Feb 11 Author @JorgeB , parity check finished without any errors this time. Included diagnostics after it was finished. firefly-diagnostics-20260211-0853.zip
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.