I’ve encountered an issue now where I’ve removed the MicroSD card from my Tracker Mini, inserted it into a known good card reader and experienced significant data loss.
This is with a high-end Sandisk 512 GB SD card.
Step by step:
Remove MicroSD card from Tracker Mini
Insert into Inland card reader (note: I’ve used this reader for years without issue)
Connect card reader to Windows 10 PC
Try to navigate the folder structure
At this point navigation will slow and become unresponsive.
Eventually get navigation back, eject the drive to attempt a re-mount or avoid another issue
Disconnect the card reader when Windows says it is safe
Reconnect the card reader to the Windows 10 PC
Windows will note that the drive “needs repair”. After attempting repair, all I see are the following contents:
I’ve had this happen twice with two different memory cards. The first time this happened was using the Tracker Mini in USB Storage Mode and now with my card reader. At this point I am extremely concerned.
Sorry to hear that you’ve had this issue twice. Never ran into this, but I’ve only used the SD cards that Polyend supply.
One thing that I find curious is that your card is 512 Gigs using FAT32, which I thought had a partition limit of 32 Gigs. Perhaps it’s using exFAT but only displays as FAT32?
I feel like I followed that guide with both of my cards. I’m wondering if using larger cards (512 in this case) poses a risk. It’d be great to have an official word from Polyend regarding maximum card size.
My card started displaying that message at some point…I completely ignored the repair request and is been working with no issues: copying/deleting files, renaming, new projects, audio recording…all works as expected.
I do a backup of all the content every other month into the NAS and delete the previous one.
I think that the culprit here is windows…flagging the card as containing errors for some reason
If I ever want to “repair it” I will probably just backup the content and just format it straight away and copy everything back in…I would definitely never use a repair tool without backing up the content of the card.
That’s… weird. I’ll put the card in the Tracker Mini and hope for the best. I was hoping to back up the contents prior to copying over the new firmware and flashing it but the card goofed up before I could even attempt that.
Worst case scenario - I’ll reformat the card and restore to a backup from late July, losing about two months of work.
Well, looks like I’m in a real weird spot. After inserting the card into my Tracker Mini it loaded the last Project but has nothing else on the card, seemingly.
This is what the Sample Loader shows for card contents:
I’ll try to read the card in my Linux machine tomorrow and see what happens. But I’m pretty sure I’m at a loss, here. That said, do we have an official “supported cards and sizes” from Polyend?
I could very well be wrong, but I’m guessing that there’s enough people out there using the Tracker with all sorts of card sizes. I don’t think any misbehaviour has been correlated to SD card size so far.
Just for testing purposes, do you have the SD card that came with your Tracker, and would you mind using it to interact with the Tracker as you normally would for a day or 2. It really could help to test a card ready made for the Tracker vs. what you’re currently working with.
If I can find the original card, I can give that a try. Given that the sample libraries I tend to use wouldn’t even fit on the stock card - I likely put the card into a bin of cards and filled that away.
To be honest, I don’t expect an issue with the stock card and I think I’m currently on the High End of data capacity for most users of the Tracker line - so I’m wondering if it’s an issue with Fat32, using 512gb card and perhaps how the Tracker interacts with the drive contents and how Windows 10 handles reading the files.
