failed to detect tape block size Case #07038467

[GMVHS]

Hello,

we have trouble with our TapeDrive. OS is a w2019 and the tapedrive is a HP LTO-6 Ultrium 6250. Has anybody this combination running?
We use B & R Version 12

thanks

[Dima P.]

Hello GMVHS,

Try to find the biggest supported block size for your tape drives (should be somewhere in the vendors software or specification) and set the same value manually in the tape drive properties in Veeam B&R Console. Thank you!

[GMVHS]

Hello,

the value in Veeam was allready set to 65536 Bytes. In the Veeam Console i have no possibility to change the value.
There is no vendor software, so i can't change blocksize.

i must say, we have upgraded from w2012r2 up to w2019 with a new Installation. Everything goes fine except the tape.

Thanks for any hints

[GMVHS]

Hello,

a partial solution is given with the HP Library & Tape tool. Erasing the tape with option "quick" and the tape is ready to be written.

Missing is a possibility to read the older used tapes, example for recovering or so...

GM

[Dima P.]

Hello GM,

Thank you for sharing the news and glad that you got a workaround.

Missing is a possibility to read the older used tapes, example for recovering or so...

Should not be an issue when your are using tapes written by Veeam because we always set the documented / allowed block size values.

[JoshS]

I wouldn't usually bump a thread this old but this is the top Google search for this error, which we similarly encountered on an HPE server.

We found this to be due to the default Windows drivers for the HBA, and resolved it after installing the HPE drivers. Although this download is two years old, it's the latest for a range of HPE HBAs and it resolved this issue:

https://support.hpe.com/connect/s/softw ... 8d0886ae74

[devlopur]

Hey,

I ran into the same problem but somehow it's keep showing me error. some help me to fix it

Thanks

[Vodochnik]

@devlopur

Try to quick erase a tape in some other tool (you have not provided any details about your drive/library)
Please check similar topic: post503316.html#p503316

[IanW_82]

I wouldn't usually bump a thread this old but this is the top Google search for this error, which we similarly encountered on an HPE server.

We found this to be due to the default Windows drivers for the HBA, and resolved it after installing the HPE drivers. Although this download is two years old, it's the latest for a range of HPE HBAs and it resolved this issue:

https://support.hpe.com/connect/s/softw ... 8d0886ae74

Thank you for the link, I've been trying to fix this issue for a couple of days following a server rebuild from 2012 R2 to 2019.