Custom Query (1560 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (436 - 438 of 1560)

Ticket Resolution Summary Owner Reporter
#1504 worksforme WD Elements external hard drive errors with "not capable of SMART self-check" kageurufu
Description

I get the following error from smartd with one of my external drives, connected over USB.

Device: /dev/sdf [SAT], not capable of SMART self-check
Device: /dev/sdf [SAT], failed to read SMART Attribute Data

I am able to query using smartctl, execute short and long tests, and get the results

smartctl 7.2 2020-12-30 r5155 [x86_64-linux-5.10.40-1-lts] (local build)
Copyright (C) 2002-20, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Device Model:     WDC WD140EDFZ-11A0VA0
Serial Number:    [redacted]
LU WWN Device Id: 5 000cca 290c402e0
Firmware Version: 81.00A81
User Capacity:    14,000,519,643,136 bytes [14.0 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Form Factor:      3.5 inches
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   ACS-2, ATA8-ACS T13/1699-D revision 4
SATA Version is:  SATA 3.2, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is:    Thu Jun 24 11:59:23 2021 MST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
#1508 duplicate MKNSSDS2500GB Mark van Eck
#1512 wontfix Deprecate the mailing list in favor of StackExchange Ohad Schneider
Description

I suggested moving off the old-style mailing list in a recent thread: https://listi.jpberlin.de/pipermail/smartmontools-support/2021-July/000728.html

The advantages should be clear, StackExchange (SE) is more efficient than mailing lists by orders of magnitude in practically every parameter.

To address the criticism in that thread:

  1. mailing lists are publicly available, often times mirrored by other mailing list archives, you have them in your mailbox for personal archive etc. So you can find something again.

SE is also publicly available and mirrored in other (albeit sometimes shady) sites, not to mention a million sensitive local sites where internet access is restricted (e.g. in the Israeli Defense Force). It's just way past the point of "too big to fall", there's just no way that content "disappears" from the internet, it's like saying Wikipedia will disappear. And even if it did, it's cached by multiple sites including Google, and every few months you get a full data dump of *all* SE content uploaded to the Web Archive: https://archive.org/details/stackexchange. If you want to talk about safety, you can't beat those guys...

  1. It's a matter of time until privately owned platforms (such as StackExchange) might suddenly start charging to read answers (Experts Exchange). Or the service might be attacked and is down right then when you need it

I think the comparison to Stack Exchange is about as ludicrous as saying Google or Wikipedia will start charging money, but at any rate how is this different than SourceForge or MarkLogic?

  1. A public discussion board, such as the one suggested in ticket 217, is generally a better idea, but I've seen exactly this happening with the monitoring plugins mailing list. Everything was moved from mailing list to a discussion board (not sure which one) and because people have abandoned the project and problems with DSGVO/GDPR and technical security vulnerabilities of the discussion board started to arise, the discussion board was shut down. Including all archives. Everything is gone. And there was a lot of helpful information there which would still apply today. Just visit https://monitoring-portal.org/ to see for yourself.

Irrelevant, you have zero cost and zero technical maintenance. Either you use ServerFault as-is, or you open an SE sub-site (e.g. smartmontools.stackexchange.com) like they did for a million other topics.

Smartctl is hard core enough, and if anything is behind some sort of a wall, it's these mailing lists which are hard to search and more daunting to participate in for the average user.

Batch Modify
Note: See TracBatchModify for help on using batch modify.
Note: See TracQuery for help on using queries.