March 9, 20215 yr Hallo, mir sind heute im Syslog folgende Fehlermeldungen aufgefallen: Mar 8 21:00:48 nas kernel: ata4.00: exception Emask 0x0 SAct 0xffffffff SErr 0x40000 action 0x6 frozen Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: SEND FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:00:48 nas kernel: ata4: hard resetting link Mar 8 21:01:46 nas kernel: ata4.00: exception Emask 0x0 SAct 0xff3fffff SErr 0x0 action 0x6 frozen Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: SEND FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:01:46 nas kernel: ata4: hard resetting link Mar 8 21:02:46 nas kernel: ata4.00: exception Emask 0x0 SAct 0x71ffffff SErr 0x0 action 0x6 frozen Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4.00: failed command: SEND FPDMA QUEUED Mar 8 21:02:46 nas kernel: ata4: hard resetting link Mar 8 21:03:46 nas kernel: ata4.00: exception Emask 0x0 SAct 0x67ffffff SErr 0x0 action 0x6 frozen Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: READ FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: SEND FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4.00: failed command: WRITE FPDMA QUEUED Mar 8 21:03:46 nas kernel: ata4: hard resetting link https://forums.unraid.net/topic/53774-strange-disk-errors-in-syslog/?tab=comments#comment-525038&searchlight=1 Hier wird beschrieben, dass der SSD Trim zweimal ausgeführt werden soll?! Wie geht das? Ist das überhaupt sinnvoll? Gibt es irgendeine andere Lösung? Verbaute Hardware: Asrock J4105-ITX Samsung 870 EVO 500GB System läuft auf 6.9.0 SSD Trim läuft bei mir jeden Montag um 21:00 Uhr.
March 9, 20215 yr Kabel? https://forums.unraid.net/topic/74889-solved-unraid-661-ata600-failed-command-write-fpdma-queued/ Ansonsten hier das Kommando: fstrim -v /mnt/cache
March 10, 20215 yr Author 9 hours ago, mgutt said: Ansonsten hier das Kommando: fstrim -v /mnt/cache Habe bemerkt, dass ich zwei verschiedene SATA Controller verbaut habe. (Intel und ASMedia) Daraufhin habe ich die SSD auf einen Intel Controller umgesteckt. Das manuelle ausführen des fstrim Befehles verursacht nun keine Probleme mehr. Warte noch die automatische Ausführung ab. 8 hours ago, AndreasNe said: Ich dachte bei der Version 6.9.0 ist der SSD-Trim nicht mehr notwendig. Warum sollte es nicht mehr notwendig sein?
March 10, 20215 yr Community Expert 44 minutes ago, Anym001 said: Warum sollte es nicht mehr notwendig sein?
March 10, 20215 yr Author Okay danke für die Info. Hab ich leider nicht mitbekommen. @mgutt Vielleicht kannst du das ja bei dem Topic "Häufig gestellte Fragen" ergänzen, dass dies ab 6.9 nicht mehr benötigt wird. Edited March 10, 20215 yr by Anym001
Archived
This topic is now archived and is closed to further replies.