Hello,
I’d like to report filesystem corruption on my SSD plugged in the deck. It just became unreadable when turning the unit on. It was formatted in FAT32. Recently the deck was mostly used in computer mode to update and organize the library with various PC software.
I was using Mediamonkey for copies and mp3tag for tagging. Then Engine for analysis.
The deck could not detect the drive anymore, but it was still providing access to it from a PC.
These massive tag operations never cause problems when performed locally, but it’s on NTFS drive directy connected to the PC motherboard.
I have an old backup, but I lost weeks of updating my library from a PC.
I tried to fix the drive and recover data with Windows and Linux tools, with limited success. I also connected the drive in the PC directly to perform the operations a second time and avoid potential issue due to the deck in between. The result was similar.
That disk is corrupted in a way that it prevented my PC to boot simply when the deck was on in computer mode with the SSD inside! Even after removing SSD from pc or deck, the computer would not boot or access UEFI interface at many occasions!
The cause of the corruption is really hard to identify due to the configuration and context.
‘chkdsk’ report: The type of the file system is FAT32. An error occurred while reading the file allocation table (FAT 1). An error occurred while reading the file allocation table (FAT 2). There are no readable file allocation tables (FAT).
‘dosfsck’ indicated that the dirty bit is on (mounted disk), without being able to remove it (complex issue with few help online) .
SSD is a Kingston UV500 mSata in a SATA box. It was not bought on purpose obviously but it is still new.
I don’t know how confident we can be with FAT32 and hundreds of GB partitions, but I am not confident with ExFat on W10 either, as I experienced corruptions on them as well in a pure Windows context, which seems to be well known issue.
Also, I have read that in rare occasions there could be voltage issues during msATA to SATA conversion depending on converter quality…
Thanks to dosfsck and dmde I could bring the SSD basically back online and try again to recover data with tools. It still ongoing but I don’t have many hopes. At this stage it’s just for the investigation and understanding. Later I’ll check for physical failure.
I don’t know if anybody had a such problems, but it is a severe issue!
A new SSD in SATA is on the way, Western Digital…
Thanks for your help and info.