Ok I restarted. Then used binhex krusader to transfer files from disk3. This morning I had a "Unraid Parity Disk SMART Health [199]:04-04-2021 20:48 Warning [Tower] - udma crc error is 68 WDC-yada yada yada" this is parity disk 1.

 

So what does that mean after doing all those parity checks. Is the drive no bueno?

 

Also included the diag file.

tower-diagnostics-20210405-0810.zip

27 minutes ago, Cartierusm said:

This morning I had a "Unraid Parity Disk SMART Health [199]:04-04-2021 20:48 Warning [Tower] - udma crc error is 68 WDC-yada yada yada" this is parity disk 1.

...

Is the drive no bueno?

 

As discussed earlier in this thread  

On 4/3/2021 at 9:36 PM, trurl said:

Those are just CRC errors, they indicate a connection problem instead of a disk problem. You can acknowledge those by clicking on it in the Dashboard. It will warn you again if those increase.

 

And syslog is showing those again

Apr  4 19:15:55 Tower kernel: ata6.00: ATA-9: WDC WD80EFAX-68KNBN0, VAKBJVVL, 81.00A81, max UDMA/133
Apr  4 19:16:17 Tower kernel: md: import disk0: (sde) WDC_WD80EFAX-68KNBN0_VAKBJVVL size: 7814026532 
Apr  4 20:36:49 Tower kernel: ata6.00: exception Emask 0x10 SAct 0x0 SErr 0x280100 action 0x6 frozen
Apr  4 20:36:49 Tower kernel: ata6.00: irq_stat 0x08000000, interface fatal error
Apr  4 20:36:49 Tower kernel: ata6: SError: { UnrecovData 10B8B BadCRC }
Apr  4 20:36:49 Tower kernel: ata6.00: failed command: READ DMA EXT
Apr  4 20:36:49 Tower kernel: ata6.00: cmd 25/00:40:80:9f:0a/00:05:99:00:00/e0 tag 13 dma 688128 in
Apr  4 20:36:49 Tower kernel:         res 50/00:00:7f:9f:0a/00:00:99:00:00/40 Emask 0x10 (ATA bus error)
Apr  4 20:36:49 Tower kernel: ata6.00: status: { DRDY }
Apr  4 20:36:49 Tower kernel: ata6: hard resetting link

and more like that.

 

And an increased count from before so might be worthwhile to check those connections. Power and SATA, both ends, including splitters. Change SATA cable if you have a spare.

Ok thanks.

Ok I hate to be that guy, but what's the best way to take that disk 3 and reformat it so that my system/parity is intact when I'm done? I read the wiki, but seems like every time I do something there's 50 ways to do it. 

48 minutes ago, Cartierusm said:

take that disk 3 and reformat it so that my system/parity is intact when I'm done?

  

On 4/4/2021 at 9:49 PM, jonathanm said:

Parity is updated for all writes, including formatting to a new file system. I'd copy the data instead of moving it, much faster, and you can verify the copy is complete and intact before you format the drive.

 

Unraid parity is realtime. Any write operation to a data disk in the parity array updates parity at the same time. Format writes an empty filesystem to the disk. That write operation is treated just like any other with parity being updated at the same time.

 

Just in case you didn't get it, once you format that disk any data it had on it is gone. Did you copy it elsewhere?

 

52 minutes ago, Cartierusm said:

I read the wiki

https://wiki.unraid.net/UnRAID_6/Storage_Management#Converting_to_a_new_File_System_type

https://wiki.unraid.net/UnRAID_6/Storage_Management#Changing_a_File_System_type

 

Got it. Thanks. Yes copied everything. 

1 hour ago, Cartierusm said:

Ok I hate to be that guy, but what's the best way to take that disk 3 and reformat it so that my system/parity is intact when I'm done? I read the wiki, but seems like every time I do something there's 50 ways to do it. 

Reformatting a drive is covered here in the online documentation accessible via the ‘manual’ link at the bottom of the unRaid webGUI.

Thanks. Already completed!! We're up and running again. Also, I switched the bay that parity was in and so far so more crc errors.