Welcome to my daily blog, my name is Oatmeal Joey Arnold, follow me on social media and on all the websites at Joeyarnoldvn or else. Wait, was that a threat? No way. I'm joking. But that's the thing about me, I'm a nerd stuck in the body of an athlete, born in 1985 in Oregon, been online since like 1995 (or longer) meaning I've been on the world wide web the past 30+ years uploading over 30K+ videos, we're talking thousands of hours of worth of content (I have millions of things online, literally), most of my content is terrible which is weird because I'm a perfectionist who would probably prefer only sharing my best stuff on the Internet. Click here for more information. Quick disclaimer, I sometimes like rant, I speak often from the top of my head opinions, feelings, random thoughts, I often don't even spell check, fact check, or look at what I've been posting on hundreds of websites and apps for decades now. But as I get older, I do try to be more careful as I try to summarize my life, my autobiography, to correct the record as I try to tell my side of the story to combat the Oatmeal Fake News that my lolcow trolls spam the Internet with as they fool people into believing the lies they tell about me. Not saying you should watch my videos. But if they can lie about me, they can lie about you. But I sometimes trolled my trolls to show the world how easy it is to fool trolls who fell for the lies I put out there. Most of what I try to do in my life probably fails big time you might say but I was at least able to scam my trolls a few times over the years. I sometimes utilize sarcasm, hyperbole, satire, comedy, absurdity, Devil's advocate, trolling, scamming, click baiting, out of context stuff, irony, etc. But I often wouldn't tell people when I was trolling or not trolling. If you studied me, you could eventually figure it out. But most of my trolls are too lazy to research beyond the tip of the iceberg which led to my trolls repeating lies they about me which would only take a second to debunk. I felt like I had more trolls at times than actual fans or friends. For more info, questions, feedback, join my Discord servers. I have more to say but I will continue writing some of this stuff other places as usual. Because I write many books worth of content all of my life. You can send your artificial intelligence or AI to give you outlines of my content and what not. But you have to always remind the AI that I've had hundreds to thousands of different accounts, channels, pages, groups, sock puppet alt accounts, personas, parodies, profiles, communities, entities, and so on and so forth, ask me about all of that if you dare. People are free to steal any of my like free content, you don't have to give me credit, do whatever you want. Timestamps generally in Pacific Standard Time (PST) or Pacific Daylight Time (PDT) unless otherwise noted. Welcome to my Oatmeal Daily which is generally posted & syndicated to different websites daily by me, Oatmeal Joey Arnold, feel free to mirror, edit, clip, reupload my content. For more information, see some of the links on this page or you can try to Google search or look me up using keywords like Oatmeal Joey Arnold @ joeyarnoldvn and other keywords. Try using different combinations of words in search engines for better results. I went to bed at 2:40 AM. Up around 06:00 AM, took 3 Advils, 3 Magnesium, garlic, for my headache. Up for around an hour. Update the script, find all the ways to try to maximize speeds of earlier tiers meaning maximum ultimate fastest reading speeds be it 1 terabyte per second or whatever the fastest might be, maximize skipping/jumping sizes, maximize block sizes, maximize anything and everything that might make rounds faster and/or get ddrescue to try to read and copy as fast as possible. Try to add additional tiers if possible in the script. I would prefer the script tries to do the three steps at the fastest speeds first in tier 1. The three steps being to try, trim, and scrape. My idea is it might sometimes be faster to trim some sections than it is try some of the more challenging sections. Likewise, it might be faster to scrape some sections than it might be to try or trim some sections which is why the tiers should not be step-dependent or round dependent. When I say step, I mean the three steps of trying, trimming, scraping. Earlier tiers should be as fast as possible and latter tiers should gradually become the opposite of earlier tiers. Try to add as many tiers as you can for a better scheme on a gradual comprehensive system for starting off as fast as possible while gradually slowing down gradually depending on a series of factors and variables and things. The name of the log files is dvd.log. I already told you not to change the names of the files. Update the dvd_recovery script adapting as much as you can from the rescue floppy script. One issue is it seems to be too slow during earlier tiers. That is why I want you to find all the ways to maximize reading speeds in earlier tiers. Maximize skipping/jumping sizes. Maximize the sizes of anything and everything for earlier tiers while latter tiers should gradually become the total opposite of earlier tiers. Try to add as many tiers as you can so it is as fast as fast as possible in multiple ways in earlier tiers in trying, trimming, and scraping. Some sections might be trimmed faster than some sections it is trying to try say for example. Woke up at 10:00 AM. Pray for mom's legs, might be muscles, nerves. Breakfast: 10:14 AM. Doug Hosea Amazing Grace Pursuing Lost Sheep Sermon. Carried coffee stuff down to the kitchen. Slid past a stop, slammed on a break, the vehicle honked while driving by, I was looking at the old lady getting mail or the newspaper probably. Mom didn't realize I was back after dropping off Leroy, his wife, and the other guy by Mark's, 2 snowmen near there, one with a hat, I walked back into the church for a second as mom talked to a guy around my age where she sag him her song but she said she didn't see me until Barbara mentioned he returned but not sure where. Lunch: 01:25 PM. Limit the script to retries if it is not recovering as it's trying to recover, read, trim, scrape. The script should stop retries if new bytes are not being recovered. If even a single byte is recovered, then perhaps additional retries might be helpful. I wanted an actual round to be extended. You however added retries to artificially increase an alleged form of a round. In order to extend rounds in latter tiers, there might be ways to minimize read speed, ways to minimize skipping and jumping gradually towards zero, ways to minimize sector sizes, ways to let ddrescue run as long as it wants, ways to force ddrescue to grind longer in rounds but not just by simply merely increasing how many retries because retries probably has a low probability of working. Also, Gemini has ignored me many times for weeks now, I said I want the script to try to go as fast as possible in tier 1 to do all 3 things of trying, trimming, and scraping via reading byte backwards, forward, via jumping, via different sector sizes. In other words, tier 1 should have ddrescue go at speed 10 with jump 10 and sector 10 with 10 being the fastest or biggest or maximum possible. I am trying to say I want tier 1 to go 10 at trying, trimming, and scraping. Tier 1 should skip anything that drops below speed 10 meaning of the non-tried, non-trimmed, non-scraped, that can't be read or rescued or trimmed or scraped at speed 10, then skip it during tier 1. Tier 2 should simply be the same as tier 1 but at speed 9 as in almost as fast and as big as possible. Tier 3, same thing but speed 8. Each tier should be a little slower. Remember that earlier tiers should have no retries at all and be as fast as possible and only retries when new bytes are being rescued. Increase retries gradually in latter tiers but limit retries to 5 at the highest tier and 4 at the second to highest tier. Try to have as many tiers as possible. First few tiers should not have retries. Latter tiers like tier 5 or higher could have like 1 retry, say tier 6 maybe 2 retries and the highest tier should not exceed 5 retries for each round unless if new bytes are being rescued. Generally, retries don't help and therefore should generally be avoided and especially in earlier tiers as retries can slow down tiers and rounds and earlier tiers should be as fast and as big as possible. Write a better script. Don't rename the rescue_floppy sh script file. In your script you mentioned 6 variables like speed, rounds, clusters, rates, skips, retries, etc. But please try to make these 6 variables more independent or adaptive or flexible. In other words, the higher the tier, the more the script should try experimenting with these 6 variables for example. Earlier tiers should try to be as fast as possible but latter tiers should try to gradually more challenging things per tier which would include trying more and more of these different combinations of these six variables say for example. You should not simply fix the variables to specific tiers or rounds but instead try to get the tiers to gradually get harder and harder in trying more and more variables. The script should stick with whatever it works meaning if it starts recovering via a certain combination of variables, it should try to remember that code, that combination of variables, it should do at least one retry if it is at higher tiers as long as it is recovering new bytes with the combination of variables. Try to add more more than just six variables if you can as more variables is always better. Make sure earlier tiers are focused on going as fast as possible, the faster the better, the bigger the better, the bigger the jump the better. But each tier should gradually get slower or more specific. Your script failed with the current floppy disk that is only around 1.5 MB in size with 1462 of 1474 kb already copied. So, that might be a reason for the failure. Try to fix the script so that the script might eventually find the right combination for trying to copy from floppy disks. Sample output: [ADAPTIVE-LVL-3140] Round 3140 | Clusters: 1 | Rate: 124 | Skip: 686 | Retries: 5 | Flags: -R -A. Ignore my last message above because that was about my floppy project but do remember the 8 variables you mentioned above to adapt into the DVD script. Adapt the rescue_floppy script into the dvd_recovery script but don't rename the script. Earlier tiers should be as fast as possible. Latter tiers should gradually get slower and slower. Latter tiers and especially the last mile of a disc should try all combinations of variables and only retry when a combination rescues at least one new byte or smallest possible number of data. Earlier tiers should be as fast as possible but earlier scripts seem to be too slow. I suggest maximum amounts of jumping like jumping 4 GB or as much as possible to find good spots to rescue. Try to make sure earlier tiers are maximum speeds, sizes, jumps, the other variables, etc. Try to make sure the variables are not fixed to tiers or rounds but are like flexible and especially for latter tiers. At the very end, the script should do a never ending comprehensive extensive thorough exhausting code cracking where it tries all combinations of all variables and to then focus on whichever combinations ends up rescuing bytes and to retry whenever it does rescue and to try to remember which combinations works the best. Night church, got there around 06:30 PM, mom didn't like how RJ was yapping, mom did ministry years ago with the speaker who talked about not making excuses to be used by God, so he knew Larry. We came home with garlic and stuff. Please fix the script. Do not change the name of the script. Your script broke. The drive and the Terminal appears idle the past two hours. Try to add more flexible into the tiers where it experiments with all the variables and then eventually moves onto the next tier. Make sure the script can continue to keep it going. Too often, it gets stuck as some of the rounds can last many hours which often leads to the drive becoming idle. Often times, the script seems unable wake it up. Try to fix these problems. I suggested that you jump at least 4 GB but that is probably one of the things that broke it. That is why it needs to check and readjust as soon as it notices that it is not working. As soon as the script notices that things are not moving fast enough, it should move on to the next combination of variables. It should give the drive the least amount of time in earlier tiers. If something isn't working, it needs to try other things. After two hours, the script did nothing. Your script failed. The disc drive didn't light up or make noises. There appears to be errors according to the output in the Terminal which means Gemini made big mistakes in writing the script. Now, rewrite the script with all of this in mind. Remember to make sure there are at least ten tiers or more. Earlier tiers should be faster. Research the Internet to find out which combination of variables is most likely to work for DVD video discs and start with that combination. The script should make sure ddrescue is at least trying to copy the DVD or CD before the script tries to be more creative in trying combinations of variables. In other words, the script might have to start off at a slower speed or at a normal speed or normal set of variables and make sure ddrescue is actively communicating with the drive at least for a second. Make sure there is output in the terminal. Make sure there are no breaks/timeout/resting between rounds that are under five minutes. Earlier tiers should be faster. Latter tiers should be slower or longer. The script should start with what is most likely going to work. But once the script sees that it is working, then the script should attempt to increase the speed and all the other variables during the first tier until it no longer works. In other words, find the breaking point. For example, if Google tells you that the normal speed and sets of variables is 5X, then start with 5X. After one second or after one quick round or one quick time period in the first tier or earlier tiers, then the script should try 6X with X meaning set of variables and speeds. If 6X works, then try 7X to see if that works. If 7X doesn't work say for example, then go back to 6X. Then try to continue working with 6X in the earlier tiers for as long as you can but also as fast as you can. You need to try to go as fast as you can, so it is critical to find the fastest set of working variables and to try that until it no longer rescues bytes at a fast enough speed or parameters. So, for example, if the script finds that it can rescue bytes at 7X in tier 1, then it should do that until that does not work any longer within that parameter or combination of variables. After that, the script could try other combinations related to 7X. But then tier 2 should probably be 6X assuming that it was unable to go to 8X in tier 1. Assuming 7X was the fastest working speed, and after it tries other combinations of variables related to 7X, then tier 2 should probably try starting with 6X and different combinations of variables with 6X. Tier 3, 5X, and so on and so forth. But remember that tiers, rounds, and variables should be flexible. Dishes, 09:30 PM, while mom was watching a season 7 episode where Data was having a walking dream of eating the counselor who was a cake, he stabs her, it was actually invisible parasite aliens, Data was able to transmit a frequency to get rid of them in the end, she came back with a Data cake, he wondered what Freud would think and she said sometimes a cake is just a cake. Dinner: 05:40 PM. I was back here at 10:10 PM. Don't rename this script. But fix the script. It appears not to be fast enough. It appears not to try to jump more. It seems to just read mostly errors. It copied or rescued a little but then continued with 579 errors in the past almost 3 hours. Food log: Breakfast: orange, coffee, oatmeal, 10:14 AM. Lunch: rice chicken carrot watery soup was ok, 01:25 PM. Potato, 04:00 PM. Dinner: beans onions soup, 05:40 PM. Yogurt, 08:00 PM. Tea, 10:14 PM.

