Michael_P

Members
  • Posts

    395
  • Joined

  • Last visited

Everything posted by Michael_P

  1. Hello, after upgrading from 6.8.3 to 6.10.3 I have been getting OOM errors every night around midnight and the system kills a random process, the first night it was my W10 VM and last night it was Plex. Can anyone shed some light as to why? Memory usage is only in the neighborhood of ~50%. I hate to be "That Guy", but it's been running fine for years under 6.8.3 so I can't imagine what would be causing it to go OOM now. It seems to happen right after sending the nightly status email. urserver-diagnostics-20220622-0505.zip
  2. A good backup routine is a better use of resources. If you were to ever encounter one of these edge of edge case errors, just diff the backup against live data.
  3. In such a scenario, where the parity does not match and produces an error, and you have checksums of your data that match, then there is no error in your data and a "bit flip" in an "empty" portion of the drive would not be an issue. You'd simply rebuild parity as you already know that your data is intact (via the checksum verification).
  4. The drive showing signs of failure isn't new, it's got 44k power on hours, I'd replace it if I were you if it's still needed
  5. Just do one at a time if uptime is your primary goal, "protection" would be just limited to 1 disk failure
  6. Are you running a pihole or pfblockerng on your network for DNS?
  7. If the system is sending corrupted data, the age of the SSDs is irrelevant
  8. If bad memory is corrupting your data, changing file systems won't stop the corruption - it'll just stop telling you about it.
  9. I have that same case, looks pretty much the same too 😆 I've had it for over 20 years now, most recently it was pulling duty as a windows media center pc living in a closet, retired it 2 weeks ago As for your drives, should be able to mount them in any *nix distro if they're still alive
  10. That's not rot, that's an error. URE's would still be logged (in theory) as an error by the drive and can be immediately recognized if monitored by the OS. The theory is that it will pretty much guarantee the death of a normal RAID implementation since drives are well above 12~ TBs now, and read failures during a, for example, RAID 5 array will drop a disk during rebuild and thus the array will be lost. It's only theory tho, as the MTBURE is not set in stone. It's a guess as to the chance, and even then the drive is likely to recover from the error anyway. IMHO, bit rot and URE are WAAAAAAY less important to worry about than just keeping backups of your important data, and verifying your backups
  11. Yes. But unlikely (random cosmic ray blasts a bit on the drive for instance), the drive would still likely report a read error. Data "decaying" in any reasonable amount of time, really unlikely.
  12. It'll look like this, then you can match the serial# to the disk #:
  13. Anything behind your VPN does not require any other paid services to access, you simply connect via a client to your VPN to access anything behind it. Anything you want to access OUTSIDE of your network can be done thru a paid VPN, but the two are mutually exclusive.
  14. What are you trying to use the VPN providers for? If your services are behind your VPN, you just need to access the VPN with your client.
  15. Keep splitters to a minimum if at all possible, and no more than 4 drives per molex connector or you will start to exceed it's current handling capability and the drives will start behaving badly (it's also a fire hazard)
  16. At my age, I don't want to work through anything, i want to crack a beer and press play
  17. Generally, reallocated sectors are a pre-fail indicator. Without any other details, it's impossible to comment on your specific situation, but for me any bad sectors is a drive failure and I replace. All drives are needed to rebuild any other failed drive, so using sketchy drives in the array isn't worth it.
  18. With all of the network gear, and POE cameras, the whole rack runs about $30/month to run 24/7
  19. The problem with sketchy disks in a parity/RAID environment is you still need all of them to work when they're needed most.
  20. For a NAS/media server, I'd say not even a little bit. I'm not an Intel fanboy or anything, but it just works. If you like tinkering or need a crap-ton of I/O, then AMD.
  21. For Plex, Intel as the new iGPUs are all you'll need for transcoding.
  22. Definitely make sure you have your power delivery well thought out, avoid splitters at all costs or you'll start having issues. Sonarr along with Prowlarr. You can set up default quality profiles, and manually change individual shows *cough*linux distros*cough* if needed.