Axel, could it depend on your hardware? From what I've seen, the error
only occurs when scanning/adding not SMART capable devices, so perhaps
if you only have internal HDDs or SMART capable usb drives you could
avoid the crash. Try connecting some old USB or FW enclosure.
Apparently, the versions of gsmartcontrol (0.8.7) and smartmontools
(6.2) shipped with debian are not compatible with each other: on the
official website (
http://gsmartcontrol.berlios.de/home/index.php/en/Home ) I haven't found
anything about the required version of smartmontools, but the release
note for 0.8.7 is dated 2012-08-11 (and says it ships smartmontools 5.43
with the windows version), and looking at
http://sourceforge.net/apps/trac/smartmontools/wiki I see that in that
date indeed smartmontools v5.43 had just been released and v6 had not
yet been. gsmartcontrol has never been updated since.
I installed an older version of smartmontools (5.43 from LMDE) and the
bug disappeared. From what I've seen, the output from smartmontools is
slightly different between the two versions; could the problem arise
from that? For example, on my computer gsmartcontrol crashes when
probing the drive unit (/dev/sr0). I manually ran the same command
gsmartcontrol uses and the output was:
- using smartmontools 5.43,
$%sudo 'smartctl' -T permissive -i -H -c '/dev/sr0'
smartctl 5.43 2012-06-05 r3561 [x86_64-linux-3.11.8-desktop-f] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
Vendor: TSSTcorp
Product: CD/DVDW TS-H552L
Revision: 0614
>> Terminate command early due to bad response to IEC mode page
- using smartmontools 6.2,
$%sudo 'smartctl' -T permissive -i -H -c '/dev/sr0'
smartctl 6.2 2013-07-26 r3841 [x86_64-linux-3.11.8-desktop-f] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: TSSTcorp
Product: CD/DVDW TS-H552L
Revision: 0614
>> Terminate command early due to bad response to IEC mode page
=== START OF READ SMART DATA SECTION ===
The exit status was 2 in both cases, but as you can see, v6.2 outputs
some more lines (the ones starting with ===). Those lines are also
present in 5.43 for drives which have SMART capability, but not for
those who don't; in 6.2 they are present in the output regardless of the
SMART capabilities of the drive. I believe the error must have to do
with that.
I'll paste one further example, obtained with smartmontools 5.43: one
drive which has smart capabilities and one who doesn't. Again, version
6.2 prints both lines starting with === for both drives.
$%sudo 'smartctl' -T permissive -i -H -c '/dev/sda'
smartctl 5.43 2012-06-05 r3561 [x86_64-linux-3.11.8-desktop-f] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Fujitsu MHV
Device Model: FUJITSU MHV2100BH PL
Serial Number: NW9YT6B2H7AY
Firmware Version: 892C
User Capacity: 100,030,242,816 bytes [100 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: ATA/ATAPI-7 T13 1532D revision 4a
Local Time is: Wed Jan 22 22:00:41 2014 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
[...]
$%sudo 'smartctl' -T permissive -i -H -c '/dev/sdd'
smartctl 5.43 2012-06-05 r3561 [x86_64-linux-3.11.8-desktop-f] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
Vendor: Maxtor 7
Product: Y250P0
Revision: YAR4
User Capacity: 251,000,193,024 bytes [251 GB]
Logical block size: 512 bytes
Logical Unit id: 0x00d04b530704a31b
Serial number: Y65GHQBE
Device type: simplified disk
Local Time is: Wed Jan 22 22:00:48 2014 CET
Device does not support SMART
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
