[Q] Internal Storage Unavailable - Droid Incredible Q&A, Help & Troubleshooting

I am having problems with clockwork recovery.
When I open I get:
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
E:Can't mount CACHE:recovery/command
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
E:Can't mount CACHE:recovery/log
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
I am running stock un-rooted, s-off. I ran OTA.
I know exactly what the problem is. My internal storage of my phone wont mount.
I have read a lot of things on how to mount your internal storage. A lot of people say you just have to reboot your phone.
That didn't work.
I know the problem is defiantly not the SD card. I tried 5 different ones.
I read somewhere to remount internal storage you have to take phone apart and put internal storage chip back in.
I can't format internal storage, because it is grayed out in the option under SD card setting.
What can I do. I think I have tried everything?
Please help.

cubusmybro said:
I am having problems with clockwork recovery.
When I open I get:
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
E:Can't mount CACHE:recovery/command
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
E:Can't mount CACHE:recovery/log/block/mmcb1k0p2
E:Can't mount /dev/block/mmcb1k0p2
(File exists)
I am running stock un-rooted, s-off. I ran OTA.
I know exactly what the problem is. My internal storage of my phone wont mount.
I have read a lot of things on how to mount your internal storage. A lot of people say you just have to reboot your phone.
That didn't work.
I know the problem is defiantly not the SD card. I tried 5 different ones.
I read somewhere to remount internal storage you have to take phone apart and put internal storage chip back in.
I can't format internal storage, because it is grayed out in the option under SD card setting.
What can I do. I think I have tried everything?
Please help.
Click to expand...
Click to collapse
Hi,
I don't understand how you can be running unrooted but using cwm?
But I'll guess you are rooted and having problems mounting /cache (dev: /dev/block/mmcb1k0p2) which is an ext3 fs.
I had same messages for the /emmc fs, but that is msdos/fat32, so a slightly different 'cure'.
I used adb shell (or you could use term emulator) to do something like this:
su ; fsck /dev/block/mmcb1k0p2 // look up the correct qualifiers, but I think it'll default to something acceptable. Tell it to repair as needed. Reboot.
For my case I used "fsck_msdos /dev/{whateverThePathWas} and it repaired it and it mounted.
Note: Replacing , replugging the internal storage sounds iffy because all of it is on a single chip which is soldered onto the board. /dev/block/mtd* are only offsets into flash, not anything separate. It seems like more of a format issue or bad blocks.
Good luck
Hashi
PS: Depending on ROMs (I baked my own) , you might not have fsck* but I think you will. Also, some ROMs may use init.d to force an fsck already and this won't work if it did that. Worth a shot.

hachamacha said:
Hi,
I don't understand how you can be running unrooted but using cwm?
But I'll guess you are rooted and having problems mounting /cache (dev: /dev/block/mmcb1k0p2) which is an ext3 fs.
I had same messages for the /emmc fs, but that is msdos/fat32, so a slightly different 'cure'.
I used adb shell (or you could use term emulator) to do something like this:
su ; fsck /dev/block/mmcb1k0p2 // look up the correct qualifiers, but I think it'll default to something acceptable. Tell it to repair as needed. Reboot.
For my case I used "fsck_msdos /dev/{whateverThePathWas} and it repaired it and it mounted.
Note: Replacing , replugging the internal storage sounds iffy because all of it is on a single chip which is soldered onto the board. /dev/block/mtd* are only offsets into flash, not anything separate. It seems like more of a format issue or bad blocks.
Good luck
Hashi
PS: Depending on ROMs (I baked my own) , you might not have fsck* but I think you will. Also, some ROMs may use init.d to force an fsck already and this won't work if it did that. Worth a shot.
Click to expand...
Click to collapse
I kind of have an idea what you mean, but I am just rooted on stock ROM, and I don't think that has fsck, but I don't even know what that is.
I punched in that command into terminal emulator as follows:
#su ; fsck /dev/block/mmcb1k0p2 //
#
All I got in return was a hash, I rebooted, and problem wasn't fixed yet.
I am also not sure what you mean by, "look up the correct qualifiers."
fsck: permission denied is what I get when I just type that in.
Thank you. I think that I am on the right track.

Related

[Q] Mount SDCard in console

Hi.. how i can mount/remount sdcard in console? because something is wrong.. in every roms when i goes to sdcard in setting its show unavailable.. once time ago i wrote something in console as remount and it was okey.. but i forgot it how i can do that.. i tried many combination of command mount but nothing. maybe i can find in google with keyword "mount/remount in linux" can be possible?
but through astro i can explore sdcard.. its strange..
please help. And thanks for answers
Code:
mount /dev/block/mmcblk0pN /sdcard -t FSTYPE
N is number of partition (usually 1) and FSTYPE is vfat or ext2 (usually vfat)
Google is a good help so please use it!
i look on mount and sdcard is mounted.. but still i cannot explore it with anything except astro.. i think maybe is problem in kernel.. i have last kernel version... working sdcard full for everyone? maybe is problem only in my phone.. or its global error
Sd card works in latest kernel, probably is your problem, reformat the card.
Try this:
vdc volume mount /sdcard

