Jump to content

JorgeB

Moderators
 View Profile  See their activity

  • Posts

    67,572

  • Joined

  • Last visited

  • Days Won

    707

 Content Type 

Everything posted by JorgeB

  1. JorgeB
    This suggests more a device problem, enable turbo write and see if it's faster transferring to the array, assuming no major controller/hdd bottlenecks.
  2. JorgeB
    No, at least it shouldn't, there are some known firmware issues that can result in actual errors but AFAIK only with ZFS in a raid config.
  3. JorgeB
    Run without -n or nothing will be done.
  4. JorgeB
    Those diagas are not after booting in safe mode, probably the previous ones.
  5. JorgeB
    You need to run on the disk, not the device or parity will be invalid, dm-14 means you're using encryption, it should be disk 15 (or cache if there isn't one), but would need the diags to be sure.
  6. JorgeB
    That's not the issue, AMD officially supports 3200MHZ as max for that CPU, and Ryzen has been known to have stability issues (even corrupt data) with overclocked RAM and Unraid.
  7. JorgeB
    No, move it to the safe mode entry:
  8. JorgeB
    https://forums.unraid.net/topic/57181-docker-faq/?do=findComment&comment=564309
  9. JorgeB
    Edit syslinux.cfg on the flash drive and move "menu default" form normal to safe mode.
  10. JorgeB
    Need to click on cache1, then:
  11. JorgeB
    You can run the scrub by clicking on cache on the main page then scroll down to the scrub section.
  12. JorgeB
    You can check here for some bench results.
  13. JorgeB
    Did you run the scrub and confirmed all errors were corrected?
  14. JorgeB
    Upgrading to v6.9 will use a newer kernel.
  15. JorgeB
    You can't, first need to fix that, if they are shucked drives it could be the 3.3v SATA pin issue, make sure you google that.
  16. JorgeB
    This is a rather common issue with the SATA controller on Ryzen boards, newer kernel on v6.9 helps in some cases, newer BIOS might also help, but you already did that.
  17. JorgeB
    Looks right for the disks you have, it will slowdown as it goes to the slower inner tracks.
  18. JorgeB
    Diags show that you formatted sdb: Jan 24 23:41:08 unRAID emhttpd: shcmd (398): /sbin/wipefs -a /dev/sdb1 Jan 24 23:41:08 unRAID emhttpd: shcmd (399): mkfs.btrfs -f /dev/sdb1 Then added sdc to the pool, this also wiped that device: Jan 24 23:41:08 unRAID emhttpd: shcmd (401): /sbin/wipefs -a /dev/sdc1 Jan 24 23:41:08 unRAID root: /dev/sdc1: 8 bytes were erased at offset 0x00010040 (btrfs): 5f 42 48 52 66 53 5f 4d So there's no device still with old pool data to recover from.
  19. JorgeB
    This shows that on of the cache devices dropped offline in the past: Jan 24 14:47:07 tower kernel: BTRFS info (device sdb1): bdev /dev/sdc1 errs: wr 1507246927, rd 137577961, flush 19733411, corrupt 0, gen 0 See here for what to do and how to better monitor a pool, then recreate the docker image.
  20. JorgeB
    Yes.
  21. JorgeB
    SMART looks OK, but if new cables don't help try with a different disk. P.S. unrelated but that's an SMR disk, could have performance degradation.
  22. JorgeB
    SMART is showing some issues, it will likely fail again in future, but difficult to guess if it will be tomorrow or a year from now.
  23. JorgeB
    A few sync errors are normal, even expected, after an unclean shutdown, just run a correcting check.
  24. JorgeB
    Files that copy without errors can be assume OK (if data checksums are not disable). Would need to see the syslog to confirm but most likely that file is corrupt, you should be able to recover with btrfs restore, but the file will still be corrupt.
  25. JorgeB
    Try booting in safe mode and post diags after that if it still doesn't work.
×
×
  • Create New...