Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,594

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    Which is it?
  2. JorgeB
    It's normal for the first check after the issue is fixed to still find errors, next ones should not find any.
  3. JorgeB
    Check the System Event Log in the BIOS or over IPMI if available, it might have more info on the affected DIMM.
  4. JorgeB
    That's obviously not normal, diagnostics grabbed after a problem might give some clues.
  5. JorgeB
    Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
  6. JorgeB
    So are most SATA disks, still too hot, you should keep them under 40C, 45C tops. Power on hours can't be changed, unless there's some firmware issue they are correct.
  7. JorgeB
    Delete and recreate the docker image, and make it smaller, 200GB is too much.
  8. JorgeB
    Delete and re-create the docker image.
  9. JorgeB
    Do you mean new to you? Disk is very far from new, it's also running very hot. Diags are after rebooting so we can't see the error but wait for the result of the long test, though I would strongly recommend to improve cooling.
  10. JorgeB
    See turbo write for better write speeds, but note that having two users writing at the same time will still slow down Unraid a lot, Unraid doesn't stripe disks, so it can never perform as well as RAID soltutions, it does have other advantages though.
  11. JorgeB
    Please post the diagnostics: Tools -> Diagnostics
  12. JorgeB
    That disk appears to be failing, and xfs failed to format it correctly.
  13. JorgeB
    If you mean disk5, yes it appears to be failing, but there's no recent SMART test, run an extended test.
  14. JorgeB
    One only.
  15. JorgeB
    It's not being detected, try connecting it to a different controller/port and/or using new cables.
  16. JorgeB
    du isn't reliable with btrfs, space used on the GUI is correct, note that if you have for example a vdisk on cache the file can bloat way beyond the reported used space, this can help with that.
  17. JorgeB
    According to the diags there's 0 array activity.
  18. JorgeB
    This now suggests a device limit, after the RAM cache is exhausted, enable turbo write, write directly to one of the disks and grab the diags after it slows down, then post them here.
  19. JorgeB
    Click on that disk (with the array stopped) and change fs to xfs.
  20. JorgeB
    Disk2 only shows filesystem corruption, not ATA errors, that should be fixable by checking filesystem: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui
  21. JorgeB
    Yes, but still a clear issue, I would start with trying to fix that, try a different NIC, cable, switch, source PC, etc
  22. JorgeB
    In the diags posted there's only 1 disk assigned, post new ones after there was a problem mounting the other disk.
  23. JorgeB
    If more drives are causing similar ATA errors then there might be other issue, diags showing that might help.
  24. JorgeB
    If the new cables didn't help it almost certainly a disk problem, sometimes errors are weird, just recently had a disk that passes every SMART test, you can do a perfect copy with dd, but try to mount the disk with any filesystem and you get error after error.
  25. JorgeB
    Nice work, if you don't object I was thinking of moving this to the general guides section or it will likely drop from the 1st page here.
×
×
  • Create New...