SoCold

Members
  • Posts

    29
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

SoCold's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. I just wanted to give a brief update (and hopefully closure) for this thread. I have replaced my SATA power cables and followed the guide on Ironwolf disk errors. Knock on wood I haven't had issues for a bit. I'll put all 3 disks in the array soon and that will be a better test but I appreciate the help working through this.
  2. I swapped out my SATA power cables yesterday for all new ones. rebuilt the disabled drive and crossed my fingers. Woke up this morning to a notification for disk read errors. The drive is still enabled but I made it less than 24hrs with the drive in service. I can see the errors in the log but I don't seen anything else suspicious around that time. It did happen right at 2am but I don't think I have anything scheduled for them so maybe just a coincidence. Diagnostics attached. elliot-diagnostics-20211004-0835.zip
  3. Ok, I can check my power cables and may just preemptively replace them. Should I still be concerned with the controller? Is my MOBO the core issue here and I’m going to keep running into issues until I replace that?
  4. By controller problem would that be the HBA I just installed? My previous issues were with my onboard SATA but I went with the LSI to avoid using the onboard SATA controller all together. I have a spare drive in there so I’m good with running any extended test I need to.
  5. I do, my phone went off immediately. I get messaged via telegram and love that feature. I hadn’t gone back and put eyes on fox common problems since I rebuilt the disc after installing the HBA.
  6. I'm starting to pull my hair out here. I went to check fix common problems this evening to see how things were looking and I got a disc error. elliot-diagnostics-20210915-1856.zip
  7. I tried again today in safe mode and was able to complete the firmware update and confirm the new revision. Everything followed your guide, same card, same revisions so thank you for that. In theory now I should be able to connect the optical drive to the HBA and everything “should” be good? I’m still getting up to speed on HBAs and I want to make sure I’m not doing anything incorrect or that will never work. What I’ve found so far on supported devices for the 9300-8i isn’t the clearest.
  8. I went ahead and got an LSI 9300-8i to have a little extra room for future expansion. I installed the card yesterday was able to get all 5 drives detected but not the optical. This morning I woke up to disc errors again. I planned to follow your guide and upgrade the firmware, everything seemed to work but when I check it I still see the old rev number. Firmware always shows "16.00.01.00" even after flashing. I'm thinking of disconnect all of my discs and reconnecting them via MOBO SATA and then flashing the card with nothing connected to it? elliot-diagnostics-20210913-1337.zip
  9. Hi Jorge, I think you've helped me out in the past so thank you again! The add-on controller is definitely going to be the way to go for me at this point if my issue is the onboard SATA controller again. I don't want to get off topic but I have a few questions if you don't mind me posting them here. -Currently I'm using 6 SATA ports on my MOBO, 1 optical, 2 SSD (cache) and 3 HDD. Should I be looking to move all SATA devices to the add-on controller or just HDDs? -I've looked at the Unraid Hardware Compatibility doc quick and newegg but any recommendations on where to start researching SATA and or SAS controllers? I'm not looking for anyone else to do the work for me just any head start is appreciated. Thanks
  10. Diagnostics attached for reference. I've had some disk issues in the past that I've posted about and the answer has been to update the MOBO and keep Unraid up to date. It looks like there's a recent BIOS update for the board so I can do that but I wanted to post the diagnostics before that. Fix Common Problems Errors elliot-diagnostics-20210908-0944.zip
  11. Looks like they updated, just had to reinstall last night and it works again now Thanks for pointing me to that
  12. I've been running pi-hole for years mostly issue free but yesterday it died on me. I've had some recent disk errors that were traced back to SATA controller issues and hopefully were resolved with the last beta but this seems to be something new. Whenever I start the docker I get the following in the log and then it just keeps restarting. I've tried removing the docker and starting over but no luck so far and a google search has only turned up people having OS issues on raspbian when running on a pi. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole [✗] Aborting installation: iproute2 and iproute packages were not found in APT repository. [cont-init.d] 20-start.sh: exited 1. [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting.
  13. I feel like I'm missing something obvious but I'm stuck at the moment with Hashed Keys for UHD discs. I used to go to https://www.makemkv.com/forum/viewtopic.php?f=12&t=16959 and download the latest file and I was good to go. It's been a while since I have but now it looks like there is no file to manually download anymore but rather "MakeMKV automatically downloads the latest hash key file as needed, provided you have "contact the web server" enabled in your preferences" I don't see that option anywhere and searching seems to just lead to the same "My beta key stopped working" question asked a few hundred times. Hopefully it's something simple and I doubt I'm the first person to run into this. Thanks
  14. Knock on wood but I think I'm good now. Rebuild completed with no errors and disk is enabled again. Thanks for the help!
  15. Thank you Jorge, I just started a rebuild, fingers crossed (again)