Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,812

  • Joined

  • Last visited

  • Days Won

    708

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    parent transid verify failed on 180224 wanted 4989515 found 4989510 This error is fatal with btrfs, it means some writes were lost due to write barriers not being respected, most times a controller/device firmware issue, you'll need to re-format but can try the btrfs restore option here, though it doesn't always work 100% with this error.
  2. JorgeB
    Don't see how, if you can get them to boot, try another PC if available, delete the BIOS, it's not needed for Unraid and makes booting faster and it will prevent the issues that can happen with with some boards/BIOS.
  3. JorgeB
    Probably can only solve that by rebooting.
  4. JorgeB
    Check filesystem on disk 3
  5. JorgeB
    Samba is single threaded, still should be able to get much more then 300MB/s, assuming fast enough devices and a relatively recent high clock CPU.
  6. JorgeB
    Any idea what's creating all those lsof commands? Alternatively boot in safe mode and disable all services, then start enabling them one by one until you find the culprit.
  7. JorgeB
    Sorry for the late reply, was away for a week, not sure the NVMe devices should be visible in the BIOS, I would assume so, recommend trying a different OS, use Windows or a different Linux distro just to see if it's the same or not, I would expect yes.
  8. JorgeB
    Start by running memtest.
  9. JorgeB
    That won't cause any issues with disk identification, new system might sill support CSM boot anyway, but if it doesn't just enable UEFI boot by renaming EFI- to EFI in the flash drive.
  10. JorgeB
    If you updated using the GUI you can revert to the previous release by copying the bz* file from the /previous folder in the flash drive overwriting the new ones.
  11. JorgeB
    Sorry, not familiar with that model, but it should come up if you search the forum.
  12. JorgeB
    Yes, that model is reported to work.
  13. JorgeB
    Stock Unraid cannot spin down SAS devices, install the SAS spin down plugin.
  14. JorgeB
    SATA splitter should not be used for more than 2 hard drives, molex is OK for more.
  15. JorgeB
    Unlikely that's the problem, but it does show you're using a SATA port multiplier, and those are not recommended, though usually they cause disk related issues, not server crashing.
  16. JorgeB
    Do you mean every time or when the server is inaccessible? If just when the server is inaccessible it's normal if the server crashed.
  17. JorgeB
    Sorry for the late reply but was away for a week, not sure you still need help with this, lots of drive errors spamming the log, including from both cache devices, at last reboot there was no btrfs filesystem on sdl, there was on sdk, please post the output of btrfs fi show
  18. JorgeB
    It's not possible using redundancy, it would be possible using a previous snapshot, but I assume you were not creating those, if not you can do it for the future with for example the snapshot plugin.
  19. JorgeB
    Settings are mostly used to select use cache mode, allocation method and split level, also don't forget to set the minimum free space, default is 0. You can try again before getting a new one.
  20. JorgeB
    Not sure that will help, but it won't hurt, do this: on the main GUI page click on flash, scroll down to "Syslinux Configuration", make sure it's set to "menu view" (on the top right) and add this to your default boot option, after "append initrd=/bzroot" e.g.: append initrd=/bzroot nvme_core.default_ps_max_latency_us=0 Reboot and see if it makes a difference.
  21. JorgeB
    If the server now also crashes with v6.9.2, a previous known good release with it, it suggests something changed or there could be a hardware problem, enable the syslog server and post that after a crash to see if it catches something.
  22. JorgeB
    Best bet is using the existing container support thread/discord, assuming there's one.
  23. JorgeB

    docker errors

    JorgeB replied to atakan's topic in Docker Engine

    Try booting in safe mode, if it's the same I would try a new flash drive config.
  24. JorgeB
    Run a scrub, then delete/restore all corrupt files, they will be listed in the syslog, since corruption in only happening on one device it might suggest a device problem.
  25. JorgeB
    Depends on the controller/expander, see here for some actual numbers.
×
×
  • Create New...