Re: 12-current, since 323508 / Sept 13 - smartctl / smartmontools - unable to query drives
> On Oct 4, 2017, at 11:42 AM, Herbert J. Skuhra <herb...@gojira.at> wrote: > > On Wed, Oct 04, 2017 at 11:14:00AM -0700, David P. Discher wrote: >> Seeing an odd behavior - even with r324216 as of about Oct 2nd, smartctl can >> no longer query any disks >> >> Anyone have any pointers ? Smartmontools hasn’t changed since Feb, so by >> all indications, this is a regression in FreeBSD-current/-head. >> >> Thanks ! > > Rebuild smartmontools! Doh ! Thanks - this was indeed the problem. I’ll need to be more careful with head. -- David P. Discher https://davidpdischer.com/ signature.asc Description: Message signed with OpenPGP
Re: 12-current, since 323508 / Sept 13 - smartctl / smartmontools - unable to query drives
Just recently tested smartctl (a few days ago) r324135 and I found that the auto detection seems to be broken but manually selecting the device type works. Are you positive you tested every device type? I was a bit surprised to find that atacam works for my onboard controller and the HBA only works with sat,auto and scsi On Wed, Oct 4, 2017 at 11:14 AM, David P. Discher <d...@dpdtech.com> wrote: > Seeing an odd behavior - even with r324216 as of about Oct 2nd, smartctl > can no longer query any disks > > Always getting: > > > sudo smartctl -x /dev/ada0 > Password: > smartctl 6.5 2016-05-07 r4318 [FreeBSD 12.0-CURRENT amd64] (local > build) > Copyright (C) 2002-16, Bruce Allen, Christian Franke, > www.smartmontools.org > > /dev/ada0: Unable to detect device type > Please specify device type with the -d option. > > Use smartctl -h to get a usage summary > > Even with specifying the type, I can’t query the drives. I’m trying to > nail down the commit now, I think its between r320087 and r323508. > > Anyone have any pointers ? Smartmontools hasn’t changed since Feb, so by > all indications, this is a regression in FreeBSD-current/-head. > > Thanks ! > > -- > David P. Discher > https://davidpdischer.com/ > > > ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: 12-current, since 323508 / Sept 13 - smartctl / smartmontools - unable to query drives
On Wed, Oct 04, 2017 at 11:14:00AM -0700, David P. Discher wrote: > Seeing an odd behavior - even with r324216 as of about Oct 2nd, smartctl can > no longer query any disks > > Always getting: > > > sudo smartctl -x /dev/ada0 > Password: > smartctl 6.5 2016-05-07 r4318 [FreeBSD 12.0-CURRENT amd64] (local build) > Copyright (C) 2002-16, Bruce Allen, Christian Franke, > www.smartmontools.org > > /dev/ada0: Unable to detect device type > Please specify device type with the -d option. > > Use smartctl -h to get a usage summary > > Even with specifying the type, I can’t query the drives. I’m trying to nail > down the commit now, I think its between r320087 and r323508. > > Anyone have any pointers ? Smartmontools hasn’t changed since Feb, so by all > indications, this is a regression in FreeBSD-current/-head. > > Thanks ! Rebuild smartmontools! -- Herbert ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
12-current, since 323508 / Sept 13 - smartctl / smartmontools - unable to query drives
Seeing an odd behavior - even with r324216 as of about Oct 2nd, smartctl can no longer query any disks Always getting: > sudo smartctl -x /dev/ada0 Password: smartctl 6.5 2016-05-07 r4318 [FreeBSD 12.0-CURRENT amd64] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org /dev/ada0: Unable to detect device type Please specify device type with the -d option. Use smartctl -h to get a usage summary Even with specifying the type, I can’t query the drives. I’m trying to nail down the commit now, I think its between r320087 and r323508. Anyone have any pointers ? Smartmontools hasn’t changed since Feb, so by all indications, this is a regression in FreeBSD-current/-head. Thanks ! -- David P. Discher https://davidpdischer.com/ signature.asc Description: Message signed with OpenPGP
Re: patch for smartmontools on latest head
> > http://dpaste.com/1B04AVB > > I believe that this patch should do the right thing on all version of FreeBSD, > so it could be better to integrate it upstream, if possible. > > Without the patch the port fails with errors like: > ./freebsd_nvme_ioctl.h:34:8: error: redefinition of 'nvme_command' Thank you! I already found report in the list but had no time to look on it. I will check it and commit to the source. ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
patch for smartmontools on latest head
http://dpaste.com/1B04AVB I believe that this patch should do the right thing on all version of FreeBSD, so it could be better to integrate it upstream, if possible. Without the patch the port fails with errors like: ./freebsd_nvme_ioctl.h:34:8: error: redefinition of 'nvme_command' -- Andriy Gapon ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: smartmontools now broken on -current (by svn r301771, r301778?)
Also, on my system running nda, smartmontools work. And the latest version is compiling in Netflix's tree, which is where I took all these patches from... Warner On Sat, Jun 11, 2016 at 5:57 PM, Warner Losh <i...@bsdimp.com> wrote: > I'm skeptical. The ATA stuff isn't anything that I've committed to, so > that isn't new. > > The nvme stuff is because smartmontools defines nvme stuff that > conflicts with the FreeBSD defines... > > Warner > > > On Sat, Jun 11, 2016 at 9:42 AM, Ngie Cooper (yaneurabeya) > <yaneurab...@gmail.com> wrote: >> >>> On Jun 11, 2016, at 09:40, Michael Butler <i...@protected-networks.net> >>> wrote: >>> >>> The recent nvme updates have broken smartmontools .. >>> >>> imb@toshi:/home/imb> sudo smartctl -a /dev/ada0 >>> smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-ALPHA2 amd64] (local build) >>> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org >>> >>> /dev/ada0: Inappropriate ioctl for device >>> Please specify device type with the -d option. >>> >>> Attempts to recompile the utility also fail: >> >> Hi Michael, >> Please file a bug — in ports first, and if necessary in the base >> system. >> Thank you! >> -Ngie ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: smartmontools now broken on -current (by svn r301771, r301778?)
I'm skeptical. The ATA stuff isn't anything that I've committed to, so that isn't new. The nvme stuff is because smartmontools defines nvme stuff that conflicts with the FreeBSD defines... Warner On Sat, Jun 11, 2016 at 9:42 AM, Ngie Cooper (yaneurabeya) <yaneurab...@gmail.com> wrote: > >> On Jun 11, 2016, at 09:40, Michael Butler <i...@protected-networks.net> >> wrote: >> >> The recent nvme updates have broken smartmontools .. >> >> imb@toshi:/home/imb> sudo smartctl -a /dev/ada0 >> smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-ALPHA2 amd64] (local build) >> Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org >> >> /dev/ada0: Inappropriate ioctl for device >> Please specify device type with the -d option. >> >> Attempts to recompile the utility also fail: > > Hi Michael, > Please file a bug — in ports first, and if necessary in the base > system. > Thank you! > -Ngie ___ freebsd-current@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: smartmontools now broken on -current (by svn r301771, r301778?)
> On Jun 11, 2016, at 09:40, Michael Butler <i...@protected-networks.net> wrote: > > The recent nvme updates have broken smartmontools .. > > imb@toshi:/home/imb> sudo smartctl -a /dev/ada0 > smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-ALPHA2 amd64] (local build) > Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org > > /dev/ada0: Inappropriate ioctl for device > Please specify device type with the -d option. > > Attempts to recompile the utility also fail: Hi Michael, Please file a bug — in ports first, and if necessary in the base system. Thank you! -Ngie signature.asc Description: Message signed with OpenPGP using GPGMail
smartmontools now broken on -current (by svn r301771, r301778?)
The recent nvme updates have broken smartmontools ..
imb@toshi:/home/imb> sudo smartctl -a /dev/ada0
smartctl 6.5 2016-05-07 r4318 [FreeBSD 11.0-ALPHA2 amd64] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/ada0: Inappropriate ioctl for device
Please specify device type with the -d option.
Attempts to recompile the utility also fail:
c++ -DHAVE_CONFIG_H -I. -DBUILD_INFO='"(local build)"'
-DSMARTMONTOOLS_SYSCONFDIR='"/usr/local/etc"'
-DSMARTMONTOOLS_SMARTDSCRIPTDIR='"/usr/local/etc"'
-DSMARTMONTOOLS_DRIVEDBDIR='"/usr/local/share/smartmontools"'-O2
-pipe -march=core2 -fstack-protector -fno-strict-aliasing -Wall -W -c
-o cciss.o cciss.cpp
In file included from os_freebsd.cpp:43:
./atacmds.h:77:9: warning: 'ATA_SET_FEATURES' macro redefined
[-Wmacro-redefined]
#define ATA_SET_FEATURES0xef
^
/usr/include/sys/ata.h:399:10: note: previous definition is here
#define ATA_SET_FEATURES0x05/* set features */
^
In file included from os_freebsd.cpp:74:
./freebsd_nvme_ioctl.h:34:8: error: redefinition of 'nvme_command'
struct nvme_command
^
/usr/include/dev/nvme/nvme.h:201:8: note: previous definition is here
struct nvme_command
^
In file included from os_freebsd.cpp:74:
./freebsd_nvme_ioctl.h:67:8: error: redefinition of 'nvme_status'
struct nvme_status {
^
/usr/include/dev/nvme/nvme.h:234:8: note: previous definition is here
struct nvme_status {
^
In file included from os_freebsd.cpp:74:
./freebsd_nvme_ioctl.h:77:8: error: redefinition of 'nvme_completion'
struct nvme_completion {
^
/usr/include/dev/nvme/nvme.h:244:8: note: previous definition is here
struct nvme_completion {
^
In file included from os_freebsd.cpp:74:
./freebsd_nvme_ioctl.h:94:8: error: redefinition of 'nvme_pt_command'
struct nvme_pt_command {
^
/usr/include/dev/nvme/nvme.h:765:8: note: previous definition is here
struct nvme_pt_command {
^
1 warning and 4 errors generated.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
CAM ABI change requires recompile of hald and smartmontools
A kernel built today shows the following messages: ata2: FAILURE - zero length DMA transfer attempted ata2: setting up DMA failed cam_periph_mapmem: attempt to map 4294954816 bytes, which is greater than 65536 cam_periph_mapmem: attempt to map 4294954832 bytes, which is greater than 65536 ata2: FAILURE - zero length DMA transfer attempted ata2: setting up DMA failed ata2: FAILURE - zero length DMA transfer attempted ata2: setting up DMA failed cam_periph_mapmem: attempt to map 4294954832 bytes, which is greater than 65536 I found that stopping hald was causing this. A freshly compiled hald solves this problem. This ABI breakage deserves a heads-up, IMHO, since the messages look quite frightening. I did not observe any damage on my system with 5 SATA drives in a ZRAID1, but I'm going to perform a scrub, just to be sure. Regards, STefan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: CAM ABI change requires recompile of hald and smartmontools
On 12/15/13 07:35, Stefan Esser wrote: A kernel built today shows the following messages: ata2: FAILURE - zero length DMA transfer attempted ata2: setting up DMA failed cam_periph_mapmem: attempt to map 4294954816 bytes, which is greater than 65536 cam_periph_mapmem: attempt to map 4294954832 bytes, which is greater than 65536 ata2: FAILURE - zero length DMA transfer attempted ata2: setting up DMA failed ata2: FAILURE - zero length DMA transfer attempted ata2: setting up DMA failed cam_periph_mapmem: attempt to map 4294954832 bytes, which is greater than 65536 I found that stopping hald was causing this. A freshly compiled hald solves this problem. This ABI breakage deserves a heads-up, IMHO, since the messages look quite frightening. I did not observe any damage on my system with 5 SATA drives in a ZRAID1, but I'm going to perform a scrub, just to be sure. Regards, STefan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org Sorry about this -- I forgot to bump the libcam version. r259416 should fix it for people just upgrading now. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Smartmontools
Other than nooptions ATA_CAM, is there a fix or circumvention to allow smartmontools to work correctly under 9.0 and -CURRENT? slippy# smartctl -a /dev/ad0 smartctl 5.41 2011-06-09 r3365 [FreeBSD 9.0-STABLE i386] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device Unable to get CAM device list /dev/ad0: Unable to detect device type Smartctl: please specify device type with the -d option. Use smartctl -h to get a usage summary slippy# -- Cheers, Cy Schubert cy.schub...@komquats.com FreeBSD UNIX: c...@freebsd.org Web: http://www.FreeBSD.org The need of the many outweighs the greed of the few. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Smartmontools
On Feb 1, 2012, at 9:49 PM, Cy Schubert wrote: Other than nooptions ATA_CAM, is there a fix or circumvention to allow smartmontools to work correctly under 9.0 and -CURRENT? slippy# smartctl -a /dev/ad0 smartctl 5.41 2011-06-09 r3365 [FreeBSD 9.0-STABLE i386] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device Unable to get CAM device list /dev/ad0: Unable to detect device type Smartctl: please specify device type with the -d option. Use smartctl -h to get a usage summary slippy# I can't say for certain, but my guess is that you've been victimized by recent changes to CAM headers. Have you tried recompiling to get everything in sync? Scott ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Smartmontools
In message e5fba775-b6b6-4086-ba2b-d74a19cf4...@samsco.org, Scott Long writes : On Feb 1, 2012, at 9:49 PM, Cy Schubert wrote: Other than nooptions ATA_CAM, is there a fix or circumvention to allow smartmontools to work correctly under 9.0 and -CURRENT? slippy# smartctl -a /dev/ad0 smartctl 5.41 2011-06-09 r3365 [FreeBSD 9.0-STABLE i386] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device Unable to get CAM device list /dev/ad0: Unable to detect device type Smartctl: please specify device type with the -d option. Use smartctl -h to get a usage summary slippy# I can't say for certain, but my guess is that you've been victimized by recen t changes to CAM headers. Have you tried recompiling to get everything in sy nc? Everything (kernel and userland) but smaartmontools (and other ports) has been rebuilt (two days ago). Rebuilding the port did the trick. Thanks. :) -- Cheers, Cy Schubert cy.schub...@komquats.com FreeBSD UNIX: c...@freebsd.org Web: http://www.FreeBSD.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
freebsd-9.0 smartmontools and ada devices
Hi Guys, I have upgraded my desktop from 8.2-stable to 9.0-RC1 (from source), using a GENERIC kernel. I have installed the smartmontools-5.41_3 package from a mirror and found that smartmontools does not like the ada devices anymore. Previously (8.2) I had a GENERIC kernel, with ahci loaded in loader.conf. There an older smartmontools (5.40) worked without a problem on the ada devices. The output of smartctl looks like this: # dolphin# smartctl -a /dev/ada0 smartctl 5.41 2011-06-09 r3365 [FreeBSD 9.0-RC1 amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device Unable to get CAM device list /dev/ada0: Unable to detect device type Smartctl: please specify device type with the -d option. Use smartctl -h to get a usage summary # Has anybody seen it? John -- John Hay -- j...@meraka.csir.co.za / j...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: freebsd-9.0 smartmontools and ada devices
On Tue, Oct 18, 2011 at 09:39:24AM +0200, John Hay wrote: Hi Guys, I have upgraded my desktop from 8.2-stable to 9.0-RC1 (from source), using a GENERIC kernel. I have installed the smartmontools-5.41_3 package from a mirror and found that smartmontools does not like the ada devices anymore. Previously (8.2) I had a GENERIC kernel, with ahci loaded in loader.conf. There an older smartmontools (5.40) worked without a problem on the ada devices. The output of smartctl looks like this: # dolphin# smartctl -a /dev/ada0 smartctl 5.41 2011-06-09 r3365 [FreeBSD 9.0-RC1 amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device Unable to get CAM device list /dev/ada0: Unable to detect device type Smartctl: please specify device type with the -d option. Use smartctl -h to get a usage summary # Just to follow up on myself. :-( I have build smartmontools from ports and even though it is the same version, it works. So for me the package amd64/packages-9-current/All/smartmontools-5.41_3.tbz did not work, but the port does. John ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: freebsd-9.0 smartmontools and ada devices
Op di 18 okt 2011 09:39:24 schreef John Hay: Hi Guys, I have upgraded my desktop from 8.2-stable to 9.0-RC1 (from source), using a GENERIC kernel. I have installed the smartmontools-5.41_3 package from a mirror and found that smartmontools does not like the ada devices anymore. Previously (8.2) I had a GENERIC kernel, with ahci loaded in loader.conf. There an older smartmontools (5.40) worked without a problem on the ada devices. The output of smartctl looks like this: # dolphin# smartctl -a /dev/ada0 smartctl 5.41 2011-06-09 r3365 [FreeBSD 9.0-RC1 amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device Unable to get CAM device list /dev/ada0: Unable to detect device type Smartctl: please specify device type with the -d option. Use smartctl -h to get a usage summary # Has anybody seen it? Yes, but rebuilding smartmontools fixed it for me. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: freebsd-9.0 smartmontools and ada devices
On Tue, Oct 18, 2011 at 11:02:42AM +0200, John Hay wrote: On Tue, Oct 18, 2011 at 09:39:24AM +0200, John Hay wrote: Hi Guys, I have upgraded my desktop from 8.2-stable to 9.0-RC1 (from source), using a GENERIC kernel. I have installed the smartmontools-5.41_3 package from a mirror and found that smartmontools does not like the ada devices anymore. Previously (8.2) I had a GENERIC kernel, with ahci loaded in loader.conf. There an older smartmontools (5.40) worked without a problem on the ada devices. The output of smartctl looks like this: # dolphin# smartctl -a /dev/ada0 smartctl 5.41 2011-06-09 r3365 [FreeBSD 9.0-RC1 amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net error sending CAMIOCOMMAND ioctl: Inappropriate ioctl for device Unable to get CAM device list /dev/ada0: Unable to detect device type Smartctl: please specify device type with the -d option. Use smartctl -h to get a usage summary # Just to follow up on myself. :-( I have build smartmontools from ports and even though it is the same version, it works. So for me the package amd64/packages-9-current/All/smartmontools-5.41_3.tbz did not work, but the port does. CAM ABI was changed right before RC1. The issue was mentioned in the Ken' announcement. The packages were obviously built with the old headers. pgpCP3eHnNxYY.pgp Description: PGP signature
Experimental port of smartmontools available
All, The current CVS version of smartmontools http://smartmontools.sourceforge.net now has support for FreeBSD. A couple of notes: 1) SCSI support is there, but has not been highly tested. It uses CAM, so any version of FreeBSD with CAM should work (hopefully) 2) ATA support requires ATAng, or a fairly recent CURRENT. I do plan on eventually creating a /usr/ports/systutil/smartmontools and submitting to the appropriate place, but haven't gotten there yet. Please try it out and send any problem reports to the smartmon-support mailing list. Thanks, Ed ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to [EMAIL PROTECTED]
