Member Avatar for santonu911

The problem with the 1 gig scan disk memory stick is very real and needs to be solved by the factory. the psp and any other reader will not read the card after it has been corrupted.
I have had this problem and tried to reformat the card in every way possible. Nothing works. you cannot delete anything off the stick because once your stick is corrupted everything on your card cannot be changed thru your any other device. Whatever you try to do it will say "failed" delete failed, format failed, save failed.

I tried helping a few people with this problem and went thru all the steps and more. If anyone has anything more creative. Please help me.

  • 2 Contributors
  • 1 Reply
  • 214 Views
  • 3 Hours Discussion Span
  • Latest Post Latest Post by Shinedevil

Dani AI

Generated

Short summary and practical next steps for the 1 GB Memory Stick PRO Duo problem described by . The failure mode described ("delete failed, format failed, save failed") plus 's correct observation that repartitioning from Linux can fix filesystem/partition-table corruption together point to two broad causes: a recoverable filesystem/partition-table problem, or a controller/flash failure that forces the device into a read-only or unusable state. The methods below separate diagnosis from repair and reduce the chance of destroying recoverable data.

A short diagnostic sequence (in order): connect the card using a dedicated USB card reader (not via the PSP) and try multiple USB ports or another PC; confirm the host sees the device and reports capacity (Disk Management on Windows, Disk Utility on macOS, or lsblk/dmesg on Linux); if the device shows expected capacity but the filesystem is RAW or unmountable, the problem is likely software/partition-related; if the device shows 0 bytes, wildly wrong capacity, or immediately errors, controller/flash hardware failure is likely.

If the OS sees the correct device and its hardware is writable, a low-level partition/format cycle can recover the card. An elevated Windows DiskPart sequence often used for this purpose is shown below; it will clear readonly attributes, remove partitions, and recreate a FAT partition:

diskpart
list disk
select disk X   # replace X with the card's disk number
attributes disk clear readonly
clean
create partition primary
format fs=fat32 quick
assign
exit

If DiskPart fails (errors about write protection or I/O errors) or the device still misreports capacity, stop further write attempts. Imaging the card read-only with a forensic tool (ddrescue on Linux) is the only safe data-preservation step before any recovery attempt; otherwise the card should be considered failed and replaced. For low-cost cards (1 GB) replacement is usually more practical than professional recovery. As noted, repartitioning helps when the controller accepts writes; persistent write failures indicate the controller/flash has reached a fault state.

Member Avatar for Shinedevil

Well, if you boot up into a linux OS and get the right drivers, you can format the san-disk.
I have an article on here about formatting a back-track os onto a flash drive, you can pretty much do the same for your san-disk and it will work.
The article is here if you want to read the full thing: http://www.daniweb.com/hardware-and-software/linux-and-unix/threads/421356/creating-a-backtrack-5-r2-usb-persistent

However I'll post the instructions down here if you need it,

From a terminal session:

fdisk /dev/sdb     (##Or the device letter of your flash drive)
d
n
p
1
enter
enter
t
b
a
1
w

Then from another terminal session, or from the same after you format the drive partition:

mkfs.vfat -F 32 -n 'diskname' /dev/sdb1

Then you should have a fresh new san-disk ready to be used, keep in mind that you won't have any data on it, and I'm sure you can't exactly recover that stuff anyways.

Though, if you want to try it... you could do a chkdisk on the drive when you are in a terminal session, that might work, though, I've never done it, so I can't say for sure, nothing to lose though.

So, Try this command if you're adventureous:

fsck /dev/sdb1

Maybe it will work, maybe it won't, I don't know.

But in anycase, I hope that any part of this helped you, it should. :3

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.