Keep losing sd ext - Nexus One Q&A, Help & Troubleshooting

I created an sdext with rom mgr and usaully take it from 2 to 3 with amon ra. Confirm ext 3 with partition tool.
Lately I have lost ext three times. Not sure why.
I have used DT and went to a rom that has auto a2sd and maybe that did it. Don't know if DT has been reinstalled off of one the roms I flash between. Next time I opened the Jave app to see a blank sdcard. Deleted that app. This time I opened Quick boot and and went into CWMod recovery and did a basic bu. Bu completed but could not boot, hung on X. Saw that sdext wont mount.
Restore seems to go ok, but at bottom of recovery screen it says:
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Error mounting /sd-ext/!
Skipping format...
E: Can't mount /dev/block/mmcblk0p2
(File exists)
Can't mount /sd-ext/!
Third time now and wondering what might be causing it.
I have sdformatter and can make another ext 3 partition and copy sd backup from pc to phone. Did that last time. Maybe rom mgr has been having issues. I don't do anything with rm I always boot into recovery. May need to go to amon_ra 1.9a full time.
Maybe stop using sdext and try ModInstallLocation, but heard that was no longer in Market.
Under MyPhone with MIUI .5 it shows sdext, but empty
MIUI .5 did load, don't know why it did and MicroMod 2.10 didin't, maybe too much mem used in the desire rom.
Under Quick System it shows ext as 458 and 323 free. Makes no sense. Maybe just the last reading it had. Internal free 69mb.
Maybe I just need to mount thru adb: mount /dev/block/mmcblk0p2. Not sure exactly how to type the syntaxes on sdk stuff.
I am not at home so can't see if I can mount sd thru pc or recovery or open sdformatter and see what it says.
Frustrated!
Ken

Can run DT which is not supported on MicroMod, I believe. I thought when you wipe and flash the ext is formatted and restored so DT would be removed if there.
I ran DT zipalign and it was ok. That was the only option to do other than Dalvik to sd. So do I have an ext or not?
I am cconfused on DT with different roms. I like MM 2.10 and would like to use it.
BTW: TB does not show an sd-ext either

Well, I restored an MIUI .5 bu and it works. Did a bu and showed ext backed up. But TB and Root Explorer show no ext info, mem size.

Related

Huge Problem With Cyanogen Auto Apps2sd

So I partitioned my sd card so i would be able to automatically have apps to sd like the faqs of the cyanogen mods said, but now that i have done the process and partition my sd card 500mb ext, 34mb linux swap, not only has it not worked and the apps are still taking up memory on my phone, it is not noticing the secondary partition in the settings and when i reboot my phone, after the g1 screen and android screen, my phone just goes blank. does anyone have any input? ive wiped and reflashed the rom, now im just clueless. and if it matters, i used Paragon Partition Manager to partition my sd card.
You could re-partition it by using the console in recovery mode.
http://forum.xda-developers.com/showthread.php?t=533731
Look at the 2nd code box and follow it. This is how I did it my first time.
It is really easy.
yea the only thing is it is either saying not found, or error could not stat device dev/block/mmcblk0 no such file or directory. so im stuck i cant even format my card and get back to 8 gigs its sayin 6.06 gigs. ionno im stuck.
Can't you use your partition manager to delete the partitions you made? Then just make 1 partition: fat32, then use the code on the link.
I use paragon Partition mgr. and that is an option to use.
If you partion your card after flashing your rom, then you must reflash your rom for changes to take effect. You have to do that so the system can change the way it runs
Oops sorry, I just reread your first post and saw that I missed that you did reflash. Try going into your recovery console and type ums_enable to mount your card and than try downloading gparted and try to reformat that way, when you are done type ums_disable to unmount. Have you tried taking your sd out when you try to boot up just to see if you can get past, it is possible that your sd corrupted
its ok thank you both, i used the recovery erase all partitions and im gonna read the second box and partition threw the console instead of on the manager.
I just had the same thing happen to me earlier today. I have the 404 Cyanogen MOD and now my SD card is stuck. I can't figure out how to get rid of that partition. All of the directions are not step by step. And this rookie is stressed out. Please let me know where or which directions you used to format your SD.
surfereddie said:
I just had the same thing happen to me earlier today. I have the 404 Cyanogen MOD and now my SD card is stuck. I can't figure out how to get rid of that partition. All of the directions are not step by step. And this rookie is stressed out. Please let me know where or which directions you used to format your SD.
Click to expand...
Click to collapse
To get it back to just a fat32 partition.... THIS WILL WIPE ALL DATA ON YOUR SDCARD!!!! MAKE A BACKUP OF FAT32 also this will only work with 1.3.1 and up cyanogen recovery image
boot into recovery and go to the recovery console and type
parted /dev/block/mmcblk0
rm 1
rm 2
rm 3 (if you have a linux-swap partition)
print (after the 4th or 5th line there is a number after a line that reads disk size or something and that will be the end value for the next command. Sorry on my g1 now)
mkpartfs primary fat32 0 xxxx(substitue with number above)
quit
reboot recovery
Then reflash your rom. That will clear all partitions of your sdcard and leave you with one whole partition that is fat32.

