All pre-release builds from SVN snapshots now report "pre-7.4" in the
output and man pages. A tarball generated with 'make dist' still uses
the plain version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
A note for packaging the upcoming release 7.3:
https://www.smartmontools.org/ticket/1426#comment:12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1893202
Title:
update-smart-drivedb overwrites
Key 721042C5 lifetime has been extended to 2025. Old update scripts
should still work as gpg does not refuse verification if
(signature_timestamp > pubkey_expiry_time).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
uld
fork() then.
Please try this in smartmontools.service file:
...
[Service]
Type=notify
+TimeoutStartSec=300s
...
To find a reasonable TimeoutStartSec value and see which device checks
last very long, use for example:
# time /usr/sbin/smartd -q onecheck
Christian Franke
smartmontools.org
--
You received t
See related upstream ticket:
https://www.smartmontools.org/ticket/1222
** Bug watch added: www.smartmontools.org/ #1222
https://www.smartmontools.org/ticket/1222
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> update-smart-drivedb is not available
This was an upstream decision from Debian maintainer, see
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1858121
You could either manually replace /var/lib/smartmontools/drivedb.h with
a downloaded version from RELEASE_6_5_DRIVEDB branch. Or
See https://www.smartmontools.org/ticket/801
Please upgrade smartmontools to at least 7.0 or update the drive database:
https://www.smartmontools.org/wiki/Download#Updatethedrivedatabase
** Bug watch added: www.smartmontools.org/ #801
https://www.smartmontools.org/ticket/801
--
You
Public bug reported:
The new maintainer of the Debian smartmontools package re-added update-
smart-drivedb in smartmontools 7.0-1.
See this commit for the related comment in README.Debian:
https://salsa.debian.org/debian/smartmontools/commit/c894f39ddcbc48f478bad9ddf7702944eadbba8f
Please
Please note that the new maintainer of the debian package re-added
update-smart-drivedb in smartmontools 7.0-1. See this commit for the related
comment:
https://salsa.debian.org/debian/smartmontools/commit/c894f39ddcbc48f478bad9ddf7702944eadbba8f
--
You received this bug notification because
> At quick glance, I don't see a quick and easy way to test email
notifications.
1. '-M test' in smartd.conf enables test messages. Here a quick example
which does not touch smartd.conf and runs only one smartd check cycle in
debug mode:
# sed -n '/^DEVICESCAN/s,$, -M test,p' /etc/smartd.conf \
> @Christian F. - would such a configurability of the used mailer be something
> that upstream would want add?
I don't see much benefit in adding such complexity as various distributions
already override our defaults with custom '-M exec' scripts (Debian/Ubuntu:
smartd-runner, Fedora/RedHat:
> If you don't care, so be it.
Leaving the decision to actual package maintainer(s). I only maintain the
upstream project :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/181
Title:
10mail
If this works:
$ echo -e 'Subject: Test sendmail\n\nFoo' | /usr/sbin/sendmail
some.one@some.where
but this does not:
$ echo Bar | mail -s 'Test mail' some.one@some.where
you should possibly address the issue to the maintainer of the mailutils
package. I typically use the 'bsd-mailx' package as
>The 10mail script is trying to send messages with /usr/bin/mail (aka
mailx), which is a user agent, not intended for automated message
sending.
'mail' and its various variants are user agents, but also intended for
automated message sending. This is the case since the early (pre-Linux)
days.
Fixed upstream 2018-11-25:
https://www.smartmontools.org/ticket/1131#comment:5
Included in smartmontools-7.0 and in 5.41-6.6 drivedb branches.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802720
> ... It's quite common for VCS-based builds to anticipate the next
version.
Which is also the case for smartmontools since its early days (~2002).
"6.5+svn4324-1" is a few commits (drivedb.h additions) ahead of 6.5
(r4318), so it reports "6.6":
https://www.smartmontools.org/changeset/4318
See my comments in this smartmontools ticket:
https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1810215
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1774569
Title:
gsmartcontrol,
> If not is there any way to turn off uas ?
Try kernel parameter:
usb_storage.quirks=0bc2:331a:u disables UAS transfer mode,
usb_storage.quirks=0bc2:331a: disables all quirks.
The latter might be risky as kernel developers disabled SAT ATA PASS-
THROUGH in UAS mode for some good reason.
> Read Device Identity failed: scsi error unsupported field in scsi command
> ...
> [6041018.009417] usb 3-2.4: New USB device found, idVendor=0bc2,
> idProduct=331a
> ...
> [6041018.009432] usb 3-2.4: Manufacturer: Seagate
> ...
> [6041018.015808] scsi host5: uas
This is typical for Seagate USB
> Upstream is now 6.7 and includes support for NVMe devices that was not
> present before.
No, NVMe devices are supported on Linux since release 6.5 (2016-05-07 r4318).
> Once in Disco, we need to see about backporting this to 18.04 to get that
> NVMe support into Bionic.
Bionic currently
Fixed upstream since r4399.
https://www.smartmontools.org/changeset/4399
Fix is included in new smartmontools-6.6 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1451572
Title:
'SMART error
> ... any other help pointer (man page, comment in config, ...) that
would help?
No need for man page, as --with-nvme-devicescan also results in a brief
change to smartd.8.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Add '-d nvme' directive to 'DEVICESCAN' line in /etc/smartd.conf. Note
that this will exclude other devices unless e.g. '-d scsi -d ata -d sat'
is added also.
Background: The NVMe support in smartmontools is still EXPERIMENTAL. To
avoid any serious problems after smartmontools package upgrade, I
> This bug is present in smartmontools 6.2 2013-07-26 r3841 on trusty
amd64.
Please be more specific:
- which (RAID?) controller is used?
- smartctl command line to reproduce the problem?
- smartd.conf file to reproduce the problem?
Generic SCSI code (-d scsi, -d sat) uses SG_IO if supported by
Fix is included in smartmontools-6.5 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1569843
Title:
smartd spindown check fails on newer disks, disabling check. Disks
then spin-up when
I guess this will not be fixed in new packages, see Bug #1574894.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1209085
Title:
update-smart-drivedb uses old download link
To manage notifications
The /usr/sbin/update-smart-drivedb script was intentionally removed by (Debian)
maintainers, see:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804299
So I guess this bug will end up with "wontfix".
We at upstream decided to keep the script and let maintainers disable it
via ./configure
It is possibly is a bug in the Intel X25 G1 firmware Intel did never fix
(a similar bug in G2 was fixed). But I don't remember any related report
since the G1 series was introduced in 2009(!).
It is possibly not a smartmontools bug, except if the problem did not
occur with older versions.
Please
It is possibly is a bug in the Intel X25 G1 firmware Intel did never fix
(a similar bug in G2 was fixed). But I don't remember any related report
since the G1 series was introduced in 2009(!).
It is possibly not a smartmontools bug, except if the problem did not
occur with older versions.
Please
This is possibly not the Intel firmware bug mentioned in my previous
comment but an older one:
X18/X25-M/V G2 series with Firmware before 2CV102J8 may hang if self-
test log is read. G1 series may also be affected. Smartctl and smartd
print a related warning for G2 series but not for G1.
Please
This is possibly not the Intel firmware bug mentioned in my previous
comment but an older one:
X18/X25-M/V G2 series with Firmware before 2CV102J8 may hang if self-
test log is read. G1 series may also be affected. Smartctl and smartd
print a related warning for G2 series but not for G1.
Please
> ... kernel: [1128701.864075] ata4.00: cmd b0/d5:01:06:4f:c2/...
> ... kernel: [1128701.864075] res ... Emask 0x4 (timeout)
This ATA cmd is a correct SMART READ LOG 0x06 (self-test log) command.
If the command fails with "timeout", this is possibly not a
smartmontools issue.
> Device info:
>
> ... kernel: [1128701.864075] ata4.00: cmd b0/d5:01:06:4f:c2/...
> ... kernel: [1128701.864075] res ... Emask 0x4 (timeout)
This ATA cmd is a correct SMART READ LOG 0x06 (self-test log) command.
If the command fails with "timeout", this is possibly not a
smartmontools issue.
> Device info:
>
This Debian bug report is likely related and provides a patch:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722989
** Bug watch added: Debian Bug tracker #722989
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722989
--
You received this bug notification because you are a member of
Public bug reported:
Package: smartmontools-6.1+svn3812-1 and older.
Due to sourceforge platform upgrades (http://sourceforge.net/blog
/upgrades-april22/), the smartmontools SVN repository was moved to a new
location. The update-smart-drivedb script from a smartmontools build
before r3814
This device supports SAT. Its USB Id was added to drivedb.h in r3572:
http://sourceforge.net/apps/trac/smartmontools/changeset/3572
Possible fixes:
- update smartmontools, or
- run /usr/sbin/update-smart-drivedb, or
- use smartctl -d sat
--
You received this bug notification because you
Public bug reported:
Description: Ubuntu 12.04 LTS
Release: 12.04
Package: syslog-ng
Version: 3.3.4.dfsg-2ubuntu1
Having syslog-ng configured with mongodb as a destination, I happened to
encounter deadlocks where syslog-ng would stop to process any messages.
The impact is quite severe, as almost
The upstream fix is included in 10.10
(smartmontools-5.39.1+svn3077-1ubuntu1). Please close this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/497256
Title:
smartctl -n standby wakes up drive
This is not an Ubuntu specific issue. SMART attributes and especially
the raw values are not standardized at all.
The Power_On_Hours value 56006373544470 = 0x32f01216 suggests that
the raw bytes encode two values. This looks somewhat similar to the
format used by Sandforce based SSDs: 32-bit
A firmware patch is now available from Samsung, see above link for
details.
You should provide an Update with smartctl which does not issue IDENTIFY
DEVICE commands.
Information from IDENTIFY DEVICE is essential for smartctl full functionality.
A possible quick fix would be to add the new
Fixed in smartmontools 5.40 released 2010-10-16.
--
OCZ Vertex: Device: /dev/sdX [SAT], same Attribute has different ID numbers:
https://bugs.launchpad.net/bugs/661434
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
The warning messages appear because the threshold of attribute 177 is
missing in the SMART threshold data reported by SandForce based SSDs.
Updating drivedb.h won't suppress the messages.
Smartmontools now accepts missing attributes. The change will be included in
upcoming release 5.40
This should be partly fixed in newer smartmontools releases. Only some
of the controller specific parts of the code may still use the old ioctl
(http://sourceforge.net/apps/trac/smartmontools/ticket/93).
** Bug watch added: sourceforge.net/apps/trac/smartmontools/ #93
The issues reported in comment 8 will be addressed upstream:
http://sourceforge.net/apps/trac/smartmontools/ticket/113
http://sourceforge.net/apps/trac/smartmontools/ticket/114
** Bug watch added: sourceforge.net/apps/trac/smartmontools/ #113
Fixed in upstream smartmontools 5.39.1
http://sourceforge.net/apps/trac/smartmontools/ticket/37
** Bug watch added: sourceforge.net/apps/trac/smartmontools/ #37
http://sourceforge.net/apps/trac/smartmontools/ticket/37
--
smartctl -n standby wakes up drive
Some disks (e.g. Samsung T series) spin up on smartctl -A /dev/ice,
others (Samsung F1 series) don't. It is likely also firmware depended
whether the standby timer is reset on smartctl -A /dev/ice or not.
--
smartctl keeps disk spinnning
https://bugs.launchpad.net/bugs/399150
You received this
46 matches
Mail list logo
