Date: Mon, 22 Jun 2009 20:56:57 +0200 From: Thomas Backman <serenity@exscape.org> To: FreeBSD current <freebsd-current@freebsd.org> Subject: Re: smartmontools/smartctl regression - CAMGETPASSTHRU ioctl failed Message-ID: <78F1C3C2-679D-4580-A255-2D7B9C02022B@exscape.org> In-Reply-To: <462E2000-6856-46A7-B89C-03F9CE398F5E@exscape.org> References: <462E2000-6856-46A7-B89C-03F9CE398F5E@exscape.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 20, 2009, at 11:27 AM, Thomas Backman wrote: > I know there have been some recent changes in the area (although TBH > I don't know what CAM is, so...). It used to work a few weeks ago > when I last checked, but now I get this: > > # smartctl -A /dev/da0 > smartctl version 5.38 [amd64-portbld-freebsd8.0] Copyright (C) > 2002-8 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > smartctl: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > cam_lookup_pass: No such file or directory > cam_lookup_pass: either the pass driver isn't in your kernel > cam_lookup_pass: or da0 doesn't exist > Standard Inquiry (36 bytes) failed [Operation not permitted] > Retrying with a 64 byte Standard Inquiry > smartctl: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > cam_lookup_pass: No such file or directory > cam_lookup_pass: either the pass driver isn't in your kernel > cam_lookup_pass: or da0 doesn't exist > Standard Inquiry (64 bytes) failed [Operation not permitted] > A mandatory SMART command failed: exiting. To continue, add one or > more '-T permissive' options. > --------------- > A rebuild of smartmontools did nothing. Am I missing a kernel option > or something? I'm running GENERIC plus DTRACE minus WITNESS/ > INVARIANTS, no other changes. > > Regards, > Thomas Oh, man. I'm such a moron. Or klutz, at least. "... or da0 doesn't exist" is indeed correct. The disks are ad* on this computer. I'm much too used to da* and didn't even think about the possibility that I might actually have the name wrong... Normally, I would stay quiet about it, but seeing how this is/was essentially a bug report, I guess I'll have to tell the truth: there was no bug here in my case. *blushes* Regards, Thomas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?78F1C3C2-679D-4580-A255-2D7B9C02022B>