servidude

Members
  • Content Count

    59
  • Joined

  • Last visited

Community Reputation

2 Neutral

About servidude

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Look at @HyperV's post above: The problem is that the format changed slightly in the docker repository, v.6.9.2 has adjusted to it, but if you are using older versions you will have to manually fix the file (and keep the bit in the go file).
  2. What @Ford Prefect said! I too am still using 6.8.3 (still waiting for another point release or two before moving to 6.9) and very grateful to you all for your help with fixing this issue.
  3. Thanks, I'm using Firefox where it's Tools | Browser Tools | Web Developer Tools, then click on Console.
  4. Same issue here. unRAID 6.8.3 with v5.6.3 of the plugin.
  5. I'm seeing similar notifications about 3 supposedly corrupted files, but no names! BLAKE2 hash key mismatch, is corrupted BLAKE2 hash key mismatch, is corrupted BLAKE2 hash key mismatch, is corrupted The corresponding syslog entries are also missing file info, for example: Feb 28 18:17:44 Tower bunker: error: BLAKE2 hash key mismatch, is corrupted What is the cause of this (apparently I'm not the only one seeing it), and how can I fix it - is there a way to reset the file hashes?
  6. Thanks for your thoughts on this. I've tried, somewhat naively, to time a file copy from /mnt/diskX to /mnt/diskY (and /mnt/diskZ) and compare the results. They weren't particularly illuminating (nor consistent). If I understand this correctly, the write speed would be affected by where on the drive's platter the data is being deposited, which is usually something beyond the user's control. Is my assumption correct?
  7. OK then, thanks for clearing that up. What would you suggest as a better way for testing read/write speeds of individual drives?
  8. Thanks, @jbartlett, for the WIP updates! I've been using your excellent docker for some time now and have a couple of questions: Would you expect these speed tests to show up any difference in file system performance? I'm trying to see if I can measure a quantifiable difference between my XFS and BTRFS formatted drives (the graphs don't show anything obvious). Any possibility or plans to measure write (not just read) speeds? Thanks again, and happy holidays!
  9. I'm trying to run some disk benchmarks to compare two identical drives in the array, one running XFS the other BTRFS. The DiskSpeed docker doesn't appear to give me the results I'm looking for. So instead I am running fio from the command line (it's in Nerd Pack), with the settings listed here: fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --bs=4k --iodepth=64 --readwrite=randrw --rwmixread=75 --size=4G --filename=/mnt/disk1/test/testfile I notice the parity drive is active during this test - why is that? I thought writes to /mnt/diskX (as opposed to /mn
  10. I think I discovered a typo in this excellent plugin, the tool tip for the CPU temperature is missing an "s": How to reproduce: hover over the CPU temperature in the footer. It will say "Procesor" instead of "Processor". Can anyone confirm?
  11. This is a nice plugin @dmacias thank you! I just tried setting it up on my ASRock E3C236D2I and think I got fan control working.... kind of. Couple of questions: my FRNT_FAN1 has a max RPM of 1500, but your plugin keeps detecting it as 3000 or 2900 RPM. Is there a way to tweak this? my REAR_FAN1 is not detected when I hit the "Configure" button, even though its RPM can be read out. Am I correct in assuming this is because it's a non-PWM fan? lastly, do I need to switch off any kind of "smart" fan control in the BIOS for this to work? Thanks in advance, and onc
  12. Thank you for this @itimpi! So the final step would then be, copy the data back to the new drive (with its new files system)?
  13. Is this possible/sensible? I currently have all my array drives set to BTRFS for the extra features like scrub (which I use) and snapshot (which I don't), but I'd like to try XFS on at least some of the drives, since it's supposedly quite a bit faster. Do I need to use the standard procedure for file system conversion here, or can I get by with just moving the data to another drive, reformatting the now empty drive with XFS, and then.....? Do I need to rebuild parity, or create a new config, or...? Thanks for any pointers.
  14. The version of the container, i.e. the same version I would add to a docker pull command. Asking since I want to know which version to reinstall if my update breaks things. Thanks!