KeithAbbott

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

1 Neutral

About KeithAbbott

  • Rank
    Newbie

Converted

  • Gender
    Undisclosed
  1. Mine is behaving the same way, using Firefox.
  2. 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...
  3. 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...
  4. Thanks much for the reply, looks like I found my weekend project. I do have a spare Windows 10 workstation that I will use, instead of my server. That way, I'm not messing with my "production" box, and I can then erase the BIOS also. Thanks for providing the link, that gave me exactly what I need. Oh, one other question. Is it best practice to run the monthly parity check with the setting to not write corrections to the parity disk?
  5. OK, thanks. I've reran the parity check once again, this time with the setting to write corrections to the parity disk. My next scheduled parity check is in early April, so I'll know then whether the new controller has solved the problem or not. 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 bi
  6. I have replaced my SAS2LP with an LSI 9207-8i. I reran the parity check, this time without the setting to write corrections to the parity disk. It is still finding the same five errors as before. If I rerun parity check again (except this time writing corrections to the parity disk), will it make the corrections and then behave properly (no errors) thereafter? Mar 6 23:06:21 SageTV kernel: mdcmd (42): check nocorrect Mar 6 23:06:21 SageTV kernel: md: recovery thread: check P ... Mar 7 00:48:05 SageTV kernel: md: recovery thread: P incorrect, sector=23530044
  7. I've rerun the parity check after rebooting, and attached the resulting diagnostics ZIP file. Here's the relevant snippet from the syslog: Feb 2 01:30:01 SageTV kernel: mdcmd (42): check Feb 2 01:30:01 SageTV kernel: md: recovery thread: check P ... Feb 2 03:12:23 SageTV kernel: md: recovery thread: P corrected, sector=2353004440 Feb 2 03:12:23 SageTV kernel: md: recovery thread: P corrected, sector=2353004448 Feb 2 03:12:23 SageTV kernel: md: recovery thread: P corrected, sector=2353004456 Feb 2 03:12:23 SageTV kernel: md: recovery thread: P corrected, sector=2353
  8. No, I had not. I will reboot and rerun the parity check, and post the results.
  9. Well, I ran another parity check overnight, and wouldn't you know this one came back with zero errors. First time in probably over a year. My next scheduled parity check is a week from today, I'll see how that one goes and post the results. In the meantime, I'm looking at replacing my SAS2LP with an LSI 9207-8i. Good choice? Anything I should be aware of? Anything I need to do besides unplugging the SAS2LP and plugging the 9207-8i in?
  10. New diagnostics ZIP file attached, this one was created after a parity check was completed, but before any system reboot occurred. Thanks for the info about the SAS2LP, looks like I will be shopping for an LSI controller card. Although I would still like someone to take a look at my diagnostics file and confirm whether that was the root cause or not. sagetv-diagnostics-20210125-1946.zip
  11. Thanks for the quick response. My monthly parity check has had "Write corrections to parity disk" set to "Yes" ever since I first set it up. I will rerun the parity check tonight and repost the diagnostics ZIP file, maybe that will give a better clue as to what is happening. My parity check takes 19 hours to run, so I probably will not have anything to post until later tomorrow.
  12. Diagnostics ZIP file attached, as requested. sagetv-diagnostics-20210124-0813.zip
  13. I have unRAID 6.8.3 set up to do a parity check monthly. Every month, it finds 5 errors. It seems likely that the errors are from the parity drive itself. Are there any other options to correct this short of replacing the parity drive? I tried to search this forum for suggestions, but didn't spot anything that matched my situation. If I missed an applicable post, please reply with the link and I'll go from there. Thanks in advance!
  14. I would also like the Inter-Tech 4U 4408, although in the US it is the NORCO RPC-4308.
  15. ZyXEL GS108B 8 Port Gigabit Ethernet Switch with Metal Housing & Green Energy Saving Technology $23.95 with free shipping.