sata/ssd errors (interface fatal error, failed command: WRITE FPDMA QUEUED)
FedoraForum.org - Fedora Support Forums and Community
Results 1 to 4 of 4
  1. #1
    Join Date
    Apr 2018
    Location
    bash shell
    Posts
    76
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Question sata/ssd errors (interface fatal error, failed command: WRITE FPDMA QUEUED)

    I have a Samsung SSD 850 PRO 256GB running for about 5 years now, which recently started producing these errors:

    Code:
    kernel: ata6.00: exception Emask 0x10 SAct 0xc SErr 0x400100 action 0x6 frozen
    kernel: ata6.00: irq_stat 0x08000000, interface fatal error
    kernel: ata6: SError: { UnrecovData Handshk }
    kernel: ata6.00: failed command: WRITE FPDMA QUEUED
    kernel: ata6.00: cmd 61/40:10:58:19:27/05:00:19:00:00/40 tag 2 ncq dma 688128 out
                     res 40/00:18:58:2e:27/00:00:19:00:00/40 Emask 0x10 (ATA bus error)
    kernel: ata6.00: status: { DRDY }
    kernel: ata6.00: failed command: WRITE FPDMA QUEUED
    kernel: ata6.00: cmd 61/78:18:58:2e:27/04:00:19:00:00/40 tag 3 ncq dma 585728 out
                     res 40/00:18:58:2e:27/00:00:19:00:00/40 Emask 0x10 (ATA bus error)
    kernel: ata6.00: status: { DRDY }
    kernel: ata6: hard resetting link
    kernel: ata6: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
    kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT1.SPT1._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
    kernel: ACPI Error: Aborting method \_SB.PCI0.SAT1.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
    kernel: ata6.00: supports DRM functions and may not be fully accessible
    kernel: ata6.00: disabling queued TRIM support
    kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT1.SPT1._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330)
    kernel: ACPI Error: Aborting method \_SB.PCI0.SAT1.SPT1._GTF due to previous error (AE_NOT_FOUND) (20190509/psparse-529)
    kernel: ata6.00: supports DRM functions and may not be fully accessible
    kernel: ata6.00: disabling queued TRIM support
    kernel: ata6.00: configured for UDMA/133
    kernel: ata6: EH complete

    I haven't made any major changes to this system, other than to move it across the office and to install the latest F30 kernel (5.2.7-200.fc30.x86_64).

    Smart status says that the disk is OK and the last self-test completed successfully.

    Anyone seen this before? Could it be that the SSD is dying, or could it be a bad cable after moving the system a few weeks ago?

    I'd appreciate some help.

    Thank you.




    PS:
    here is the smart data

    Code:
    SMART Attributes Data Structure revision number: 1
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      5 Reallocated_Sector_Ct   0x0033   100   100   010    Pre-fail  Always       -       0
      9 Power_On_Hours          0x0032   091   091   000    Old_age   Always       -       45026
     12 Power_Cycle_Count       0x0032   099   099   000    Old_age   Always       -       153
    177 Wear_Leveling_Count     0x0013   099   099   000    Pre-fail  Always       -       42
    179 Used_Rsvd_Blk_Cnt_Tot   0x0013   100   100   010    Pre-fail  Always       -       0
    181 Program_Fail_Cnt_Total  0x0032   100   100   010    Old_age   Always       -       0
    182 Erase_Fail_Count_Total  0x0032   100   100   010    Old_age   Always       -       0
    183 Runtime_Bad_Block       0x0013   100   100   010    Pre-fail  Always       -       0
    187 Uncorrectable_Error_Cnt 0x0032   100   100   000    Old_age   Always       -       0
    190 Airflow_Temperature_Cel 0x0032   071   046   000    Old_age   Always       -       29
    195 ECC_Error_Rate          0x001a   200   200   000    Old_age   Always       -       0
    199 CRC_Error_Count         0x003e   099   099   000    Old_age   Always       -       90
    235 POR_Recovery_Count      0x0012   099   099   000    Old_age   Always       -       103
    241 Total_LBAs_Written      0x0032   099   099   000    Old_age   Always       -       7496626407
    
    SMART Error Log Version: 1
    No Errors Logged
    Last edited by fedup4ever; 13th August 2019 at 09:22 PM. Reason: add smart data

  2. #2
    Join Date
    Jul 2009
    Posts
    25
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)

    Re: sata/ssd errors (interface fatal error, failed command: WRITE FPDMA QUEUED)

    it is not a samsung ssd error, it is a module error, Could not resolve symbol [\_SB.PCI0.SAT1.SPT1._GTF.DSSP], AE_NOT_FOUND (20190509/psargs-330) if u installed a new kernel try to use a older one and check if the problem continue...

  3. #3
    Join Date
    Jul 2009
    Posts
    25
    Mentioned
    1 Post(s)
    Tagged
    0 Thread(s)

    Re: sata/ssd errors (interface fatal error, failed command: WRITE FPDMA QUEUED)

    ok, after some time googleing i fund a possible fix, if it dont work nothing will change in ur sistem, is just a test, try to press E in the grub menu and go to the end of the command line, it normally end with "quiet" , after the quiet u must write acpi=off as the exemple:
    RUB_CMDLINE_LINUX="resume=UUID=1e4495cf-cb4d-47f6-b6cd-be45a788bbc3 rhgb quiet acpi=off
    after this u press ctrl+x and the system will try to boot, if it boot without the error than we fund the solution

  4. #4
    Join Date
    Apr 2018
    Location
    bash shell
    Posts
    76
    Mentioned
    0 Post(s)
    Tagged
    0 Thread(s)

    Re: sata/ssd errors (interface fatal error, failed command: WRITE FPDMA QUEUED)

    first of all, thanks for taking the time to help, I appreciate it.

    before I turn off acpi, I started from the top and I googled the first two lines, which came up with the following link:
    https://forums.unraid.net/topic/1427...s-help-solved/

    it is suggested that either the SATA cable is not plugged correctly, or that the cable is defective. I'll see if I can find some new SATA cables tomorrow and then also turn off acpi. Interesting...

Similar Threads

  1. Replies: 9
    Last Post: 28th December 2013, 03:30 PM
  2. Replies: 7
    Last Post: 9th April 2009, 07:50 PM
  3. Replies: 1
    Last Post: 11th March 2007, 07:06 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •