Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,645

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    É possivel, mas primeiro a pool tem de ser convertida para raid1, depois basta seguir estas instruções.
  2. JorgeB
    Also, and just FYI, those trans ID errors are usually caused by bad RAM or devices that don't respect write barriers or FUA, due to the very close transition ID difference I would suspect the latter.
  3. JorgeB
    a means always.
  4. JorgeB
    It won't make any difference, at least it shouldn't, it's not an OS issue.
  5. JorgeB
    That doesn't mean it won't work, let it run.
  6. JorgeB
    Nothing is being detect by Linux, either NIC is dead or doesn't like your board, do you have another PC you can try it in?
  7. JorgeB
    Mount error suggests some writes were lost, see here for some recovery options, option #2 is the more likely to work with that error, if successful then reformat the pool.
  8. JorgeB
    Any SAS2 or SAS3 model, SAS1 LSI HBAs are limited to 2TiB Those are SAS2 so not a problem.
  9. JorgeB
    If you have dockers running stop the docker engine and see if there's any difference, if yes get a dedicated device for appdata.
  10. JorgeB
    Could be a disk, but it's not that uncommon for newer kernels to be slightly slower, and since your CPU is not very powerful and the speed loss is not much my money is more on that.
  11. JorgeB
    It can't, only up to 2TiB.
  12. JorgeB
    Not sure if you CPU is affected, worth checking:
  13. JorgeB
    I suspect it might be the name of the device not being correctly parsed, maybe the period? External_USB_3.0_20130522013291
  14. JorgeB
    Please post diags to see the hardware used, there are some known issues.
  15. JorgeB
    First try an SMB transfer from a computer to see if it's the same, if yes grab the diagnostics after the stall and post them here.
  16. JorgeB
    Post a SMART report for disk1.
  17. JorgeB
    Should be perfectly safe, array SSDs won't get trimmed, so some write performance degradation could happen, especially with cheap ones, other than that you don't need anything special.
  18. JorgeB
    It already does report correct used and free space (except in some unrelated cases due to btrfs bug), this thread is from 2020.
  19. JorgeB
    Log shows flash drive issues, it dropped offline: May 10 23:39:12 afterdark kernel: usb 2-1.6: USB disconnect, device number 4 May 10 23:39:12 afterdark rc.diskinfo[11534]: SIGHUP received, forcing refresh of disks info. May 10 23:39:12 afterdark emhttpd: Unregistered - flash device error (ENOFLASH3) If using a USB 3.0 port try USB 2.0 instead.
  20. JorgeB
    It's known issue:
  21. JorgeB
    Unassign the disk, start/stop array, re-assign the disk to begin another rebuild.
  22. JorgeB
    Then looks like some issue with UD and/or encryption, can't help with that.
  23. JorgeB
    Doesn't look like a disk problem to me, it was mounting before with unencrypted xfs: May 6 18:35:28 Unraid unassigned.devices: Adding disk '/dev/sda1'... May 6 18:35:28 Unraid unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime '/dev/sda1' '/mnt/disks/Intenso_External_USB_3.0' May 6 18:35:28 Unraid kernel: XFS (sda1): Mounting V5 Filesystem May 6 18:35:29 Unraid kernel: XFS (sda1): Ending clean mount Then it didn't mount with encrypted xfs, does it still work if you reformat without encryption?
  24. JorgeB
    Syslog is showing a problem with cache2, looks more like a connection problem, replace cables and post new diags after array start.
  25. JorgeB
    Syslog is spammed with other issues, can't see the disks errors, but disk itself looks fine, and the high number of UDMA CRC errors suggest a bad connection, replace SATA cable/slot and try again.
×
×
  • Create New...