Michael_P

Members
  • Posts

    668
  • Joined

  • Last visited

Everything posted by Michael_P

  1. User name checks out Are all 3 drives on the same controller (Marvell perhaps?). It's unlikely all 3 failed at the same time so you'll need to look for commonalities - controller, connection, power (including distribution to the drives, ie splitters) You didn't include the diagnostics, so there's no SMART reports to look at.
  2. It was still online in some fashion as I could still read the files on the drive, just not write
  3. My cache drive decided to go read only this morning, not sure exactly why. A reboot brought it back online but I'm unsure as to what to diagnose to avoid it happening again. At the moment, I've decided to move everything off of it and re-format it just to be safe. Coincidentally, perhaps, but I've recently updated to 6.12.3 and the system was rock solid on 6.11.1 Diagnostics before and after reboot attached urserver-diagnostics-20230724-0605.zip urserver-diagnostics-20230724-0704.zip
  4. I wouldn't say it was a mistake, but I would absolutely rather have Arc support over ZFS.
  5. I use Nextcloud to sync my mobile devices to the server, UrBackup for the desktops, and rsync for server to server along with a cold grab n go HDD for the can't lose data.
  6. You can* mount it in Windows, just Google it and follow one of the many guides to 'Mount a Linux disk in Windows'
  7. It's the bashing it'll take if you have to rebuild any other drive in the array that would be the killer. My experience with Seagate drives hasn't been good, they typically keel over rather quickly once they start failing. If you don't have your "can't lose" data backed up, now's a good time
  8. Depends on your tolerance for risk - if another drive happens to fail you'll need it and the rest to stay healthy enough to rebuild
  9. They're looking for an outbound VPN to mask downloading Linux ISOs I've had pretty good luck with PIA and binhex's deluge-vpn docker container
  10. If it's a single parity system, personally I'd do a new config if rebuilding on top of the same drive is your only option. Losing another disk during the rebuild would suck twice as much
  11. SMART fail is a drive fail - no point in ignoring SMART, that's its only job
  12. rsync - it won't encrypt the data for you but you can send to an encrypted volume
  13. If it happens at the same time of day, it's probably Plex choking during its scheduled maintenance, limit the memory to the plex docker (advanced view), set as needed for your setup
  14. Depends on if you will need to transcode video to devices that won't be able to direct stream
  15. Your docker image file is stored on your 'docker' share in /mnt/user/docker/ If your docker image file is getting filled, you have a container that's writing to that file instead of a disk share - you need to verify that whatever folders (downloads, temp and such) are configured in your docker containers point to a folder in one of your shares or disks.
  16. It's not x4, it's x2 in x4 clothes. Will you notice a performance difference, depends on if you ever need to do more than 1 or 2 things at once on any of the drives, and more so for drives slung off of the multiplier.
  17. Every time I upgrade/replace a drive, all 24 are used to re-build it - and it already takes over 30 hours
  18. Your board supports up to 64G, you only have 32G installed You have a docker that's writing to the docker image instead of a disk share
  19. This isn't accurate, you can use whatever SATA ports are available