[Bug 1809003] Re: version mismatch in smartmontools?
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. https://bugs.launchpad.net/bugs/1809003 Title: version mismatch in smartmontools? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1809003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893202] Re: update-smart-drivedb overwrites package installed file
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 package installed file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1893202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1893126] Re: update-smart-drivedb: embedded GPG key expires in 2020
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. https://bugs.launchpad.net/bugs/1893126 Title: update-smart-drivedb: embedded GPG key expires in 2020 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1893126/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888009] Re: smartmontools.service: start operation timed out. Terminating.
> Status: "Checking 38 devices ..." > ... > Jul 17 17:31:38 ia804105.us.archive.org smartd[57674]: > Monitoring 38 ATA/SATA, 0 SCSI/SAS and 0 NVMe devices > Jul 17 17:32:59 ia804105.us.archive.org systemd[1]: > smartmontools.service: start operation timed out. Terminating. This suggests that the first device checks last longer than the systemd setting DefaultTimeoutStartSec=90s. The current version of smartd notifies READY=1 only after the first checks are completed. In traditional daemon mode (no -n option and no NOTIFY_SOCKET) it would 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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888009 Title: smartmontools.service: start operation timed out. Terminating. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1888009/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1878264] Re: nvme smart error count email after upgrading to 20.04
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. https://bugs.launchpad.net/bugs/1878264 Title: nvme smart error count email after upgrading to 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1878264/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873546] Re: GSmartControl interprets code 231 incorrectly
> 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 copy the new entry to the local smart_drivedb.h file, see -B option on smartctl man page for details. > Would compiling from source code be a safe solution? For smartctl: yes. For smartd daemon: yes, but may require manual changes to systemd service file. With default ./configure settings, everything is installed below /usr/local and does not interfere with the Ubuntu package. We also provide current source tarballs and binaries at https://builds.smartmontools.org/. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873546 Title: GSmartControl interprets code 231 incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1873546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1873546] Re: GSmartControl interprets code 231 incorrectly
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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1873546 Title: GSmartControl interprets code 231 incorrectly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1873546/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1858121] [NEW] Please re-add update-smart-drivedb
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 consider to re-add the script also in the Ubuntu package. In the past, the Ubuntu package usually followed Debian (https://bugs.launchpad.net/bugs/1574894). Note that since smartmontools 6.6 the script verifies the download with gpg. Christian smartmontools.org PS: We released smartmontools-7.1 at 2019-12-30. ** Affects: smartmontools (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1858121 Title: Please re-add update-smart-drivedb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1858121/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574894] Re: Can't update smartmontools drivedb: /usr/sbin/update-smart-drivedb is missing
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 you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574894 Title: Can't update smartmontools drivedb: /usr/sbin/update-smart-drivedb is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1574894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833331] Re: 10mail script should use sendmail command, not the mail command
> 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 \ | /usr/sbin/smartd -c - -q onecheck 2. Or: run smartd's internal warning script directly. This does not require root and does not access any device. Set SMARTD_ADDRESS from '-m ...' and SMARTD_MAILER from '-M exec ...'. Example: $ SMARTD_ADDRESS='some.one@some.where' \ SMARTD_MAILER=/usr/share/smartmontools/smartd-runner \ /usr/share/smartd_warning.sh --dryrun Remove --dryrun to actually exec .../smartd-runner. @Christian E. - A possible enhancement for 10mail would be to fall back to sendmail if mail is not available. Something like: #!/bin/bash mail=/usr/bin/mail sendmail=/usr/sbin/sendmail if [ -x $mail ]; then echo "$SMARTD_FULLMESSAGE" | $mail -s "$SMARTD_SUBJECT" $SMARTD_ADDRESS elif [ -x $sendmail ]; then $sendmail $SMARTD_ADDRESS
[Bug 1833331] Re: 10mail script should use sendmail command, not the mail command
> @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: smartdnotify, ...) I added two (now tested:-) wrappers for sendmail to upstream examplescripts directory: https://www.smartmontools.org/changeset/4930 -- 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 script should use sendmail command, not the mail command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833331] Re: 10mail script should use sendmail command, not the mail command
> 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 script should use sendmail command, not the mail command To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/181/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1833331] Re: 10mail script should use sendmail command, not the mail command
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 'mail' provider and don't remember similar problems. Alternatively you could disable (chmod -x) 10mail and add some /etc/smartmontools/run.d/11sendmail script, something like: #!/bin/bash /usr/sbin/sendmail $SMARTD_ADDRESS
[Bug 1833331] Re: 10mail script should use sendmail command, not the mail command
>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. POSIX and its predecessor say: "Send Mode can be used by applications or users to send messages from the text in standard input." See: http://pubs.opengroup.org/onlinepubs/007908799/xcu/mailx.html http://pubs.opengroup.org/onlinepubs/9699919799/utilities/mailx.html If no script (like smartd-runner) is specified with '-M exec' directive, smartd also uses 'mail' as a default (see smartd_warning.sh): mail -s "$SMARTD_SUBJECT" $SMARTD_ADDRESS
[Bug 1802720] Re: Micron 1100 SATA SSD not recognized by smartctl
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 Title: Micron 1100 SATA SSD not recognized by smartctl To manage notifications about this bug go to: https://bugs.launchpad.net/smartmontools/+bug/1802720/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809003] Re: version mismatch in smartmontools?
> ... 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 https://www.smartmontools.org/changeset/4319 https://www.smartmontools.org/changeset/4324 https://www.smartmontools.org/changeset/4594 Suggested fix: Release 7.0 :-) https://www.smartmontools.org/browser/tags/RELEASE_7_0/smartmontools/NEWS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809003 Title: version mismatch in smartmontools? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1809003/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04
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, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1774569/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810215] Re: Smart data works on 16.04 but not 18.4
> 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. Both reportedly work according to these comments: https://www.smartmontools.org/ticket/971#comment:12 https://www.smartmontools.org/ticket/1092#comment:3 ** Bug watch added: www.smartmontools.org/ #971 https://www.smartmontools.org/ticket/971 ** Bug watch added: www.smartmontools.org/ #1092 https://www.smartmontools.org/ticket/1092 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: Smart data works on 16.04 but not 18.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1810215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1810215] Re: Smart data works on 16.04 but not 18.4
> 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 devices on recent Linux kernels if UAS mode is enabled. See info and related tickets about UAS on Linux here: https://www.smartmontools.org/wiki/USB -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1810215 Title: Smart data works on 16.04 but not 18.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1810215/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1809004] Re: update disco to latest smartmontools
> 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 provides a post 6.5 SVN snapshot (2016-05-21 r4324) which should include NVMe support. Try: smartctl -d nvme --scan 6.7 will be released soon (possibly as 7.0). The main new feature is 'smartctl --json' support. https://www.smartmontools.org/browser/trunk/smartmontools/NEWS -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1809004 Title: update disco to latest smartmontools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1809004/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1451572] Re: 'SMART error (FailedOpenDevice) detected' emails now being sent to root after removing a USB portable hard drive
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 (FailedOpenDevice) detected' emails now being sent to root after removing a USB portable hard drive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1451572/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685332] Re: does not monitor NVMe drives
> ... 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. https://bugs.launchpad.net/bugs/1685332 Title: does not monitor NVMe drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1685332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1685332] Re: does not monitor NVMe drives
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 decided to exclude NVMe devices from default smartd DEVICESCAN (and 'smartctl --scan') result. This will be changed in some later release. Package maintainers could override this decision by using --with-nvme- devicescan configure option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1685332 Title: does not monitor NVMe drives To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1685332/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658469] Re: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
> 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 kernel. Controller specific code might use some now deprecated SCSI ioctl. The deprecated SCSI_IOCTL_SEND_COMMAND is still used if -d 3ware or -d marvell is specified. https://www.smartmontools.org/ticket/93 ** Bug watch added: www.smartmontools.org/ #93 https://www.smartmontools.org/ticket/93 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/658469 Title: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/658469/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1569843] Re: smartd spindown check fails on newer disks, disabling check. Disks then spin-up when polled for SMART data.
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 polled for SMART data. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1569843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209085] Re: update-smart-drivedb uses old download link
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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1209085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1574894] Re: Can't update smartmontools drivedb: /usr/sbin/update-smart-drivedb is missing
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 --without-update-smart-drivedb. @maintainers: - Please remove update-smart-drivedb.8.gz from the package. The man page does not make any sense if the script is missing. - Please consider providing drivedb.h as a separate package which is updated more frequently. Same is discussed for FreeBSD, see FreeBSD Bugzilla 208398. ** Bug watch added: Debian Bug tracker #804299 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=804299 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1574894 Title: Can't update smartmontools drivedb: /usr/sbin/update-smart-drivedb is missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1574894/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471462] Re: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem
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 test if '-F nologdir' changes anything. If not, test whether another problem occurs if '-l selftest' is not specified: Don't use '-a' in smartd.conf, use '-H -f -t -l error' instead. All that could be done in smartmontools is to add another -F ( --firmwarebug) option to suppress accesses to self-test log. If desired, please create a ticket upstream. But I'm not sure whether this enhancement is worth the (non-trivial) effort for a single SSD series introduced 6+ years ago. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to smartmontools in Ubuntu. https://bugs.launchpad.net/bugs/1471462 Title: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1471462/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1471462] Re: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem
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 test if '-F nologdir' changes anything. If not, test whether another problem occurs if '-l selftest' is not specified: Don't use '-a' in smartd.conf, use '-H -f -t -l error' instead. All that could be done in smartmontools is to add another -F ( --firmwarebug) option to suppress accesses to self-test log. If desired, please create a ticket upstream. But I'm not sure whether this enhancement is worth the (non-trivial) effort for a single SSD series introduced 6+ years ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471462 Title: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1471462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471462] Re: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem
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 update the SSD firmware if possible. See also this ticket from 2010: "smartd Read SMART Self Test Log Failed on Intel X25-M SSD": https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/597518 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471462 Title: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1471462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1471462] Re: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem
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 update the SSD firmware if possible. See also this ticket from 2010: "smartd Read SMART Self Test Log Failed on Intel X25-M SSD": https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/597518 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to smartmontools in Ubuntu. https://bugs.launchpad.net/bugs/1471462 Title: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1471462/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1471462] Re: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem
> ... 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: > INTEL SSDSA2MH080G1GC, ... Some older Intel SSDs have known issues with the SMART READ LOG 0x00 (log directory) command: After this command was completed, the drive may hang. Smartd reads the log directory to check which log is supported, see https://www.smartmontools.org/ticket/89. This very old X18/X25-M G1 series SSD may be affected or not. Please try whether the problem persists if '-F nologdir' is added to the smartd.conf configuration line. ** Bug watch added: www.smartmontools.org/ #89 https://www.smartmontools.org/ticket/89 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to smartmontools in Ubuntu. https://bugs.launchpad.net/bugs/1471462 Title: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1471462/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1471462] Re: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem
> ... 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: > INTEL SSDSA2MH080G1GC, ... Some older Intel SSDs have known issues with the SMART READ LOG 0x00 (log directory) command: After this command was completed, the drive may hang. Smartd reads the log directory to check which log is supported, see https://www.smartmontools.org/ticket/89. This very old X18/X25-M G1 series SSD may be affected or not. Please try whether the problem persists if '-F nologdir' is added to the smartd.conf configuration line. ** Bug watch added: www.smartmontools.org/ #89 https://www.smartmontools.org/ticket/89 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1471462 Title: On bootup smartd reports FailedReadSmartSelfTestLog but there is no hardware problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1471462/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1353761] Re: gsmartcontrol crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1353761 Title: gsmartcontrol crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsmartcontrol/+bug/1353761/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1209085] [NEW] update-smart-drivedb uses old download link
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 downloads drivedb.h from the old respository which is still present but set to R/O. Possible fix: - Update to smartmontools 6.2 (final, r3841), or - Replace update-smart-drivedb with a new one generated from 6.2 tarball. Adjust the branch version number in line 'BRANCH=RELEASE_6_2_DRIVEDB'. This should work for smartmontools 5.40 to 6.1. These drivedb.h branches are still maintained. ** Affects: smartmontools (Ubuntu) Importance: Undecided Status: New -- 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 about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1209085/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1092882] Re: Version degradation- cant understand my external USB HDD
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 are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1092882 Title: Version degradation- cant understand my external USB HDD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/smartmontools/+bug/1092882/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1049202] [NEW] syslog-ng-mod-mongodb has deadlock problems
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 all applications which write to /dev/log will block indefinitely, making the system completely unusable. Going through the fixes which had been commited since the version currently in Ubuntu 12.04, I found various fixes concerning mongodb. There is: c08618370fc018629d623148452403fb7d0e6f40afmongodb: Fix a race condition in the queue wakeup mechanism And on the 3.4 branch there is also a fix concerning deadlocks: d5f78c833a20d3eb5da7372dd70bc79f2f971814afmongodb: Fix a queue notify-wakeup deadlock Having both of these patches applied, the issue did not reappear. As these patches only modify code of the mongodb destination module, the risk of introducing regression for users not deploying that modue is minimal, while for those that use syslog-ng-mod-mongodb, the patches help to avoid a very severe problem which, if it occurs, causes denial of service for most parts of the system. Therefore, I think that these patches should find their way into LTS. Also, there are multiple other bugfixes that have been commited since 3.3.4. It might be a good idea to look at those as well. ** Affects: syslog-ng (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1049202 Title: syslog-ng-mod-mongodb has deadlock problems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/syslog-ng/+bug/1049202/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 497256] Re: smartctl -n standby wakes up drive
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 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 696006] Re: smartctl reports extremely high (bogus) values
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 hours count (lower 4 bytes) + 24-bit milliseconds count (using reserved byte). If 0x1216 = 4630 hours is a reasonable value for this drive please whether -v 9,msec24hour32 produces reasonable output (this requires smartmontools = 5.40 ... r3133). An ST9250827AS with older(?) firmware 3.AHC produced normal Power_On_Hours values. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/696006 Title: smartctl reports extremely high (bogus) values -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 684809] Re: Using smartctl with Samsung F4 EcoGreen drives may result in data loss
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 drive database entry for F4EG (see upstream changesets r3216, r3219). Then smarctl will print a warning if such a drive is detected. Note that the warning will persist even if the firmware patch is installed Samsung decided to keep the version number unchanged ... A better fix is to upgrade to smartmontools 5.40 and run the new update- smart-drivedb script then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/684809 Title: Using smartctl with Samsung F4 EcoGreen drives may result in data loss -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661434] Re: OCZ Vertex: Device: /dev/sdX [SAT], same Attribute has different ID numbers:
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 661434] Re: OCZ Vertex: Device: /dev/sdX [SAT], same Attribute has different ID numbers:
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 http://sourceforge.net/apps/trac/smartmontools/changeset/3132 http://sourceforge.net/apps/trac/smartmontools/roadmap -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 658469] Re: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO
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 http://sourceforge.net/apps/trac/smartmontools/ticket/93 -- program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO https://bugs.launchpad.net/bugs/658469 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 491324] Re: smartmontools init scripts fails on 'status' action
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 http://sourceforge.net/apps/trac/smartmontools/ticket/113 ** Bug watch added: sourceforge.net/apps/trac/smartmontools/ #114 http://sourceforge.net/apps/trac/smartmontools/ticket/114 -- smartmontools init scripts fails on 'status' action https://bugs.launchpad.net/bugs/491324 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 497256] Re: smartctl -n standby wakes up drive
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 https://bugs.launchpad.net/bugs/497256 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 399150] Re: smartctl keeps disk spinnning
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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
