After update to 7.2.3 unraid starts to corrupt my single drive pool for media, i have rebuilt the drives several times xfs and btrfs also changed 4 different drives and changed data cables and sata ports. This occurred after the update to 7.2.3 i am downgrading now to 7.2.2 to see if it fixes the problem...

vault-187-diagnostics-20260108_2011.zip

Edited January 8Jan 8 by grohotnius

Edit2: getting ahead of myself. There seems to be hardware issues related to the sata controller and or disk sde

how are these connected to the system and/or are you using power splitters?

Edited January 8Jan 8 by MowMdown

Hi. Thanks for getting back to me.

The single drive is connected directly to the motherboard sata conector and its a mehanical drive 4tb. I also have 2 ssd drives that are connected to the sata on the motherboard.

one ssd for app-data , another for media storage, and an nmve cache drive all single drives formated to brtfs and xfs and i have no problems with them no data loss.

There are no power spliters like molex to sata.

So i have tried out several 1 to 4 tb drives that are older but known good drives tested with hard disk sentinel all are 100%.

I agree, i think it is a hardware problem by the faults i am having, but i have replaced everything in the chain- sata port-sata cable-hdd-difrent power cable port several times and multiple hdd.

Once you replace everything in the chain for me it looks like a software problem.

Now i have downgraded the os to 7.2.2 and it seems to work the drive is taking in the data and the data is browsable over the network and keeps its integrity. I am rebuilding the media drive now again.

PS.-- The problem i had with the drive was the data files where visible, but when you access them or try to open you cant reed it or copy it.

So to not lose my mind i will also try an ssd on the same port -cable and power and rebuild the drive and i will se how it goes.

I have experience with windows 2012 server and freenas and when i had a problem similar to this it turned to be a problem with the update......mostly a software problem due to the combination of used hardware.

Thanks for taking the time......

Edited January 8Jan 8 by grohotnius

9 hours ago, grohotnius said:

This occurred after the update to 7.2.3 i am downgrading now to 7.2.2 to see if it fixes the problem...

This seems extremely unlikely, as there are no changes that would explain that; the kernel is the same.

There's an apparent issue with the controller, affecting both ports:

Jan 8 20:11:48 Vault-187 kernel: ata7: link is slow to respond, please be patient (ready=0)

Jan 8 20:11:48 Vault-187 kernel: ata8: link is slow to respond, please be patient (ready=0)

Jan 8 20:11:52 Vault-187 kernel: ata7: found unknown device (class 0)

Jan 8 20:11:52 Vault-187 kernel: ata8: found unknown device (class 0)

Jan 8 20:11:52 Vault-187 kernel: ata7: found unknown device (class 0)

Jan 8 20:11:52 Vault-187 kernel: ata7: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Jan 8 20:11:52 Vault-187 kernel: ata8: found unknown device (class 0)

Jan 8 20:11:52 Vault-187 kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)

Jan 8 20:11:57 Vault-187 kernel: ata7.00: qc timeout after 5000 msecs (cmd 0xec)

Jan 8 20:11:57 Vault-187 kernel: ata7.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Jan 8 20:11:57 Vault-187 kernel: ata7.00: revalidation failed (errno=-5)

Jan 8 20:11:57 Vault-187 kernel: ata8.00: qc timeout after 5000 msecs (cmd 0xec)

Jan 8 20:11:57 Vault-187 kernel: ata8.00: failed to IDENTIFY (I/O error, err_mask=0x4)

Jan 8 20:11:57 Vault-187 kernel: ata8.00: revalidation failed (errno=-5)

Jan 8 20:11:57 Vault-187 kernel: ata8: hard resetting link

Jan 8 20:11:58 Vault-187 kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 300)