Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,871

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    You'd need to use the CLI, compression is not yet supported with the GUI.
  2. JorgeB
    It suggests a config problem, you can either redo the flash drive and copy only the bare minium from the old /config folder (key, super.dat and pools folder) and reconfigure the rest of the server or copy that then start restoring the other config files one by one, or a few at a time to see if you find the culprit.
  3. JorgeB
    Yes and yes, set the share to cache=only and select that pool.
  4. JorgeB
    Click on the pool, scroll down to the balance section and choose "convert to raid1c3" then click on "balance"
  5. JorgeB
    It's still looping on deleting the missing device, first time I see this, suggest backing up and re-formatting the pool.
  6. JorgeB
    Yes?
  7. JorgeB
    For now only using the plugin. Yes, that's been possible for a long time.
  8. JorgeB
    We are only talking about disk3, you can copy from UD to the array using your favorite tool.
  9. JorgeB
    Use a new flash drive with a trial license for the new server, once the transfer is done start using the old flash drive, you can copy the /config folder to keep all settings.
  10. JorgeB
    SMART looks fine, most likely a power/SATA cable problem.
  11. JorgeB
    Disk dropped offline, that's why there's no SMART, you should check/replace cables and then post diags, assuming it's v6.
  12. JorgeB
    This shows the network is the problem, iperf only tests network bandwidth, results are not device/share related.
  13. JorgeB
    You can disable the mover logging.
  14. JorgeB
    But since the old disk has a failing now SMART attribute make sure anything important is backed up before formatting the emulated disk, though that attribute usually doesn't affect surface.
  15. JorgeB
    To the array. That's what parity is for, but since the emulated disk had a lot of filesystem corruption it suggests parity wasn't 100% valid. If the data on the old disk looks better you use it instead of the one form the emulated disk, i.e., format the emulate disk, rebuild to the new disk, then copy the data from the old disk.
  16. JorgeB
    That should be safe, unless you need to reconnect the disks to the RAID controller and for some reason it loses the cofing and re-initializes them, but that should not happen, Unraid won't touch the data if you just do a new config, assign all disks to the correct slots and check "parity is already valid" before array start, then if the disks are unmountable due to an invalid partition error post here and I'll post the instructions for something you can try.
  17. JorgeB
    You need to upgrade to latest Unraid release to run a SMART test on a SAS device, or do it manually using the console.
  18. JorgeB
    Mount the old disk with UD and compare the data (array must be stopped or you need to change the XFS UUD first in UD), it should be in a better state, if so best to copy everything from there.
  19. JorgeB
    Parity protected array to array copy will always be slow, since you're are going to rebuild parity you could disable it now so it would move the data much faster, of course array will not be protected once you do that.
  20. JorgeB
    SMART looks OK but all the "Recovered via rewrite in-place" are not a good sign run a long SMART test.
  21. JorgeB
    That will happen if you were using a path not in /mnt/user, /mnt/disk# or /mnt/pool_name
  22. JorgeB
    Start the array in normal mode now, the emulated disk should mount, then check if contents look correct, also check the lost+found folder for any partial/lost files.
  23. JorgeB
    Changed Status to Solved Changed Priority to Other
  24. JorgeB
    No sure what you mean, it should open a filesystem check window, but do it on the console instead, type: xfs_repair -v /dev/md3
  25. JorgeB
    Run it again without -n or nothing will be done.
×
×
  • Create New...