Bug 29424 - Вылетает, не может получить список дисков
Summary: Вылетает, не может получить список дисков
Status: CLOSED FIXED
Alias: None
Product: Sisyphus
Classification: Development
Component: gsmartcontrol (show other bugs)
Version: unstable
Hardware: all Linux
: P3 normal
Assignee: Evgenii Terechkov
QA Contact: qa-sisyphus
URL: http://gsmartcontrol.sourceforge.net/...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-10-02 21:37 MSK by Vyacheslav Dikonov
Modified: 2015-10-07 08:25 MSK (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vyacheslav Dikonov 2013-10-02 21:37:00 MSK
Пакет gsmartcontrol не работает следующим образом:

При первом запуске просит вручную указать путь к smartctl (smartmontools установлен и работает). При этом список устройств пуст. После задания пути сканирование устройств приводит к падению оболочки gsmartcontrol cо следующей руганью:

bash-3.2$ gsmartcontrol
<warn>  [hz] Warning: exit: Device open failed, or device did not return an IDENTIFY DEVICE structure.
<warn>  [app] execute_smartctl(): Error while executing smartctl binary.
<warn>  [app] StorageDevice::execute_device_smartctl(): Error while executing smartctl binary.
<warn>  [hz] Warning: exit: Device open failed, or device did not return an IDENTIFY DEVICE structure.
<warn>  [app] execute_smartctl(): Error while executing smartctl binary.
<warn>  [app] StorageDevice::execute_device_smartctl(): Error while executing smartctl binary.
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Vendor"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Product"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Revision"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Logical block size"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Device type"
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::substr
Аварийный останов
bash-3.2$ 

Сканирование делается при запуске, так что вылет случается сразу после запуска.

$ sudo smartctl --scan
/dev/sda -d scsi # /dev/sda, SCSI device
/dev/sdb -d scsi # /dev/sdb, SCSI device

$ sudo smartctl --info /dev/sdb
smartctl 6.2 2013-07-26 r3841 [i686-linux-3.10.13-std-pae-alt1] (ALT Linux 6.2-alt1)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org


Имеется неизвестный smartmontools винт:
=== START OF INFORMATION SECTION ===
Device Model:     ST3000NC002-1DY166
Serial Number:    Z1F1F0W2
LU WWN Device Id: 5 000c50 04eb3616a
Firmware Version: CN02
User Capacity:    3 000 592 982 016 bytes [3,00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    7200 rpm
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s)
Local Time is:    Wed Oct  2 21:35:14 2013 MSK
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
Comment 1 Evgenii Terechkov 2014-03-11 10:36:36 MSK
Тоже словил:
=============================================================================
teer@teer ~ $gsmartcontrol-root 
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Rotation Rate"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Rotation Rate"
<warn>  [app] SmartctlParser::parse_section_info_property(): Unknown property "Rotation Rate"
<warn>  [hz] Warning: exit: Command line did not parse.
<warn>  [app] execute_smartctl(): Error while executing smartctl binary.
<warn>  [app] StorageDevice::execute_device_smartctl(): Error while executing smartctl binary.
terminate called after throwing an instance of 'std::out_of_range'
  what():  basic_string::substr
=============================================================================

Кстати, в 2012-м уже вышла версия 0.8.7.
Comment 2 Evgenii Terechkov 2014-08-20 08:16:07 MSK
Похоже, придется самому заняться...
Comment 3 Evgenii Terechkov 2015-10-07 08:24:51 MSK
Похоже, починилось в 0.8.7.