Custom Query (1359 matches)

This is an external 1TB USB 3.0 drive.

Information from the label on the bottom of the drive:

Seagate Expansion Portable Drive Model: SRD0NF1 PN: 1TEAP5-500

UASP has to be disabled for this drive on Linux, else SMART parameters cannot be read from the drive (scsi error unsupported field in scsi command).

Please find attached the output of smartctl -q noserial -x /dev/sdX

​C.Lee Taylor reported via database mailing list:

lsusb
Bus 002 Device 007: ID 1058:1078 Western Digital Technologies, Inc.
Bus 002 Device 006: ID 1058:1078 Western Digital Technologies, Inc.


smartctl -i -a /dev/sda
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-112-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

/dev/sda: Unknown USB bridge [0x1058:0x1078 (0x1065)]
Please specify device type with the -d option.



smartctl -i -a -d sat /dev/sda
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.4.0-112-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family:     Western Digital Elements / My Passport (USB, AF)
Device Model:     WDC WD10JMVW-11AJGS3
Serial Number:    WD-WX61A64LCP73
LU WWN Device Id: 5 0014ee 604bf5fd1
Firmware Version: 01.01A01
User Capacity:    1,000,204,886,016 bytes [1.00 TB]
Sector Sizes:     512 bytes logical, 4096 bytes physical
Rotation Rate:    5400 rpm
Device is:        In smartctl database [for details use: -P show]

Forwarded from: ​https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893657

(Issue (1) described bellow may not apply to upstream smartmontools, as /etc/smartmontools/run.d/10mail seems to be a Debian-specific file... but at least issue (2) should apply to upstream smartmontools as well.)

Hi.

I've stumbled over the following issues in smartd:

At first I had bascally the following smartd.conf:

DEVICESCAN -d auto -d removable -n standby,4 -a -m root,mylocaluser,my@email.com -M exec /usr/share/smartmontools/smartd-runner

In order to test it, I've added -M test.

Now on restart, only root got mail, and the postfix logs didn't even show any tries for mylocaluser and my@….

I've added -M once, as I assumed the support for comma-separated multiple addresses as explained in the smartd.conf manpage for -m, may just not work with -M-exec-invoked /etc/smartmontools/run.d/10mail but only with -M once, -M daily or -M diminishing (and that this might be some other mail sender than /etc/smartmontools/run.d/10mail - which it actually seems to be).

Interestingly, it still didn't work. Only if I removed -M exec... I got mail sent to all three recipients.

So I think there are two issues here: 1) /etc/smartmontools/run.d/10mail, which seems to be used per default by debian (as there is no -M once or so) should support multiple addresses in -m. It's likely not obvious to the user that there are two methods of sending warning mails, and it should just work as one would naively assume by reading the documentation of -m.

2) In contrast to what the manpage claims, it seems that if -M exec is in place, -M once/etc. are not executed as well.

IMO both are severity=important, as they may prevent information about failing drives being passed on.

Cheers, Chris.