Custom Query (1566 matches)
Results (478 - 480 of 1566)
| Ticket | Resolution | Summary | Owner | Reporter | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| #89 | fixed | Use log directory to check for old error/self-test log support | ||||||||||||||||||||
| Description |
Smartctl and smartd assume that the old SMART error log (log address 0x01) is supported if an error-logging capability bit in IDENTIFY or SMART data is set. Same applies to old SMART self-test log (log address 0x06). These logs were introduced in ATA-5 and are now outdated because 48-bit LBA addresses are not supported. Recent devices may only support the newer 48-bit capable logs (extended comprehensive error-log, extended self-test log) introduced in ATA-6.
Error SMART Error Log Read failed: Input/output error Smartctl: SMART Error Log Read Failed Error SMART Error Self-Test Log Read failed: Input/output error Smartctl: SMART Self Test Log Read Failed Misleading kernel messages may appear during smartd startup: ... kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
... kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
... kernel: ide: failed opcode was: 0xb0
... smartd[...]: Device: /dev/hda, Read SMART Self Test Log Failed
... smartd[...]: Device: /dev/hda, no SMART Self-Test log; remove -l selftest Directive from smartd.conf
(
Smartctl and smartd should read the log directory (log address 0x00) to check whether the old logs are still supported and print an " |
|||||||||||||||||||||
| #309 | wontfix | Use drive letter of Truecrypt mounted drive in Windows | ||||||||||||||||||||
| Description |
Trying to use smartctl to access a truecrypt mounted drive in Windows using the drive letter. Smartctl says "Function not implemented". When I use the device name (e.g. /dev/sdb) everything works fine. See sample output below. C:\>smartctl --health F: smartctl 6.2 2013-07-26 r3841 [x86_64-w64-mingw32-win7-sp1] (sf-6.2-1) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org Standard Inquiry (36 bytes) failed [Function not implemented] Retrying with a 64 byte Standard Inquiry Standard Inquiry (64 bytes) failed [Function not implemented] A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. |
|||||||||||||||||||||
| #1419 | fixed | Upgrade website to use Trac 1.6/Python3 | ||||||||||||||||||||
| Description |
Problem descriptionOur trac is using Py2 which is EOL ~1yr already We are using EdgeWall trac to manage smartmontools project, as well as few plugins which are written on Py27, which is EOL from January 1, 2020 already. As result py2 is no longer receiving any fixes (including security) and is getting slowly removed from the upstream packages. E.g. in the FreeBSD which we are using to host this instance, trac is already marked as "depricated" and soon will be removed due to py27 dependency. Upstream project is slowly moving to py3, however it is still in "development" branch only (Trac-1.5.2-py3-none-any.whl). Even after removal from the upstream i will be able to continue to host this trac instance (e.g. using jail and installation using pip2), but it will take more efforts and will give us more and more security concerns. Installed pluginsPlugins for trac are also written on py2 and will require upgrade or rewrite
Possible options
|
|||||||||||||||||||||
