itimpi

Moderators
  • Posts

    19709
  • Joined

  • Last visited

  • Days Won

    54

Posts posted by itimpi

  1. If you are having problems doing it on the server you can always instead plug the flash drive into a PC/Mac to make a backup as it is in standard FAT32 format.  All you need is the contents of the ‘config’ folder as that contains all your settings and the licence key.

  2. Just now, Shomesomesho said:

    https://old.reddit.com/r/unRAID/comments/1byaqxn/scripts_to_pause_torrents_during_parity/

     

    Seeding torrents from the array slows down parity operation. I'd rather pause the seeding than slow down the parity operation. I don't want to close the torrent client completely, as that stops downloads to the cache. And without pause being recognized as a stop/end, and using the Increments feature of Parity Check Tuning plugin means the torrent docker would remain shut down for days until the parity operation is finished.


    from an earlier request I have been working on an option to pause (rather than stop) user specified  docker containers during parity operations and resume them when an increment ends.   Sounds like that might satisfy this need without the need for a script?

  3. It is not clear to me why you think there would be any files on a drive you have just added?   Have I missed something?    
     

    Normally when you add a new drive to the array Unraid Clears it (I.e. sets it to be all zeroes) to avoid invalidating parity.    When that completes you then format the drive to create an empty file system and make it ready for use.   This is the process documented here for adding drives in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.

  4. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.


  5. Looking at you diagnostics you may have managed to get 2 shares which differ in capitalisation (not certain because of anonymization)

     

    appdata                           shareUseCache="prefer"  # Share exists on cache
    domains                           shareUseCache="prefer"  # Share exists on cache
    E-------------------)             shareUseCache="yes"     # Share exists on disk1, disk2
    isos                              shareUseCache="yes"     # Share exists on disk1, disk2, disk4
    j------------------s              shareUseCache="yes"     # Share does not exist
    N-----------p                     shareUseCache="yes"     # Share exists on disk2
    O----------e                      shareUseCache="yes"     # Share exists on disk1, disk2
    P-------------s                   shareUseCache="yes"     # Share exists on disk1, disk2
    P--X                              shareUseCache="yes"     # Share exists on disk1, disk2, disk4
    S--------m                        shareUseCache="no"      # Share exists on disk2, disk3
    system                            shareUseCache="yes"     # Share exists on disk1
    J------------------s              shareUseCache="no"      # Share exists on cache, disk1, disk2, disk4


    as you can see the one that has files on the cache starts with a capital J and is set to “no” for using cache so gets ignored by mover.

  6. 2 hours ago, icarus69 said:

    Thanks. Whatever the difference between bits and bytes, though, changing to a Cat6 cable incresed the speeds recorded by OpenSpeedTest significantly, so I'm assuming that was the issue.


    If by any chance you have a LAN cable where not all 4 twisted pairs are connecting end-to-end then a 1000Mbps LAN typically silently degrades to 100Mbps.   This can be confusing as no error is indicated and the LAN is operational - just not at the expected speed.   It may be just that the original cable was defective in this way?

  7. 46 minutes ago, MikeyRaa said:

    Upon boot my Unraid box is reporting a checksum error with the bzfirmware file. I have been able to fix on previous versions of the OS by downloading the install files manually, grabbing a copy of the bzfirmware file and replacing it on the OS install USB stick.

     

    However, the manual install files for version 6.12.8 are no longer available online. I anyone able to help with this?

     

    Thanks,

    Mikey 

    The easiest thing would be to download the current 6.12.10 zip file and then copy over all the bz* type files from the zip.    As a side-benefit you will be upgraded to the latest release.  At the moment this seems the most stable release.

  8. 5 minutes ago, boardinace8 said:

    Looking at the config folder it might just be the disk.cfg that I need to copy. Is that correct?

    No.   if you want just the drive assignments it is the super.dat file.

     

    Having said that why not copy everything over?   Avoids you setting everything up from scratch (unless of course you explicitly want to do so).

     

     

     

  9. 17 hours ago, Shomesomesho said:

    Is there a way to modify this script to consider a paused parity operation as stopped/finished?

    What is it you actually want to do if the check is paused?   There may be a better way to achieve this.?

     

    Also what is the Use Case you have for even running a script at start/end?    Just asking as if it is a good one I could consider adding support for this as a standard feature in the Parity Check Tuning plugin.

  10. 2 hours ago, Original_Vecna said:

    Yes. Which is again, why I'm here posting. I believe I already said I checked online and couldn't find anything of use. That little blerb did nothing to help, the "procedure" on that page does not work.

    Fair enough - but you did not say what you had tried.    The procedure I pointed you to worked for me, so not sure why it is not working for you.

  11. 2 hours ago, HomerJ said:

    Then I was thinking that I probably need to install a plugin for it so I found it and installed it. After rebooting again,

    If you are passing through hardware to a VM then any drivers needed are loaded into the VM - not into Unraid.    You need to remove any driver you tried to install at the Unraid level and then reboot the system.

  12. You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog.

     

    your description makes it sound like you may only be getting a 100Mbps connection to your Unraid server despite you thinking it should be 1000Mbps.

  13. The ‘config’ folder on the flash drive contains all your settings (including your licence).    If you copy across the contents of the config folder (except for the licence file) to the flash drive to be used for the new server then all settings are transferred.  To give you a chance to check thing out I would recommend, however, that you disable the Docker and VM services on the current server before copying the config folder so that they are not auto started on the new server.   You may also want to disable array autostart.

     

    Note that Unraid will never automatically format any drive.   This always requires manual action from the user.

  14. Thanks for that feedback.

     

    Given that extra information I was able to recreate the issue and will put a fix into the next release of the plugin.  I need to initialise a variable that the CustomMerge script expects to already have been loaded before it is called.   The error will occur anytime you make a change under Settings->Disk Settings away from the defaults.

    • Like 1
  15. It depends on whether you are prepared to take any risks with the current data.

     

    The simplest and probably quickest way would be to use the New Config tool and via that assign the disks that you want to finish up with removing the surplus drives; start the array;  format the new disks;  and then build parity based on those.    You could then mount each of the drives removed in turn via Unassigned Devices and copy their data back to the array.   This has the risk, though, of one of the removed drives failing before you can copy their data back to the array (thus losing the contents).

     

    Any other approach is going to be more laborious but it should be possible to keep parity protection in place so you are protected against a single drive failure, but it will take longer and put more overall stress on the drives.

  16. The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted.  You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash.  The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field. 

  17. 3 hours ago, YaSo said:

    Is it alright to stop the array in mid 'parity work' and then use the Tuning plugin you mentioned? And do you know if it will do this parity check each time I add a drive?

    You can install the plugin with the check already running.   Not much point in stopping the current check as you would just need to start again from the beginning.   The plugin is not responsible for initiating the operation (which is Unraid’s responsibility), it just adds better management of what happens after it is started.

     

    3 hours ago, YaSo said:

    Also, is it alright to copy data to the data drive while the parity check is running?

    Yes, but it will run much slower than when the check is not running (and also slow down the Check while they are both running) due to contention on the drives.  You should therefore avoid doing large amounts of writes to the data drives while a check/sync is running as doing them separately would end up being faster, but small amounts would be fine.

     

    3 hours ago, YaSo said:

    And do you know if it will do this parity check each time I add a drive?

    When you add a drive, parity is not regenerated.   Instead the drive is Cleared (if not pre-cleared) to avoid it affecting parity.   You can find a discussion of Clear v Preclear here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page. 
     

     

     

     

     

  18. Have you read this section of the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page that covers using WireGuard?  The Unraid OS->Manual section in particular covers most features of the current Unraid release.