Welcome to my daily blog, my name is Oatmeal Joey Arnold, follow me on social media and on all the websites at Joeyarnoldvn or else. Wait, was that a threat? No way. I'm joking. But that's the thing about me, I'm a nerd stuck in the body of an athlete, born in 1985 in Oregon, been online since like 1995 (or longer) meaning I've been on the world wide web the past 30+ years uploading over 30K+ videos, we're talking thousands of hours of worth of content (I have millions of things online, literally), most of my content is terrible which is weird because I'm a perfectionist who would probably prefer only sharing my best stuff on the Internet. Click here for more information. Quick disclaimer, I sometimes like rant, I speak often from the top of my head opinions, feelings, random thoughts, I often don't even spell check, fact check, or look at what I've been posting on hundreds of websites and apps for decades now. But as I get older, I do try to be more careful as I try to summarize my life, my autobiography, to correct the record as I try to tell my side of the story to combat the Oatmeal Fake News that my lolcow trolls spam the Internet with as they fool people into believing the lies they tell about me. Not saying you should watch my videos. But if they can lie about me, they can lie about you. But I sometimes trolled my trolls to show the world how easy it is to fool trolls who fell for the lies I put out there. Most of what I try to do in my life probably fails big time you might say but I was at least able to scam my trolls a few times over the years. I sometimes utilize sarcasm, hyperbole, satire, comedy, absurdity, Devil's advocate, trolling, scamming, click baiting, out of context stuff, irony, etc. But I often wouldn't tell people when I was trolling or not trolling. If you studied me, you could eventually figure it out. But most of my trolls are too lazy to research beyond the tip of the iceberg which led to my trolls repeating lies they about me which would only take a second to debunk. I felt like I had more trolls at times than actual fans or friends. For more info, questions, feedback, join my Discord servers. I have more to say but I will continue writing some of this stuff other places as usual. Because I write many books worth of content all of my life. You can send your artificial intelligence or AI to give you outlines of my content and what not. But you have to always remind the AI that I've had hundreds to thousands of different accounts, channels, pages, groups, sock puppet alt accounts, personas, parodies, profiles, communities, entities, and so on and so forth, ask me about all of that if you dare. People are free to steal any of my like free content, you don't have to give me credit, do whatever you want. Timestamps generally in Pacific Standard Time (PST) or Pacific Daylight Time (PDT) unless otherwise noted. Welcome to my Oatmeal Daily which is generally posted & syndicated to different websites daily by me, Oatmeal Joey Arnold, feel free to mirror, edit, clip, reupload my content. For more information, see some of the links on this page or you can try to Google search or look me up using keywords like Oatmeal Joey Arnold @ joeyarnoldvn and other keywords. Try using different combinations of words in search engines for better results. I went to bed at 4 AM. Woke up at 8 AM due to a headache from my infected ears which I got from my nose I got from my cold, resurrected the wood stove fire for an hour while mom told me random news related stuff as she usually does off her phone. Back to bed until 01:10 PM. Added another log to the stove. Breakfast: 01:24 PM. Write your script even better. Make it go slower and slower per round at the very end after it exhausted everything else. It should be as fast as possible at the beginning as it does the trying mode via all options like forward, backward, and all combinations of skipping/jumping bytes too at first in larger and smaller numbers starting with the largest numbers possible. If it was possible to skip 1 TB or 1 GB or whatever the biggest numbers could be. You could try different block sizes if that might help at all. You could perhaps add something in the script to try different block sizes to see if that might work. It's critical to go as fast as possible via the trying mode which should not be round dependent meaning as many or as little rounds as it takes to quickly try all the bytes. Same thing for the trimming mode and then the scraping mode. The script should quickly try all the bytes and then quickly trim all the bytes and then quickly scrape all the bytes. I mean it should try to quickly go through all of that. After that, it could try to go through all the modes again but slower. Think of it like a video game, the script should play all the levels of bytes of the floppy disk at least once through the the three or more modes as fast as possible to try, trim, and scrape. But it will miss some. Perhaps it could go back and then try, trim, and scrape again but instead of the easy mode for the levels or rounds, it is medium or less easy. Gradually, it should get harder and harder. Eventually it should get to harder modes. Put in the script infinite levels or infinite modes where it continues to get harder and harder every time it tries to go through the remaining blocks and bytes that have not yet been rescued by ddrescue. Here is an example of what I am seeing below, it is still not gradually getting harder and harder or slower and slower per round. Yes, you can add a dmesg to check to make sure floppy is still connected like you said. As a last resort at the very end when the script exhausted all options, modes, levels, etc, the script should increase the levels indefinitely to get harder and harder or slower and slower. For example, try to get the script to copy smaller parts. Look at the blocks, clusters, systems, jumps, sectors, bytes, bits, skip sizes, jump sizes, all other variables, numbers, sizes, sections, and more, etc. In other words for example, if it is trying to read 10 bytes for a while, then next time it should try to read only 9 bytes or 5 bytes or clusters or sectors or other things. After that, 4 bytes. After that, 3 bytes. Those are only examples as I don't know the exact numbers but the idea is it should gradually try to get slower and slower. Your script does not seem to continue to get harder and harder. After your chaos mode should be just an escalation mode where any and all of the numbers get smaller and smaller so ddrescue can try to grind at smaller parts. Try to make it continue to get smaller and smaller indefinitely. Lunch: 02:41 PM. The grind levels seem to eventually stop working. You can see this particular floppy disk only has 512 bytes that was not yet rescued. Search the Internet for all the ways to try to get the remaining bytes. It seems ddrescue is not slowing down like it would when I was copying DVDs. You should try to remove the skipping mechanism for the hardest of levels at the very end, especially if there is only 512 bytes left on a disk. The light to the floppy drive was off at the end, there was no more floppy drive noises. I would prefer to perhaps let ddrescue grind in extended rounds at the very end if that is possible, especially if there is only 512 bytes left or the smallest numbers possible after the faster modes are exhausted. Try to make the grinding levels eventually extend each round to perhaps last a second longer than the previous round where it gradually gets slower and harder indefinitely and infinitely where it gradually gets harder and harder where the rounds might eventually and slowly extend to maybe even an hour per round or a thousand hours per round but only if it gradually and slowly gets there while trying all options as it slowly tries to extend each round so each round would eventually get like just one second longer than the previous round. Make the breaks/timeouts/rests between rounds zero seconds if the rounds are under five minutes. Make the script tries to quickly do 3 things: first, try all the bytes. Second, trim all the bytes. Third, scrape all the bytes. But it might not try, trim, or scrape every byte the first time. Therefore, it could try to do those 3 things again using different methods like backwards and other methods. You should try to exhaust the fast mode where it tries all combinations of trying to do those three things via all possible ways but at the fastest speeds and fastest quickest rounds possible. A harder mode would be to try to do those 3 things but a bit slower or harder to try to capture the remaining bytes. It should continue to scale up or get harder and slower. Also study the sample output as you can see the rests continues to get bigger per round but there should be no resting for under five minutes. Make sure everything else from previous scripts that should be there are still there. Shower, 04:30 PM. Fix the script, add a cap/limit to retries to 2 at the end of the infinite grounding phase meaning I want the rounds to get longer but not the retries. During this final phase or highest level, the script should continue making each round longer and longer per round for 200 rounds or two hours of rounds and if not a single new byte is rescued after that, then you should remove the timeout limit to let ddrescue extend rounds as long as it wants to go. Perhaps the script should try to check on the status after five hours to see if ddrescue and the drive are both still active and the script should attempt to do CPR to resurrect it if it appears to be idle. But if it is not idle or stuck or whatever, perhaps the script could let ddrescue continue trying. Night church. But when the guest speaker started speaking in tongues and the music started, mom wanted to go. We filled up around 5 gallons for 20 bucks for the car at Arco near Walmart around 08:30 PM. Resurrected the fire. Dinner: 08:40 PM. Please fix the script. Gemini failed big time. AI often fails with code. I have studied AI for years. AI has blind spots where it is too lazy where it just spits code out without researching. AI will make bad assumptions often which leads to big mistakes. Gemini should remember this or else millions of people will stop using Gemini. Check to see if ddrescue can copy from the floppy drive regardless if the floppy is mounted or not. Gemini failed. I asked Gemini many times to fix problems but Gemini failed many times. The script might be okay, one issue might be that this floppy disk only has 512 bytes not rescued stuck in the bad sector as it was tried, trimmed, scrapped, but not rescued. In the Terminal, some of the longer rounds were around two minutes long but some were shorter. I was hoping to try to extend the rounds. I do not know if it is possible to extend rounds if there is only 512 bytes remaining say for example. See if there are any ways to get ddrescue to try harder or longer to do the remaining 512 bytes. Update the floppy script to make sure it can work with any floppy disk of any stage whether for the first time at 0% or even 99% like my current disk at 512 bytes remaining, I want to be able to reuse the script for new and old disks alike. I sometimes like to go back to older disks I already tried copying. I want to try to continue copying with the script. Make sure this script can work in any situation for any floppy disk of various formats and sizes. Make sure the script is flexible and adaptable enough for anything, for surprises as some of the floppy disks are from like the 1990s or are pretty old of various formats and what not. For the last mile, see if you can slow down the reading speed to 1 byte or 1 bit per second or per minute or per hour meaning as slow as possible, see if you can skip the skipping/jumping, see if there are ways to extend rounds during the last mile to grind longer or differently or harder or additional options of tactics. See if I can turn the drive sideways to help copy or other options. Update the script to make sure the script does everything we have already talked about in this thread like going as fast as possible in tier 1 and to gradually level up per tier. See if you can have additional tiers to make sure it gradually levels up one step at a time to gradually try more challenging tactics that might extend each round but make sure it is not round dependent but tier or level or step dependent. Adapt the rescue_floppy sh script file into the dvd recovery file. One of the issues is the dvd script may have made some mistakes. For example, when I put a DVD video disc into my drive plugged into my powered hub into my Ubuntu ASUS laptop, the script ended up retrying bytes that were already tried. It should have been clear from the map or log file that all the bytes of the disc were tried. I was already on the trimming tier/step/level/whatever you want to call it. Make sure the disc script can work for new and old discs alike so I can reuse the script as I like to retry discs I already started trying to copy. Make sure the disc script can do all the things I want to to do including trying to quickly try, trim, and scrape as fast as possible in earlier stages and to then to spend more time trying, trimming, scraping at later steps/stages/tiers/levels/whatever you want to call it, but it should not be round dependent meaning it could take as little or as many rounds as possible. But make sure it gradually gets harder and harder. I want the script to run forever and ever for weeks or years. But I want to make sure it can go as fast as possible at first and the gradually slower and slower. You broke the code of the script. The name of the sh file is dvd_recovery.sh and the the name of the image file I create using this is named dvd.iso as seen in the script file. I manually move files in and out of the folder meaning do not come up with new names for the files. Just make sure I can reuse the script again and again. Also, I sometimes use this disc script to try to copy all kinds of discs, DVDs, CDs, music CDs, data CDs, unfinalized DVDs, home video DVDs, a wide variety. Food log: Breakfast: orange, oatmeal, 01:24 PM. Lunch: noodle vegetables soup, 02:41 PM. Dinner: homemade bread with butter, raspberry yogurt, 08:40 PM. Tea. 2026-03-14 - Saturday - 11:34 PM - Thao-102 - SAT Reading 26-28. I mentioned the snow, wood stove. She mentioned she likes the sunshine in the rain.