Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,540

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    It's not being detected, this is a hardware issue, try a different slot.
  2. JorgeB
    Please post diags, and the name of the share you are trying to move data.
  3. JorgeB
    At boot time and besides the OS flash drive these were also connected: Nov 12 17:28:17 Tower kernel: scsi 1:0:0:0: Direct-Access Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 4 ... Nov 12 17:28:17 Tower kernel: scsi 2:0:0:0: Direct-Access JetFlash Transcend 16GB 1100 PQ: 0 ANSI: 6 They were since removed, but they still count until you reboot, or maybe until array re-start.
  4. JorgeB
    On the main page, not the dashboard.
  5. JorgeB
    You need to format it, next to array start/stop button.
  6. JorgeB
    It's missing from the UD devices plugin, not the array, you can delete that on the right side.
  7. JorgeB
    Where are you seeing that?
  8. JorgeB
    No need to format then, but if you still want to just read the first couple of posts in the Unassigned Devices plugin thread and you'll find the answer.
  9. JorgeB
    There are problems with the cache filesystem, you should backup and re-format.
  10. JorgeB
    Please use the existing docker support thread:
  11. JorgeB
    What controller are you using? Don't see any detected except the unused onboard SATA ports, make sure it's well seated or try a different slot.
  12. JorgeB
    I would recommend to backup and re-format cache now.
  13. JorgeB
    It's a problem with the onboard SATA controller, quite common with Ryzen boards, upgrading to latest beta should help (or disabling iommu if not needed).
  14. JorgeB
    You can type in the console: rm -r /path/to/folder Everything inside that folder will be deleted.
  15. JorgeB
    Yes. Unlikely to help and it can't fix the data corruption, best to just re-format. With the array stopped wipe the SSDs with: blkdiscard /dev/sdX Then start the array and format the pool
  16. JorgeB
    Run xfs_repair again without -n, and if it asks for it add -L.
  17. JorgeB
    Syslog you posted is before rebooting, please post complete diags after.
  18. JorgeB
    Most times --rebuild-tree doesn't create a lot of lost+found folders, but it will depend on the level of corruption, I would also recommend converting all the remaining reiser drives to xfs since reiser is not recommended for years now.
  19. JorgeB
    Yep.
  20. JorgeB
    Whatever you prefer, assuming the old hardware can run v6.
  21. JorgeB
    Glad all is good, this part is strange, never happened before with v6, especially without an apparent reason, maybe v5 related, but I'll keep it in mind to use the other option when possible.
  22. JorgeB
    Most times you need to run the balance twice, it's a btrfs issue and it's mentioned in the beta release notes.
  23. JorgeB
    Yes, corruption on a single filesystem can (and usually does) affect the user shares.
  24. JorgeB
    Please use the existing docker support thread:
  25. JorgeB
    You should re-create the docker image.
×
×
  • Create New...