Custom Query (1566 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (478 - 480 of 1566)

Ticket Resolution Summary Owner Reporter
#89 fixed Use log directory to check for old error/self-test log support Christian Franke Christian Franke
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.

smartctl -a ... prints misleading messages then:

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 -x ... is not affected)

Smartctl and smartd should read the log directory (log address 0x00) to check whether the old logs are still supported and print an "unsupported" message if not.

#309 wontfix Use drive letter of Truecrypt mounted drive in Windows somebody dgray512
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 Alex Samorukov Alex Samorukov
Description

Problem description

Our 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 plugins

Plugins for trac are also written on py2 and will require upgrade or rewrite

plugin description status
ManPageRendererPlugin renders our man pages very easy to port
TracAccountManager Manage Trac user accounts. Critical to have, not ported, complex to port, see ​https://trac-hacks.org/ticket/13720
TracRecaptchaRegister small plugin to show google re-captcha on the first reg. Should be trivial to port. depends on TracAccountManager
TracSpamFilter SPAM filtering for trac. Must have. complex to port, porting not yet started
TracTocMacro TOC macros for WIKI very easy to port

Possible options

  1. Start testing Trac 1.5/Devel to see how much efforts would take to move trac to it. Problem is that there is no timeline yet, and plugins still need to be ported (at least TracAccountManager which is very critical to us).
  2. Use other options, e.g. Github, which now provides WIKI, pages and other. Gitlab could be used as an alternative. Downside is that we will have to port our existing pages and wiki to it, however, that should be a one time job. This would also significantly change our release procedure.
  3. Do nothing and support trac/py2 as much as we can, e.g. using jail and self-built py. However, this is insecure and will not help us in the long term
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.