Weird -
All my Intel boxes (with Intel graphics) ran this fine. (7 boxes)
All my AMD boxes (with AMD graphics) I got this: (3 boxes)
LLR1:~ # hw-probe -all -upload
Probe for hardware ... Ok Reading logs ... Ok
Can't connect to linux-hardware.org:80 (Connection timed out)
Connection timed out at /usr/lib/perl5/vendor_perl/5.26.1/LWP/Protocol/http.pm line 50.
ERROR: failed to upload dataLLR1:~ #
LLR2:~ # hw-probe -all -upload
Probe for hardware ... Ok Reading logs ... Ok
Can't connect to linux-hardware.org:80 (Connection timed out)
Connection timed out at /usr/lib/perl5/vendor_perl/5.26.1/LWP/Protocol/http.pm line 50.
ERROR: failed to upload dataLLR2:~ #
My AMD boxes (all were upgraded from 41 > 42 > 15.0 > 15.1 )
LLR1:~ # hw-probe
Executing hw-probe -all -upload
Probe for hardware ... Ok
Reading logs ... WARNING: X11-related logs are not collected (try to run 'xhost +local:' to enable access or run as root by su)
Ok
Can't connect to linux-hardware.org:80 (Connection timed out)
Connection timed out at /usr/lib/perl5/vendor_perl/5.26.1/LWP/Protocol/http.pm line 50.
ERROR: failed to upload data
LLR1:~ # curl -sSf https://linux-hardware.org
curl: (7) Failed to connect to linux-hardware.org port 443: Connection timed out
LLR1:~ # zypper se -si curl
Loading repository data...
Reading installed packages...
S | Name | Type | Version | Arch | Repository
---+----------------+---------+--------------------+--------+--------------------------
i | curl | package | 7.60.0-lp151.5.9.1 | x86_64 | openSUSE-Leap-15.1-Update
i | libcurl4 | package | 7.60.0-lp151.5.9.1 | x86_64 | openSUSE-Leap-15.1-Update
i | libcurl4-32bit | package | 7.60.0-lp151.5.9.1 | x86_64 | openSUSE-Leap-15.1-Update
i+ | php7-curl | package | 7.2.5-lp151.6.22.1 | x86_64 | openSUSE-Leap-15.1-Update
i | python3-pycurl | package | 7.43.0.2-lp151.1.1 | x86_64 | openSUSE-Leap-15.1-Oss
LLR1:~ #
For those that are interested - my failure to connect on both of my AMD desktops was due to an old rule in iptables blocking all 80.xx.xx.xx connections.
Once I removed that entry and restarted iptables hp-probe worked as expected.
When I build this pc, learning form previous issues because not having a clue on the command line or in the bios, which hard disk, what OS was, I bought two the same size like before, but different brands.
The labels on the disk even colour match, seagate green for openSUSE and Westerndigital blue, for windows.
Do you know both models have a shorter average MTBF (like on those statistics Backblaze puts out annually)? Or have you personally experienced issues with your two dard disks?
In any case, maybe you should keep a closer look at what smartd (if active) or smartctl are reporting:
sudo **smartctl** -a /dev/sda > smartctl-2020-04.text
sudo **smartctl** -a /dev/sdb >> smartctl-2020-04.text
*# . . . repeat for every connected mass-storage device*
less -N smartctl-2020-04.text
I’ve been keeping those reports over years. I generate a new one and compare it to the previous one at the begin of every monthly backup session.
I hope your green disk is ok, don’t care about the blue one. Just kidding. Cheers!
user@localhost:~> sudo -E hw-probe -all -upload
WARNING: 'edid-decode' package is not installed
Probe for hardware ... Ok
Reading logs ... Ok
Uploaded to DB, Thank you!
Probe URL: https://linux-hardware.org/?probe=9a422a10d3