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
Hi, Thank you for reaching out! What error do you get in server log and client log when you run the report? Please check that you have Multi Thread activated in Systems>>Settings>>O...
09:10 15 Apr 2024
Hello, Thank you for reaching out! We did testing in sample data in current released version 2024-03-16. This is not repeatable with this combination. We recommend you to report this as a bug w...
09:08 15 Apr 2024