Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Michael_P

Members

Everything posted by Michael_P

  1. both of these? raw.githubusercontent.com githubusercontent.com
  2. Sure, you can spin up a Windows VM using your OS SSD, attach your SSD and RAID pool disks to the VM then transfer over the virtual network interface to Unraid's pool. Little fiddly but totally doable
  3. I didn't say anything about using unraid to host it
  4. Are you exceeding its capacity?
  5. Just make sure it's less than the amount you have free
  6. 32GB, limited Plex to 4GB - can confirm that works and the scheduled task no longer runs the server OOM.
  7. That's what's running you OOM. Mine started doing it after upgrading from 6.8.3 to 6.10.3, haven't figured out why yet, likely doesn't like a media file for some reason when it generates thumbs and runs away. Doesn't do it if you change all of these to never You can change it to whatever you want when you add media, just make sure to disable them again before the scheduled task. I set a memory limit based on @Squid's suggestion above, going to test tonight to see if it runs away again.
  8. In HA, the modem should only see the virtual interface
  9. What time is your Plex scheduled tasks set to run?
  10. 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
  11. 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.
  12. 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).
  13. 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
  14. Just do one at a time if uptime is your primary goal, "protection" would be just limited to 1 disk failure
  15. Are you running a pihole or pfblockerng on your network for DNS?
  16. If the system is sending corrupted data, the age of the SSDs is irrelevant
  17. If bad memory is corrupting your data, changing file systems won't stop the corruption - it'll just stop telling you about it.
  18. 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
  19. 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
  20. 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.
  21. *if the drive reports the error
  22. It'll look like this, then you can match the serial# to the disk #:
  23. 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.
  24. 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.
  25. 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)

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.