Custom Query (1546 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (265 - 267 of 1546)

Ticket Resolution Summary Owner Reporter
#943 fixed NetBSD regression in smartmontools 6.6 Alex Samorukov
Description

Smartctl is broken on netbsd/sparc64 (BE) arch

To test if smartctl still works on be i installed NetBSD7.0/sparc64 in the qemu.

It was found that smart support is mostly broken.

bash-4.4# uname -a
NetBSD netbsd 7.0 NetBSD 7.0 (GENERIC.201509250726Z) sparc64
bash-4.4# ./smartctl -d ata /dev/wd0c -A
smartctl 6.7 2017-11-16 r4625 [NetBSD 7.0 sparc64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

Read SMART Data failed: request failed, error code 0x02

=== START OF READ SMART DATA SECTION ===
bash-4.4# ./smartctl -d ata /dev/wd0c -Ai
smartctl 6.7 2017-11-16 r4625 [NetBSD 7.0 sparc64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Device Model:     QEMU HARDDISK
Serial Number:    QM00001
Firmware Version: 2.5+
User Capacity:    5,368,709,120 bytes [5.36 GB]
Sector Size:      512 bytes logical/physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ATA/ATAPI-7, ATA/ATAPI-5 published, ANSI NCITS 340-2000
Local Time is:    Sun Nov 19 10:35:54 2017 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

Read SMART Data failed: request failed, error code 0x02

=== START OF READ SMART DATA SECTION ===

At the same time native tool works correctly:

bash-4.4# atactl wd0 smart status
SMART supported, SMART enabled
id value thresh crit collect reliability description                 raw
  1 100    6     yes online  positive    Raw read error rate         0
  3 100    0     yes online  positive    Spin-up time                16
  4 100   20     no  online  positive    Start/stop count            100
  5 100   36     yes online  positive    Reallocated sector count    0
  9 100    0     yes online  positive    Power-on hours count        1
 12 100    0     yes online  positive    Device power cycle count    0
190  69   50     yes online  positive    Airflow Temperature         31 Lifetime min/max 31/0

Links:

Todo:

  1. install NetBSD 7.0 intel to check if bug is BE/sparc specific, check atactl code for the hints.
  2. Check previous smartmontools version (6.5)

Autodetection is broken in smartmontools 6.6/netbsd

sparc64# ./smartctl /dev/wd0c
smartctl 6.7 2017-11-16 r4625 [NetBSD 7.0 sparc64] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/wd0c: Unable to detect device type
Please specify device type with the -d option.

Use smartctl -h to get a usage summary

Code in the netbsd_smart_interface::autodetect_smart_device(const char * name) is very wrong

#1265 invalid sample ticket Alex Samorukov
#1266 fixed Server migration - progress tracking Alex Samorukov Alex Samorukov
Description

About

We are migrating from the Peer1 VM to the FreeBSD host. This story is required to track progress as there are many things to do.

Trac migration

  • ☑ Change DNS A/AAAA records
  • ☑ Restore latest (29.11.19) backups
  • ☑ Restore MySQL database
  • ☑ Create new SSL keys
  • ☑ Restore nginx configuration
  • ☑ Restore trac data to the new server
  • ☑ Restore SVN sync from the sf.net to trac (done, every 3m)
  • ☑ Create system service to start trac on server restart, validate it
  • ☑ Fix loading plugins in the trac/plugins dir
  • ☑ Re-enable re-captcha plugin
  • ☑ Check if new user registration is working properly
  • ☑ Fix man pages and docbook HTML renderer
  • ☑ Check if SMTP is working
  • ☑ Re-enable TracTocMacro plugin

Related services

  • ☑ Restore SVN mirroring to the GitHub (sync2git process)
  • ☑ Restore builds.smartmontools.org website
  • ☑ Re-Enable doxygen docs generation
  • ☑ Create new user to store the backups, sync content to another locations and provide access to another members
  • ☑ Switch to mailgun as external SMTP server

Long-term changes

  • ☐ Think about moving trac to VM or docker containers to allow fast relocation if needed
  • ☐ Check if documentation is up to date. Setup export of it to the backups.
  • ☐ Create DR documentation and put it with a backups
Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.