Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,485

  • Joined

  • Last visited

  • Days Won

    706

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Yes, everything will be deleted, all data, all partitions.
  2. JorgeB
    For now yes. Yes, would be good to compare if the errors are in the same sectors or not.
  3. JorgeB
    Some Marvell controllers have issues with IOMMU enable, especially the 9230 like you're using, this works for some but Marvell controllers in general are recommended for Unraid v6.
  4. JorgeB
    Please run two consecutive checks without rebooting (so we can compare the errors) and post the complete diagnostics: Settings -> Diagnostics
  5. JorgeB
    Whatever you prefer, reconstruct write is faster at the expense of all disks spinning up for writes, more info here.
  6. JorgeB
    Some Marvell controllers, especially the 9230 which you're using has known issues with iommu enable, this works for some. It's still enable on the diags posted.
  7. JorgeB
    The device added to the pool will be added automatically and the pool converted to raid1, this is default behavior for a 2 device pool, after the balance finishes you can convert to raid0.
  8. JorgeB
    Changed Status to Retest
  9. JorgeB
    Same for me, this also strongly suggest beta24 wasn't your problem: If you still have issues please post the diagnostics after upgrading: Tools -> Diagnostics
  10. JorgeB
    That one is probably for when the drives are using a sector other than 512B, which happens when people get drives used on netapp and similar enclosures, but I don't have any SAS devices so not familiar with those commands.
  11. JorgeB
    You need to use the mdX device: https://forums.lime-technology.com/topic/61614-shrink-array-question/?tab=comments#comment-606335
  12. JorgeB
    If you can have both devices connected at the same time you can do an online replacement, see the notes about single device "pool".
  13. JorgeB
    Both disks getting disabled at the same time suggests a connection/controller issue, I would start by upgrading the firmware on both HBAs, especially the second one which is very old, and it's where both disabled disks are connected, both disabled disks likely also share a miniSAS cable, so you can also swap/replace that to rule it out, after that and since disk9 is mounting correctly you can rebuild on top and re-sync parity, you can do both at the same time, if it happens again it would be important top see the syslog.
  14. JorgeB
    It will use the existing pool as is, as long as all members are assigned after the new config.
  15. JorgeB
    Good, it can takes a few minutes after enabling for the share to appear.
  16. JorgeB
    The toggle is for unassigned devices:
  17. JorgeB
    It will only appear over SMB if the share toggle is set to enable.
  18. JorgeB
    Correct, didn't remember. Stop array, unassign parity disk, start/stop array, re-assign parity, start array to begin parity sync.
  19. JorgeB
    Just power back on and it should start rebuild the data disk (from the beginning), if it doesn't or if there is any unmountable disk please post diagnostics.
  20. JorgeB
    That noise doesn't look normal, at least I have an 8TB Ironwolf and it doesn't make that.
  21. JorgeB
    Once a drive gets disable it needs to be rebuilt, on top of the old disk or to a new one, just check that the emulated disk is mounting correctly and contents look OK before rebuilding on top.
  22. JorgeB
    Ask Broadcom to check the serial number, they're happy to do it.
  23. JorgeB
    Also a flash related error, try a different flash drive.
  24. JorgeB
    Adding new hardware usually changes the IDs of some of the existing one, so any passedthrough device might need adjustment to the new ID.
  25. JorgeB
    Still ATA errors, make sure it's not the 3.3v SATA pin issue, you can google that, other than that try a different port/controller.
×
×
  • Create New...