Jump to content

itimpi

Moderators
 View Profile  See their activity

  • Posts

    20,789

  • Joined

  • Last visited

  • Days Won

    57

 Content Type 

Everything posted by itimpi

  1. itimpi
    If you are new to Unraid what is the rationale for running such an old release as it is quite a few years old now and support for it will be limited? The latest release is the 6.12.6 release.
  2. itimpi
    It depends on how you have the Shares set up. There are the appdata backup and VM Backup plugins for regular backups of docker container data and VM vdisks for shares configured to stay on the cache.
  3. itimpi
    It is reasonably easy to do via the CLI as long as you run the array in Maintenance mode while doing it. It would be nice, though, to have a GUI way of forcing a Clear on the disk so it can be safely removed.
  4. itimpi
    It could have been. Macvlan crashes are known to eventually crash the server on the Unraid 6.12.x releases. We would need the persistent syslog produced by the syslog server so we could see what lead up to the crash to give a more informed view.
  5. itimpi
    No need to use New Config! Stop array; unassign parity drive; start array. If you want to use New Config then it is covered here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.
  6. itimpi
    I think that the Nvidia-Driver plugin replaces this one giving similar functionality and is compatible with the 6.12.x releases.
  7. itimpi
    @toughiv I see this in the syslog: Dec 23 11:39:03 Tower root: Fix Common Problems: Warning: Deprecated plugin Unraid-Nvidia.plg Not sure if it can cause problems or not.
  8. itimpi
    You can rename any of the .plg files in the config folder on the flash drive to have a different extension and then reboot to stop a particular plugin from ,loading.
  9. itimpi
    Using xfs_repair is the correct solution. A rebuild cannot fix an unmountable status.
  10. itimpi
    Do you use Jumbo Frames on the network? This is known to cause issues with some NICs.
  11. itimpi
    The one that corresponds to the IP address of your server.
  12. itimpi
    You can use either that setting, or put the Unraid Server’s address in the Remote Server field.
  13. itimpi
    Did you use the mirror to flash option?
  14. itimpi
    The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to get a log that survives a reboot so we can see what happened prior to the reboot.
  15. itimpi
    Yes. The syslog shows Macvlan related crashes. You therefore need to either switch to ipvlan or disable bridging on eth0 if you want to continue using Macvlan.
  16. itimpi
    You should post your system's diagnostics zip file in your next post in this thread to get more informed feedback. It is always a good idea to post this if your question might involve us seeing how you have things set up or to look at recent logs.
  17. itimpi
    I agree that some improvement could be made to the presentation - even if just to point to the relevant part of the online manual.
  18. itimpi
    you should not have done step 2) as you never do a format as part of a data recovery operation. I think you were formatting the emulated drive rather than the physical one.? This created an empty file system on the emulated drive and updated parity to reflect this. The rebuild process then rebuilt this empty file system as the rebuild process makes a physical drive match the emulated one.
  19. itimpi
    Do you run VMs with hardware pass-through?
  20. itimpi
    I thought you might have - but I was not certain that was what that syslog was so better to make sure. Unfortunately that syslog did not show an obvious reason for a crash.
  21. itimpi
    A preclear is not as important if you are using it as a replacement disk as the rebuild process writes to every sector anyway.
  22. itimpi
    If you have not already done it you should enable the syslog server to get a syslog that survives a reboot.
  23. itimpi
    Not sure I understand the question? I thought the rebuild worked but you made the mistake of running a format which is why you ended up with an empty drive. 1 parity disk handles 1 drive failing, whereas 2 allows for 2 failing.
  24. itimpi
    why did you format the drive? Running xfs_repair without the -n parameter was the correct thing to do to make the drive mountable again with its data intact. Now that you have done the format, it is possible that disk recovery software such as UFS Explorer on Windows can recover the data but it is not certain.
  25. itimpi
    According to the diagnostics you did a format of disk5 which created an empty file system (i.e. wiped its data). A format is never part of recovering a disk with its data intact and you would have got a dialog telling you this when you attempted the format.
×
×
  • Create New...