Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,826

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It worked for me and I never had the plugin installed.
  2. JorgeB
    Both diags posted don't show a correcting check, assuming you have really done that and the errors return it suggests a problem with a controllers or a disk, controller would be my first guess, very unlikely the Intel controller would cause issues, so I would start with replacing that Asmedia controller with a different model.
  3. JorgeB
    Run a read test with the diskspeed docker to see if all disks are performing normally.
  4. JorgeB
    Enable the syslog server and post that after a crash.
  5. JorgeB
    Not needed, device might have dropped, reboot when you can and try again.
  6. JorgeB
    Looks like the flash drive is not being detected.
  7. JorgeB
    I expected as much, but it was worth trying. It's not a general bug, I and many other users have the same Mellanox NIC and it's detected without any issues, the question is why it's not working for you, maybe @bonienlwill have and idea.
  8. JorgeB
    Backup the licensed key, after the backup is done recreate the flash drive with a new install, copy the /config folder from the trial key to the licensed key, restore only the key from the backup.
  9. JorgeB
    Constant crashing, start by running memtest.
  10. JorgeB
    Most likely, network bandwidth looks good, you can get better speeds transferring to a cache pool with one or more fast flash devices.
  11. JorgeB
    If the error has been consistent I would try to get a replacement.
  12. JorgeB
    Yes, use the last backup and then reconfigure the remaining.
  13. JorgeB
    You can use UD to mount the drive.
  14. JorgeB
    It is, but the same solution was posted in the post above that one.
  15. JorgeB
    Browse /temp with for example midnight commander (mc on the console) and check contents.
  16. JorgeB
    Sdc is part of a different filesystem, should still be able to recover data from the NVMe device using the recovery options here, use the ones that have 'degraded' in the mount options.
  17. JorgeB
    Please post the output of: btrfs fi show
  18. JorgeB
    Type: btrfs-select-super -s 1 /dev/sdc1 Then post new diags.
  19. JorgeB
    That means the pool had another device, which is now missing, do you know/still have that device?
  20. JorgeB
    New diags please.
  21. JorgeB
    It should mount now.
  22. JorgeB
    Type in the console: btrfs-select-super -s 1 /dev/nvme0n1p1 If the command is successful see if it now mounts with UD or after re-assign to a pool, but to a pool without missing devices or it can be wiped (again).
  23. JorgeB
    Cache1 appears to be failing, run an extended SMART test.
  24. JorgeB
    If it happens again to the same disk please post in this thread so we can remember what was done.
  25. JorgeB
    And the GUI is still inaccessible correct? If yes, I'm not seeing anything obvious, try rebooting in safe mode, disable docker/VM services and start the array to see if there's any difference.
×
×
  • Create New...