BART: mounting dev block mmcblk0p2 on system sd failed no such file or directory

OK I need help... I am not a noob but I cant seem to figure this one out.
I was running CM nightly 238 with the new 15 MB Hboot and radio, cm 2708port kernel, and custom MTD. everything was fine, I made a change in settings to adjust compcache and VM heap size and rebooted.... and when it started up my ext partition was gone.... So I decided to go ahead and restore a BART backup i made a day earlier.. But now bart gives an error: mounting dev block mmcblk0p2 on system/sd failed no such file or directory. I looked and there is no system/sd anymore... (I think there was, at least I KNOW bart worked the day before) So I wiped and reflashed my 238 build again and fr-patch is giving me a new error, after removing 05mountsd, and running fr-patch140.txt sdext it says that fdisk: cant open /dev/block/mmcblk1 no such device or address.... and that sd-ext mount is installed but it is not right and that I should make some noise... So I am.
I have tried, re-formatting and partitioning my sdcard with Recovery, and many other bits of code I found while searching google and XDA,, and still no luck... So any advice is really appreciated!
Also after this last attempt to re-partition, using default sizes via amon RA, I now cant mount sdcard via PC, but i can push to it with ADB....
--EDIT--
It turns out all this was because my ext partition was gone because the sdcard is corrupt. So I need to fix it some how. Because it seems the size has got messed up... it says total 16.2G.. and they are never over..usualy a little under. also when I try to reformat using amon RA gparted utitlity it says error: file system full, when it tries to make the ext partition... yet I have removed all the partitions using rm 1 , rm 2 ....ect

error mounting sdcard after moving apps to sdcard

on GDXv25 abd alfv8a have all the extra goodies for vold and all that. I change my SDCARD to a bigger one. format a partition for ext4 and leave the rest as default. On moving old stuffs back to it it seems to behave very well. Then I decide to move some of the apps to offload internal storage. The moving seems totally ok but after reboot my sdcard seems not be able to mount anymore. Go into CWM recovery and try to mount my sdcard. It says error mounting /sdcard yet I could succesfully mount my ext4 partition. At this point should I go ahead and re-format the sdcard again? What happens to those apps that I offload to the sdcard? are they toasted?
I'd to get some opinion before I re-format it since it will bring me over the point of no return. I still have no clue why all of a sudden after the moving of my apps that the partition won't mount anymore
On my linux I try to mount it via USB... it gives an error saying can't mount coz it can't read superblock. I gather some operations must have wiped into superblock. Sh*t hits the fan so to speak
by the way it is a new sdcard ... I dun think i damage it. But from CWM I can't even go ahead and format it because it says error mounting the partition.
I am amazed - I thought you don't need to mount before you can format. what's the deal here? I can't mount and I can't format?
vientito said:
On my linux I try to mount it via USB... it gives an error saying can't mount coz it can't read superblock. I gather some operations must have wiped into superblock. Sh*t hits the fan so to speak
Click to expand...
Click to collapse
That error message simply means that the ext filesystem in the sd-ext partition is kaputt and needs to be repaired (for example, manually restore a copy of the superblock) or formatted.
And that's your reason why you ran into problems ... something went wrong as you moved your old stuff onto the new card, and the next app you put onto the sd-ext finally triggered the problem.
Of course there's also the slight chance that the phone doesn't like the SD card.
finally I am able to format that sdcard by inserting into my kodak video playsport camera and format that from there! It's ridiculous that under CWM I am not able to do something as simple as formatting. That should not be a "feature" at all! Error mounting the card I could accept that but not able to format a card with screwed up superblock that's not acceptable.
With this exercise, I realize how valuable a backup it is. With all those apps xferred to the sdcard, I practically cross a bridge. Even with old usable card re-insert into phone those apps are gone and are no longer available. Only a backup (of course on a usable putaway MMC card) could have saved me all the trouble.
I still dunno what have gone wrong in the first place. Perhaps there's something I dun quite understand about moving apps to xternal storage.

[Q] Please help - can't boot into recovery mount error

