Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    63,929

  • Joined

  • Last visited

  • Days Won

    675

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    You need to erase the bios from flash.
  2. JorgeB
    It needs to be patched, but it still works.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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.
  8. JorgeB
    The script is supported, just needs to be patched, though there are multiple other disk tools to burning disks before use for users that want to do that, badbocks for example which is also included with unRAID.
  9. JorgeB
    Yeah, I already noticed they had removed the latest bios for most boards, unfortunately only after I already updated all three X11SSM-F I have, still they are working fine so far so I'll wait for a new bios instead of downgrading.
  10. JorgeB
    ?
  11. JorgeB
    No, the disk is only added to the array if successfully cleared.
  12. JorgeB
    Please post your diagnostics: Tools -> Diagnostics
  13. JorgeB
    Since v6.2 that new disks are cleared on the background, array is available during that time.
  14. JorgeB
    The issue of the filesystem getting fully allocated on SSDs (resulting in trim not working on the drive) seems to be resolved, this was one of the contributing factors for the slowdown, but possibly not the only one, I myself never noticed that issue.
  15. JorgeB
    You can just acknowledge the current values on the dashboard page by clicking on the SMART status, this way, and if notifications are enable, you'll get warned when they change.
  16. JorgeB
    The CRC attribute monitoring was added on v6.4.1, those errors might be old since CRC attribute doesn't reset, as long as they don't keep increasing you're fine.
  17. JorgeB
    LSI2008 doesn't support trim on most SSD, try connecting it to the onboard SATA ports.
  18. JorgeB
    Usually it's plug'n play, good idea to have a screenshot of current assignments just in case.
  19. JorgeB
    You want to avoid either of those, the first one has a port multiplier, that's and accident waiting to happen, the 2nd one is no longer recommended for unRAID, it can cause sync errors including file corruption and drop disks, the currently recommended 8 ports controllers are LSI, any LSI with a SAS2008/2308/3008 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed.
  20. JorgeB
    You need to change cache slots back to 1, then click on cache and check that filesystem is set to auto or xfs.
  21. JorgeB
    Yep
  22. JorgeB
    btrfs snapshots and then btrfs send/receive to another disk.
  23. JorgeB
    Yes, it's normal, about 1TB per GB.
  24. JorgeB
    Yes, it's done
  25. JorgeB
    Before that you can also try btrfs check using the backup superblock: btrfs check -s 1 /dev/sdn1 Also try the lowmen mode which might give different result: btrfs check -s 1 --mode=lowmem /dev/sdn1
×
×
  • Create New...