@redblueflame This command still works "fsck /dev/{parition name here}" In my case fsck/dev/sda2 worked to bring me back to my original partition.

@redblueflame Anytime I add roms or preform a scrape I am using my PC connected over the network to the recall/share folder. The only reason I attempted fdisk -l to check the disk was after Recalbox failed. I then went through Recalbox login from prompt then from there initiated the Linux command. My current setup is a mini computer using an SSD flashed with Recalbox as the primary.

@redblueflame Thanks for getting back to us, in my case I have attempted both. When using the integrated scraper only with mamedb selected as server this failure occurred. I then used the external scraper as recommended and everything was working perfectly until I tried scrapping Wii games then the same issue happened again. At first thought, I believed maybe I had exceeded my storage limitations on the drive. Unfortunately this was not the case, I haven't even used a quarter of the drive capacity before failure. Thinking that maybe it was my drive that was the problem I then tried with another drive and again I had the same issue. Whats weird is that a new partition is created with exactly 128MB that only has the base factory Recalbox os. When I do an fdisk -l I can see additional partitions so not sure if its a matter of the Boot record getting corrupted here?

@KizerAir This is exactly the same issue I am having as well. The same issue happened when I tried to scrap as well. I am wondering if there is an issue with the 64 bit version, have you tested the 32 bit version yet? I think, I will attempt that to check the stability.