Recovery Issues

Issue started after a nandroid backup (using clockwork 2.5.0.5). Backup froze, i ended up pulling the battery. When i go back into clockwork to try the backup again i now get the following:
clockwork recovery v2.5.0.5
e:can't mount /dev/block/mmcblk0p2 (file exists)
e:can't mount CACHE:recovery/command
e:can't mount /dev/block/mmcblk0p2 (file exists)
e:can't mount CACHE:recovery/command
e:can't mount /dev/block/mmcblk0p2 (file exists)
I wiped cache, factory reset, wiped dalvik. Even tried formatting boot system, system, data and cache. Was able to reload stock 2.1 through hboot, re-rooted, but get same error and cannot get clockwork to mount sd-card to go any higher.
When I try to mount sd-card through clockwork the following appears:
e:Can't mount /dev/block/mmcblk1p1 (or /dev/block/mmcblk1) (no such file or directory)
Any help is greatly appreciated.
Is the SD card full?
Absent that, perhaps make a copy of the SD card on PC, reformat FAT32, place last known working backup on SD and see if you can restore that backup.
If that fails, perhaps d/l another ROM on PC, transfer to SD card, flash, see what you get.
I tried two different sdcards. Both were formatted as fat32. From the articles i have looked at i think i may have screwed up the internal storage. Followed this article:
h t t p://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage
They say to run "parted /dev/block/mmcblk0 mkfs ext2". When i do that it formats the sdcard to ext2. Still have the same issue. Doesn't appear to see the internal at all.
What command can i run from adb shell to display all the storage, volumes or partitions the system i can see?
Again any help is greatly appreciated!
I think just typing command 'mount' will list all mounts.
________________________________
Unrevoked forever
SkyRaider Sense 3.5
Radio 2.15.00.09.01

[Q] Can't mount /sdcard?

I might be showing my noobness tonight, but for some reason I cannot mount my sdcard via adb. It mounted the system just fine. Here's the error I get:
Code:
mount: mounting /dev/block/mmcblk0p1 on /sdcard failed: Device or resource busy
~ # mount /system
It sounds like the sd card is being used by something but if I'm in recovery how is that possible? I've heard people in other threads talk about dead sd cards but mine works fine other than this. Any ideas?
No one? No one's had this problem?
What command are you using to mount? Try just adb remount, not in shell. It should mount everything if it's not mounted. I have never had this issue.
Sent from my T-Mobile myTouch 3G Slide
Found the problem, clockwork already mounted it... whoops

Boot loops and CWM issues

