While I was using the device I got a pop up showing, SD card is corrupt.
I tried formatting with windows and got error message windos was unable to complete format
I tried with chkdisk and got error saying the partition is RAW format
I tried using Minitools Partition recovery wizard. It showed that there is no partition. So I created a partition, and applied. After finishing all the operation, It showed bad disk
I tried to format with ubuntu and got the following error.
Code:
Error creating file system: Command-line `mkntfs -f -F -L "" "/dev/sdb"' exited with non-zero exit status 1:
stdout: `Cluster size has been automatically set to 4096 bytes.
Creating NTFS volume structures.
'
stderr: `/dev/sdb is entire device, not just one partition.
mkntfs forced anyway.
Failed to sync device /dev/sdb: Input/output error
Syncing device. FAILEDFailed to fsync device /dev/sdb: Input/output error
Warning: Could not close /dev/sdb: Input/output error
' (udisks-error-quark, 0)
I tried with gparted. Same like minitools, It showed my disk as unallocated partition.
I tried to create a partition and got this error
Code:
No partition table found on device /dev/sdb
Then I tried to create a partition table and got the errors
Code:
Input/output error during write on /dev/sdb
Code:
Error fsyncing/closing /dev/sdb: Input/output error
Code:
Error opening /dev/sdb: No medium found
If there is no way to fix my card, Samsung may provide replacement. But I am concerned about possibilities of Data Recovery and Misuse if I give my card to them.
Try with this with gparted:
Device>Create partition table...
Then try to format your sdcard
I had the same issue once with the same card. Thank god I made a backup earlier. I am not sure if this is a Moto problem or the card's but I did found out something. When Marshmallow asks to format the card as internet or portable, it doesn't quite reads the type. But once you format it as internal in order to move all the apps and then decide to format it as portable later, the phone acts weird and ultimately, the card starts having problems. If you ask me personally, I always hated this "format as internal" ****ty feature in Marshmallow. I really hope Nougat will fix this ridiculous issue.
I had bought my Evo from Amazon and they always have an amazing return policy. My card got corrupted within a month and I called them immediately to initiate a refund process. But the fact is the card was never corrupted. The phone made it that way! Now I am using a Sandisk Ultra 16 gb but I only inserted it after formatting it in my pc as FAT32. And then made it portable in my Moto of course. These memory cards usually have a very low life. It gets corrupted quite easily if proper care is not taken.
I suggest you return your card or get it fixed under your warranty asap man. And always remember, do not format it as internal memory. You dont wanna risk all your private stuffs by doing that. SD cards are always better as portable. After all, they were made for that purpose!
Good luck and Good day!
[Scroll down to the end for the TL;DR of my $ 0.02]
As someone who's had bad luck with failing flash drives a few times, specially ones which were crucial to work, can really understand how frustrating it can be of you're stuck with a bad disk.
Before going further, based on my own experience, I'd say given chance that the drive could be failing, it's advisable not do anything that might write on the drive. Any OEM or vendor tests or repair utilities, are likely to cause more harm than fix things back up. This obviously, is if you've data on there you'd not want to lose. Second step from here would be looking for VID captured through SMART to ascertain exact manufacturer, this could be important consider the flash storage within the card is from a vendor other than the company that sells the card. Depending on how much, possible data loss, could cost, you could consider getting professional services specially if the device your disk was tied to is enterprise managed. If not so, then cost of recovery could be several (hundred) times more than cost of the disk.
Using software available online, even ones which are paid, could offer only a brute force level hit and trial data recovery, with their very limited functionality. Most, even ones such as icare or easus have mostly been built around standard SATA drives, which are far more notorious with retaining data after several rewrite cycles. Even SMART is still largely in the ide/sata domain. But if your data isn't life or death crucial you could give it a shot. On lucky days I've recovered entire partition with tools as basic as Recuva, though of course after the format has been fixed.
Fixing the raw error ideally should get dealt with by the wonder tool Rufus, but as you obviously would have figured it that would happen at cost of data loss. Though Rufus can be counted on last ditch efforts to salvage the disk by fixing bad sectors. Being available across platforms I've found it to be my GO TO tool for all things related to flash drives, specially when I have to try a new distro or mount an old one out of the blue. The only catch I can think of is the disk not being read via USB adapter, which I've found getting fixed with using a standard SD adapter and connecting via MTP.
The ideal flow of data recovery: copy image, mount as virtual partition, followed by Sector level scan for recoverable fragments is going to depend on your disk not having physical failure, as the last user pointed out too. In which case, it would be a case of coat vs risk assessment. Most vendors are happy to return the disk or give a replacement, but that being the worst case scenario, so perhaps it would boil down to deciding between bearing cost of a new memory card or risking compromising private data, that should be the clincher. And the experience and the knowledge gained in the experience as the silver lining.
TL;DR: buy a new one in favor of safeguards personal data, be severely critical of Manufacturer, seller, Amazon et al and get a free replacement without return citing privacy issues by giving hell to the call center kid
OR format to a readable version with chance of permanent data loss by Googling for RAW error fix, and torrenting a suitable program for 'evaluation' and get done with it.
Sent from my athene_f using XDA Labs
Fix Corrupted RAW Samsung EVO 32GB card
While formatting the Windows system, if your Samsung EVO 32GB card corrupted then do not worry, just try some easy ways to fix raw SD card and recover data from your raw SD card. First of all, I think you try use the Disk Management Tool which is an inbuilt tool present in Windows system. Also, you try to use CHKDSK command. After trying these ways, you can try to ix corrupted raw SD card and then recover the data from SD card.
sudheerkdty said:
While I was using the device I got a pop up showing, SD card is corrupt.
I tried formatting with windows and got error message windos was unable to complete format
I tried with chkdisk and got error saying the partition is RAW format
I tried using Minitools Partition recovery wizard. It showed that there is no partition. So I created a partition, and applied. After finishing all the operation, It showed bad disk
I tried to format with ubuntu and got the following error.
Code:
Error creating file system: Command-line `mkntfs -f -F -L "" "/dev/sdb"' exited with non-zero exit status 1:
stdout: `Cluster size has been automatically set to 4096 bytes.
Creating NTFS volume structures.
'
stderr: `/dev/sdb is entire device, not just one partition.
mkntfs forced anyway.
Failed to sync device /dev/sdb: Input/output error
Syncing device. FAILEDFailed to fsync device /dev/sdb: Input/output error
Warning: Could not close /dev/sdb: Input/output error
' (udisks-error-quark, 0)
I tried with gparted. Same like minitools, It showed my disk as unallocated partition.
I tried to create a partition and got this error
Code:
No partition table found on device /dev/sdb
Then I tried to create a partition table and got the errors
Code:
Input/output error during write on /dev/sdb
Code:
Error fsyncing/closing /dev/sdb: Input/output error
Code:
Error opening /dev/sdb: No medium found
If there is no way to fix my card, Samsung may provide replacement. But I am concerned about possibilities of Data Recovery and Misuse if I give my card to them.
Click to expand...
Click to collapse
HDD low level format
How?
Related
so i was flashing from dudes 1.1 to cyans 3.4.6 (been out of the game for a lil while) and i figured itd be best to wipe sd and g1. I reformatted to fat32 then made ext2 partition with paragon partition manager. After that the pc needed to restart and it all went smooth until it booted up again.
the pc wont read my sd anymore now (im using a standard SD adapter), windows will show its plugged in and reccomend me to reformat it to fat32 but then it always says formatting failed.
I tried using partiton again and all it does is read it as 7.6 gb ext2 drive, it wont let me format/reformat/delete partition/ create partition. it says something like No unallocated space.
Basically...Is my card fried? = /
I doubt its fried.
If it's fried, then windows will not even detect it.
Unfortunately, I do not know the fix.
Sounds like Vista is having problems reading the card... know anyone with a Mac or Linux box?
tissle said:
I doubt its fried.
If it's fried, then windows will not even detect it.
Unfortunately, I do not know the fix.
Click to expand...
Click to collapse
Not necessarily. I've seen this problem for bad SD cards.
Infact, mine appears to have died today too. It now says "blank SD card" and wants to be formatted. Damn.
Guess it's a trip to Fry's for me.
i tried using my linux liveboot cd, it detects it but linux wont mount..
damn frys is soo far for me ..like 45 min
so no body knos a fix huh?
if u don't need anything off the card, just format it.
from within windows just do a format.
or..
in linux, put the card in
Code:
df
find the one that matches ur card (/dev/sdb or /dev/sdc normally)
Code:
shred -f -n 0 -z -v /dev/sdc
this will completely wipe the card.
now type in
Code:
sudo gparted /dev/sdc
and recreate your partitions (i recommend a fat32 partition )
=O a fix from the sensai himself. i will try it when im home thanks so much haykuro!
tried in linux but command lead to a no such directory or file. and partition editor wouldnt show any other option but my actual hd. it says "cannot mount" when i insert it so it knows its there .. : /
SO I half bricked my nook by deleting off partitions from the emmc, and now it only boots from SD card... without the SD card it won't turn on at all
I know my issue is partitioning the mmcblk0 as it used to be but I can't access it from adb shell, it does not find the parted command or gives me no permission
I have tried bootable CLW and have tried to reflash stock firmware but nothing does the trick
any one have any tips? or have run into this problem?
If you don't have parted, use fdisk. Take a look at the manual repartitioning post: http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110. Basically you'll want to do something similar, except you'll create all the partitions instead of just p6,p7,p8.
jll544 said:
If you don't have parted, use fdisk. Take a look at the manual repartitioning post: http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110. Basically you'll want to do something similar, except you'll create all the partitions instead of just p6,p7,p8.
Click to expand...
Click to collapse
thanks for the link, I been very busy this week with final projects and final exams approaching so this thing isn't my number one priority but nevertheless I would love to fix it asap...
I manage to recreate all the partitions, however the number of cylinders, heads, and sectors is different then it should be in my disk, when I use fdisk expert mode to change these things and do the w to write changes to disk the changes are not there once I do the p command, as if I never wrote the changes to disk... and still my nook will not boot off emmc.
Anny suggestions?
Update: The SD card I'm using for this is brand new and it is showing corruption sometimes. I think that the SD card is broken but I'm not sure. While I am debugging this I will not give more details to avoid other's damage. In the meantime, if someone is interested and wants to take the risk, please PM me.
------
In summary, this is a method to mount from the PC a sd-ext formatted partition on the SD card inside the phone.
The linux kernel inside Android can potentially understand ext2/3/4, NTFS and other advanced filesystems, but you have to mount them manually to see their data within the phone. That is a hassle, but it can be solved if you are root. However, if you connect your phone to your PC with this setup the alternative filesystems in the external SD card cannot be seen from the PC.
I did not find in Internet how to solve the latter issue, but I figured it out. So here I will explain how:
see the ext4 partition within the phone <-- this is not new!!
see the ext4 partition by connecting the phone to a Linux PC <-- these are the news!!
I do not have a lot of time now to explain the steps in detail. I will update the post later, but basically:
- Using Ubuntu and gparted, I formatted my external SD card with 2 partitions: first one small (32MiB) FAT to satisfy Android and second one big (~16GiB) ext4 where my data remains. This assures that the FAT filesystem cannot grow above the 32MiB limit.
- Then, with Ubuntu and fdisk I deleted (yeah!) the partition table and created a new partition table that says that the FAT filesystem occupies the entire SD card space. This step is the important, it means that the whole card will be exported from the phone when connected to a PC (since the partition table says that there is only one big partition for the whole SD card). However, due to the small size format in the first step the FAT partition cannot grow above the 32MiB mark (where the ext4 filesystem still resides).
- With this setup you can still access the ext4 data (it will not be touched by FAT accesses!!) using mount and the loop device, both from within the phone and from a PC with Linux (if you have another OS, maybe you can use a VM with Linux).
More or less, that's all without the details. I'll update this post later with a step-by-step guide.
Thanks to share that information...
You are welcome. It is a pity that my SD card is not working properly with my phone (it works Ok in the PC). I think that it is a kernel (Froyo) problem so I planned to upgrade to Gingerbread before doing more tests. But right now I have no time...
This question probably belongs in the thread "[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26]", except that I can't post there yet.
I was able to create a working dual boot card per the instructions. However, I could not make a working card that made use of all 16 GB of my card, rather than just the <4GB size of the image file. The card still worked when I used fdisk on my Mac to increase the size of the last, 'sdcard', partition to fill up the available space. However, that did not increase the capacity of the FAT volume in that partition, leaving the extra space still unavailable.
After saving the files from that volume, I then used the Mac's Disk Utility to erase the partition and re-create it as a FAT partition using all the available space. Once I did that, unfortunately, the Nook would then not recognize anything on the SD card and would only boot into the Nook's own ROM.
As an alternative, I tried leaving the existing partitions alone and editing the MBR with fdisk to create a new partition using the available space, which I then formatted as a FAT partition with Disk Utility. Again, the Nook would no longer recognize the SD card and would only boot into its stock ROM.
I actually tried the above with two 16GB SD cards, a SanDisk Class 4 and a Samsung Class 10, and with two Nooks. Moreover, I tried a number of manipulations of the MBR, mostly to make it identical to the original one except for necessary size changes. Nothing worked to get a card that would boot and use the full 16 GB. I'll admit I haven't tried everything, such as trying to resize to something less than the full 16GB, but I've put so much time into this already that I don't want to do any more until I get some feedback.
aarons510 said:
This question probably belongs in the thread "[ROMS]NEW! Dualboot Mirage CM7 / ICS CM9 Image for SDcard [3/26]", except that I can't post there yet.
I was able to create a working dual boot card per the instructions. However, I could not make a working card that made use of all 16 GB of my card, rather than just the <4GB size of the image file. The card still worked when I used fdisk on my Mac to increase the size of the last, 'sdcard', partition to fill up the available space. However, that did not increase the capacity of the FAT volume in that partition, leaving the extra space still unavailable.
After saving the files from that volume, I then used the Mac's Disk Utility to erase the partition and re-create it as a FAT partition using all the available space. Once I did that, unfortunately, the Nook would then not recognize anything on the SD card and would only boot into the Nook's own ROM.
As an alternative, I tried leaving the existing partitions alone and editing the MBR with fdisk to create a new partition using the available space, which I then formatted as a FAT partition with Disk Utility. Again, the Nook would no longer recognize the SD card and would only boot into its stock ROM.
I actually tried the above with two 16GB SD cards, a SanDisk Class 4 and a Samsung Class 10, and with two Nooks. Moreover, I tried a number of manipulations of the MBR, mostly to make it identical to the original one except for necessary size changes. Nothing worked to get a card that would boot and use the full 16 GB. I'll admit I haven't tried everything, such as trying to resize to something less than the full 16GB, but I've put so much time into this already that I don't want to do any more until I get some feedback.
Click to expand...
Click to collapse
Well you're missing just one step after fdisk. If Disk Utility is failing at it you could try terminal:
First you need to find out where your /sdcard is being mounted at. Use "diskutil list" to find out
Once you find out where it's being mounted (eg. /dev/disk4s7). You will then need to unmount the volumes before you can format it.
Code:
$ diskutil unmountDisk /dev/disk4s*
$ diskutil partitionDisk "/dev/disk*" 1 MBRFormat "MS-DOS FAT32" "sdcard" "*M"
Replace * with the actual values needed. You might need "sudo" to perform the format command. Make sure you're formatting the correct mount point or else you might end up wiping your system. But if you were able to use fdisk, I'm sure you have a good understanding of terminal.
Haven't tried it myself. But it should(might) work.
-Racks
Won't "diskutil partitionDisk ..." wipe out all volumes on disk?
racks11479 said:
[See previous post!]
Click to expand...
Click to collapse
When I type
Code:
diskutil partitionDisk
in Terminal to get usage info, I see, inter alia, the following:
Code:
(Re)Partition an existing disk. All volumes on this disk will be destroyed.
But that is clearly not what I want to do. Am I missing something?
Updated update:
I have tried, several times and on both SD cards and both Nooks, diskutil eraseVolume, a presumably more powerful version of the erase option in Disk Utility. I tried one or another of the commands:
Code:
diskutil eraseVolume MS-DOS sdcard /dev/disk4s7
diskutil eraseVolume 'MS-DOS FAT32' sdcard /dev/disk4s7
on cards that were booting, but with the small sdcard partition or the small volume on the enlarged partition. I also tried at least one of those commands on a card that was already not working after modification. In all cases, the commands ran without error but produced a non-booting card. Changing the 'ob' partition id back to 'oc' with fdisk didn't help, nor did any restoration of the original fdisk MBR info.
In sum, the only change that I have been able to make to a card as originally written from the image without making it unbootable was to enlarge the sdcard partition while leaving the sdcard volume untouched, and therefore not using most of the capacity of the partition.
Some more general but related questions.
Since I've got your attention, Racks, let me ask a few questions whose answers might help me and others understand what is going on here and what might go wrong with this and other Nook Color boot setups. Of course, also please point out where anything I think I know is, in fact, wrong.
1) I understand that the firmware boot code on the Nook first looks for something on an inserted SD card to boot from. It seems it looks for a file named u-boot.bin on the first partition of the inserted card to which to transfer control. Does it also check other things on the card before transferring control to u-boot.bin? Does it look at the file MLO? Does it look at the partition labeled sdcard, or at any other partition, before doing so?
2) Presuming that it does transfer control to u-boot.bin, what does the latter check before either booting from the (default) ROM on the card or, if the Home button is being held down, going to the interactive boot dialogue? My experience has been that, when using one of my 'non-working' cards, the Nook goes quickly to the ROM on internal memory without showing any visible signs of doing anything else first. In other words, it 'knows' that it can't boot from a ROM on the sdcard before actually trying to do so.
Okay so i was just doing a bit of file management. I removed a 1.4gb psp iso i had on my nexus 7 and then i checked how much space i had left using storage option in settings. I checked it and it said i had 25gb free when before i removed my file i had only 13gb free. Tried rebooting device and then used es file explorer to see all files. Opened es file explorer and then noticed everything was gone. Only stock items were folders were left eg Android, Download etc. All my msuic and some game data was gone. Opened up asphalt 7 to see if it would still work but it doesnt anymore. Tried opening real racing 3 And it asks me to redownload game data. My widgets are still in homescreen and work and some of the other apps i have still work as well eg plague inc, subway surfer and most of the other ones.
Any idea on how this happened and how i can recover my files? I have a bugsense file as well that was left on my device.
As to recovery of lost files your options are not good. (And if we're talking a non-rooted device, the odds are approximately equal to 0%) Recovery in ext4 filesystems is technically much more challenging than in simple filesystems such as FAT. And this pessimistic outlook presumes that the filesystem is healthy/clean. If the reason for the problem occurring in the first place was a corrupted filesystem, then the odds go from simply bad to pathetically poor.
Sorry, dude... got any Nandroid or TiBu backups stored on your PC?
If you had Putin's top-secret files on your N7 and the CIA got hold of it, the first thing a forensic analyst would do is try to take a raw (block) device dump off of the "cold" device. (If you are still running the N7 with the regular OS the /data partition is being continually written to, and this further reduces the chances of file recovery every second the device is booted).
In the case of an analyst with less resources, this might mean using a custom recovery boot to get the raw device copy; unfortunately, the /data partition is huge - nearly 30 GB - so you would have to mount a extN filesystem via OTG... and doing so thus precludes using adb, so you would need to use a recovery with a touch interface and command-line entry (e.g. TWRP)
# mkdir /mnt/myOTGdisk
# mount -t ext2 -o rw /dev/sda1 /mnt/myOTGdisk/
# dd bs=8196 if=/dev/block/platform/sdhci-tegra.3/by-name/UDA of=/mnt/myOTGdisk/userdata.img
Doing such a thing would allow you to examine that huge image file with forensic file recovery tools from a PC (probably running Linux) as in principle you captured the entire ext4 filesystem.
The thing is, efforts spent in file recovery should be proportional to the value of the files being recovered. I'm not sure if your saved gaming history rises to that occasion. For sure the dude at the CIA won't want to help you with that.
As to the source of your troubles, it's hard to say. With TWRP booted, you can run the "e2fsck" program to see if the /data ext4 filesystem is corrupted, e.g.
# mount | grep /data ( see which mmcblk0 partition is /data, on grouper it is mmcblk0p9 )
# umount /sdcard
# umount /data
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/UDA
(For the last command above, you might need to use the block device name /dev/block/mmcblk0p?? instead of the UDA symlink )
If the above command shows that you have a corrupted /data filesystem, I would re-initialize that filesystem ( "fastboot format userdata" ) - note this wipes all userdata including the psuedo-SD card.
Finally, I should point out that some type of hardware failure might have occurred somewhere in that huge 30 GB partition - if that is the case then there will be problems down the road again. If that is the case, the only way to detect this will be a write test which nearly fills that partition, followed by a filesystem sanity check as shown above.
Probably that would need to be done in the recovery rather than in the normal OS, as a nearly full /data filesystem will probably wedge the device.
Phew, I've said enough.
Good luck
I never tire of reading your posts, bftb0, ("...the odds are approximately equal to 0%")...genius.
But don't the CIA have access to Cray, 'Kasparov' DeepBlue beating SuperComputers that could make mincemeat out of the kind of thing your alluding to... in less time than it takes to flash a ROM... or have I been watching too many James Bond movies?
Vaguely rhetorical question - think I already know the answer...
Still... what a great post.
Rgrds,
Ged.
---------- Post added at 01:22 AM ---------- Previous post was at 12:50 AM ----------
Hi, leont1280...
You could try running this ...
Disk Usage - http://play.google.com/store/apps/details?id=com.google.android.diskusage&hl=en
It gives a graphical 'map' or overview of your storage, and you can visually see where everything is (or should be), great for tracking down missing stuff... but as bftb0 has mentioned, it doesn't look promising.
Rgrds,
Ged.
Use astro file manager u can check it out
Sent from my Nexus 7 using Tapatalk 2
Right bftb0 i did what you said in twrp and i recieved the following summary information.
/dev/block/mmcblk0p10: 28133/1835008 files (3.2% non-contiguous) , 1571673/733977
Any idea on what that means?
Also under the mount option in Twrp i can Unmount and mount the System, Data and its Cache. However i cant Mount the SD Card. Should that be a concern?
bftb0 said:
As to recovery of lost files your options are not good. (And if we're talking a non-rooted device, the odds are approximately equal to 0%) Recovery in ext4 filesystems is technically much more challenging than in simple filesystems such as FAT. And this pessimistic outlook presumes that the filesystem is healthy/clean. If the reason for the problem occurring in the first place was a corrupted filesystem, then the odds go from simply bad to pathetically poor.
Sorry, dude... got any Nandroid or TiBu backups stored on your PC?
If you had Putin's top-secret files on your N7 and the CIA got hold of it, the first thing a forensic analyst would do is try to take a raw (block) device dump off of the "cold" device. (If you are still running the N7 with the regular OS the /data partition is being continually written to, and this further reduces the chances of file recovery every second the device is booted).
In the case of an analyst with less resources, this might mean using a custom recovery boot to get the raw device copy; unfortunately, the /data partition is huge - nearly 30 GB - so you would have to mount a extN filesystem via OTG... and doing so thus precludes using adb, so you would need to use a recovery with a touch interface and command-line entry (e.g. TWRP)
# mkdir /mnt/myOTGdisk
# mount -t ext2 -o rw /dev/sda1 /mnt/myOTGdisk/
# dd bs=8196 if=/dev/block/platform/sdhci-tegra.3/by-name/UDA of=/mnt/myOTGdisk/userdata.img
Doing such a thing would allow you to examine that huge image file with forensic file recovery tools from a PC (probably running Linux) as in principle you captured the entire ext4 filesystem.
The thing is, efforts spent in file recovery should be proportional to the value of the files being recovered. I'm not sure if your saved gaming history rises to that occasion. For sure the dude at the CIA won't want to help you with that.
As to the source of your troubles, it's hard to say. With TWRP booted, you can run the "e2fsck" program to see if the /data ext4 filesystem is corrupted, e.g.
# mount | grep /data ( see which mmcblk0 partition is /data, on grouper it is mmcblk0p9 )
# umount /sdcard
# umount /data
# e2fsck -f -n /dev/block/platform/sdhci-tegra.3/by-name/UDA
(For the last command above, you might need to use the block device name /dev/block/mmcblk0p?? instead of the UDA symlink )
If the above command shows that you have a corrupted /data filesystem, I would re-initialize that filesystem ( "fastboot format userdata" ) - note this wipes all userdata including the psuedo-SD card.
Finally, I should point out that some type of hardware failure might have occurred somewhere in that huge 30 GB partition - if that is the case then there will be problems down the road again. If that is the case, the only way to detect this will be a write test which nearly fills that partition, followed by a filesystem sanity check as shown above.
Probably that would need to be done in the recovery rather than in the normal OS, as a nearly full /data filesystem will probably wedge the device.
Phew, I've said enough.
Good luck
Click to expand...
Click to collapse
Right bftb0 i did what you said in twrp and i recieved the following summary information.
/dev/block/mmcblk0p10: 28133/1835008 files (3.2% non-contiguous) , 1571673/733977
Any idea on what that means?
Also under the mount option in Twrp i can Unmount and mount the System, Data and its Cache. However i cant Mount the SD Card. Should that be a concern?
leont1280 said:
Right bftb0 i did what you said in twrp and i recieved the following summary information.
/dev/block/mmcblk0p10: 28133/1835008 files (3.2% non-contiguous) , 1571673/733977
Click to expand...
Click to collapse
Hmmm, mmcblk0p10 - you must have a tilapia (3G N7) device, yes?
If you had any filesystem errors, that e2fsck run would have produced copious reams of output. If a filesystem is clean, it produces only 5 or 6 lines of summary output.
leont1280 said:
Any idea on what that means?
Also under the mount option in Twrp i can Unmount and mount the System, Data and its Cache. However i cant Mount the SD Card. Should that be a concern?
Click to expand...
Click to collapse
I've seen the same business with TWRP and the /sdcard mount - I wouldn't worry about it. (It is not a "normal" mount in the sense of extN or FAT device partition mount - it behaves sort of like a strange symlink where the target directory and descendants all appear to have different file ownership and permissions than what exist in the true (underlying) filesystem. No doubt this is all performed in the kernel... I don't know whether a command-line invocation of "mount" can create this mount point, or whether a specific syscall/ ioctl is needed)
But back to your N7 - the lack of any errors in the filesystem check is good news, but also suggests that your files didn't disappear through a hardware failure. Are you sure you didn't fat-finger things when using the file manager? (I suppose it is possible that the file manager has a bug...)
I didn't look into what tools are available for extN forensic/recovery work. I can guess that the effort would be non-trivial, though.
bftb0 said:
Hmmm, mmcblk0p10 - you must have a tilapia (3G N7) device, yes?
If you had any filesystem errors, that e2fsck run would have produced copious reams of output. If a filesystem is clean, it produces only 5 or 6 lines of summary output.
I've seen the same business with TWRP and the /sdcard mount - I wouldn't worry about it. (It is not a "normal" mount in the sense of extN or FAT device partition mount - it behaves sort of like a strange symlink where the target directory and descendants all appear to have different file ownership and permissions than what exist in the true (underlying) filesystem. No doubt this is all performed in the kernel... I don't know whether a command-line invocation of "mount" can create this mount point, or whether a specific syscall/ ioctl is needed)
But back to your N7 - the lack of any errors in the filesystem check is good news, but also suggests that your files didn't disappear through a hardware failure. Are you sure you didn't fat-finger things when using the file manager? (I suppose it is possible that the file manager has a bug...)
I didn't look into what tools are available for extN forensic/recovery work. I can guess that the effort would be non-trivial, though.
Click to expand...
Click to collapse
Im pretty sure i didnt accidently delete it myself. When i was doing file management i was using my laptop with the N7 3g connected to it via MTP. Once i deleted the iso file the N7 started acting strange. I did notice a bit of lag that was usually out lf the ordinary and when i checked available space left it increased to 25gb rather than saying 13gb
aaah, having the same problem here, i was cleaning my n7 using my laptop, found a strange folder on my sd card, looked inside and it has a back up of some of my deleted files! interesting! i deleted the folder, then i started cheking other folders, like my ebooks, audio books and etc, but all my folders were empty!
so i disconnected my tablet, and after reconnecting, bam, all files gone.