This is done by running some Seagate command line utilities (SeaChest) explained by changes we will be making areĭisable Low Current Spinup (not confirmed if this is required) The solution involves making changes to the settings of the Ironwolf disk. I'm far from an expert - I'm just consolidating valuable information scattered - if this is doing more harm than good, or is repeated elsewhere, then close this off. Read through, and only carry anything out if you feel comfortable. Whilst I will list each step I did and it's all possible within Unraid, it's your data. NOTE: Carry out these steps at your own risk. This thread is also here to hopefully provide a central place for those with the same hardware combo to track developments. This thread is here to consolidate the great advice given by others to hopefully make it easier for people to follow. The workaround is reversible, so if an official fix comes along you can revert your settings back. There have been various comments and suggestions over the threads, and it appears that there is a workaround solution. The drive in question is the 8TB Ironwolf ST8000VN004, although 10TB has been mentioned, so it may affect several. It happened to me three times in a week across two of my four affected drives. Getting it back on would require checking, unassigning, reassigning and rebuilding its contents (about 24 hours). Typically when spinning up the drive could drop off the system. People with specific Seagate Ironwolf disks on LSI controllers have been having issues with Unraid 6.9.0 and 6.9.1. NOTE: There's a TL DR section at the end of this post with required steps
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |