Database Info

[Q] fstab can't mount system, sdcard, or anything really.

So yeah, my phone was regular 2.3.4 and it wouldn't always reboot easily (took multiple tries). So I figured I'd install CyanogenMod 7 like all the cool kids. I'm a programmer, this should be easy, right? Wrong.
So after much trial and error fastboot decided to randomly find my phone and let me unlock it (long story...). I start playing around with adb and fastboot, having a good old time. I decide to do the ClockworkMod Recovery image and it works great. I try to do an "update from sdcard" with the latest CyanogenMod for Nexus S and it amazingly works!... Except that it still won't boot up. It sits on the Google loading screen--I suspect failing to mount anything.
I found out about this:
Code:
ClockworkMod Recovery v4.0.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/platform/s3c-sdhci.0/by-name/media (null)
2 /system ext4 /dev/block/platform/s3c-sdhci.0/by-name/system (null)
3 /cache yaffs2 cache (null)
4 /data ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata (null)
5 /misc mtd misc (null)
6 /boot mtd boot (null)
7 /recovery mtd recovery (null)
8 /bootloader mtd bootloader (null)
9 /radio mtd radio (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
Notice all of the (null)s....
Also this:
Code:
-- Install from sdcard...
Finding update package...
I:Update location: /sdcard/update.zip
W:failed to mount /dev/block/platform/s3c-sdhci.0/by-name/media (No such file or directory)
E:Can't mount /sdcard/update.zip
Installation aborted.
mtd: successfully wrote block at 0
I:Set boot command ""
E:Unable to write to ums lunfile (No such file or directory)
...and this, clearly from fstab:
Code:
/dev/block/platform/s5pc110-onenand # mount -a
mount -a
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/userdata on /data failed
: No such file or directory
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/system on /system failed
: No such file or directory
mount: mounting /dev/block/platform/s3c-sdhci.0/by-name/media on /sdcard failed:
No such file or directory
There's no s3c-sdhci.0 in /dev/block/platform.... only s5pc110-onenand (which happens to be the title of the processor and memory used in my phone).
So yeah, that's where my brain gives out.
I'd like to install CM7, or at the least get a working phone back somehow.
Oh yeah, I tried doing adb shell and a nandroid restore command w/ downloaded nandroid backup. No love. It told me "unknown volume for path [/sdcard] Can't mount /sdcard". No ****.
Ideas?
Thanks!

Small update:
about 1 out of 100 times, it'll allow me to mount the sdcard after some random fiddling. I have tried multiple recovery images, erasing partitions, flashing random things... nothing works!
The one or two times it mounted the sdcard, I was able to perform an "update from sdcard" but then it would just do what it has done for a long time--sit at the google loading screen for hours and never actually boot into the real OS.
Sigh. Hardware issue maybe?

Hi,
what's your phones status?
My Nexus seems at a similar state now I came across http://forum.xda-developers.com/showthread.php?t=991276 and had to try it (why not, I have nandroid backups, Titanium etc. ...) I applied a setting, rebooted and got stuck at the google logo. It would boot into recovery but there it has no access to sdcard, system, data (but cache is mounted). After lots of fiddling I got it to work once, whiped, flashed a rom and all looked good again. But now I did a reboot and the phone is stuck again and in recovery (CWM 3.something) I get no sdcard
What happened and how to fix it?

I managed to flash a stock system back on the phone and it still didn't work, so I called Samsung and they let me RMA the phone. I got it back three weeks later, in good shape. They had to replace the PBA, the mainboard, and they did it all for free. They even gave me a shipping label to use when I shipped it out. Nice.
At the least, I think it's necessary to flash a stock bootloader and lock the phone before calling them.
Good luck!

Good for you
I tried flashing a stock rom, both using fastboot and also using Odin, both methods fail or get stuck while flashing the system.img
Looks like I've screwed up
If I could at least once get to the data on sdcard ...

i think i found a workaround
i tried flashing the old clockworkmod (3.1.0.1) and the flashing the latestest one twice and then clockworkmod was able to mount the sdcard. huge relief. installed the rom and then rebooted and the system booted well.
also tried installing the clockwork manager app and flashing the latest recovery from the app and then rebooted into recovery. it was able to mount the sdcard now.
not sure if this random success or a fix. it worked.

Had the same exact issue. Sprint tech replaced the phone for me for $35 without insurance. But basically the internal memory would only mount once every 10-100 reboots.
Definitely a manufacturing issue.

obsanity said:
Had the same exact issue. Sprint tech replaced the phone for me for $35 without insurance. But basically the internal memory would only mount once every 10-100 reboots.
Definitely a manufacturing issue.
Click to expand...
Click to collapse
Have you tried reflashing the recovery twice?
Did the sprint tech provide the details on what exactly the issue was?
In my case, the phone is contract free and I have to approach samsung support if this issue occurs again.
Since the sdcard is some times mounting, i am hopeful that there should be a way out via sw.

gsrdemon said:
Have you tried reflashing the recovery twice?
Did the sprint tech provide the details on what exactly the issue was?
In my case, the phone is contract free and I have to approach samsung support if this issue occurs again.
Since the sdcard is some times mounting, i am hopeful that there should be a way out via sw.
Click to expand...
Click to collapse
Samsung service center repaired the device (mother board replaced); in warranty.
Sent from my Nexus S

Need FS Block Size: Bad Magic Block Error

SHORT: I need the filesystem block size (location would be nice too; however, I can guess that) so I can use e2fsck to restore my super-block.
LONG: I have been having issues for the past several days where I cannot umount /system. I thought it may have been a bad conversion going to/from or from/to rfs and ext4 and thought doing the conversion again had fixed it. But alas...it didn't.
I cannot umount the files system from adb ("device is busy" error) or CWMR ("Couldn't find valid filesystem superblock" in the log) on any version of ROM or using any kernel that I can find. Voodoo can seem to convert the filesystem (back/forth), but it only seem to work if I tell it to from the Voodoo Control and then reboot, which is odd. Still cannot umount.
When I try and use Navenedrob's Ext4 Formatter, it fails for /system. CWMR's log shows:
/tmp/tune2fs: Bad magic number in super-block while trying to open /dev/block/stl10
Couldn't find valid filesystem superblock
Should be fixable with e2fsck, if I can get the correct information from tune2fs.
Typically, the command should be:tune2fs -l /dev/block/stl10 OR tune2fs -l -L /system
That said, tune2fs is tell me "-l" is an unknown option.
Can someone who is familiar with tune2fs (or other filesystem tools) in the Android/BusyBox environment please post either the correct command or a list of the contents of the filesystem super-block? Please be sure to include if your /system is in EXT4 or RFS.
Man, I haven't see this **** in years. Even then, it was pretty exclusive to virtual/networked file system (e.g. LVM).
Any-who, much appreciated....

So, after sleeping on it, I came to realize an error in my thinking...
I cannot use e2fsck to fix an RFS filesystem. Even more upsetting is that I cannot seem to find anything on The Google about command line RFS tools. Guess I could try a conversion and EXT filesystem, then change the superblock, then convert back to RFS, but that seems awfully convoluted.
Suggestions?

I suggest you odin with pit and check repartition. That *usually* fixes everything.
Sent from my debloated ep1q charge......bro.

Thanks for the tip...I probably should have mention that I've used Pit+ED1 numerous times in a effort to fix this. It goes through successfully; however, it doesn't actually wipe the partition and I've found old files in /system.
UPDATE:
Last thing I tried is manually wiping everything from /system (in CWMR + adb shell). Also, wiped everything I could find having anything to do with voodoo or EXT4 (just in case). After power off then back to recovery, I found I could umount /system. Created a new partition, formatted, then wacked the partition.
I just (successfully) ran ED1+pit from the Samsung Flashing Utility (which I have NOT tried using before) and I am now in the process of upgrading. Once I have root back, I'll go see if the fix for /system was permanent.

[RECOVERY] CWR for Nexus 7

I will say this up front for all to read in big bold letters
I DO NOT KNOW IF THIS WORKS. I DO NOT HAVE A DEVICE TO TEST
I ran this through Koush's automated CWR creator located at http://builder.clockworkmod.com/
Touch Version:
https://docs.google.com/open?id=0B0ozkQsJWIScSjdqbEJvemJEU0U
Normal Version:
https://docs.google.com/open?id=0B0ozkQsJWIScUGVpZjdyT25YZ0E
recovery.fstab
Code:
# mount point fstype device
/sdcard vfat /dev/block/sda1
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
fstab.grouper
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 ro wait
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MDA

Working or not, that is a damn good start. Thank you
Sent from my SPH-D710 using xda premium

Umm, this doesn't actually work that well, it forces you to use a USB stick as /sdcard and there's no back button.
P

paulobrien said:
Umm, this doesn't actually work that well, it forces you to use a USB stick as /sdcard and there's no back button.
P
Click to expand...
Click to collapse
Thanks, Paul! At least you confirmed things for me.
I did just use Koush's auto-builder, as my server hard drive crashed, so I couldn't use my own code.

use the cwm made by birdman.
Sent from my HTC Glacier using xda premium

smirkis said:
use the cwm made by birdman.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
I rather wait till I get my own device, I can test my own builds before releasing them. I was just excited to give this a try.
Of course, someone might have this done before I get my N7 And if that is the case, I will probably be building a TWRP

Is it CWR (ClockWorkmod Recovery) or CWM ClockWorkMod .
Usually i use CWM.

imfloflo said:
Is it CWR (ClockWorkmod Recovery) or CWM ClockWorkMod .
Usually i use CWM.
Click to expand...
Click to collapse
Those are the same thing, correct me if I am wrong.

mmmcfc said:
Those are the same thing, correct me if I am wrong.
Click to expand...
Click to collapse
Yep. Both are same
Sent from my GT-S5670 using xda premium

imfloflo said:
Is it CWR (ClockWorkmod Recovery) or CWM ClockWorkMod .
Usually i use CWM.
Click to expand...
Click to collapse
Pwahahahah nice =)
Sent from my Nexus 7 using xda premium

