Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,735

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Check the System/IPMI Event Viewer, there should be more info there.
  2. JorgeB
    Drive isn't generating any read errors so far, and if it does parity2 will kick in, when the rebuild is done you can replace it.
  3. JorgeB
    As you prefer, results will be the same, but it's easier if you let it finish so you can just use that disk alone, and mount the array without it if needed.
  4. JorgeB
    There are ATA errors in multiple devices, could be a controller issue, use all the onboard SATA ports and then try again ideally with a different controller for the remaining two devices.
  5. JorgeB
    Without the diags it's more difficult to guess, but with dual parity I would likely continue with the rebuild.
  6. JorgeB
    It would have been much better to see if the emulated disk was fixable before starting to rebuild on top of the old disk, now you don't have the option to use it, and it would probably be fine, current filesystem corruption is fatal, you might be able to recover the data with btrfs restore, 2nd option here, after that you'll need to format the disk.
  7. JorgeB
    I know it happens, can't tell you exactly why as it's beyond my knowledge, likely because an expander is kind of like a switch. It will downgrade the performance of all connected devices, there are a couple of examples of that on the link I posted above.
  8. JorgeB
    Yes, it's a good option, it's listed above, also on the recommended controllers list.
  9. JorgeB
    Most likely, since the Microserver uses molex to SATA, so no 3.3v.
  10. JorgeB
    Enable the syslog server and post that log after a crash.
  11. JorgeB
    If this is true disk should be mostly OK, assuming no other writes to the array, there will always be some writes to parity due to mounting and unmounting the other filesystems, to keep other options open if needed post new diags after trying to mount the affect disk with the UD plugin.
  12. JorgeB
    There are two invalid disks with single parity, so they can't be emulated, you're best option is to do a new config, if the filesystems are still OK they should mount, or at least be fixable.
  13. JorgeB
    Can't really help with command as I don't have SAS drives, maybe google can help.
  14. JorgeB
    Disks are formatted with type2 protection, you need to remove that first:
  15. JorgeB
    It's logged as a disk problem, but these can be intermittent, and since the extended SMART test passed the disk is OK for now, keep monitoring.
  16. JorgeB
    That's the link width, that's OK, what's degraded is the speed, or generation, PCIe 1.0/2.0/3.0, sometimes there's an "Auto" option, it will depend on the BIOS.
  17. JorgeB
    Like mentioned in the release notes you need to re-assign your cache, but IMHO you should try v6.9.1 and the cache will come back if you do.
  18. JorgeB
  19. JorgeB
    You'll need to clear the FCP error, then grabs new diags after it comes up again, without rebooting.
  20. JorgeB
    If no errors are found during memtest run a couple o consecutive parity checks and post new diags, all without rebooting.
  21. JorgeB
    Did you reboot after getting the error? Not seeing any issues so far.
  22. JorgeB
    Is this UD device still mounted?
  23. JorgeB
    Yes, most often is.
  24. JorgeB
    It would, IMHO not much point in creating one for v6.9.2 since it's no longer being developed, but if the issue remains in v6.10-rc2 you should create one in the per-release section.
  25. JorgeB
    Start by running memtest.
×
×
  • Create New...