linux64
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| linux64 [2025/03/27 19:14] – [Problems & Solutions] bengt | linux64 [2025/04/18 14:34] (current) – [efi partition too small] bengt | ||
|---|---|---|---|
| Line 142: | Line 142: | ||
| Eventually I found https:// | Eventually I found https:// | ||
| # mv "/ | # mv "/ | ||
| + | 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 ==== | ==== 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: | 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 {} \; >movies_sha256.txt | + | $ find movies/ -type f -exec sha256sum {} \; >checksum.txt; |
| - | $ sort -o movies_sha256.txt movies_sha256.txt | + | or |
| + | $ find movies/ -type f | sort | xargs -d' | ||
| + | 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 " | ||
| ==== Picade ===== | ==== Picade ===== | ||
linux64.1743102892.txt.gz · Last modified: 2025/03/27 19:14 by bengt