WizADSL Posted May 13, 2021 Share Posted May 13, 2021 (edited) I've seen some forum topics relating to this error but it seems they were for UNRAID versions prior to 6.9.2. I'm seeing what are probably benign (I hope) errors when drives are spun up on UNRAID 6.9.2. I was recently running 6.8.3 and have only started seeing these errors after the upgrade. Nothing whatsoever has changed beyond the UNRAID version. Diagnostics attached. tower-diagnostics-20210513-1220.zip Edited May 13, 2021 by WizADSL Quote Link to comment
arturovf Posted May 13, 2021 Share Posted May 13, 2021 You may correct the title, it says 6.9.3 Quote Link to comment
WizADSL Posted May 19, 2021 Author Share Posted May 19, 2021 One-time bump, has anyone seen this before? Thank you. Quote Link to comment
JorgeB Posted May 19, 2021 Share Posted May 19, 2021 Likely nothing to worry about, but they appear limited to the Seagate 8TB drives, and while it's not the affected model this might still help: Quote Link to comment
WizADSL Posted May 26, 2021 Author Share Posted May 26, 2021 On 5/19/2021 at 12:45 PM, JorgeB said: Likely nothing to worry about, but they appear limited to the Seagate 8TB drives, and while it's not the affected model this might still help: I tried what is suggested in that post and it didn't make a difference. I did notice the if the disk spins up automatically as a result of accessing data on the drive the error does not appear. The error only seems to occur if the drive is explicitly spun up either by the user or when the array does explicitly it such as when you stop the array. 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.