[2.0, 2.1, ?3.0?][GCD=ux0][sleep mode] Official game cartridge seen as a SD2VITA causing "memory card removed" message everytime it sleeps.

[jubilees]

hello, O have recently installed the latest henkaku to my vita and it was fine until I used the save data manager and after that I started getting" memory card removed" message everytime it sleeps.

[CelesteBlue-dev]

Please send ur0:tai/storagemgr_logs.txt

[CelesteBlue-dev]

Please test : https://github.com/CelesteBlue-dev/PSVita-StorageMgr/releases/tag/v2.1

[jubilees]

Is this for SD2Vita or is it applicable to the sony 64gb memory card? Sorry for the noob questions, I'm fairly new to this.

[CelesteBlue-dev]

you copy storagemgr.skprx and storage_config.txt to ur0:tai and add the .skprx line in config.txt
Then you can configure for exemple MCD=uma0 to mount official memcard to uma0:.

[jubilees]

Ok, I copied them both to it. How can I configure?

[CelesteBlue-dev]

in ur0:tai/config.txt under *KERNEL
add :
ur0:tai/storagemgr.skprx
in ur0:tai/storage_config.txt
change MCD=uma0 by any mount point you want
for exemple you can do :
UMA=ux0
GCD=grw0
MCD=xmc0

[jubilees]

Do I have to change the mount point or can I leave it as it is?

[CelesteBlue-dev]

as you want, what do you want to mount as ux0 ? sd2vita ? memorycard ? psvsd ?

[jubilees]

Memory card

[jubilees]

Hey mate! So I did it all like you said and the message no longer pops up! Thanks a lot!

[jubilees]

Hello, so I received the message again after leaving a game open and letting the vita fall into sleep mode.

[CelesteBlue-dev]

you use v2.1 ?
please make a video

[jubilees]

Yes I did. I was also testing it out yesterday and the ps vita doesn't show the message anymore if there is no game cartridge inside the slot.

Edit: it did it again without the game cartridge inserted. I'll make a video as soon as I can.

Edit 2: so I've noticed that this has been hapoening about every day and a half, almost two days.

[CelesteBlue-dev]

"I was also testing it out yesterday and the ps vita doesn't show the message anymore if there is no game cartridge inside the slot."
This is an issue where StorageMgr treats official cartridge as a SD2VITA...
to fix...

[miinht]

This has also just started happening to me. Although I have only encountered this once so far (first time this has happened ever actually)- I leave my Vita on sleep mode and the next morning when I switch it on it says "Memory card has been removed etc.". Not sure if this makes a difference but I should add that when I left my Vita on sleep mode it was during a game left open I'm running storagemgr 3.0 plugin

@CelesteBlue-dev Is this issue still present as of v3.0? Any ideas what might cause this? Not sure if this is an issue with this plugin or with gamesd.skprx as well...

@jubilees Does this still happen to you or not anymore? Also what did you set up your storagemgr plugin as? Like is your sd2vita mounted as uma0 or ux0? Concerned because I researched online that this usually happens before your memory card dies out but now I can't tell if it's happening because of this plugin or memory card is actually about to die

[jubilees]

@itsminht No it doesn't happen anymore to my ps vita. I do not have an sd2vita, I just have a game cartridge inside the slot and while I was checking my vita I had noticed that when it wasn't inside the vita the message wouldn't pop until 3 days later. The only thing I did was what celeste mentioned to do up earlier in the thread. After I did it, the message stopped popping up only to come back a few days later. I didn't do anything else after and it doesn't pop anymore.

[miinht]

Ahh okay, but why would you use the storagemgr plugin for your ps vita if you don't have sd2vita? So like you only use sony memory card right? I stumbled across your reddit post and was in a similar situation to yours in regards to the error message.

[jubilees]

Honestly, I have no idea, that's why early in this thread I had put that I don't use sd2vita but celeste told me do what was stated above. I hear you man, I found no one when I was looking for the solution. Until someone told me to submit an issue in github. Hopefully if you do what I did, the message won't pop anymore.