Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

SDXC 64GB the following partition can't be recovered


  • Please log in to reply
2 replies to this topic

#1 Bonumy

Bonumy

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:05:09 PM

Posted 04 June 2013 - 03:53 PM

Hi,

I unpluged too fast my ScanDisk microSDXC Ultra 64Gb from my phone. Now i can see free space (27Gb) just in my PC-WIN7-64bit. In my phone-Galaxy GT-N7000 the card is not recognized. The used place (33GB) can not be seen (probebly in RAW file system).
I saved allready all the data with testdisk.
TESTDISK in Win7 write the following partition can't be recovered

testdisksdcard.jpg
 

edit: Linux see all the sizes, i can format the card in any format(fat, ntfs, extFat) but in Win7 i see just the last free space 27GB

 

I did allready some test in Parted Magic following instruction byJames Litten from similar topic.

 

DISK HEALT

.smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.8.10-pmagic64] (local build)
Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org

Standard Inquiry (36 bytes) failed [Invalid argument]
Retrying with a 64 byte Standard Inquiry
Standard Inquiry (64 bytes) failed [Invalid argument]
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.

 

FDISK

Disk /dev/mmcblk0: 63.9 GB, 63864569856 bytes
255 heads, 63 sectors/track, 7764 cylinders, total 124735488 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000e14fd

        Device Boot      Start         End      Blocks   Id  System
/dev/mmcblk0p1            2048   124735487    62366720   83  Linux
root@partedmagic:~#
 

IMAGE

# Rescue Logfile. Created by GNU ddrescue version 1.16
# Command line: ddrescue -r 3 /dev/mmcblk0p1 /media/sda3/image.dd /media/sda3/rescuelog.log
# current_pos  current_status
0xEDE8F0000     +
#      pos        size  status
0x00000000  0xEDE900000  +
 

Welcome - Parted Magic (Linux 3.8.10-pmagic64)
root@partedmagic:~# ddrescue -r 3 /dev/mmcblk0p1 /media/sda3/image.dd /media/sda3/rescuelog.log

GNU ddrescue 1.16
Press Ctrl-C to interrupt
rescued:    63863 MB,  errsize:       0 B,  current rate:    2555 kB/s
   ipos:    63863 MB,   errors:       0,    average rate:   11754 kB/s
   opos:    63863 MB,     time since last successful read:       0 s
Finished   

 

TESTDISK

Disk /dev/mmcblk0 - 63 GB / 59 GiB - CHS 1948992 4 16

Warning: the current number of heads per cylinder is 4
but the correct value may be 128.
You can use the Geometry menu to change this value.
It's something to try if
- some partitions are not found by TestDisk
- or the partition table can not be written because partitions overlaps.

 

EDIT:

After deaper seacher the same like ^^

Now:

Disk /dev/mmcblk0 - 63 GB / 59 GiB - CHS 1948992 4 16

     Partition                  Start        End    Size in sectors

 1 * Linux                   32   0  1 1948991   3 16  124733440

 

>[  Quit  ]  [ Write  ]
 

I dont know what mean option WRITE...

 

Thank You.


Edited by Bonumy, 05 June 2013 - 02:04 AM.


BC AdBot (Login to Remove)

 


#2 Bonumy

Bonumy
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:05:09 PM

Posted 06 June 2013 - 06:21 AM

so many experts here and nobody answer? :-(

#3 Bonumy

Bonumy
  • Topic Starter

  • Members
  • 3 posts
  • OFFLINE
  •  
  • Local time:05:09 PM

Posted 10 June 2013 - 10:01 AM

Hi,

 

i finally i have fix it with this instruction:

 

http://kb.sandisk.com/app/answers/detail/a_id/12517

 






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users