Jump to content

urbanracer34

Members
 View Profile  See their activity

  • Posts

    168

  • Joined

  • Last visited

 Content Type 

Report Comments posted by urbanracer34

    [6.8.3] VERY slow move from Cache to array

    in Stable Releases

    Posted · Edited by urbanracer34

    I don't have Turbo write enabled right now. I'l enable it after the copy. 

     

    But I'm getting these errors in the system log now:

     

    Mar 8 11:31:22 GIBSON kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
    Mar 8 11:31:22 GIBSON kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT3._GTF, AE_NOT_FOUND (20180810/psparse-514)
    Mar 8 11:31:22 GIBSON kernel: ata4.00: configured for UDMA/133
    Mar 8 11:31:22 GIBSON kernel: ata4: EH complete
    Mar 8 11:33:21 GIBSON kernel: ata4.00: exception Emask 0x10 SAct 0x1f0 SErr 0x400100 action 0x6 frozen
    Mar 8 11:33:21 GIBSON kernel: ata4.00: irq_stat 0x08000000, interface fatal error
    Mar 8 11:33:21 GIBSON kernel: ata4: SError: { UnrecovData Handshk }
    Mar 8 11:33:21 GIBSON kernel: ata4.00: failed command: WRITE FPDMA QUEUED
    Mar 8 11:33:21 GIBSON kernel: ata4.00: cmd 61/40:20:88:ef:9d/05:00:b4:01:00/40 tag 4 ncq dma 688128 out
    Mar 8 11:33:21 GIBSON kernel: res 40/00:40:88:04:9e/00:00:b4:01:00/40 Emask 0x10 (ATA bus error)
    Mar 8 11:33:21 GIBSON kernel: ata4.00: status: { DRDY }
    Mar 8 11:33:21 GIBSON kernel: ata4.00: failed command: WRITE FPDMA QUEUED
    Mar 8 11:33:21 GIBSON kernel: ata4.00: cmd 61/40:28:c8:f4:9d/05:00:b4:01:00/40 tag 5 ncq dma 688128 out
    Mar 8 11:33:21 GIBSON kernel: res 40/00:40:88:04:9e/00:00:b4:01:00/40 Emask 0x10 (ATA bus error)
    Mar 8 11:33:21 GIBSON kernel: ata4.00: status: { DRDY }
    Mar 8 11:33:21 GIBSON kernel: ata4.00: failed command: WRITE FPDMA QUEUED
    Mar 8 11:33:21 GIBSON kernel: ata4.00: cmd 61/40:30:08:fa:9d/05:00:b4:01:00/40 tag 6 ncq dma 688128 out
    Mar 8 11:33:21 GIBSON kernel: res 40/00:40:88:04:9e/00:00:b4:01:00/40 Emask 0x10 (ATA bus error)
    Mar 8 11:33:21 GIBSON kernel: ata4.00: status: { DRDY }
    Mar 8 11:33:21 GIBSON kernel: ata4.00: failed command: WRITE FPDMA QUEUED
    Mar 8 11:33:21 GIBSON kernel: ata4.00: cmd 61/40:38:48:ff:9d/05:00:b4:01:00/40 tag 7 ncq dma 688128 out
    Mar 8 11:33:21 GIBSON kernel: res 40/00:40:88:04:9e/00:00:b4:01:00/40 Emask 0x10 (ATA bus error)
    Mar 8 11:33:21 GIBSON kernel: ata4.00: status: { DRDY }
    Mar 8 11:33:21 GIBSON kernel: ata4.00: failed command: WRITE FPDMA QUEUED
    Mar 8 11:33:21 GIBSON kernel: ata4.00: cmd 61/08:40:88:04:9e/00:00:b4:01:00/40 tag 8 ncq dma 4096 out
    Mar 8 11:33:21 GIBSON kernel: res 40/00:40:88:04:9e/00:00:b4:01:00/40 Emask 0x10 (ATA bus error)
    Mar 8 11:33:21 GIBSON kernel: ata4.00: status: { DRDY }
    Mar 8 11:33:21 GIBSON kernel: ata4: hard resetting link
    Mar 8 11:33:21 GIBSON kernel: ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    Mar 8 11:33:21 GIBSON kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
    Mar 8 11:33:21 GIBSON kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT3._GTF, AE_NOT_FOUND (20180810/psparse-514)
    Mar 8 11:33:21 GIBSON kernel: ACPI BIOS Error (bug): Could not resolve [\_SB.PCI0.SAT0.PRT3._GTF.DSSP], AE_NOT_FOUND (20180810/psargs-330)
    Mar 8 11:33:21 GIBSON kernel: ACPI Error: Method parse/execution failed \_SB.PCI0.SAT0.PRT3._GTF, AE_NOT_FOUND (20180810/psparse-514)
    Mar 8 11:33:21 GIBSON kernel: ata4.00: configured for UDMA/133
    Mar 8 11:33:21 GIBSON kernel: ata4: EH complete
    Mar 8 11:33:29 GIBSON webGUI: Successful login user root from 192.168.1.158

     

    BIOS IS ACTUALLY UP TO DATE! Tried flashing, have same revision.

    Dockers wanting to update, but don't in the end?

    in Stable Releases

    Posted

    50 minutes ago, bonienl said:

    Are you using pihole as DNS server for your Unraid machine?

     

    When network connection issues exist, it may result in the behavior you are seeing.

     

    No. No pihole here.

    10 minutes ago, jonathanm said:

    This issue is effecting a wide swath of people. Personally I have 27 containers on one of my servers, all 10 of the LSIO show update ready, none of the other containers do. They were all up to date yesterday.

     

    No connection issues at my end of the pipe, one of my other servers behind the same router just updated a binhex container just fine.

     

    A different server at another location with 10 containers, all 3 of the LSIO show update ready. If it's unraid's fault, then unraid is preferentially picking on LSIO.

    I am not having any connection issues here AFAIK. Connection has been stable.

×
×
  • Create New...