Project

General

Profile

can't access storage on a nexus s with 4.2 003

Added by Christopher Hobbs over 9 years ago

I've been running 4.2 002 for several months. I decided to update to 003 this evening and did so via sideload. The phone booted and everything appeared to be fine until I tried to connect the phone to my computer to copy backups over. When I tap the "Turn on USB storage" button, it just spins and I don't get any response. F-Droid is refusing to load any updates and I suspect that might be related.

I've attached a copy of my logcat output. The only line that stands out to me is this:
W/MediaScanner( 501): Error opening directory '/storage/sdcard0/', skipping: Permission denied.

I ran adb shell and was able to get into /storage/sdcard0 by using su to log in as root and chown the filesystem. This didn't resolve the mounting issue, though.

The phone was encrypted when I was running 002. I wiped all user data before rebooting (after installing 003). I was never asked for my encryption password after that. I have no idea if that information is relevant or not.

I've since downgraded to 002 and I've also tried various builds of cyanogenmod. In every case now, I'm unable to mount my USB storage. In cyanogenmod, when I tried to download F-Droid via the browser, it stated that no USB storage was present. I only installed cyanogenmod to see if the issue was Replicant or my phone.

Anyone have ideas for what might be broken or where to begin troubleshooting?

Thanks!
cmh

logcat.out (99.1 KB) logcat.out logcat dump

Replies (5)

RE: can't access storage on a nexus s with 4.2 003 - Added by Christopher Hobbs over 9 years ago

Trying to mount the storage via recovery mode yields the following:

W:failed to mount /dev/block/platform/s3c-dhci.0/by-name/media (Invalid argument)
Error mounting /sdcard!
mtd: successfully wrote block at 0
I:Set boot command ""
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc

RE: can't access storage on a nexus s with 4.2 003 - Added by Christopher Hobbs over 9 years ago

Using an updated version of clockwork, trying to mount /storage/sdcard0 via recovery yields the following:

I:605 Volume sdcard0 /storage/sdcard0 state changed from 1 (Idle-Unmounted) to 3 (Checking)
I:/storage/sdcard0: Checking
I:605 Volume sdcard0 /storage/sdcard0 state changed from 3 (Checking) to 1 (Idle-Unmounted)
I:/storage/sdcard0: Idle-Unmounted
I:400 0 volume operation failed (Success)
Error mounting /storage/sdcard0!
I:Set boot command ""
I:Can't partition non mmcblk device: /devices/platform/s3c-sdhci.0/mmc_host/mmc0/mmc0:0001/block/mmcblk0

RE: can't access storage on a nexus s with 4.2 003 - Added by Christopher Hobbs over 9 years ago

I managed to resolve the issue by reverting back to a stock ROM (4.1.2). When I booted the stock ROM, I received a notice about formatting the SD memory. Doing so (slowly) brought all the features back. Everything worked fine after reinstalling 0003 from there.

RE: can't access storage on a nexus s with 4.2 003 - Added by Paul Kocialkowski over 9 years ago

So in the end, it appears that there was something wrong with the USB storage memory itself:

D/MountService(  353): volume state changed for /storage/sdcard0 (checking -> nofs)

Sadly, this may be a sign that it's dying. I had a similar problem happening to my Galaxy S (I9000). Perhaps flashing the new image caused a lot of I/O on the mmc device which ended up in it failing and losing the partitions table for external storage or something. So I'm afraid this is not related to Replicant in particular.

RE: can't access storage on a nexus s with 4.2 003 - Added by Christopher Hobbs over 9 years ago

I concur, it is not an issue with Replicant.

    (1-5/5)