Hello all,
i have been around on the site for a while reading, learning, and rooting my DInc. I have SkyRaider 3.5 w/ stock kernal. Currently running CWM 2.5.0.5. I was going to dip into the realm of setting CPU settings for different functions. I DLed SetCPU from the market and installed. i figured this would be a good time to do a backup through CWM in case i eff something up. after the backup completed, i selected the "reboot system now"
Upon rebooting, it loaded into my lock screen with the stock background and clock, not the ones i had before the backup process. when i did the slide unlock, it would just go to an all white screen with the htc green logo in the middle, and all my buttons but the power button were useless. strange i thought.....so i pulled the battery and proceeded into the CWM again to restore to a previous backup. got into CWM just fine, but now i had 5 message lines at the bottom of the CWM screen:
E:Cant mount /dev/block/mmcblk0p2
(file exists)
E:Cant mount CACHE:recovery/command
E:Cant mount /dev/block/mmcblk0p2
(File exists)
E:Cant mount CACHE:recovery/log
E:Cant mount /dev/block/mmcblk0p2
(File exists)
Then, i go into the backup and restore option, and select restore, it kicks me back to the main menu with 5 more messages:
E:Cant mount /dev/block/mmcblk1p1 (or /dev/bloc
k/mmcblk1)
(No such file or directory)
E:Cant mount /sdcard
E:Cant mount /dev/block/mmcblk0p2
(File exists)
E:Cant mount CACHE:recovery/log
E:Cant mount /dev/block/mmcblk0p2
(File exists)
I've tried doing a wipe data/factory reset, and it gives me a bunch of mounting errors and basically skips all format, then kicks me back to main menu in less than 3 seconds.
I've done a fair amount of research for this and can't find anything related to the DInc for this issue. Seen it on a few other devices (earlier droids) but not sure how much that info pertains to this device.
unfortunately i do not have a micro-sd card reader on my computer, so i have not tried re-flashing my ROM since i do not have a ROM on my SD card, not sure if it would be of any use since it sounds like my SD card is not mounting properly.
I will probably go out and buy a universal card reader (should come in handy) as well as a second SD card in case it happens to be the SD card that crapped out.
I figured I'd get this up here anyways to see if anyone can help.
Thanks so much for any advise or fixes you may be able to offer!
~Trey
update
well, i managed to do a couple hboot updates and basically return my phone to the way it was when i got it from the store. i have no idea what caused it, but the original sd card still works, albeit reformatted, and the phone is functioning perfectly so far. I'm still curious to see if anyone had any ideas about what happened. sorry i can be of service to troubleshoot since i fixed it (the long way). my phone is too vital and i have travel coming up.
Thanks,
Trey
When I tethered my incredible to my pc I would get errors. I've had to actually run defrag on my sd card. I actually have several Micro sd readers but I was lazy and did this after tethering to my pc. Seems to have fixed the problem
So, I decided to try to go back to root last night, with the help of Preludedrew. rooted using unrevoked3 and updated to CWM 3. when it was all finished, it left me in CWM recovery and i had new E: errors:
E:Can't mount /dev/recovery/log
E:Can't open /dev/recovery/log
E:Can't mount /dev/recovery/last log ?
E:Can't open /dev/recovery/last log
when i would try to mount cache or sdcard, it would still fail, and when trying to load zip from sdcard, it would error in trying to mount sdcard.
with some more help from drew, we tried using adb shell to mount/access some partitions, and the mmcblk0p2 (i think) could not be found on the device.
thankfully the phone still booted this time, but i went into the phone settings under SD & storage...and the sdcard was there showing my 15GB of total/available space.
But....under the internal phone storage section, it said "unavailable" for both total space and available space.
so the only thing we could somewhat deduce, is that the internal phone memory has crapped out, thus when i RUU'd (?) back to stock, it could not find my phone internal storage so it just reassigned my sdcard to the 0p1 block, and where the sdcard should be in the 0p2 block there is nothing. Hence why cwm cant find anything related to my sdcard since its looking in the 0p2 block.
so now that i'm back to stock, i'll take it to the verizon store today and see what they'll do about it since the internal memory seems to be crap. i have insurance, so i dont think it will be a problem getting a new phone, unless they want to try to replace the internal memory, which is fine with me.
unless anyone has any other ideas?
sorry for the noobish verbage, i'm trying to remember what i all did at 1230 last night.
Thanks,
sorry for the quick reply, but i just had the idea to try mounting my device as disk storage, since it should come up as 2 drives (internal phone and sdcard) on my computer
both drives show up under my computer, sdcard access is fine, but when i try to access the other drive, i get "please insert a disk into drive G:"
and when i switch back to charge only, it will only say "preparing sd storage" and doesnt do "preparing phone storage" like i thought i remember it doing when it was still good.
I guess just another reaffirmation that the storage space is crap.

Need Help Un-Softbricking Galaxy S2 T-Mobile Version (SGH-T989)

