Differences

This shows you the differences between two versions of the page.

--- linux64 [2025/03/27 19:18] – [Problems & Solutions] bengt
+++ linux64 [2025/04/18 14:34] (current) – [efi partition too small] bengt
@@ Line 142: / Line 142: @@
 Eventually I found https://www.reddit.com/r/Fedora/comments/186amfb/kernels_6510_does_not_install_properly_in_fedora/ and https://discussion.fedoraproject.org/t/f39-kernels-fail-to-install-when-boot-efi-machineid-is-present/96086 which apparently was a fedora 39 problem when upgrading since forever. The solution was:
   # mv "/boot/efi/$(cat /etc/machine-id)" "/boot/efi/$(cat /etc/machine-id)_disabled"
+I deleted the _disabled folder later to get back some disk storage. Seemed to boot fine, but it was the rescue stuff that was taking disk space.
 ==== efi partition to fat32 ====
@@ Line 1039: / Line 1040: @@
 Calculate sha256 of all files in folder and store in text file that can be used to check for bit rot later or when replacing disk and checking rsync:
-  $ find movies/ -type f -exec sha256sum {} \; >checksum.txt
+  $ find movies/ -type f -exec sha256sum {} \; >checksum.txt; sort -k2 -o checksum.txt checksum.txt
-  $ sort -o checksum.txt checksum.txt
+  or
+  $ find movies/ -type f | sort | xargs -d'\n' sha256sum >checksum.txt
+File checksum mismatch after copying files to a new disk can be due to memory issues. It can even vary checksumming the same file on the same disk. You can use "memtester" live in linux or reboot into memtest in the grub menu. In my case one of the two pairs/kits were faulty I eventually found out after removing/swapping pairs.
 ==== Picade =====