VelcroBP

Members
  • Posts

    211
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

VelcroBP's Achievements

Explorer

Explorer (4/14)

5

Reputation

  1. Does this container stop or prevent qbt from accessing the internet if the VPN fails? For example if the VPN sub expires overnight does qbt lose connection?
  2. I'm worried about the IPMI implications leaning motherboard. but to clarify: i was able to connect via IPMI, and it showed the chassis status as powered on, there was just no video signal via the KVM console (or physical monitor for that matter). Sent from my Pixel 5 using Tapatalk
  3. My server just suddenly went unresponsive. I got the "content unavailable" error suddenly while watching Plex. I was then unable to load the unRaid webUI or access via IPMI KVM console. Pings were also unresponsive at this point. I then plugged in a physical monitor/keyboard to the server. No video output was picked up there either. I then hit the chassis reset button to initiate an unclean reboot. Everything came back up normally and began the parity check as expected (after I manually restarted the array). This is the first instance I've had of this kind of total OS freeze-up. No recent hardware changes. I upgraded from 6.11.0 to 6.11.1 this past week. I've also manually installed Python packages that were missing from NerdPack deprecation. Those are the only software changes I can think of since the 6.11.0 upgrade a few weeks ago. I need to know what logging I can set up to help troubleshoot this if it happens again. Are there any other options I should turn on or configure? Verbose or Trace modes anywhere for hardware monitoring? I have syslog server setup and writing to Kiwi on my Windows PC. I just downloaded an unRaid diagnostic .zip so I'll have a before and after of that also. Is there anything else I can do proactively?
  4. I have a cache pool of 2 SSDs. One is starting to throw reallocated sector count errors about once a week or so. It is up to 4 now. I've attached the SMART report. My questions are: Is this indicative of imminent failure? If so I will have to shrink back down to the single cache drive until I can afford to purchase a replacement. Samsung_SSD_840_PRO_Series_S12PNEAD315804J-20220906-1008.txtIs parity the main/only benefit of a cache pool? I was thinking to replace the failing drive with a 512gb one. In that case, I could free up a physical drive slot in my server by just replacing the remaining SSD instead of adding the new and creating another pool. I don't really need the extra slot. I currently pre-clear new HDDs via a usb-SATA adapter and that seems to work fine. But it would be nice to have a warm spare.
  5. I finally bit the bullet and got the nerve to flash my BIOS. It seems to be working as expected now! Thanks so much for going the extra mile and reporting your results back!
  6. Thanks! I have setup a FreeDOS disk using Rufus. I'll hopefully be doing this later today or tomorrow. I should be reporting back this weekend, fingers crossed.
  7. Ok SM emailed got me the 3.0a download. However I don't know which file inside the ZIP is the actual BIOS, to be included in the DOS "Flash.BAT XXXX" command? Which one of these is it? the .C17 or the .SMC ?
  8. That is true, I forgot. The reason I had to rebuild everything the last time was due to changing my entire share structure. I Consolidated all media shares under one top-level share. I also had to redo my *.arr stack at that time. Since I (hopefully) don't have to change any of my paths again I could just migrate my Plex appdata. I'll have to consider it after I've updated BIOS and see how lsio's container works.
  9. My thoughts exactly. I am contacting them to request an evaluation license for SUM so I can update via IPMI, so I'll ask about 3.0a while I'm at it.
  10. I can only find v3.4 at SuperMicro's website for the MBD-X10SLH-F. Is this the version you flashed to?
  11. this is fantastic! Thanks for running this down and reporting back in such detail! I will try to get this going soon. I just completed a lengthy file system conservation on my data drives (reiser -> xfs) and am currently running down a few lingering issues. Once I'm confident that dust has settled I'll look at upgrading my server bios and trying your settings. I'm going to stick with the lsio container, simply because I don't want to rebuild my entire Plex library setup again, or reset my played status for my users. Sent from my Pixel 5 using Tapatalk
  12. CPU load is coming back down since mover stopped trying to use Disk 2. what is "re-health"? Also: I'm not sure what you're asking about normal usage?
  13. what would be causing that? Is it related to the mover job being hung up by the slow HDD? Do i have too many containers running for my system to handle, regardless of mover? Sent from my Pixel 5 using Tapatalk
  14. I did experience super slow transfer speeds with Rsync on this drive during the FS conversion process. IIRC it took almost 2 full days to move just ~5.5tb to it. I chalked it up to it being an SMR, WORM drive. I stopped the mover task and added Disk 2 to the exclusion list for my media share (Data). I mover again and now it seems to be progressing normally. I'm guessing this is a HDD issue and not an unRaid issue? I'll try for an RMA but the HDD in question is shucked from a Seagate Expansion external I bought in 2018. Maybe I can fill up the drive manually (with several overnight sessions I'm sure) and continue to use it as read-only?
  15. I knew I forgot something. thanks. mootower-diagnostics-20220807-1401.zip