Complete Android newbie/dummy. Sophisticated Linux user.
Samsung Galaxy S2 T-Mobile version (SGH-T989). I think it's called "Hercules" -- it's the S2 without a home button. I previously installed CWM with Odin and rooted it by placing an su package on the sdcard. Didn't use the phone for a couple of years. Gave it to my wife after her phone was stolen. Seems to be stuck in the boot process. It boots to where I see "Samsung" logo, but the OS never comes up. Here's what I've done so far:
Reformatted the SD card on Linux using mkdosfs -F 32 -I /dev/sdf1. The SD card is 64GB, which is technically unsupported, but when the phone worked, it was able to use the SD card with no problems.
Installed a bootloader named TWRP 2.8.7.0. I can get into TWRP's environment, but not everything works as I expect it to.
Mount
The "Select Partitions to Mount" section is empty, which is unexpected since I have an FAT32 formatted SD card installed. Furthermore, when I press the "Mount USB Storage" button, I see the following error messages on the console:
E: Mount: Unable to find partition for path '/cache'
E: Mount: Unable to find storage partition to mount to USB
Install
At the top I see: "Storage: ( MB)", and underneath I see what looks to be a Unix filesystem. Obviously / is mounted (and I assume the partition is on the phone's internal memory), but the size isn't being detected by TWRP since the storage size is undefined. When I press "Storage" it asks me to select the storage, but the list is completely empty. Again, the SD card doesn't show up. Normally I'd "blame" my unsupported SD card size, but: a) it previously worked, and b) TWRP can't detect the storage size of the root partition, so something funny is happening.
Bootup
This might be the heart of the matter. When the phone boots into TWRP, there are some very ominous looking error messages:
E: Invalid block device on '/dev/block/mmcblk0p3
/boot
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p22
/recovery
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p24
/system
ext4 ro,errors=panic
wait
', 'ext4', 42
If this were a Linux system, I would suspect one of the following:
Perhaps /etc/fstab is referencing the wrong /dev/ files.
Perhaps the block device in question (e.g. hard drive) is failing.
Perhaps udev is not populating /dev/ properly.
As a last comment, when I poke around using TWRP's file manager, /boot is empty. The kernel should be in there, yes? OK, if so, then that's a very, very big problem. /recovery is empty. Interestingly, /system contains a single directory, /bin, which is empty. /sbin contains what you'd expect. /etc has an fstab, mtab, mke2fs.conf, and recovery.fstab.
Interestingly, /dev/block/mmcblk0p24, /dev/block/mmcblk0p24, and /dev/block/mmcblk0p3 all exist. This seems to indicate that udev is doing its job correctly (and I think also that /etc/fstab is ok). So maybe this is a hardware problem?
This is very strange because although I'm very comfortable with Linux, I'm feeling particularly helpless, and like I'm going around in circles.
Can some kind soul help me find my way?
I'm having the same type of problem with my E:\ not being mounted when I go into twrp. I can't even see a directory for me to run the wipe command on.
Will you try restoring back to Factory ROM ?
peterNYC said:
Complete Android newbie/dummy. Sophisticated Linux user.
Samsung Galaxy S2 T-Mobile version (SGH-T989). I think it's called "Hercules" -- it's the S2 without a home button. I previously installed CWM with Odin and rooted it by placing an su package on the sdcard. Didn't use the phone for a couple of years. Gave it to my wife after her phone was stolen. Seems to be stuck in the boot process. It boots to where I see "Samsung" logo, but the OS never comes up. Here's what I've done so far:
Reformatted the SD card on Linux using mkdosfs -F 32 -I /dev/sdf1. The SD card is 64GB, which is technically unsupported, but when the phone worked, it was able to use the SD card with no problems.
Installed a bootloader named TWRP 2.8.7.0. I can get into TWRP's environment, but not everything works as I expect it to.
Mount
The "Select Partitions to Mount" section is empty, which is unexpected since I have an FAT32 formatted SD card installed. Furthermore, when I press the "Mount USB Storage" button, I see the following error messages on the console:
E: Mount: Unable to find partition for path '/cache'
E: Mount: Unable to find storage partition to mount to USB
Install
At the top I see: "Storage: ( MB)", and underneath I see what looks to be a Unix filesystem. Obviously / is mounted (and I assume the partition is on the phone's internal memory), but the size isn't being detected by TWRP since the storage size is undefined. When I press "Storage" it asks me to select the storage, but the list is completely empty. Again, the SD card doesn't show up. Normally I'd "blame" my unsupported SD card size, but: a) it previously worked, and b) TWRP can't detect the storage size of the root partition, so something funny is happening.
Bootup
This might be the heart of the matter. When the phone boots into TWRP, there are some very ominous looking error messages:
E: Invalid block device on '/dev/block/mmcblk0p3
/boot
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p22
/recovery
emmc defaults
defaults
', 'emmc', 72
E: Invalid block device on '/dev/block/mmcblk0p24
/system
ext4 ro,errors=panic
wait
', 'ext4', 42
If this were a Linux system, I would suspect one of the following:
Perhaps /etc/fstab is referencing the wrong /dev/ files.
Perhaps the block device in question (e.g. hard drive) is failing.
Perhaps udev is not populating /dev/ properly.
As a last comment, when I poke around using TWRP's file manager, /boot is empty. The kernel should be in there, yes? OK, if so, then that's a very, very big problem. /recovery is empty. Interestingly, /system contains a single directory, /bin, which is empty. /sbin contains what you'd expect. /etc has an fstab, mtab, mke2fs.conf, and recovery.fstab.
Interestingly, /dev/block/mmcblk0p24, /dev/block/mmcblk0p24, and /dev/block/mmcblk0p3 all exist. This seems to indicate that udev is doing its job correctly (and I think also that /etc/fstab is ok). So maybe this is a hardware problem?
This is very strange because although I'm very comfortable with Linux, I'm feeling particularly helpless, and like I'm going around in circles.
Can some kind soul help me find my way?
Click to expand...
Click to collapse
Do you have root access ?
Anyone have a fix for this? I'm having the same issue with my SGS2X (hercules). Thanks
Odin back to stock or try a different recovery, might I suggest CWM
fattest said:
Anyone have a fix for this? I'm having the same issue with my SGS2X (hercules). Thanks
Click to expand...
Click to collapse
Your best bet is to odin back to Stock, mine is a bit weird, I can't install JB via no method, always stuck at samsung logo, but ICS seems to go ok, you should try it.

Categories

Resources