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
    There are known problems with reiserfsck 3.6.25, upgrade to unRAID v6.3.3 and run it again, although in this case it may have similar results.
  2. JorgeB
    Already replied in the PM, in my experience it works the same without them, but you can generate a random one, see the end of this post:
  3. JorgeB
    That's another problem, IIRC you need to flash an earlier firmware first.
  4. JorgeB
    It's the same, just replace sas2flsh.exe with sas2flash.efi in the command you were running.
  5. JorgeB
    Don't know any, I use rsync. unless a disks redballs during the copy, I assume every file was copied OK, if there's a disk issue I already have checksums, so I run a check on that disk only.
  6. JorgeB
    AFAIK correct, after the initial copy you'd need too run rsync -c /source /destination to compare checksums.
  7. JorgeB
    Ii think this explains it well:
  8. JorgeB
    ^this, but since it's reiser make sure you update to v6.3.3 first.
  9. JorgeB
    No problem, good luck, hope you get those issues sorted.
  10. JorgeB
    There can be a small difference when changing filesystem, but never like that, only reason I can think of is that there are sparse files (like vdisks) on the source disk. ETA: On the next run add --sparse to the rsync command, it won't hurt and if there really are sparse files they will use the same space on the destination.
  11. JorgeB
    If you mean cancel the rsync, yes, you can re-format and start again, but if the destination was really empty the result should be the same.
  12. JorgeB
    One thing has nothing to do with the other, but I'm not sure I understand what you're doing, you'll need to explain in more detail what you did and what you're seeing.
  13. JorgeB
    Do you have any vdisks on that disk?
  14. JorgeB
    No, and it wouldn't matter if all 24 were in use with HDDs.
  15. JorgeB
    It can be, since each 10GbE can push 1GB/s and max usable bandwidth of a PCIE 2.0 x4 slot is around 1.6GB/s, but only if would use both ports simultaneously and your hardware is capable of reaching those speeds.
  16. JorgeB
    Max speed in a x4 slot with 8 disks is 190MB/s, so enough for most disks. https://forums.lime-technology.com/topic/41340-satasas-controllers-tested-real-world-max-throughput-during-parity-check/#comment-406521
  17. JorgeB
    OOM errors started when the mover ran, I had a similar one recently and from what I've read they are quite common with kernels 4.8 and 4.9, apparently fixed on kernel 4.10, but unRAID is still on 4.9. Since then I decreased my RAM cache and so far no more OOM errors, you could try the same, manually or using the Tips and Tweaks plugin. Values to change are vm.dirty_background_ratio and vm.dirty_ratio, default is 10 and 20, I set mine to 1 and 2 just to see if it would help and for now they are still like that.
  18. JorgeB
    Agree, memtest errors always mean a hardware issue, usually a bad stick, but definatly a problem, even if crashing has been limited to unRAID so far.
  19. JorgeB
    You can close it and keep the operation running by using screen, part of the Nerdpack.
  20. JorgeB
    Why not use copy/paste?
  21. JorgeB
    Depends on what you want to do: Add a device (use method 2), replace/upgrade or remove.
  22. JorgeB
    I need to update that, the procedures were added later (if you use the GUI it will still change back to raid1), note however that to you can't remove a disk past the minimum number that the profile in use requires, eg, if you have a 8 device raid10 pool you can remove 4 devices without changing the profile, to remove anymore you'll need to convert.
  23. JorgeB
    You can add, remove and replace cache pool devices without changing the profile in use, see the FAQ on the general support forum.
  24. JorgeB
    I tested on 2 of my servers, one has a cache pool and 2 unassigned SSDs, those were the only ones trimmed (+ loop devices), disks were spun down and continued, so no issues, other server is my SSD only server, only the cache was trimmed since array SSDs don't support it, no errors also, looks like it only attempts to trim devices that support it.
  25. JorgeB
    You can't browse to the ISO location, it will list all the ISOs on your ISO share, share location is set in Settings -> VM Manager - > Default ISO storage path:
×
×
  • Create New...