superfans124 Posted March 27, 2023 Share Posted March 27, 2023 unryzend-diagnostics-20230327-0905.zip last week I first upgraded my parity to 18tb disk, that went without a hitch, completed with no errors and warnings. then I tried to upgrade disk 7, from 8tb to a brand new 14tb (already stress tested) and half way thru, all kinds of errors started popping out (reading errors?). and this is my 2nd attempt, it already happened once over the weekend, I tried shutting it down and checked all cables and started over, but apparently this is more complicated than I can handle on my own. thanks. Quote Link to comment
Solution JorgeB Posted March 27, 2023 Solution Share Posted March 27, 2023 Problem with the onboard SATA controller, this used to be be fairly common with Ryzen boards and v6.9/v6.10, much less common with v6.11, possibly because of the newer kernel, look for a BIOS update and/or try v6.12-rc2, failing that best bet would be to use an add-on controller instead. 1 Quote Link to comment
superfans124 Posted March 27, 2023 Author Share Posted March 27, 2023 thank you 1 Quote Link to comment
superfans124 Posted March 29, 2023 Author Share Posted March 29, 2023 On 3/27/2023 at 9:43 AM, JorgeB said: Problem with the onboard SATA controller, this used to be be fairly common with Ryzen boards and v6.9/v6.10, much less common with v6.11, possibly because of the newer kernel, look for a BIOS update and/or try v6.12-rc2, failing that best bet would be to use an add-on controller instead. hi, sorry, can I trouble you again? so I checked the cables and upgraded bios, rebuild went smoothly for about 70% before I went to sleep, system crashed when I got up in the morning requiring hard reboot, once logged in notified me rebuild failed with tons of errors. this is the first diagnostics I pulled before starting the array, but after reboot... all the disks with errors are connected directly to the onboard sata ports, but I'm bit perplexed why the initial parity rebuild went thru without any trouble, but a new data disk a day later is giving me all this hassel. unryzend-diagnostics-20230329-0916.zip Quote Link to comment
JorgeB Posted March 29, 2023 Share Posted March 29, 2023 Since it's a after a reboot cannot see what happened, but most likely the same thing, you can try updating to v6.12 like mentioned. 1 Quote Link to comment
superfans124 Posted April 1, 2023 Author Share Posted April 1, 2023 On 3/29/2023 at 10:10 AM, JorgeB said: Since it's a after a reboot cannot see what happened, but most likely the same thing, you can try updating to v6.12 like mentioned. v6.12rc2 did the trick, thank you! so relieved I don't have to scramble for hardware solutions. 1 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.