(Please let me know if this is the correct forum!)
I have a Motorola Milestone 1 (A853) with Open Recovery 1.46 on a 16GB card. I've been using this to try new roms for over 2 years now. Everything was fine until I tried to create an ext 2 partition using MiniTool Partition Wizard, but things went sideways. Needless to say I wiped the card, created a new 10GB Primary Partition on it and a 4 GB ext2 for further usage. Then, I restored backup items on the card (pictures etc.) plus a fresh new version of Open Recovery. Now, every time I am at the Recovery menu and try to apply sdcard:update.zip I get this message:
E:Can't open cache/recovery/command (<-- this is nothing new - seen it many times before but still able to boot into open recovery)
-- Install from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid argument)
E:Can't mount SDCARD:update.zip
Installation aborted
.. any ideas what to do?
It seems like your phone dont mount the sdcard properly.
Try out a 2ndboot OR. (there is one from kabaldan and one from FuFu)
get a proper sdcard, and unzip to the root OpenRecovery from this url: http://forum.xda-developers.com/showthread.php?t=1897048
And voila! :good:
Thanks for the assistance guys.
The card is fine, It is seen in Windows perfectly with the 2 new partitions, but the phone is not seeing it. I was following MrTapa's guide here before the trouble started: http://forum.xda-developers.com/showthread.php?t=1750888 . When the card worked before, it was formatted using NTFS and both Windows and the phone could see it. Now, the 10 GB partition is NTFS and it has the additional 4 GB ext2 partition. Windows sees it, the phone does not.
Does Skrilax_CZ's note have anything to do with it? "If file "/system/etc/install-recovery.sh" exists on your Milestone, delete it (prior to flashing the SBF)" <-- from http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
lezztor said:
Thanks for the assistance guys.
The card is fine, It is seen in Windows perfectly with the 2 new partitions, but the phone is not seeing it. I was following MrTapa's guide here before the trouble started: http://forum.xda-developers.com/showthread.php?t=1750888 . When the card worked before, it was formatted using NTFS and both Windows and the phone could see it. Now, the 10 GB partition is NTFS and it has the additional 4 GB ext2 partition. Windows sees it, the phone does not.
Does Skrilax_CZ's note have anything to do with it? "If file "/system/etc/install-recovery.sh" exists on your Milestone, delete it (prior to flashing the SBF)" <-- from http://modmymobile.com/forums/563-m.../531599-open-recovery-v1-46-11-21-2010-a.html
Click to expand...
Click to collapse
NTFS?
Replace it with FAT32. Then it should work.
In the link you provided check step 9 (though FAT32 should work fine even with 2GB cards)
Ok - so reformatted 10GB partition to Fat32 and loaded OpenRecovery again to root of sd card - same error. I might also mention that I tried Fat32 on another smaller (2GB) card with an ext2 partition and it gave the same error. I'm beginning to believe that this phone has a problem with multi-partition sd cards?
Just tried the original way - one partition using NTFS ... same error. Frustrating .. over 3 days on this now ...
NTFS and Android can not work.
Unless someone included ntfs-3g into the kernel - but that would be a madman's work...
Delete every partition off your sd card, boot up Android, it will prompt you to format it, do it.
Copy recovery (OpenRecovery directory + update.zip) to sd card, try booting to recovery.
If it works resize FAT partition created by android to make space for an ext partition, boot Android again to see if it's ok with the changes.
Solved - if anyone is trying create an additional ext2 partition remember that BOTH the FAT32 and EXT2 must be created as PRIMARY. The app I was using defaulted to logical ...

stock rom and link2sd: can't mount ext4 partition

i have my ace running with a stock rom again since my wife is using it.
I have rooted the phone and flashed px recovery. After that, I wanted link2sd to mount the ext4 partition but whatever I try: nothing works.
when I try to mount ext 3 or ext 4 in link2sd I get this message: can't mount: no such device
when I try to mount ext2 I get this message: invalid argument
I have repartitioned and formatted both partitions already a dozen times. why can't link2sd mount this ext 4 partition?
i created the partitions using minitool partition wizard. After I placed the sd card back into my phone, I rebooted into px recovery, mount the sd-ext and formatted sd-ext, and after that, link2sd still gave the same errors.
How can I get Link2SD working?
DutchArjo said:
i have my ace running with a stock rom again since my wife is using it.
I have rooted the phone and flashed px recovery. After that, I wanted link2sd to mount the ext4 partition but whatever I try: nothing works.
when I try to mount ext 3 or ext 4 in link2sd I get this message: can't mount: no such device
when I try to mount ext2 I get this message: invalid argument
I have repartitioned and formatted both partitions already a dozen times. why can't link2sd mount this ext 4 partition?
i created the partitions using minitool partition wizard. After I placed the sd card back into my phone, I rebooted into px recovery, mount the sd-ext and formatted sd-ext, and after that, link2sd still gave the same errors.
How can I get Link2SD working?
Click to expand...
Click to collapse
I forgot that stock rom can't work with ext 4. Changing file system to ext2 worked for me and solved the problem (for now).
DutchArjo said:
I forgot that stock rom can't work with ext 4. Changing file system to ext2 worked for me and solved the problem (for now).
Click to expand...
Click to collapse
Are you sure Link2SD works well on stock rom? Because last time I checked it doesn't work well on roms without init.d support. I myself couldn't get it to work on stock rom. It crashed most of the time. Do post the result.

Categories

Resources