Jump to content

itimpi

Moderators
  • Posts

    20,701
  • Joined

  • Last visited

  • Days Won

    56

Everything posted by itimpi

  1. How is that drive connected? I do not have personal experience of SAS drives but I think a SAS drive will require different cable type to a SATA drive. FYI: the syslog is included in the diagnostics - no need normally to provide it separately.
  2. itimpi

    VM slow

    You need to leave cores free for Unraid itself to use. At the very least you want to leave core 0 (and any associated hyper-thread companion) not assigned to any VM as Unraid will be using that for its own purposes to support emulation. I would recommend that you allocate dedicated cores from the top and work down. I would also avoid having any cores shared between VMs if you want to avoid interactions.
  3. Basically this just tries to read every sector on your disks to see if they can be read without error.
  4. Do you mean simply honour the switch at the top right of the Main page that already acts as a toggle of this sort for array drives.
  5. Looks like the only thing scheduled to start around then is the CA Backup plug-in scheduled to start at 1:00 am. That should not lead to your problem though unless it is triggering something non-obvious.
  6. You have to have checksums for the data in question. If the file system is btrfs then checksums are built in for that format. For XFS you have to explicitly run a process that generates the checksums. This process needs to run before any corruption can occur. The File Integrity plug-in can help automate building checksums for xfs.
  7. A parity check will confirm that parity calculations are correct for the data sectors stored on the drives. It will not check that the data is not already corrupt.
  8. No idea - what you did is what I have always done and it has always been the correct configuration
  9. I believe that the big problem with copying individual (typically small) files is that it takes MUCH longer than creating a tar file if the files are being copied to the array. I think that the best compromise suggestion I have seen is to create a separate tar file for each folder under appdata.
  10. No, mover will not move data between array drives. I think using the unBalance plug-in is probably the best way to achieve what you want. The alternative would be to manually move data between drives.
  11. Does not seem too relevant to Unraid as the admin user is already running as root so there is never any need to use sudo. Unraid does not have users in the traditional Linux meaning
  12. For the record I am using 20H2 and not encountering SMB issues. All my shares are, though, set to ‘Public’ so not sure if trying to switch to higher security might cause an issue. Also I have no Unraid shares that are mapped to drive letters so no automatic connects from Windows - I use UNC type paths whenever I need to connect to an Unraid share.
  13. That file is generated by the emhttpd daemon, and only Limetech knows exactly what they do to populate it in any particular Unraid release.
  14. What hardware are you using? It is possible 6.8.3 does not have the driver for you NIC.
  15. Are you sure you want these set to “Yes” as with that setting the system will try and move the files to the main array. If you want them to stay on the cache you should use “Prefer”.
  16. Are you sure this is required at the Unraid host level rather than inside a Home Assistant docker container?
  17. i would expect it to be added to the ‘append’ line for whichever boot option(s) you are using.
  18. Maybe some could let you have an image file of a Apfs+ disk to allow you to test this format in the future?
  19. Definitely looks like it was due to running out of RAM as the syslog contains: Jan 26 20:57:12 MoparMedia preclear_disk_ZL00BZZE[7656]: Low memory detected, aborting... lots of other memory related messages then started occurring.
  20. No, Unraid never keeps copies of a file in 2 places intentionally. some people have exploited the fact that if a file DOES exist in 2 places then Unraid preferentially finds and uses the copy on the cache. You can then have user supplied scripts that operate a bit like mover to periodically copy the cache copy of the file over-writing the one on the array.
  21. I must admit this does seen to be something unusual Since you say that it also occur when booted into Safe Mode that rules out any plugin being the cause of your issue (which would have been the other obvious potential suspects). Hopefully somebody will spot something in the Diagnostics or come up with another suggestion as to what could cause this.
  22. Having to use the -L option is quite normal. That is mentioned here in the online documentation that can be accessed via the Manual link at the bottom of the unraid GUI.
  23. Just a thought - it is it only the Shares tab in the GUI that is mis-behaving? For instance can you see the shares across the network. If that is the case make sure that you have the Unraid server white-listed in any ad-blocker (or similar) you might have installed in the browser you are using. Ad-blockers have been known to interfere with the Unraid GUI with the Shares tab one of the more frequent victims.
×
×
  • Create New...