It all started when i was recieving very slow copy speeds on my array (around 200kbps) so i then rebooted the server only to find one of my drives had parents transid error, then i then attached another 16tb drive and followed the official data recovery guide and recovered all my data to new drive using btrfs rescue but now both the drives are unmountable with the exact same parent transid verify failed error (screenshot attached)

apart from this one of my other drives constantly gives me READ FPDMA QUEUED and disabling NCQ just changed the error given to READ DMA EXT thus making the data rebuilding process impossible as it runs at speeds of less than a MBps

I changed ports and swapped all the cables to new ones, still didnt help

I sometimes also get READ FPDMA QUEUED on other drives but a restart fixes it, i have exhausted all my possible fixes

i have total 8 sata devices, 4 on my mobo and 4 on a nvme to 5 port sata with a JSM controller as recommended by unraid, also READ FPDMA Errors can come on both mobo and card sata ports

PS. sometimes i also get 

COMRESET failed (errno=-16), but it usually dissappears within seconds

 

Also the drives giving the READ FPDMA QUEUED Errors is fine as it passed the smart tests and if i copy data from it using Midnight commander,  im not getting any errors and getting very stable speeds

kassandra-diagnostics-20241202-0215.zip

Edited December 1, 20241 yr by Vyktrii

Swap disk2 cables with a different disk and post new diags.

3 hours ago, JorgeB said:

Swap disk2 cables with a different disk and post new diags.

I tried that didnt help, but for some reason swapping the sata cables from the problematic HDDs to the sata SSDs solved the issue of comreset and read fpdma errors, but my issue of unmountable disk still remains, i doubt if my parity disk is ok after so many sata errors, so shall i recover my data by rebuilding the drive, or shall i again use btrfs recover (but that did give me mounting errors on the drive it was recovered to (screenshot in original post)

Edited December 2, 20241 yr by Vyktrii

36 minutes ago, Vyktrii said:

but my issue of unmountable disk still remains,

Post new diags.

kassandra-diagnostics-20241202-1854.zip

parent transid verify failed on logical 25903104 mirror 1 wanted 6897 found 6892

 

This error is typically fatal with btrfs, it means some writes were lost and the device/controller lied about it, btrfs restore can sometimes recover the data, 2nd option here:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-543490

 

3 hours ago, JorgeB said:

parent transid verify failed on logical 25903104 mirror 1 wanted 6897 found 6892

 

This error is typically fatal with btrfs, it means some writes were lost and the device/controller lied about it, btrfs restore can sometimes recover the data, 2nd option here:

 

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/page/2/#findComment-543490

 

my problem is that using the guide indeed restores my data to a new 16Tb drive, but then after a reboot, the drive to which the data was restored gives the similar error to the point where both drives say wanted “6897 found 6892”, like in the screenshot where both sdb1 and sde1 are giving the same error

11 minutes ago, Vyktrii said:

the drive to which the data was restored gives the similar error to the point where both drives say wanted “6897 found 6892”

That would mean that filesystem also has filesystem corruption issues, unrelated to btrfs the restore, but seems extremely unlikely that two filesystems would have issues with the exact same transid.

 

Also note that you can restore to a disk/pool using a different filesystem.

On 12/2/2024 at 11:14 PM, JorgeB said:

That would mean that filesystem also has filesystem corruption issues, unrelated to btrfs the restore, but seems extremely unlikely that two filesystems would have issues with the exact same transid.

 

Also note that you can restore to a disk/pool using a different filesystem.

So I finally finally restored data from my failed HDD to Disk 4 in my array (using btrfs restore), but now im encountering another problem, out of all of 14.5 TB of data, everything was recovered almost, except around 140gb of data, and the reason being unraid doesnt let me write anymore files to disk 4, as soon as i start to write anything it slows down to mere 400kbps after 5gb, it just writes exactly 5.6GB (tried with different files) and then says space unavailble, tried in both Krusader and MC, i think brfs restore was also stopped due to this issue, Since i ran preclear on the disk and everything was ok,  but why isnt the disk letting me write anything even though there is 360gb free ?, 
does this issue havev to do anything with the parity drive?, maybe the parity drive isnt letting me write data or something ?
also can i recover partly using the BTRFS recover command from my old disk, ik exactly whats missing as i tallied my data manually

 

Also i tried using new permissions thing, didnt help

kassandra-diagnostics-20241207-0121.zip

Edited December 6, 20241 yr by Vyktrii

Could be the share floor setting, which share are you writing to?

On 12/7/2024 at 2:23 PM, JorgeB said:

Could be the share floor setting, which share are you writing to?

I was writing directly to the disk and the minimum share space setting is well below the free space

Edited December 8, 20241 yr by Vyktrii

Try using a different tool, I'm not familiar with Kruzader, and if it fails post new diags and the paths used.

On 12/8/2024 at 5:18 PM, JorgeB said:

Try using a different tool, I'm not familiar with Kruzader, and if it fails post new diags and the paths used.

I changed the HDD and now the data was fully recovered, but it seems that i have just shifted and delayed the problem as a unassigned drive is now experiencing the read fpdma errors, but atleast my array is working, but i think this issue could come back to my array disks, can a a faulty PSU be the reason for these errors ? Im currently using a silverstone ES230 PSU, which is an 80+ PSU but has fairly powerful 5V output (110w) for HDDs (im using 8 of them)

Edited December 10, 20241 yr by Vyktrii

14 hours ago, Vyktrii said:

can a a faulty PSU be the reason for these errors ?

It can, power and SATA cables can also be a problem.

On 12/11/2024 at 2:23 PM, JorgeB said:

It can, power and SATA cables can also be a problem.

It was the PSU, i replaced it and i am now getting no errors even after running the system on full load for past 24hours