Hello All,

 

Recently, the "Fix Common Problems" plugin flagged an issue related to Parity read operations and recommended reviewing the SMART attributes. While I didn’t observe any immediate concerns in the SMART data, I would appreciate assistance in interpreting these attributes. This will help me better prepare and decide if I need to purchase replacement disks. Thank you!

Plugin Error Message

 

Unraid Dashboard

SMART SCAN details for all Drives

Parity (Western Digital) Smart attributes

 

Disk 1 (Western Digital)

 

Disk 2 (Seagate)

https://ntfs.com/disk-monitor-smart-attributes.htm

Please post diag file. hard to say as i know which drive to look into but your pictures don't tell me hwat drive is waht. you may have a filaing HD...

Attaching Diag zip. Thanks

sshomeserver-diagnostics-20241117-2058.zip

Thank you for posting diag:

=== START OF INFORMATION SECTION ===
Device Model:     WDC WD140EMFZ-11A0WA0
Serial Number:    9RJ8331C

has a passed spart value.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

I would reboot unraid to reset sys log and run FCP Plugin scan again.


I'm not seing anything big in the logs that would indicate a failure:

Nov 17 18:58:49 SSHomeServer root: Fix Common Problems: Error: parity (WDC_WD140EMFZ-11A0WA0_9RJ8331C) has read errors

Leading up to FCP reporting it looks like somethign was trying to force spin down the disk and the disk spingin back up due to activity...
 

Quote

