Jump to content

John_M

Members
  • Content Count

    3889
  • Joined

  • Last visited

  • Days Won

    10

John_M last won the day on November 29 2018

John_M had the most liked content!

Community Reputation

255 Very Good

About John_M

  • Rank
    Away for much longer than I expected

Converted

  • Gender
    Male
  • Location
    London

Recent Profile Visitors

1719 profile views
  1. Yes, you ideally want to set up a dedicated user (such as "TimeMachine" or "TM" or similar) that has no other purpose than to be the owner of the Time Machine share, rather than use an existing user, so as not to compromise the security of the backups that Time Machine makes.
  2. I'd just schedule it for once a month, making sure it doesn't clash with the parity check. I think checking every file every week is too often, which is why I check a quarter of mine each week (so each file gets checked once every four weeks and I'm simply splitting the load), but YMMV.
  3. Now fixed. Thank you very much.
  4. That's what I do. I don't check all disks every week though. A quarter of them are checked each week.
  5. What does htop show? The threads are probably spending most of their time waiting for I/O.
  6. Uneventful update from 6.8.2. Thank you. The Dynamix File Integrity plugin is still not Unraid 6.8 compatible (it tries and fails to run its scheduled check directly from the boot flash). I know it isn't the fault of this specific release and it has been mentioned in the support thread for that plugin but it still remains broken.
  7. Did it really have a space in the name? Could thst be what's throwing the creator tool?
  8. I'm guessing that you've enabled logging to a remote syslog server, which is unreachable.
  9. I would always run xfs_repair without the -L option first, and only destroy the journal if xfs_repair tells you that there's no other option. You got a corrupt file system and fixed it. It happens occasionally even if you're careful. The best way to try to avoid it happening again is to avoid unclean shutdowns so, if you haven't got one already, consider getting a UPS.
  10. I'm not sure I understand what you are trying to do. Are you trying to follow some procedure to shrink the array (possibly trying not to invalidate parity)? That's the only case where running a script to clear an array drive makes any sense to me. If so, I would abandon that plan and reboot, then do a New Config keeping all previous assignments except the disk you want to remove. Then start the array and let the parity rebuild.
  11. Actually, you don't. The OP's CPU doesn't support VT-d but yours does. You need to enable IOMMU in the BIOS.
  12. Are you saying that you are trying to connect the (local) Mac to the (remote) server via a VPN tunnel? The remote endpoint is provided by the OpenVPN docker. What is providing the local endpoint?
  13. First thing would be to run MemTest from the boot menu for at least 24 hours. When it crashes do error messages appear on the console or does it just freeze?
  14. Consumer grade motherboards tend to need a graphics card if there's no GPU integrated into the processor. I'd suggest getting a cheap, low spec video card just to keep it happy. Even if you don't intend keeping a monitor attached it's very useful to be able to do so temporarily for troubleshooting. You can get something like a Radeon HD 6450 or a GeForce GT 710 for less than $£€40.
  15. First, post your diagnostics (one diagnostic file is worth hundreds of words of description): Tools -> Diagnostics and post the resulting zip file. Second, reboot and choose MemTest from the boot loader and let it run for at least 24 hours.