Runtime error 203

[Jeremy59]

Hi,
I tried with different versions of hd-Sentinel for linux. I always have a "Runtime error" type error.
With the last verion 020c, I have this error :

runtime_error.jpg (13.15 KiB) Viewed 3431 times

I am under openSUSE Leap 15.6

Thanks for your help.
regards
Jeremy

[hdsentinel]

Sorry for the troubles. Sounds really interesting.
Probably related to one or more disk(s) / device(s). If possible, I recommend to try to disconnect some drive(s), external disks or so (if possible) just to verify which one(s) may be related.

Also I suggest to start the Linux version with the following command line parameters:

./hdsentinel -enabletest -txt -r report.txt

This will log all detection steps / raw results between the software and the drives to testmode.txt and creates a report at the end (but probably the report file not created because of the error).

Please send the testmode.txt file (and the report.txt file if created) in e-mail to info (at) hdsentinel (dot) com address, so then it is possible to examine what may cause the problem in the operation.

[Jeremy59]

Sorry for the troubles. Sounds really interesting.
Probably related to one or more disk(s) / device(s). If possible, I recommend to try to disconnect some drive(s), external disks or so (if possible) just to verify which one(s) may be related.

Also I suggest to start the Linux version with the following command line parameters:

./hdsentinel -enabletest -txt -r report.txt

This will log all detection steps / raw results between the software and the drives to testmode.txt and creates a report at the end (but probably the report file not created because of the error).

Please send the testmode.txt file (and the report.txt file if created) in e-mail to info (at) hdsentinel (dot) com address, so then it is possible to examine what may cause the problem in the operation.

Thanks for your response.
In fact, I have this error with any parameters or no parameter

2025-01-18_09-00-21.jpg (21.1 KiB) Viewed 3031 times

I had to reinstall the server. HDSentinel was working fine for a few intermediate tests. But once the server preparation was complete and restarted, the problem reappeared.

Can you tell me if the application needs any specific accesses or libraries ?

[Jeremy59]

Sorry for the troubles. Sounds really interesting.
Probably related to one or more disk(s) / device(s). If possible, I recommend to try to disconnect some drive(s), external disks or so (if possible) just to verify which one(s) may be related.

Also I suggest to start the Linux version with the following command line parameters:

./hdsentinel -enabletest -txt -r report.txt

This will log all detection steps / raw results between the software and the drives to testmode.txt and creates a report at the end (but probably the report file not created because of the error).

Please send the testmode.txt file (and the report.txt file if created) in e-mail to info (at) hdsentinel (dot) com address, so then it is possible to examine what may cause the problem in the operation.

I found the origin of the problem with the "strace hdsentinel" command that I launched on the server where I have the error and the same command on a virtual machine which does not have the problem.

Result of "strace hdsentinel" on the server :

2025-01-18_12-12-54.jpg (659.23 KiB) Viewed 3026 times

Result of "strace hdsentinel" on the VM :

2025-01-18_13-45-41.jpg (144.81 KiB) Viewed 3026 times

On my server I have the empty directory /etc/timezone. This, does not exists on VM
So I removed that empty directory from my server and HdSentinel is running fine.

Perhaps a control could be added in HDSentinel to avoid this inconvenience?

[hdsentinel]

Thanks for checking and pointing on this.
Probably a compiler issue, as HDSentinel Linux code does not attempt to directly use the file, but probably a library attempts to open that during the init stage.

As I found, some other Linux apps may experience similar, eg.
https://doublecmd.h1n.ru/viewtopic.php?t=4289

I'll check how to add an extra protection against such issue. Thanks for your attention!