Jump to content

trurl

Moderators
 View Profile  See their activity

  • Posts

    44,363

  • Joined

  • Last visited

  • Days Won

    137

 Content Type 

Everything posted by trurl

  1. trurl
    Do you know what your disk assignments were?
  2. trurl
    The main thing you want to avoid is assigning a data disk to a parity slot, since the data would get overwritten by parity. Assign all disks to data slots and no disks to parity slots, then start the array. Ideally, there should be only 2 disks that show as unmountable. Those are your parity disks. If more than 2 are unmountable it is more complicated. Try that and post a screenshot of Main - Array Devices.
  3. trurl
    OK, just wanted to make sure your weren't still on some version before V5. Did you have cache disk(s)?
  4. trurl
    What version of Unraid were you running before?
  5. trurl
    Do you have a backup of the old flash? All you need to get everything back about your configuration is the config folder from the old flash.
  6. trurl
    169 is a self assigned IP which happens when DHCP fails. Double check all connections, cables, plugs, ports.
  7. trurl
    Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post.
  8. trurl
    Have you done memtest?
  9. trurl
    What do you mean by a "connectivity issue"? The internet is full of bots that automatically seek out systems to attack, and will relentlessly attack any systems they find. If you want to access your server remotely you MUST use a VPN. The WireGuard VPN is built in to Unraid:
  10. trurl
    Do you mean a USB2 flash drive? It is more important to boot from a USB2 PORT.
  11. trurl
    https://wiki.unraid.net/Shrink_array#:~:text=The "Remove Drives Then Rebuild Parity" Method,-For removing one&text=This method does not keep,remaining drives and their contents. Maybe it was this part of step 7:
  12. trurl
    Why and how is your server on the internet? It should be behind your router firewall. Close ports on your router immediately. You also have some problems with disks and with flash drive, but get your server off the internet first then we can work through the other things.
  13. trurl
    In any case you should post your diagnostics from this release if you want help/want to help.
  14. trurl
    Assuming you are running a recent version of Unraid you can download a zipped backup of Flash from Main - Boot Device - Flash - Flash Backup If you are "set it and forget it " make sure you have Notifications setup to email you.
  15. trurl
    It has no way to know so a correcting parity check always corrects parity. What do you mean by this? Only a reboot after an unclean shutdown will trigger a (noncorrecting) parity check.
  16. trurl
    Better yet keep a current backup of Flash. Then not only will you have your drive assignments but also all the other configurations from the webUI.
  17. trurl
    There's a link to the release thread just a few posts above.
  18. trurl
    Running it from the webUI on encrypted drives should still do the correct thing; i.e., -L is usually necessary, since the log can't be used if the disk is unmountable.
  19. trurl

    xfs_repair typo

    trurl commented on Mizerka's report in Stable Releases

    Changed Status to Closed
  20. trurl
    What did it actually say? The -n (nomodify) flag means check but don't repair anything.
  21. trurl
    What version of Unraid are you running?
  22. trurl
    Also, see this section on that same wiki page: https://wiki.unraid.net/Check_Disk_Filesystems#Drive_names_and_symbols
  23. trurl
    You have to stop the array, then start it in maintenance mode, to run repair. https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui If you already repaired the sdX1 partition using the command line, then you have already invalidated parity. A correcting parity check would be needed in this case.
  24. trurl
    No. User share settings only affect writing new files. Existing files will not be moved, and the share includes all disks for reading.
  25. trurl
    You can't repair the sdX device, and you shouldn't repair the sdX1 partition of a disk in the array, or you will invalidate parity. You must run it on the md# device. If you do it from the webUI then it will do it correctly.
×
×
  • Create New...