deltaexray Posted March 9, 2021 Share Posted March 9, 2021 I found it. Let's see if it works Quote Link to comment
deltaexray Posted March 9, 2021 Share Posted March 9, 2021 So update: Moved back to v6.8, same Issue. Even the same error in the log Quote Link to comment
JorgeB Posted March 9, 2021 Share Posted March 9, 2021 5 minutes ago, deltaexray said: So update: Moved back to v6.8, same Issue You need to re-sync parity, just downgrading won't fix anything. Quote Link to comment
deltaexray Posted March 9, 2021 Share Posted March 9, 2021 So a complete parity check should fix it and bring it bake to normal? Yeah I was kinda expecting that, I just wasn't sure if a parity check would make it better or worse Quote Link to comment
JorgeB Posted March 9, 2021 Share Posted March 9, 2021 Just now, deltaexray said: So a complete parity check should fix it and bring it bake to normal? No. 2 minutes ago, JorgeB said: You need to re-sync parity Stop the array, unassign parity, start array, stop array, re-assign parity, start array to begin parity sync. Quote Link to comment
deltaexray Posted March 9, 2021 Share Posted March 9, 2021 (edited) And what's with the data on the other 2 drives? It makes sense to me that you have to do something like that but If I lose some data it's .. bad. Edit: parity sync is doing it's job, we'll see when it's done. So for now, a big Thank you Edited March 9, 2021 by deltaexray Quote Link to comment
deltaexray Posted March 10, 2021 Share Posted March 10, 2021 Quick update: Everything's back to normal, without any issues:) 1 Quote Link to comment
KeithAbbott Posted March 13, 2021 Author Share Posted March 13, 2021 On 3/8/2021 at 7:34 PM, KeithAbbott said: With the new LSI 9207-8i controller, comes a new question. I think the firmware version is 18.xx.xx.xx, so I am thinking that I should be upgrading the firmware to 20.00.07.00. I am running it in IT mode, and from researching on this forum, it looks like I should probably remove/erase the BIOS, which would speed up the boot process a bit. In summary, upgrade the firmware and remove the BIOS. Any cautions against doing that? Any guidance either for or against? So my weekend project for today was to upgrade the firmware and remove the BIOS on my LSI 9207-81 controller card. Upgrading the firmware was easy-peasy; however, removing the BIOS was a bit more of a challenge. I had to try multiple workstations, and finally found an old non-UEFI machine that allowed me to boot into FreeDOS and run the sas2flsh command. Glad that's done... Quote Link to comment
craigr Posted March 14, 2021 Share Posted March 14, 2021 3 hours ago, KeithAbbott said: So my weekend project for today was to upgrade the firmware and remove the BIOS on my LSI 9207-81 controller card. Upgrading the firmware was easy-peasy; however, removing the BIOS was a bit more of a challenge. I had to try multiple workstations, and finally found an old non-UEFI machine that allowed me to boot into FreeDOS and run the sas2flsh command. Glad that's done... Yeah, that's the trouble, you need a desktop that predates UEFI to use sas2flsh.exe, or a motherboard that uses a very early version of EUFI that will work with sas2flash.efi. My 12 year old desktop now runs Chromium OS for my son's 1st grade at home learning. Many evenings after he's asleep I have gone in there and flashed LSI cards with a DOS flash drive 😅. Two servers ago I ran a E3-1285v4 with a SuperMicro board and that UEFI worked with sas2flash.efi. I was shocked after I upgraded and sas2flash.efi didn't work anymore. craigr Quote Link to comment
KeithAbbott Posted April 7, 2021 Author Share Posted April 7, 2021 Today was my first monthly parity check since I replaced my SAS2LP with an LSI 9207-8i. Success! Zero parity errors! Now, time to upgrade to 6.9.1... 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.