Internal drive MPC X SE

After I installed STEMS the internal files (Sounds, VSTs, etc) vanished from my internal drive. The internal drive is now empty and shows as 2GB. Is there a way I can restore it back to when it was new out the box?

Hello, I have exactly the same problem on MPC Key 61 following the beta 3 update, the disk is full, I only have 19MB left out of 350MB while the disk is 32GB! It's definitely a partition error, but I couldn't find the procedure to factory reset and reformat the internal drive? could anyone help us?

What filesystem you’re on ?
so far I’ve gathered info from several folks on FB which drives dissapeared.
The ratio is: 3xExFat 1xNTFS and 2x unknowns as they had no idea lol.
One of the things I usualy do is to check how do the partitions look like under the hood, I’ve not done it yet this time (adhd kicked in) - I’ll double check it in the afternoon after work. My suspicion is that (maybe) they mount a small partition on external drive when detected, and then it’s is used for temp files or something… don’t know, but on the other hand they would have to resize the current partition and messing with customer data is a no no in my book so doubt it tbf.

I am on the original internal disk, so I suppose formatted in several exfat partitions. Everything disappeared following the update to v3beta, even the demos are no longer present, I attach some photos and video.

https://support.akaipro.com/helpdesk/attachments/69127239427
https://support.akaipro.com/helpdesk/attachments/69127239428

https://drive.google.com/file/d/1v9VbzU7To_WuGE2DvpLp66D4q0wCCHnV/view?usp=drive_link

Thanks for your help

no additional sata disk or usb key connected during the update

Those akai helpdesk attachemnts won't show as they require you are logged in to view them

Only you will see those images as they are still linked to your support account, you'll need to save them and host somewhere with public access, e.g. free image host, dropbox shared link etc.

Oops, i'm sorry.

https://www.icloud.com/photos/#0134XxMd ... cg4I7Hoq1w

https://www.icloud.com/photos/#059KPXsv ... EDEb_GbDZA

I finally received a response from Akai support who provided me with the restoration files for mpc key 61, but it still does not work after restoration, the partitions are not reformatted. I am attaching a photo to see if you see anything unusual. I see the 29.1 GB partition unused, but how do I reformat everything else to restart a clean installation on that one??
https://drive.google.com/file/d/1W1xlPsSjo4SOBEGq_-Pjy94X_uaBq7qW/view?usp=sharing

I can see that you're SSH'd to your keys...
head to
/media/az01-internal/Settings/MPC/
and then delete MPC.settings file - it stores patches for directories in the browser.
after you delete it, issue a 'shutdown' command to turn your mpc off. If you won't do it but instead you shut it down manually, your mpc will write the settings file back again as it stores it in memory for the duration of current session.
Turn it back on and you shopuld be greeted with welcome screen and all settings wiped and restored to their defaults.
Will wait for you to report back

I did what you explained to me, I got the welcome screen, but the internal disk still displays 0gb out of 2gb used! I should have a lot more space, for me by updating to v3, it created a new partition. I don't dare format for fear that it won't start anymore after! What do I risk? What files do I need after formatting the disk? For me the partition /dev/mmcblk1 should be part of /dev/mmcblk0… but I don't know any more about it

I think I narrowed it down to a directory called sdcard in the root folder. Your browser should point to /media/az01-internal-sd/ which is actual internal card but for some reason they overlayed it with /sdcard.
On my machine that directory point to the root folder of actual partition afaik. Just out of curiosity, find that directory and double check it's size. There is a bunch of stuff in it and I have suspicions that it will add up to those two gigs

It looks like the Filesystem from the internal Drive is corrupt. So at boot, it will not mountet. if you have ssh access edit the fstab file that the system recognice the device(mmcblk1). Then run e2fsck to repair the file system.