January 15, 20251 yr Hi all, does anyone have a SAS3 expander backplane and use sleep on their server? I am wondering if some drive issues when coming out of sleep are related to compatibility with a SAS3 expander. It seems when I hit the sleep button in the GUI, the systems goes straight to sleep immediately, when I resume from sleep I then see the errors below. I don't have diagnostics for the current setup as I have been swapping hardware in and out, trying to locate the issue. Thoughts Edited January 15, 20251 yr by crowdx42 Edit File
January 15, 20251 yr Author So that is what is causing the error above? Is there a solution? Just don't use sleep? The server seems to be working fine otherwise.
January 15, 20251 yr Community Expert if sleep is triggering it then don't use sleep. I don't have a good answer / solution. This is a theory based on the screenshot of a potential problem. it was a guess... Usually we want sas set to "it mode" initiator target and run drives as a additional attached storage via the SATA interface. Depending on the sas back plain and how that hardware chips and firmware may direct and cause this. As there may be a firmware update for that balckplane... this seems more like the disk went to SLEP in the backplane per settings while something was still trying to access the disk. thus the path was cut off. Many reasons... I would really need a diag file. you may need to setup a syslog server to help capture this in the act to see the before dmesg log. Sometimes unraid can capture this with a previous sylog boot Webui > tools > diagnostic Please post a diag.
January 15, 20251 yr Author The eBay seller has shipped a new backplane, once I get that installed I will try some testing again, most likely this will occur over the weekend. Until then, I will keep the server up or stop the array before shutting it down. I agree that it seems like sleep is initiating before the drives are able to do their sleep process and thus when the drives wake, Unraid does not find the drive correctly and this then sometimes ends in the drive getting the Red X beside it, as Unraid believes the drive dropped off the array before the array stopped.
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.