<?xml version="1.0" encoding="UTF-8"?>
<oembed>
 <version>1.0</version>
 <type>link</type>
 <provider_name>Ami Sapphire's Notices</provider_name>
 <provider_url>http://cwcyrix.nsupdate.info/gnu-social/public/</provider_url>
 <title>Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)'s status on Tuesday, 04-Apr-2023 09:37:53 EDT</title>
 <author_name>Clarissa Walker (amisapphire@cwcyrix.nsupdate.info)</author_name>
 <author_url>http://cwcyrix.nsupdate.info/gnu-social/public/index.php/amisapphire</author_url>
 <url>http://cwcyrix.nsupdate.info/gnu-social/public/notice/59</url>
 <html>This one I caught a few hours ago: happened while archiving some Nintendo 64 ROMs.&lt;br /&gt;
&lt;br /&gt;
Miraculously, the initial transfer from two days ago did not corrupt any of them (those are big endian; also lucky, because there is no local mirror...), but copying them for the byte-swapped conversion set directly on the server corrupted one ROM in that copied set. This is becoming much less frequent, at least.&lt;br /&gt;
&lt;br /&gt;
Checked RAID5 status, array is fine. This issue shows up over a wireless network; should try wired network and local transfer... and probably examine the SATA ports on the motherboard, among other things (which I may eventually replace anyway).</html>
</oembed>
