Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,737

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    If it's still unmountable you just need to click on format, next to array start/stop button.
  2. JorgeB
    Please post the diagnostics.
  3. JorgeB
    Starting the array in normal mode.
  4. JorgeB
    There a discussion about that in many topics, e.g.: https://forums.unraid.net/bug-reports/stable-releases/slow-smb-performance-r566/?do=findComment&comment=8514
  5. JorgeB
    Not really surprised since that usually helps when none of the disks are detected, Marvell and Linux just don't go together.
  6. JorgeB
    Yep.
  7. JorgeB
    Yes, and these are automatic, just need to click on it.
  8. JorgeB
    Parity swap only works to replace a disabled disk with old parity, not to add a new data disk, first replace parity, once that's done add the old parity as data.
  9. JorgeB
    It uses a Marvell controller, they are not recommended for Unraid, you can try this to see if it helps: https://forums.unraid.net/bug-reports/stable-releases/disks-missing-after-upgrading-to-670-r536/?do=findComment&comment=4583
  10. JorgeB
    Syslog in the diags starts over after every reboot, if the crashing gets worse enable the syslog server and post that after a crash.
  11. JorgeB
    Check filesystem on that disk, primary superblock could be gone but it might find a backup one, as long as just the first few sectors were wiped.
  12. JorgeB
    Disks are dropping offline, this is usually a power/connection problem, try swapping slots/cables with different disks and see if the issues follows the disks or not.
  13. JorgeB
    Diags are before array start with the emulated disk, so can't see if a valid filesystem was detected, try checking filesystem on that disk and/or post new diags, I mentioned rebuilding only if the emulated disk was mounting, not much point in rebuilding if the filesystem can't be fixed.
  14. JorgeB
    Still likely the reason for the problem, depending on what/how much of the partitions was damaged data might still be recoverable, you can try this, assuming parity is still valid: -Stop the array -Unassign one of the data disks -Start the array -Post new diags Unraid will recreate the partition, depending on what is missing/damaged on the other disks it might work or not, if the emulated disk mounts and contents look correct you can just rebuild the disk, then repeat for the other ones, one at a time.
  15. JorgeB
    The false pending sector issue? That's not file system related.
  16. JorgeB
    Seems to be a common issue, some/most times it goes way after a couple of power cycles.
  17. JorgeB
    Backplane appears to use regular SFF-8087, so you just need a couple of SFF-8087 to SFF8087 cables, or SFF-8643 to SFF-8087 if you go with a SAS3 model.
  18. JorgeB
    It's not
  19. JorgeB
    Recently one user with the same controller found it overwrote the first few sectors of every disk destroying the data after a firmware update, did you make any?
  20. JorgeB
    That's a known issue, user shares always add some overhead, but some users/configs are much more affected than others, direct i/o shouldn't make any difference with recent releases, IMHO best option is still to use disk shares whenever possible.
  21. JorgeB
    Googling the p840 looks like it uses double wide SFF-8087, which is uncommon, first time I've seen those, but if you get for example one of the recommended LSI HBAs you just need to need to get a cable that matches the LSI on one end, regular SFF-8087 (SAS2 models) or SFF-8643 (SAS3 models) and whatever you have on your backplane.
  22. JorgeB
    Not familiar with that one, but we don't recommend RAID controllers for Unraid, only true HBAs.
  23. JorgeB
    If they don't provide a way of doing it using Linux you're limited to Windows.
  24. JorgeB
    Just re-assign it.
  25. JorgeB
    Enable the syslog server and post that after a crash.
×
×
  • Create New...