Conversation
Notices
-
Finally, I have started updating my No-Intro set... from September 2018 to a more recent set, ranging from 2021 - 2023, depending on the set.
Around January 2023, homebrew, pirate, and aftermarket stuff is no longer included by default. In my opinion, this is good, because is would be initially assumed that original commercial ROM and disk images would be present.
However, they can be added back in with different settings. I separated the aftermarket ones from the original sets in the /alt/ directory for now; may move those to /aftermarket/. Someday, I will grab the pirate ones as well; those need different settings.
-
Almost forgot, was running into some file corruption issues for some time on the rebuilt file server.
First noticed the issue when I was creating some slipstreamed Windows XP CDs to use on the programmer machine.
It became worse when I was transferring data to that same server to store No-Intro ROMs; almost 20 ROM archives had bad CRC errors and the GBA pack had one corrupted file which wasn't present on the main laptop.
I eventually replaced all four data cables with some I bought a few years ago and were in storage for a bit less. Those replacements were originally meant for a compile box, but the box is now a laptop instead. 😝
I haven't run into the corruption issue since, but I'll keep watch for it. This is why I originally use an external hard drive to do initial work on, then send it to the file server later, but the external drives are not on hand right now.
-
Found the telltale sign re: bad data cable... it was on RAID5 drive 2 (layout: 0 - 1 - 2 - 3; drives are in order of manufacture date). That particular 4TB drive now has a UDMA CRC Error Count of 1, a recent happening during a bunch of large file transfers.
Since I replaced them all, this may no longer be an issue right now.
-
This one I caught a few hours ago: happened while archiving some Nintendo 64 ROMs.
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.
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).