• Posts

  • Joined

  • Last visited

  • Days Won


John_M last won the day on April 19 2021

John_M had the most liked content!


  • Member Title
    Away for much longer than I expected


  • Gender
  • Location

Recent Profile Visitors

4107 profile views

John_M's Achievements


Experienced (11/14)



  1. Unraid 6.10 has built-in support for splitting the scheduled parity check into multiple shorter periods. See Settings -> Scheduler
  2. The first step to diagnosing is to try a different browser. In fact, try as many browsers as you can. Are there any nginx error messages in the server's syslog? Post your diagnostics whenever you make a bug report.
  3. Those plugins shouldn't be a problem if they are all up to date but you can test by booting into safe mode, which ensures that no plugins are loaded.
  4. It's Disk Utility, in the /Applications/Utilities folder.
  5. I looked for documentation about the about the scrub and balance schedulers that were recently introduced for btrfs volumes. What kind of scrub is done on a schedule? Is it a correcting one or a read-only one, given that there's a choice when a scrub is run manually? What kind of balance is done on a schedule? Is it a full one or one based on partially filled extents? Does the presence of the Block group usage parameter imply that it's the latter?
  6. It looks like you have a problem with your "dockers" pool (corrupt 515432): Apr 25 11:52:19 Unraid1 kernel: BTRFS info (device sdm1): bdev /dev/sdm1 errs: wr 0, rd 0, flush 0, corrupt 515432, gen 4
  7. Maybe something in this thread might help:
  8. That looks like a hardware problem to me.
  9. Can you enter the username (it can only be 'root') and password manually? Browsers store username/password combinations against the URL of the page. If you're using https the URL has changed from https://<hash> to https://<local ip address with dashes>.<hash> with this update.
  10. A Samba bug? See here (from page 7 of this thread):
  11. Nov 14 16:23:38 NIKOS-TOWER kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu: finishing device. According to the syslog snippet you posted you are loading the amdgpu driver which will prevent the card being passed through to a VM. Either stop loading the amdgpu driver or, if you need it for another AMD GPU, bind your 5700XT card to the VirtIO driver on the Tools -> System Devices page. As mentioned in the release notes, at the top of this page, which would explain the different behaviour.
  12. My upgrade from 6.9.2 to 6.10.0-rc2 was uneventful, thank you. Shouldn't that say 'Network traffic' instead of 'General Info'?
  13. It looks like you have the Turbo-write plugin installed. I believe it's responding to the spin-ups and spin-downs, rather than causing them, but it might be worth disabling it temporarily just in case.
  14. I'm not sure how I was meant to know that.