We are CWM Touch official, upgrade through app($1.99) or download for manual install here (free)http://www.clockworkmod.com/rommanager

[twrp 2.6.3.2][read me]

I just need to get the word out, now that I have seen this go from a couple user issue to maybe, getting out of control.....The new TWRP has a issue with formatting data, I have experienced this first hand. It ended for me in a softbrick, and a few users on the forums...I would never want this to happen to anyone.. Im sure TWRP feels the same.... Just be aware of the issue.. I have posted on there fourm page about the issue...Thx as always lj
sbdags said:
You'll have to format the data partition manually with the following in the terminal emulator under advanced in twrp.
mke2fs -T ext4 /dev/block/mmcblk0p8
Note you will lose everything on internal so move backups and your ROM zips to flash onto your micro SD.
Click to expand...
Click to collapse
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8

[MOD] [PERFORMANCE] ext4 journal disabler [CM|AOSP]

The ext4 filesystem which is primarily used on android phones has a feature called "journal". This is a "file" which acts like a "middleman" when the system writes data on your storage. So before a file gets transferred to the destination a part of the file will always be at first in the journal. The benefit is that you have less chance to "loose" a file when the system is interrupted during the transfer (power failure, connection failure ...) because the journal has a copy of the part which was transferred to the final destination. So when the system restarts the device can finelize the transfer because the journal has the needed information, what exactly was transferred and what wasn't.
But this security feature has a negative impact of your I/O performance. And since a smartphone has a battery and soldered storage chips a fatal failure is much less possible than with conventional PC.
My mini ZIP disable journal on the data and cache partition, because these are the ones on which android writes data. On the system partition android just read the files and a journal will not slow down the read performance (which should be logical if you read the first part)
PS: should be logical but anyway, to use my script you need to have ext4 on cache an data. if you haven't changed the filesystem, then you will probably have ext4 because it's the stock filesystem for android
!!! if you have encrypted system this will not work !!!
so this mod dont work on OxygenOS because its has enforced encryption
the minimal binary:
Code:
#!/sbin/sh
umount /dev/block/bootdevice/by-name/cache
umount /dev/block/bootdevice/by-name/userdata
e2fsck -pv /dev/block/bootdevice/by-name/cache
e2fsck -pv /dev/block/bootdevice/by-name/userdata
tune2fs -O ^has_journal /dev/block/bootdevice/by-name/cache
tune2fs -O ^has_journal /dev/block/bootdevice/by-name/userdata

Hi, thanks for sharing, your file will work on any rom?
Sent from my OnePlus3 using XDA Labs

fanbogo said:
Hi, thanks for sharing, your file will work on any rom?
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
any rom and ext4 on data and cache

I'm using stock oxygen, update from today
Sent from my OnePlus3 using XDA Labs

fanbogo said:
I'm using stock oxygen, update from today
Sent from my OnePlus3 using XDA Labs
Click to expand...
Click to collapse
i see .. i have tested the script with adb and also the final zip before i have flashed the system. i try to solve it now. its maybe because of the encrypted partition

Ok im waiting
Sent from my OnePlus3 using XDA Labs

It doesn't install on DU 10.4 (AOSP) (same issue as OOS)

nazagan said:
It doesn't install on DU 10.4 (AOSP) (same issue as OOS)
Click to expand...
Click to collapse
is your rom encrypted?

Nope, erased by format data

nazagan said:
Nope, erased by format data
Click to expand...
Click to collapse
ok damn, it seems not to work anymore like on older phones in the past. F2FS would be anyway faster ...
ok sorry guys

Thread closed at OP's request.