Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,600

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Unsupported partition layout after a format means the disk is not returning the MBR data Unraid expects, same reason why the preclear signature failed, though can't see a reason for why it's happening, do you have another disk you could try with?
  2. JorgeB
    This is a way, but basically you just need to copy everything important to the array or another disk before formatting.
  3. JorgeB
    Try rebooting.
  4. JorgeB
    Mover won't move existing files, and if files exist on source and dest you need to manually delete one of them.
  5. JorgeB
    Sync errors are expected because of the previous data corruption, if the ATA errors were solved you should run a correcting check.
  6. JorgeB
    There have been multiple hacked users in the last week or so, flash and all array data was deleted, did you have any forwarded ports from the router to your server? Or using dmz?
  7. JorgeB
    Rebooting should fix that, make sure you don't have multiple browser windows open on the GUI.
  8. JorgeB
    Looks more like a connection/power problem, replace both cables on that disk and try again.
  9. JorgeB
    Post new diags.
  10. JorgeB
    Pool filesystem is corrupt, best bet is to backup and re-format it.
  11. JorgeB
    Swap cables/slots between those disks and see where the problem follows.
  12. JorgeB
    Because of the new partition layout for non rotational devices, partitions will always be small than disks, even if they have the same original blocks, so you can never have a same capacity SSD parity with disk(s) as array device(s). It's not better supported as parity, SSDs can't be trimmed when used in the array, either data or parity, you can still used them, many people do, including myself.
  13. JorgeB
    Depends if your board has one or not, you can find more info it with Google, for example: https://superuser.com/questions/1057446/how-do-i-boot-to-uefi-shell
  14. JorgeB
    Should be fine, as long as you are at a point that you can reboot.
  15. JorgeB
    8e means 8 external ports (in this case in adition to the 8 internal ones: 8i). 9300-8i is more than enough, and if you like you can by used server puls for less than $100, look on ebay.
  16. JorgeB
    I never used Plex, go to the router page and check the port forwarding section, remove any forwarded ports to the server.
  17. JorgeB
    You're being hacked, are you forwarding any router ports to the server? Or using dmz?
  18. JorgeB
    It's the same, just need to boot into the UEFI shell instead of DOS and use the UEFI executable.
  19. JorgeB
    Looks like it, you are hacked, like a few users were in the last week, make sure no ports are open to your server, or it's in the dmz.
  20. JorgeB
    Not much you can try with m.2 devices, try a different one if available, ideally a different model, BIOS update might also help, though kind of a long shot.
  21. JorgeB
  22. JorgeB
    Swapping just a disk likely won't change anything, but if for example you added two new disks it might not be an issue anymore. It is strange that before there was the error but it wasn't causing any issues, and it did with new controller, maybe because the IDs changed order.
  23. JorgeB
    Sere here for a more detailed explanation of why this can happen with an odd number of array devices: https://forums.unraid.net/topic/33348-maybe-wrong-spot-butseparate-parity-from-data-drives/?do=findComment&comment=321674
  24. JorgeB
    No, parity2 is calculated in a different way, so that should never happen. This is a very rare situation, it can only happen with an odd number of array devices, but it won't happen every time you have an odd number of devices. If after that you assign it as parity1 it will it will be the same, since it's the parity information calculated from your currents devices that is creating the issue.
  25. JorgeB
    Same thing, because: Because of how parity1 works having an odd number of devices can create a valid (or invalid) file-system in the parity disk, and with btrfs this can cause more issues because it will be detected in the scan:
×
×
  • Create New...