Hi there!
Good news for all interested in hardware compatibility and reliability.
I've started a new project to estimate reliability of hard drives and SSD in real-life conditions based on the SMART data reports collected by Linux users in the Linux-Hardware.org database since 2014. The initial data (SMART reports), analysis methods and results are publicly shared in a new github repository: https://github.com/linuxhw/SMART. Everyone can contribute to the report by uploading probes of their computers by the hw-probe tool!
The primary aim of the project is to find drives with longest "power on hours" and minimal number of errors. The following formula is used to measure reliability: Power_On_Hours / (1 + Number_Of_Errors), i.e. time to the first error/between errors.
Please be careful when reading the results table. Pay attention not only to the rating, but also to the number of checked model samples. If rating is low, then look at the number of power-on days and number of errors occurred. New drive models will appear at the end of the rating table and will move to the top in the case of long error-free operation.
Thanks to ROSA, Fedora, Ubuntu, Debian, Mint, openSUSE, Arch, Gentoo users and others who had made this work possible by contribution to the database!
03.03.2018, 10:08, "Andrey Ponomarenko" andrewponomarenko@yandex.ru:
Hi there!
Good news for all interested in hardware compatibility and reliability.
I've started a new project to estimate reliability of hard drives and SSD in real-life conditions based on the SMART data reports collected by Linux users in the Linux-Hardware.org database since 2014. The initial data (SMART reports), analysis methods and results are publicly shared in a new github repository: https://github.com/linuxhw/SMART. Everyone can contribute to the report by uploading probes of their computers by the hw-probe tool!
The primary aim of the project is to find drives with longest "power on hours" and minimal number of errors. The following formula is used to measure reliability: Power_On_Hours / (1 + Number_Of_Errors), i.e. time to the first error/between errors.
Please be careful when reading the results table. Pay attention not only to the rating, but also to the number of checked model samples. If rating is low, then look at the number of power-on days and number of errors occurred. New drive models will appear at the end of the rating table and will move to the top in the case of long error-free operation.
Hi,
I've just created Fedora package for hw-probe. See https://github.com/linuxhw/hw-probe/blob/master/INSTALL.md#install-on-fedora.
The command to replenish the database:
sudo hw-probe -all -upload
AppImage is also available to run without installing: https://github.com/linuxhw/hw-probe#appimage
OBS project: https://build.opensuse.org/package/show/home:linuxbuild/hw-probe
Thank you.
On Sun, 05 Aug 2018 14:47:06 +0200, Andrey Ponomarenko wrote:
I've just created Fedora package for hw-probe. See https://github.com/linuxhw/hw-probe/blob/master/INSTALL.md#install-on-fedora.
Installing a package out of repository for its maintenance is not great. I tried to find a repository for it but what is Build vs. Publish vs. Use for Build? https://build.opensuse.org/repositories/home:linuxbuild/hw-probe COPR would be better for Fedora, until it is in standard Fedora distro.
Jan
05.08.2018, 16:09, "Jan Kratochvil" jan.kratochvil@redhat.com:
On Sun, 05 Aug 2018 14:47:06 +0200, Andrey Ponomarenko wrote:
I've just created Fedora package for hw-probe. See https://github.com/linuxhw/hw-probe/blob/master/INSTALL.md#install-on-fedora.
Installing a package out of repository for its maintenance is not great. I tried to find a repository for it but what is Build vs. Publish vs. Use for Build? https://build.opensuse.org/repositories/home:linuxbuild/hw-probe COPR would be better for Fedora, until it is in standard Fedora distro.
sudo dnf config-manager --add-repo https://download.opensuse.org/repositories/home:/linuxbuild/Fedora_Rawhide/h... sudo dnf config-manager --set-enabled home_linuxbuild sudo dnf install hw-probe
But it installs a lot of unused dependencies (about 140 packages on F28 Live). It's better to use lightweight all-in-one AppImage (F15 and higher) or Snap (F26 and higher):
https://github.com/linuxhw/hw-probe#appimage https://github.com/linuxhw/hw-probe#snap
Usually people don't create more than two probes per computer, so receiving updates is not necessary.
Thank you.
Hello,
On Tue, 07 Aug 2018 10:21:05 +0200, Andrey Ponomarenko wrote:
sudo dnf config-manager --add-repo https://download.opensuse.org/repositories/home:/linuxbuild/Fedora_Rawhide/h... sudo dnf config-manager --set-enabled home_linuxbuild sudo dnf install hw-probe
that looks better, thanks. Still it is from non-Fedora build but then it contains only a text script anyway.
It's better to use lightweight all-in-one AppImage (F15 and higher) or Snap (F26 and higher):
https://github.com/linuxhw/hw-probe#appimage https://github.com/linuxhw/hw-probe#snap
I do not like recommending such insecure behavior - to run untrusted binaries with root permissions - without even warning it is insecure.
Usually people don't create more than two probes per computer, so receiving updates is not necessary.
It is insecure to keep non-updated software installed/available on your computer.
Anyway it somehow does not work for me, in the past I registered https://linux-hardware.org/?probe=bf0a7f04b4
But now I cannot update the info trying to prevent a duplicate: # hw-probe -get-inventory-id Group ID: 8557d9ad # hw-probe -inventory-id bf0a7f04b4 # hw-probe -get-inventory-id Group ID: 4d2703f5 # hw-probe -inventory-id bf0a7f04b4 # hw-probe -get-inventory-id Group ID: 07746fb5 # hw-probe -get-inventory-id Group ID: 077ce20e # hw-probe -inventory-id 0xbf0a7f04b4 # hw-probe -get-inventory-id Group ID: 7b448de5 # hw-probe -get-inventory-id Error request # hw-probe -get-inventory-id Error request
Jan Kratochvil
07.08.2018, 12:05, "Jan Kratochvil" jan.kratochvil@redhat.com:
Hello,
On Tue, 07 Aug 2018 10:21:05 +0200, Andrey Ponomarenko wrote:
sudo dnf config-manager --add-repo https://download.opensuse.org/repositories/home:/linuxbuild/Fedora_Rawhide/h... sudo dnf config-manager --set-enabled home_linuxbuild sudo dnf install hw-probe
that looks better, thanks. Still it is from non-Fedora build but then it contains only a text script anyway.
It's better to use lightweight all-in-one AppImage (F15 and higher) or Snap (F26 and higher):
https://github.com/linuxhw/hw-probe#appimage https://github.com/linuxhw/hw-probe#snap
I do not like recommending such insecure behavior - to run untrusted binaries with root permissions - without even warning it is insecure.
Usually people don't create more than two probes per computer, so receiving updates is not necessary.
It is insecure to keep non-updated software installed/available on your computer.
Anyway it somehow does not work for me, in the past I registered https://linux-hardware.org/?probe=bf0a7f04b4
But now I cannot update the info trying to prevent a duplicate: # hw-probe -get-inventory-id Group ID: 8557d9ad # hw-probe -inventory-id bf0a7f04b4 # hw-probe -get-inventory-id Group ID: 4d2703f5 # hw-probe -inventory-id bf0a7f04b4 # hw-probe -get-inventory-id Group ID: 07746fb5 # hw-probe -get-inventory-id Group ID: 077ce20e # hw-probe -inventory-id 0xbf0a7f04b4 # hw-probe -get-inventory-id Group ID: 7b448de5 # hw-probe -get-inventory-id Error request # hw-probe -get-inventory-id Error request
1) Yep, it's safer to have a package in the official Fedora repositories. Spec is available in the OBS project: https://build.opensuse.org/package/view_file/home:linuxbuild/hw-probe/hw-pro...
2) The -get-inventory-id option creates a new inventory id (or 'group') to mark new probes by this id. You've created too many inventory ids per day and received an error when trying to create more. Usually it's enough to have only one inventory id.
bf0a7f04b4 is a probe id (10-digit), not the inventory id. Your inventory id is 8557d9ad (8-digit). Just use it to mark all your future probes with the help of -inventory-id option:
sudo hw-probe -all -upload -inventory-id G
It's enough to mark each unique computer once.
The command:
hw-probe -inventory-id G
does nothing without -all and -upload options.
The command:
hw-probe -get-inventory-id
creates a new group/inventory id (G) each time.
Thank you.
On Wed, 08 Aug 2018 02:11:08 +0200, Andrey Ponomarenko wrote:
- The -get-inventory-id option creates a new inventory id (or 'group') to
mark new probes by this id. You've created too many inventory ids per day and received an error when trying to create more. Usually it's enough to have only one inventory id.
bf0a7f04b4 is a probe id (10-digit), not the inventory id. Your inventory id is 8557d9ad (8-digit).
How did you find out the 8-digit id?
The command:
hw-probe -get-inventory-idcreates a new group/inventory id (G) each time.
# -inventory-id ID # Set inventory ID of the probe. You can get this ID # by the -get-inventory-id option. # # -get-inventory-id # Get inventory ID.
From the help it looks to me -get-inventory-id should return what has been set by -inventory-id. The text "Get inventory ID." does not suggest me it should create anything new.
Thanks, Jan
-
Andrey Ponomarenko -
Jan Kratochvil