• Posts

  • Joined

  • Last visited

Everything posted by VelcroBP

  1. 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.
  2. 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!
  3. 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.
  4. 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 ?
  5. 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.
  6. 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.
  7. I can only find v3.4 at SuperMicro's website for the MBD-X10SLH-F. Is this the version you flashed to?
  8. 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
  9. 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?
  10. 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
  11. 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?
  12. I knew I forgot something. thanks.
  13. I recently completed file system conversion on all my data disks following the guide from the wiki. All seemingly went well. However, the next scheduled mover task seemed to be hung up (kicked off @ 0130, still running @ 0730). I panicked and stopped mover via CLI. The server would not seem to reboot. I issued POWERDOWN via CLI and it eventually shut down, although uncleanly. After the resulting parity check (0 errors), the next scheduled mover task also seemed frozen. At this point, I launched MC and looked on each Data disk for any duplicates of something on the Cache disk. I found a couple of "***.partial" files that I don't think would be a problem, but deleted anyway because the downloads are not important. After verifying there is nothing on the Cache that's already on an array disk, I invoked mover again. According to the log, it seems to start on the first file and then just sits there. On the main UI page, there appears to be very slow write activity to an array disk, as well as reads on the cache. Below is the NetData for the array disk (which is shingled):
  14. This is fantastic to hear! I will try to mimic your results, but I'm going to stay on lsio Plex container for now. Sent from my Pixel 5 using Tapatalk
  15. So is it no longer supposed to prompt for WAN/LAN ? Mine is not after updating and restarting. Do I need to reconfigure something in the Template?
  16. What is the difference here between selecting LAN or WAN? I must have just updated this container after a while because I don't recall seeing this prompt before.
  17. I agree about the need for a check before a drive replacement and rebuild. unBalance would be after the rebuild. The FS conversion guide on the wiki indicates that the process requires a blank drive, onto which I move the contents from the drive to be converted. It also indicates that I will need to be certain parity is valid during that process. Does replacing a data drive have an impact on parity or is it maintained during the rebuild? If maintained then I'm inclined to proceed with the FS conversion immediately after the rebuild. 1. parity check 2. replace data drive and rebuild from parity 3. move contents off new drive and scatter to other disks in the array (via unBalance) 4. proceed with "mirror procedure" FS conversion process as detailed in the wiki guide 5. parity check FS conversion wiki guide I'm referencing: Sent from my Pixel 5 using Tapatalk
  18. Mine are set to No in the scheduler's "write corrections to parity disk" field. But I'm asking about manual checks in between a drive swap and FS conversion though. Now I'm confused, does the scheduled check's correction setting impact when I should run a manual check? Sent from my Pixel 5 using Tapatalk
  19. I get that. I guess I'm asking how granular do I consider maintenance? I'm inclined to run a check before replacing the drive. but should I then run another after the rebuild and before FS conversion since they're distinct maintenance operations? I'm inclined to lump them together and wait to run a second check until after all the drives are converted. I only ask because the wiki guide stresses a check before conversion and I'm curious if it's risky to consider the one before drive swap/rebuild as valid for that. I know that everyone has different risk tolerance but I wanted to see if I'm overlooking any risks by doing both a drive swap and FS conversions between checks. In my mind nothing will change in the array between the operations so shouldn't it be ok to consider parity valid at that point and begin with unBalance immediately after the drive rebuild completes? Sent from my Pixel 5 using Tapatalk
  20. I have a party check scheduled every 3 months. Currently it's been 77 days since the last one. I'm planning a couple major drive operations and am looking for advice on the best time to manually run a check during. I'm replacing a 2tb data drive with a new 8tb hdd. After the rebuild I will run unBalance to empty the new drive. Finally I will convert my data drives to XFS using the mirror method from the wiki. Should I run a parity check before or after the data drive swap? If before is recommended, can I just run that one or should I do another before starting the conversions? I'm planning on disabling Docker and my appdata backups during the conversion to prevent new data being written to the array. Sent from my Pixel 5 using Tapatalk
  21. Thanks for getting back! I'll dive in to that post and see what I can turn up.
  22. @Hoopster Sorry for the ping but I'm hoping you might have some insight? I can post logs from unRaid or from Plex if needed (though I'm not sure how/if Plex logs need sanitized..?)
  23. I ran this command as recommended in a guide and before are the results -v -s $(lspci | grep VGA | cut -d" " -f 1)lspci 04:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30) (prog-if 00 [VGA controller]) DeviceName: Onboard VGA Subsystem: Super Micro Computer Inc ASPEED Graphics Family Flags: bus master, medium devsel, latency 0, IRQ 11, IOMMU group 10 Memory at f6000000 (32-bit, non-prefetchable) Memory at f7000000 (32-bit, non-prefetchable) I/O ports at d000 Expansion ROM at 000c0000 [virtual] [disabled] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/4 Maskable- 64bit+ Kernel modules: ast supposedly i should be seeing the Intel igu populating here, specifically "i915" as the KENNEL MODULE Sent from my Pixel 5 using Tapatalk