Damaged database with a message "Fatal disk error: Bad file number"
Kristaps Žogots
9-1-22
Operating system: macOS
If linux server gets message "Fatal disk error: Bad file number", it means the database is damaged. What could be the reason for such an error? Is it something we can prevent?
9-5-22
Hi,

Unfortunately this error can occur in many cases. It can refer to some import file from an external system, that isn't imported correctly

Do you know when this started happening?
Is it repeatable in latest version with same DB (+HAL)?
Have you used debug-detailed parameter on server for more specific information?

Brgds,
Rasmus
Brittany McGrath
10-19-22
Hi Kristaps,
Can you please confirm if this issue is still outstanding or if it has been resolved?
Thank you.
Brittany McGrath
10-31-22
Marking forum post as closed now as we have not received further response.
If you have any issues or questions you wish to discuss on this please open a new post.
Thank you in advance.
Leave Comment
You can subscribe to notifications for this post by selecting the 'star' icon on the top right corner of the post.
Back to the list
Latest Posts
Piotr Wycichowski
We are now in version 8.5 260126/85561338 and still the problem occurs. I will try to report a bug. /Piotr W....
09:36 23 Apr 2026
Andis Blicāns, Grasko
Thank You for answer. In this case I used SSLNoCertificateValidation = true; SendWebRequest SSLNoCertificateValidation = false; ...
23:01 24 Mar 2026