Nov 17 04:40:06 SSHomeServer root: Fix Common Problems: Error: parity (WDC_WD140EMFZ-11A0WA0_9RJ8331C) has read errors
Nov 17 04:40:21 SSHomeServer sSMTP[2879]: Creating SSL connection to host
Nov 17 04:40:22 SSHomeServer sSMTP[2879]: SSL connection using ECDHE-RSA-AES256-GCM-SHA384
Nov 17 04:40:23 SSHomeServer sSMTP[2879]: Authorization failed (535 Authentication Failed for [email protected])
Nov 17 06:00:42 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 06:00:42 SSHomeServer emhttpd: spinning down /dev/sdb
Nov 17 06:02:53 SSHomeServer kernel: mdcmd (565): set md_write_method 0
Nov 17 06:02:53 SSHomeServer kernel: 
Nov 17 06:03:48 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 06:36:55 SSHomeServer emhttpd: read SMART /dev/sdb
Nov 17 06:37:53 SSHomeServer kernel: mdcmd (566): set md_write_method 1
Nov 17 06:37:53 SSHomeServer kernel: 
Nov 17 06:45:53 SSHomeServer emhttpd: spinning down /dev/sdf
Nov 17 07:05:39 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 07:08:56 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 07:46:21 SSHomeServer flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Nov 17 07:58:07 SSHomeServer emhttpd: read SMART /dev/sdf
Nov 17 08:11:06 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 08:13:46 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 08:59:04 SSHomeServer emhttpd: spinning down /dev/sdf
Nov 17 09:02:50 SSHomeServer emhttpd: read SMART /dev/sdf
Nov 17 09:15:34 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 09:18:46 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 10:20:30 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 10:20:30 SSHomeServer emhttpd: spinning down /dev/sdc
Nov 17 10:22:54 SSHomeServer kernel: mdcmd (567): set md_write_method 0
Nov 17 10:22:54 SSHomeServer kernel: 
Nov 17 10:23:45 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 10:23:45 SSHomeServer emhttpd: read SMART /dev/sdc
Nov 17 10:27:54 SSHomeServer kernel: mdcmd (568): set md_write_method 1
Nov 17 10:27:54 SSHomeServer kernel: 
Nov 17 10:27:56 SSHomeServer emhttpd: spinning down /dev/sdf
Nov 17 11:22:34 SSHomeServer emhttpd: spinning down /dev/sdb
Nov 17 11:22:55 SSHomeServer kernel: mdcmd (569): set md_write_method 0
Nov 17 11:22:55 SSHomeServer kernel: 
Nov 17 11:25:57 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 11:25:57 SSHomeServer emhttpd: spinning down /dev/sdc
Nov 17 11:28:55 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 11:28:55 SSHomeServer emhttpd: read SMART /dev/sdc
Nov 17 11:31:49 SSHomeServer emhttpd: read SMART /dev/sdf
Nov 17 12:53:28 SSHomeServer emhttpd: read SMART /dev/sdb
Nov 17 12:57:55 SSHomeServer kernel: mdcmd (570): set md_write_method 1
Nov 17 12:57:55 SSHomeServer kernel: 
Nov 17 13:30:48 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 13:33:47 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 14:35:15 SSHomeServer emhttpd: spinning down /dev/sdb
Nov 17 14:35:45 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 14:35:45 SSHomeServer emhttpd: spinning down /dev/sdc
Nov 17 14:37:56 SSHomeServer kernel: mdcmd (571): set md_write_method 0
Nov 17 14:37:56 SSHomeServer kernel: 
Nov 17 14:38:46 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 14:38:46 SSHomeServer emhttpd: read SMART /dev/sdc
Nov 17 14:51:17 SSHomeServer emhttpd: read SMART /dev/sdb
Nov 17 14:52:56 SSHomeServer kernel: mdcmd (572): set md_write_method 1
Nov 17 14:52:56 SSHomeServer kernel: 
Nov 17 15:40:42 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 15:43:46 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 16:10:52 SSHomeServer emhttpd: spinning down /dev/sdf
Nov 17 16:45:39 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 16:45:39 SSHomeServer emhttpd: spinning down /dev/sdc
Nov 17 16:47:56 SSHomeServer kernel: mdcmd (573): set md_write_method 0
Nov 17 16:47:56 SSHomeServer kernel: 
Nov 17 16:48:54 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 16:48:54 SSHomeServer emhttpd: read SMART /dev/sdc
Nov 17 16:52:56 SSHomeServer kernel: mdcmd (574): set md_write_method 1
Nov 17 16:52:56 SSHomeServer kernel: 
Nov 17 18:08:05 SSHomeServer rpc.mountd[6656]: v4.2 client attached: 0x49e739fa6702072b from "192.168.1.223:995"
Nov 17 18:11:53 SSHomeServer emhttpd: read SMART /dev/sdf
Nov 17 18:50:30 SSHomeServer emhttpd: spinning down /dev/sdd
Nov 17 18:50:30 SSHomeServer emhttpd: spinning down /dev/sdc
Nov 17 18:52:57 SSHomeServer kernel: mdcmd (575): set md_write_method 0
Nov 17 18:52:57 SSHomeServer kernel: 
Nov 17 18:53:45 SSHomeServer emhttpd: read SMART /dev/sdd
Nov 17 18:53:45 SSHomeServer emhttpd: read SMART /dev/sdc
Nov 17 18:57:57 SSHomeServer kernel: mdcmd (576): set md_write_method 1
Nov 17 18:57:57 SSHomeServer kernel: 
Nov 17 18:58:48 SSHomeServer root: Fix Common Problems Version 2024.11.12
Nov 17 18:58:49 SSHomeServer root: Fix Common Problems: Error: parity (WDC_WD140EMFZ-11A0WA0_9RJ8331C) has read erro

It looks like you may have been running smart on all the drives though.
Under Dashbaord is there a orange icon with a thums down?

if so click the thub and mark it cleard as smart shows a pass.

 

oh i need to scroll up more theres quite a bit of disk errors:

