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
SendAsyncWebRequest vs SendWebRequest
Paul Timms
SendWebRequest3 is a boolean function, so if this returns true and the reply header has an accepted status, you can assume that the data was sent successfully and perform some actions on the record th...
11:12 4 Apr 2025
Re: Periodic Customer Statement variance(overview vs detailed mode)
Aldevinas Katkus
same v. 2025-02-24. New DB. Just forward balances (purchase, sales invoices) from 2024 and later. In your case does turnover per period differs or just fwd. balance differs and turnover is identical i...
09:56 20 Mar 2025