DELL 124T DriveTaflag (39) Error !!!!

Hello,

Do you have any stuck tapes?

Have you tried new tape?

I could recommend first steps: Update firmware and Run diagnostics

PowerVault PV124T Firmware Update directions

https://dell.to/3ZJKg9x

Current PowerVault 124T Firmware Update Release A24

https://dell.to/3ZKWNcF

Run Extended Diagnostics:

Access the web interface of your tape drive. Navigate to the "Error Logs and Diagnostics" section to run extended diagnostics.

Thank you for your answer

There is no tape stuck in the drive , The cleaning cartridge process completes successfully, but when I start the backup I get this error. The device versions are up to date. What other suggestions do you have?

Hello,

What is the tape drive model you have?

@DELL-Charles R​  IBM LTO 4 

Hello,

It seems like the tape drive may have a hardware fault.

Can you let us know the result of the extended diagnostic?

Login

Go to Diagnostics

Run Extended Diagnostics

Hi again , 

I will check and get back to you

<Private data removed from public view. DELL-Admin>

Hello Again

The problem persists, errors are indicated where marked in the picture.
I ask for your help

Good work

Hi,

if possible, swap the drive with a known-good one to see if the error persists. This can help you determine if the issue is specific to the drive or if it's a problem with your system.

The TA39 error code is often related to the drive's cleanliness. Sometimes, a stuck tape can cause this error to occur. To try and resolve this issue, use the web interface to attempt to eject the tape. This might help to dislodge any stuck particles or debris that could be causing the problem.

Hello,

the test steps you mentioned are unfortunately not available in the web interface. I will ask you to give me information about what to do.

Hi, Let's see how our community may help. I would do first two steps would be firmware updates and restart the tape drive. Sometimes, simply restarting the drive can resolve the issue.

all software is up to date. i have also tried rebooting many times but the problem is the same :(