Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,125

  • Joined

  • Last visited

  • Days Won

    703

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    On the console type: mover stop
  2. JorgeB
    No, docker needs to be disable until all files are on cache again, if you have many small files it would be much faster moving them manually, e.g., with midnight commander (mc on the console), move from /mnt/cache to /mnt/disk#
  3. JorgeB
    Once the data is on the array, stop it, and assuming it's a single cache device, click on it and change the cache filesystem to xfs, start the array and you'll have the option to format, you can then leave it as xfs if you don't have plans to create a cache pool or change back to btrfs and format again.
  4. JorgeB
    Backup your cache, reformat and restore the data, you can use this procedure to backup/restore.
  5. JorgeB
    No, I'm still using the same method. I don't use encryption but don't see a reason why it would cause issues.
  6. JorgeB
    Keep in mind that using the default raid1 model only 250GB will be usable, despite the main page showing free space available on the pool.
  7. JorgeB
    You can try, but the result will probably be the same, you can also run a filesystem check in case there's corruption.
  8. JorgeB
    Check it's using the latest firmware P20.00.07, there were two previous releases and the 1st one especially (p20.00.00) had issues.
  9. JorgeB
    You have something using that folder, reboot stop all docker/VMs and try again
  10. JorgeB
    Try again after stopping any plex related dockers
  11. JorgeB
    There's a problem somewhere, with turbo write enable I clear disks at 100MB/s+, post your diagnostics, maybe something visible.
  12. JorgeB
    You can use midnight commander (mc on the console), it will show a progress bar with ETA.
  13. JorgeB
    That's likely a UEFI bug on the board you're using, bios update might help.
  14. JorgeB
    When CSM is disable only UEFI boot is available, so all HBA BIOS, NIC Boot ROMS, etc are skipped.
  15. JorgeB
    I don't remember what's the latest bios version, latest firmware is 20.00.07, the bios included with that will be the latest, and if you're running an older firmware it will likely also have an older bios.
  16. JorgeB
    Either boot DOS and use sas2flsh.exe or UEFI and use sas2flash.efi, both are on the wiki toolset: https://lime-technology.com/wiki/Crossflashing_Controllers#LSI_MegaRAID_with_SAS2008_chipsets Scroll down to the Notes and download LSI MegaRAID to SAS2008(P20).zip - 4.1 MB (FREEDOS, via bootable usb key), it contains both
  17. JorgeB
    It is. sas2flash -o -e 5 then confirm it was removed with sas2flash -list Bios Version should now read N/A
  18. JorgeB
    See here:
  19. JorgeB
    You need to erase the bios from flash.
  20. JorgeB
    It needs to be patched, but it still works.
  21. JorgeB
    Your cache filesystem is fully allocated resulting in ENOSPC errors, see here on how to resolve: https://lime-technology.com/forums/topic/62230-out-of-space-errors-on-cache-drive/?do=findComment&comment=610551 After it's done you'll likely need to delete and recreate the docker image since it will most likely be corrupt.
  22. JorgeB
    Array was not started yet when you grabbed the diagnostics, we need after start diagnostics, if you can't get them from the GUI type diagnostics on the console/SSH.
  23. JorgeB
    Do you need the bios? Removing the bios is the best way to get a quick boot, bios is only needed when you need to boot from an HBA attached device.
  24. JorgeB
    There is no standard recommendation, ask 10 different users and you might get 10 different answers, I for example do a single read pass with MHDD on another computer, it's the only tool I know that clearly shows slow sectors, in my experience a good predictor of future issues, and those can't be seen on preclear, most other tools and SMART attributes.
  25. JorgeB
    There multiple ways and utilities for testing disks including preclear, but all are optional, clearing a disk is only mandatory when it's added as a new disk to a parity protected array, and unRAID clears the disk in the background since v6.2, it you want to burn in the disk you can use preclear, badblocks, the disks own testing tools like WD lifeguard, Seatools, etc.
×
×
  • Create New...