@park0kyung0wo: I would say no. Software cannot damage hardware, but overheat and brutal shutdowns can.
Search Criteria
Package Details: memtest86-efi 1:11.0build1000-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/memtest86-efi.git (read-only, click to copy) |
|---|---|
| Package Base: | memtest86-efi |
| Description: | A free, thorough, stand alone memory test as an EFI application |
| Upstream URL: | https://www.memtest86.com |
| Licenses: | GPL2, custom:PassMark |
| Submitter: | UnicornDarkness |
| Maintainer: | UnicornDarkness |
| Last Packager: | UnicornDarkness |
| Votes: | 114 |
| Popularity: | 0.77 |
| First Submitted: | 2013-10-29 10:25 (UTC) |
| Last Updated: | 2024-08-26 07:41 (UTC) |
Dependencies (3)
- p7zip (p7zip-natspecAUR, p7zip-full-binAUR, 7-zip-fullAUR) (make)
- efibootmgr (efibootmgr-gitAUR) (optional) – to add a new EFI boot entry
- grub (grub-linux-defaultAUR, grub-coreosAUR, grub-blscfgAUR, grub-xen-gitAUR, grub-luks-keyfileAUR, grub-silentAUR, grub-gitAUR, grub-improved-luks2-gitAUR, grub-libzfsAUR, grub-grubenv-btrfsAUR) (optional) – to add MemTest86 entry in GRUB2 menu
Required by (0)
Sources (4)
UnicornDarkness commented on 2018-07-05 19:14 (UTC) (edited on 2018-12-07 09:41 (UTC) by UnicornDarkness)
park0kyung0won commented on 2018-07-04 20:53 (UTC)
Oh I see thanks for the reply
I'm asking for I do not know much about low level efi things, Can efi firmwares like memtest damage my hardware?... I hope not :(
UnicornDarkness commented on 2018-07-04 16:12 (UTC) (edited on 2018-07-04 16:12 (UTC) by UnicornDarkness)
@park0kyung0won: I'm sorry, I can't help you: it's not a packaging issue.
If you shutdown your computer safely under MemTest86, it may be an upstream bug.
I suggest you to contact PassMark Support[3] or try MemTest86 forum[4].
park0kyung0won commented on 2018-07-04 12:02 (UTC)
Hello
I have encountered a problem while using this package. I installed this memtest86-efi package, with option of adding entry to systemd-boot list. I aborted memtest in the middle(no particular reason, I couldn't wait), and booted back to Arch Linux. Then I got an error from S.M.A.R.T that my nvme SSD device has been degraded, which Arch Linux is installed. I had one "Media and Data Integrity Errors" on S.M.A.R.T record of that nvme SSD drive.
I was curious so I've conducted tests. Everytime I do memtest, that "Media and Data Integrity Errors" count increased by one, and that integrity error made status of my nvme SSD degraded. So I highly suspect this memtest was a cause...
buzo commented on 2018-02-27 19:33 (UTC)
Looks good, thanks for the quick fix!
UnicornDarkness commented on 2018-02-27 19:09 (UTC) (edited on 2018-02-27 19:10 (UTC) by UnicornDarkness)
Ok, done in following commit: a1c4551125f1
Tell me if you encounter issue. And if you have a better idea than p7zip to extract .img file...
UnicornDarkness commented on 2018-02-27 18:16 (UTC)
@buzo: Try to delete the ISO file by yourself.
Ok, switched from md5sums to sha512sums. I found an upstream FTP, but that is the USB version, ISO seems not present: https://www.passmark.com/ftp/memtest86-usb-7.5.1001.tar.gz I'll investigate.
buzo commented on 2018-02-27 13:49 (UTC)
Now I get a validity check error because memtest86-efi-7.5-1-x86_64.pkg.tar.xz is still there, so makepkg does not download the new version. This is broken. I think the file should be renamed after download. (And upstream should add a version number to the file name.)
And I agree, MD5 is outdated and not secure. Please switch to a modern hash (sha256sum for instance) while you are at it.
UnicornDarkness commented on 2018-02-27 12:12 (UTC)
@xiretza: Thank for your report. It would be the same issue with sha512sums... md5sums updated.
Pinned Comments
UnicornDarkness commented on 2019-06-08 08:52 (UTC) (edited on 2019-06-08 08:53 (UTC) by UnicornDarkness)
As you probably know, the
<https://www.memtest86.com/downloads/memtest86-usb.zip>URL is likely to cause problems, like this error:To avoid this problem, I prefer to reupload
memtest86-usb.ziparchive somewhere else, where this kind of breakage will not appear.I can't upload this archive on AUR directly (archive is 8 MB but AUR accepts 250 KiB maximum), so I decide to put this archive on my Git repository to avoid future breakages.
I hope it suits you.