Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,871

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Looks good for the moment, and now if one device fails pool should continue working, but of course should be fixed ASAP, also see here for better pool monitoring, you'll need to reset the current errors as explained there.
  2. JorgeB
    They will show up the same, assuming it's a compatible PCIe slot.
  3. JorgeB
    LSISAS3224: FWVersion(09.00.100.00) Update the LSI firmware to latest, IIRC it's 16.00.12.
  4. JorgeB
    That's the libvirt image, try restoring it from a backup again, ideally an earlier one if available.
  5. JorgeB
    Yes.
  6. JorgeB
    It's those, *.key, super.dat and the pools folder, all in /config, all devices should be assigned if those files are copied.
  7. JorgeB
    Great, pool is redundant now, type umount /temp and you can start the array, then run a correcting scrub, to do that click on cache and scroll down to the scrub section, when done post the result.
  8. JorgeB
    Google SMART attributes, they are universal.
  9. JorgeB
    And if you do this but restore only the bare minimum, like the key file and super.dat and pools folder for the assignments?
  10. JorgeB
    Good, now type: btrfs balance start -mconvert=raid1 /temp then again btrfs fi usage -T /temp
  11. JorgeB
    Yes, looks like the drives/HBA are not liking the spin ups, log is spammed with the moverlogger, might want to disable that, so reboot and post new diags so I can see the HBA firmware.
  12. JorgeB
    Yes, my bad, first type btrfs balance cancel /temp then btrfs balance start -dusage=50 /temp
  13. JorgeB
    No it's a btrfs allocation issue, try this: -if array autostart is enabled disable it -reboot the server since there was already a btrfs crash -check that the cache device is still sdi, if it changed adjust the command accordingly, then with the array stopped type: mkdir /temp mount -t btrfs -o skip_balance /dev/sdi1 /temp btrfs balance start -dusage=50 /temp If the balance completes successfully, post the output of: btrfs fi usage -T /temp
  14. JorgeB
    If it happens again see if you can at least get the syslog to confirm if it's the same issue: cp /var/log/syslog /boot/syslog.txt
  15. JorgeB
    Click on the thumbs-down and acknowledge.
  16. JorgeB
    Balance is failing and the pool going read-only because there's no unallocated space in one of the devices, easiest way out of this would be to backup and re-format the pool, if for some reason that's not practical I can give step by step instructions to try and fix the current pool, but it's an involved process and it won't work if a device keeps dropping, so you decide.
  17. JorgeB
    Correct.
  18. JorgeB
    Diagnostics saved during a slow period might show something.
  19. JorgeB
    Use the diskspeed docker.
  20. JorgeB
    The main issue was the devices dropping offline.
  21. JorgeB
    Should be OK for now, and there's a recent successful extended SMART test, you can acknowledge the current errors and keep monitoring.
  22. JorgeB
    Trial flash drives are not blacklisted, you can transfer the license to one.
  23. JorgeB
    If they are using the raid1 profile just stop the array, unassign the device you want to remove and start the array.
  24. JorgeB
    Same thing as before, see the bug report to try without some plugins to rule that out.
  25. JorgeB
    Looks good so far, post new diags if the log starts filling up again.
×
×
  • Create New...