Q&A
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?
Reply
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
Reply
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.
Reply
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.
Reply
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
Re: Parameters that can be specified in the parameters.txt file
Paul Timms
Hi Andis, if you go to Support > FAQ, there's a section containing all of the known parameters. Paul...
15:06 11 Sep 2026
Parameter --skip-register-on-import
Paul Timms
Is it possible to use the parameter --skip-register-on-import with multiple registers, either by using a comma-separated string or by specifying this parameter multiple times in parameters.txt? Thi...
15:00 11 Sep 2026