Replaced an older 2TB HDD with a fresh 18TB HDD. 

 

I formatted the 18TB as xfs prior to adding it to the array but I didn't preclear it. The rebuild process appeared to be operating normally however, it has stopped at 33.5% completed.

 

Data-Rebuild in progress.

Total size: 18 TB

Elapsed time: 1 day, 6 hours, 29 minutes

Current position: 6.03 TB (33.5 %)

Estimated speed: 191.2 MB/sec

Estimated finish: 17 hours, 23 minutes

Sync errors corrected: 0

 

I am unable to download a diagnostic report... it hangs at the step "df -h 2>/dev/null|todos >'/tower-diagnostics-20240422-0816/system/df.txt'"

 

I will include my System/Enhanced System logs.

 

I still have the old 2TB HDD. I am on the verge of attempting a shutdown and rebuild using the original 2TB HDD but thought it wise to seek expert advice first.

 

🙏

 

Kev Smith

Unraid server Pro, version 6.12.10

Motherboard: ASRock EP2C602-4L/D16

Processor: Intel® Xeon® CPU E5-2670 0 @ 2.60GHz

Memory: 128 GiB DDR3 Multi-bit ECC

Kernel: Linux 6.1.79-Unraid x86_64

 

tower-syslog-20240422-0041.zip tower-syslog-20240422-0841.zip

Edited April 22, 20242 yr by Kevlar75
typo

Try rebooting and attempt another rebuild, may be a good idea to replace the cables for ATA14 first.

The end of both logs finishes with errors along the lines of:

Apr 22 08:33:48 Tower kernel: ata14.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
Apr 22 08:33:48 Tower kernel: ata14.00: irq_stat 0x40000001
Apr 22 08:33:48 Tower kernel: ata14.00: cmd a0/01:00:00:00:01/00:00:00:00:00/a0 tag 7 dma 16640 in
Apr 22 08:33:48 Tower kernel:         opcode=0x12 12 01 80 00 ff 00res 00/00:00:00:00:00/00:00:00:00:00/00 Emask 0x3 (HSM violation)
Apr 22 08:33:48 Tower kernel: ata14: hard resetting link

Normally we would think these were power/sata cabling related but the fact it has occurred at the same point twice suggest it may really be a drive problem if ata14 is the new drive.

Thanks for the input. I have rebooted and it appears the rebuild was successful. I did move the new 18TB replacement drive to a different drive bay in case it was a cabling issue. I plan on doing a parity check to confirm the rebuild.

 

I will include my diagnostic file but all appears fine now.

 

Thanks again for your support.

tower-diagnostics-20240422-1655.zip

Looks OK for now, no more ATA errors.