Jump to content
We're Hiring! Full Stack Developer ×

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    64,060

  • Joined

  • Last visited

  • Days Won

    676

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    You'll need to edit config\domain.cfg on the flash drive and change SERVICE="enable" to "disable", then reboot.
  2. JorgeB
    It is, PCIe 3.0 is backward compatible.
  3. JorgeB
    Adding vfs objects = btrfs to a btrfs formatted SMB share allows copy-on-write (i.e. instant) copies to be done using windows explorer (on windows 8/server2012 or newer) using Samba's server side copy functionality, obviously as long as the copy is done on the same filesystem, e.g., from cache to cache, disk1 to disk1, etc, this would allow for example to very quickly and easily backup a vdisk before any significant change without dropping to the CLI. Alternatively allow the user to add specific vfs objects to any share using the GUI.
  4. JorgeB
    You can use a spare flash drive as the single data disk.
  5. JorgeB
    First time I hear that, maybe if it's limited to SAS drives since they are not used by many, still would think other people would have complained by now it it's a general problem.
  6. JorgeB
    50 to 60MB/s are the normal unRAID writing speed due to how parity works with the default settings, you can enable turbo write for faster writes.
  7. JorgeB
    This is usually caused by a PCIe device, it can be fixed by moving the offending device to a different PCIe slot, updating the bios or adding pci=nommconfto your syslinux.cfg after append initrd=/bzroot, so it would look like: append initrd=/bzroot pci=nommconf
  8. JorgeB
  9. JorgeB
    Good point, forget to mention that, scheduled parity checks should always be non correct.
  10. JorgeB
    The automatic parity check in case of an unclean shutdown is always non-correct, if one starts and finds one or more errors might as well cancel it and start a correcting check.
  11. JorgeB
    Not sure that is the problem, though the filesystem is fully allocated there's still space for metadata, this problem is more serious if it is fully allocated and the metadata is almost all used up since there's no space to create a new chunk, still run a balance because it's not good to be like that: https://lime-technology.com/forums/topic/62230-out-of-space-errors-on-cache-drive/?do=findComment&comment=610551 P.S. disk1 needs a new SATA cable.
  12. JorgeB
    Possibly, but that's beyond my knowledge
  13. JorgeB
    Next time please use the forum instead of pm, but yeah the NICs are detected and no driver is loaded, if there's an available driver in the kernel LT are usually quick to add it and it should be on the next release.
  14. JorgeB
    On the console type diagnostics and the zip will be saved to your flash drive, then just plug it in a desktop.
  15. JorgeB
    Please post your diagnostics: Tools -> Diagnostics
  16. JorgeB
    Most currently available cables should be at least 6Gbps (SAS2/SATA3)
  17. JorgeB
    If it tries to access them, and it could do that even if you don't write anything to them, it will disable as many disks as parity disks there are.
  18. JorgeB
    Like mentioned use the onboard SATA ports for the SSDs, as the H310 doesn't support trim.
  19. JorgeB
    Device dropping won't have anything to do with raid mode, it's a hardware/connection problem.
  20. JorgeB
    You don't remove it, after starting the array there's an option to format any unmoutable disk, next to the stop array button
  21. JorgeB
    You need to format the drive
  22. JorgeB
  23. JorgeB
    If these are to go from the HBA or expander to backplane SATA ports you need forward breakout cables.
  24. JorgeB
  25. JorgeB
    You can
×
×
  • Create New...