- Only ATA drives (both PATA and SATA), various USB to ATA bridges and drives behind some RAID controllers are supported for now. The main reasons are:
- We can't support drives which don't work with smartmontools. This affects drives which don't support SMART or don't export SMART data correctly (e.g. some USB enclosures, RAIDs, etc...).
- Smartctl's output for SCSI drives is completely different compared to ATA. Also, SCSI drives are rarely found in desktop systems and the servers rarely have X11 / Gtkmm running, so this is a low priority task.
- I only have ATA drives, so testing anything else is very difficult.
- Immediate Offline Tests are not supported. I haven't found a way to reliably monitor them yet. Besides, they run automatically anyway if Automatic Offline Data Collection is enabled.
- Testing is only supported on drives which correctly report their progress information in capabilities.
- Not all drives support disabling Automatic Offline Data Collection, even if they report otherwise. Unfortunately, there's no way to detect such drives.
- Running on GTK+ / Gtkmm versions earlier than 2.12 may cause visual artifacts, usability issues (especially with tooltips and icons), instability, etc...
- The texts probably contain a lot of grammatical errors, English being my third language and all.
If it is a SMART or drive-related problem, please try to test it with smartctl first. Chances are, the problem you're experiencing is not tied to GSmartControl, but is a drive firmware or smartctl problem. For example, to see a complete information about your /dev/sda drive, type the following in a terminal emulator (e.g., xterm, konsole or gnome-terminal):
smartctl -a /dev/sda
Note: If using Windows, the device name should be
/dev/pd1 for the second
physical drive, etc...
If you still think it's a GSmartControl issue, please collect the following information about your system. Without it, it may be very hard or impossible to fix the bug.
- Which operating system you use (for example, openSUSE Linux 13.1).
- Which version of GTK and Gtkmm you have installed. Finding this out is very distribution-specific. For example, on openSUSE it would be
rpm -q gtk2 gtkmm2. Some distributions have gtkmm24 instead. You may also search them in your distribution's graphical package manager, if there is one.
- Execution log from the program, if possible. To obtain it, run the program with
-voption, e.g. (type the following in a terminal emulator or Run dialog):
gsmartcontrol-root auto -v
Perform the steps needed to reproduce the bug, then go to "Options -> View Execution Log", and click "Save All".
Note: On Windows, run
-vswitch as Administrator.
- Detailed description of steps you performed when the bug occurred.
Once you have this information, send an email to me, Alexander Shaduri <ashaduri 'at' gmail.com>. Note that I may refer you to smartmontools support if it's a bug in smartmontools and not GSmartControl. Normally, I won't redirect your support request to them myself, because they may ask questions which only you have the answers to.
Please read the License page, Patch Licensing section before sending any patches.
You may contact me directly at Alexander Shaduri <ashaduri 'at' gmail.com>.