I have been beating my head against smartctl for over two hours now. I cannot seem to get the command "long" accepted, as the various tutorials explain. When I try to insert it, I get an error, like this: linux1:~ # smartctl long /dev/nvme0n1 smartctl 7.0 2019-05-21 r4917 [x86_64-linux-5.3.18-57-default] (SUSE RPM) Copyright (C) 2002-18, Bruce Allen, Christian Franke, www.smartmontools.org ERROR: smartctl takes ONE device name as the final command-line argument. You have provided 2 device names: long /dev/nvme0n1 (It doesn't like "short" either.) And my typing is getting worse! It doesn't help that my drive is called /dev/nvme0n1. As I mentioned earlier, the lightning strike has damaged something in this, my main computer, and I'm trying to find out what. For those who missed the earlier post, the only thing I can connect to here is the internet. I cannot see the printers or the laptop machine, and nmap basically doesn't work. I started this quest at 11:30 PM and it's now 3:30 AM. I'm going to bed! --doug
mcgarrett composed on 2021-07-22 03:30 (UTC-0400):
I have been beating my head against smartctl for over two hours now. I cannot seem to get the command
"long" accepted, as the various tutorials explain. When I try to insert it, I get an error, like this:
linux1:~ # smartctl long /dev/nvme0n1
long is an argument to an option you omitted, the type of smartctl command: smartctl -t long /dev/nvme0n1 -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 22/07/2021 12.23, Carl Hartung wrote:
On Thu, 22 Jul 2021 03:56:57 -0400 Felix Miata wrote:
long is an argument to an option you omitted, the type of smartctl command:
smartctl -t long /dev/nvme0n1
Any opinions on this list as to the utility of running such a command on an SSD? Just curious ...
Well, the actual test runs inside the hard disk firmware with its own processor, code, and memory; which means it was designed by the SSD manufacturer. Thus, it has to be fine. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On July 22, 2021 at 3:56 AM Felix Miata <mrmazda@earthlink.net> wrote:
mcgarrett composed on 2021-07-22 03:30 (UTC-0400):
I have been beating my head against smartctl for over two hours now. I cannot seem to get the command
"long" accepted, as the various tutorials explain. When I try to insert it, I get an error, like this:
linux1:~ # smartctl long /dev/nvme0n1
long is an argument to an option you omitted, the type of smartctl command:
smartctl -t long /dev/nvme0n1 -- Felix Miata Thanx to all who answered. --doug
On July 22, 2021 at 3:56 AM Felix Miata <mrmazda@earthlink.net> wrote:
mcgarrett composed on 2021-07-22 03:30 (UTC-0400):
I have been beating my head against smartctl for over two hours now. I cannot seem to get the command
"long" accepted, as the various tutorials explain. When I try to insert it, I get an error, like this:
linux1:~ # smartctl long /dev/nvme0n1
long is an argument to an option you omitted, the type of smartctl command:
smartctl -t long /dev/nvme0n1 --
Felix Miata
I give up. either the fault in the machine prevents me from running the long version, or I have finally lost what's left of my mind! --doug
On 22/07/2021 21.37, mcgarrett wrote:
On July 22, 2021 at 3:56 AM Felix Miata <mrmazda@earthlink.net> wrote:
mcgarrett composed on 2021-07-22 03:30 (UTC-0400):
I have been beating my head against smartctl for over two hours now. I cannot seem to get the command
"long" accepted, as the various tutorials explain. When I try to insert it, I get an error, like this:
linux1:~ # smartctl long /dev/nvme0n1
long is an argument to an option you omitted, the type of smartctl command:
smartctl -t long /dev/nvme0n1
I give up. either the fault in the machine prevents me from running the long version, or I have finally lost what's left of my mind! --doug
The command returns instantly. The execution happens inside the hard disk. The command text should say when you have to come back and query, with another command, the result of the test. Typically, several hours. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
On 2021-07-22 23:50, Carlos E. R. wrote:
On 22/07/2021 21.37, mcgarrett wrote:
I give up. either the fault in the machine prevents me from running the long version, or I have finally lost what's left of my mind! --doug
The command returns instantly. The execution happens inside the hard disk. The command text should say when you have to come back and query, with another command, the result of the test. Typically, several hours.
Doug. There is also the nvme command. Check if you have it (just write nvme and hit enter). If not install nvme-cli from yast. And check out: man nvme man nvme-device-self-test But just like Carlos says, let smartctl run it's course first. cheers, -- /bengan
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2021-07-23 at 13:07 +0200, Bengt Gördén wrote:
On 2021-07-22 23:50, Carlos E. R. wrote:
...
Check if you have it (just write nvme and hit enter). If not install nvme-cli from yast.
And check out: man nvme man nvme-device-self-test
I found this post again. I have nvme-cli installed, but it doesn't contain nvme-device-self-test "program". It does contain "man nvme-device-self-test", though. The program is: nvme device-self-test <device> [--namespace-id=<NUM> | -n <NUM>] [--self-test-code=<NUM> | -s <NUM>] It does not clarify if the test can be done in a device that is being used, as it happens with smartctl. - -- Cheers, Carlos E. R. (from openSUSE 15.2 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCYa85WBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVgPkAmgKmHcB6LPZRyq/S8ICt gUH3FYJ/AJ4nFgCVy8GE/t7zcoaG2XlstSBr6w== =C494 -----END PGP SIGNATURE-----
On 22/07/2021 09.30, mcgarrett wrote:
I have been beating my head against smartctl for over two hours now. I cannot seem to get the command
"long" accepted, as the various tutorials explain. When I try to insert it, I get an error, like this:
linux1:~ # smartctl long /dev/nvme0n1
It is: smartctl --test=short /dev/nvme0n1 smartctl --test=long /dev/nvme0n1 or smartctl -t long /dev/nvme0n1 As you can see in the examples section of the manual. -- Cheers / Saludos, Carlos E. R. (from oS Leap 15.2 x86_64 (Minas Tirith))
participants (5)
-
Bengt Gördén -
Carl Hartung -
Carlos E. R. -
Felix Miata -
mcgarrett