Nov 12 23:02:21 SSHomeServer kernel: ata4.00: exception Emask 0x10 SAct 0x220000 SErr 0x4090000 action 0xe frozen
Nov 12 23:02:21 SSHomeServer kernel: ata4.00: irq_stat 0x00400040, connection status changed
Nov 12 23:02:21 SSHomeServer kernel: ata4: SError: { PHYRdyChg 10B8B DevExch }
Nov 12 23:02:21 SSHomeServer kernel: ata4.00: failed command: READ FPDMA QUEUED
Nov 12 23:02:21 SSHomeServer kernel: ata4.00: cmd 60/20:88:98:00:00/00:00:80:02:00/40 tag 17 ncq dma 16384 in
Nov 12 23:02:21 SSHomeServer kernel:         res 40/00:00:20:00:00/00:00:80:02:00/40 Emask 0x10 (ATA bus error)

Nov 12 23:02:27 SSHomeServer kernel: ata4: link is slow to respond, please be patient (ready=0)
Nov 12 23:02:31 SSHomeServer kernel: ata4: COMRESET failed (errno=-16)
Nov 12 23:02:31 SSHomeServer kernel: ata4: hard resetting link
Nov 12 23:02:32 SSHomeServer kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Nov 12 23:02:32 SSHomeServer kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Nov 12 23:02:32 SSHomeServer kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out
Nov 12 23:02:32 SSHomeServer kernel: ata4.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Nov 12 23:02:32 SSHomeServer kernel: ata4.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out
Nov 12 23:02:32 SSHomeServer kernel: ata4.00: configured for UDMA/33
Nov 12 23:02:32 SSHomeServer kernel: ata4: EH complete


what HBA / SAS conection are you using?

Shutdown the system and check cables..

 

The disk errors in the logs suggest that the issue is related to one of the drives connected to the SATA port (ata4.00). Here are possible causes based on the errors:

SATA Cable Issues:

Loose or Faulty Cable: A common cause of such errors is a loose or damaged SATA cable. Try reseating the cable or replacing it with a known-good one.

Poor Cable Quality: Ensure the cable is of good quality and not damaged.

Power Supply Problem:

Inconsistent Power Delivery: If the drive is not receiving stable power, it can result in errors. Check the power connection to the drive and the capacity of your power supply.

Drive Failure:

Hardware Issues: The drive itself may be failing. Run a detailed SMART test to check the health of the drive.

Firmware Issues: Outdated drive firmware can sometimes cause compatibility issues.

SATA Port Issues:

Faulty Port: If the SATA port on the motherboard is damaged, try connecting the drive to a different port.

SATA Controller Problems: The controller on the motherboard could be experiencing issues.

Drive Configuration:

NCQ or DMA Settings: Some drives have issues with Native Command Queuing (NCQ) or Direct Memory Access (DMA). Consider disabling these settings in your BIOS or using a tool like hdparm.

Temperature or Environmental Factors:

Overheating: If the drive is overheating, it may cause errors. Ensure proper cooling for the drive.

Software/Driver Issues:

Unraid Configuration: There might be issues with how Unraid is interfacing with the drive. Check for updates or known issues with your Unraid version.

Filesystem Issues: Corruption in the file system can also manifest as drive errors.

Edited November 18, 20241 yr by bmartino1

My bet atm is a lose cable of some kind.

Check SATA Controller or BIOS

Some SATA controllers can cause compatibility issues with specific drives or Unraid settings.

Steps:

If using a third-party controller (e.g., PCIe SATA expansion card), try another controller or port.

Ensure the BIOS/UEFI settings are optimized:

Set the SATA mode to AHCI (not IDE or RAID).

Disable features like NCQ if supported by your BIOS.

 

Unraid-Specific Troubleshooting:

Rebuild Disk: If the disk is part of the Unraid array and suspect, consider rebuilding it:

Stop the array.

Remove the drive from the configuration.

Reassign and rebuild the disk.

Disable Turbo Write (Reconstruct Write):

The logs indicate changes in write methods (md_write_method).

Use the Read/Modify/Write mode and observe if errors persist.

Thanks a lot for your response.

 

I was using SAS before but now i am using just 3 SATA drives. Let me order new cables.

 

After changing cables, i will run the detailed SMART scan.  Thanks again for your help.