Guest skittleys Posted January 4, 2012 Report Share Posted January 4, 2012 Over the holidays, I obtained a 32GB class 10 microSD card. I'm excited to replace my class 2 card, but I keep running into issues. The most significant: my ext2 partition will not mount in recovery mode, thus preventing me from doing a nandroid+ext backup! I want to mention straight off that I'm hoping for a solution other than reflashing a ROM or resetting my phone. I'm very wary of this, because obviously I don't have a full backup!!!!!! I'm running MIUI 1.11.4 and Malez 0.6.1 (the changelogs for both suggest that there've been no relevant fixes in the later versions). Additionally, I am using the DT-A2SD method that comes built-in with MIUI, and it works perfectly. I've done a lot in terms of diagnostics, and I've gotten nowhere. I'll try my best to outline everything I've tried so far. At the bottom of this post, I'll add the results of numerous commands I've run in both normal + recovery modes to clarify things further. First up: the results of the nandroid+ext backup. I've attached the whole recovery.log for that session, but the key part is: Storing the ext2(Apps, Dalvik-cache) contents in the backup folder. Warning: --ext2 specified but unable to mount the ext2 partition. I also ran nandroid-mobile.sh -b -e from the shell and got the same result. Some other interesting elements from that log: Enabling USB-MS : /sbin/um: line 3: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexistent directory ./sbin/ums_toggle: line 23: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexistent directory USB Mass Storage enabled Disabling USB-MS : /sbin/um: line 3: can't create /sys/devices/platform/usb_mass_storage/lun0/file:nonexistent directory ./sbin/ums_toggle: line 23: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexistent directory USB Mass Storage disabled Copy recovery.log to SD Press HOME to confirm, any other key to abort. Copying : /sbin/um: line 3: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexistent directory. Copy completed! If it weren't for the log, I wouldn't have realised there'd been problems, because all those operations worked! One big thing i have tried: / # mount -o remount,rw -t ext2 /dev/block/mmcblk0p2 /system/sd mount: mounting /dev/block/mmcblk0p2 on /system/sd failed: Invalid argument I've also attached the results of a2sd sysinfo, which spits out crazy amounts of detail, including all of init.rc. I ran identical commands in both recovery and normal mode to see all the differences, along with some a2sd commands in normal mode. The results are below, but there are some interesting things to comment on. Some of these things might actually be normal, but I don't know for sure. A2SD is working perfectly, as demonstrated by a2sd check, ls and df.I can't access any of the scripts inside /sbin while in normal mode.I can't see /sd-ext at all when in recovery mode.All that /system/sd ever contains is one 0-byte file. In normal mode, it's called 'placeholder'. In recovery, it's called 'empty'.I haven't posted everything for this one because the rest was mostly junk or was OK, but I did notice something rather ironic at the end of a2sd forcecheck:[-] Checkpoint 19: Check for start parameter and launch start2sd if needed. [ ] Launching Apps2SD Start Program with forcecheck [ ] Starting Darktremor Apps2SD in forcecheck mode [ ] Creating Force Check Flag File... [ ] Unmounting /dev/block/mmcblk0p2... umount: can't umount /sd-ext: Device or resource busy [ ] Rebooting phone... ---------------------------------------- While in 'normal' mode: mount: rootfs on / type rootfs (ro) tmpfs on /dev type tmpfs (rw,mode=755) devpts on /dev/pts type devpts (rw,mode=600) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) none on /acct type cgroup (rw,cpuacct) tmpfs on /mnt/asec type tmpfs (rw,mode=755,gid=1000) tmpfs on /mnt/obb type tmpfs (rw,mode=755,gid=1000) none on /dev/cpuctl type cgroup (rw,cpu) /dev/block/mtdblock4 on /system type yaffs2 (ro) /dev/block/mtdblock3 on /data type yaffs2 (rw,nosuid,nodev) /dev/block/mtdblock5 on /cache type yaffs2 (rw,nosuid,nodev) /dev/block/mmcblk0p2 on /sd-ext type ext2 (rw,noatime,nodiratime,barrier=1,data=ordered) /dev/block/vold/179:1 on /mnt/sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro) /dev/block/vold/179:1 on /mnt/secure/asec type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0602,dmask=0602,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro) tmpfs on /mnt/sdcard/.android_secure type tmpfs (ro,size=0k,mode=000) ls -lhAF /: drwxr-xr-x 3 root root 0 Dec 31 22:49 acct/ drwxrwx--x 1 system cache 2.0K Dec 30 16:04 cache/ dr-x------ 2 root root 0 Dec 31 22:49 config/ lrwxrwxrwx 1 root root 17 Dec 31 22:49 d -> /sys/kernel/debug drwxrwx--x 1 system system 2.0K Dec 31 22:49 data/ -rw-r--r-- 1 system system 118 Nov 6 01:17 default.prop -rw-r--r-- 1 system system 118 Nov 6 01:13 default.prop~ drwxr-xr-x 12 root root 3.0K Jan 1 23:07 dev/ lrwxrwxrwx 1 root root 11 Dec 31 22:49 etc -> /system/etc/ -rwxr-xr-x 1 system system 92.2K Nov 6 01:13 init* -rw-r--r-- 1 system system 1.6K Nov 6 01:13 i nit.goldfish.rc -rw-r--r-- 1 system system 14.7K Nov 6 01:13 init.rc -rwxr-xr-x 1 system system 4.2K Nov 6 01:13 init.salsa.rc* drwxrwxr-x 6 root system 0 Dec 31 22:49 mnt/ dr-xr-xr-x 132 root root 0 Dec 31 1969 proc/ drwx------ 2 root root 0 Nov 6 01:11 root/ drwxr-xr-x 2 system system 0 Nov 6 01:13 sbin/ drwxrwx--x 7 system system 1.0K Dec 24 01:41 sd-ext/ lrwxrwxrwx 1 root root 11 Dec 31 22:49 sdcard -> /mnt/sdcard/ drwxr-xr-x 12 root root 0 Dec 31 1969 sys/ drwxr-xr-x 1 root root 2.0K Dec 30 22:55 system/ -rw-r--r-- 1 system system 0 Nov 6 01:13 ueventd.goldfish.rc -rw-r--r-- 1 system system 4.0K Nov 6 01:13 ueventd.rc -rwxr-xr-x 1 system system 571 Nov 6 01:13 ueventd.salsa.rc* lrwxrwxrwx 1 root root 14 Dec 31 22:49 vendor -> /system/vendor ls -lhAF /system/sd: -rw-r--r-- 1 root root 0 Aug 1 2008 placeholder ls -lhAF /sbin: -rwxr-xr-x 1 system system 111.2K Nov 6 01:13 adbd* lrwxrwxrwx 1 system system 7 Nov 6 01:13 ueventd -> ../init* ls -lhAF /sd-ext: drwxrwxrwx 2 root root 4.0K Dec 31 18:18 app/ drwxrwxrwx 2 root root 1.0K Dec 30 22:46 app-private/ drwxrwxrwx 2 root root 10.0K Jan 2 00:00 dalvik-cache/ drwxrwxrwx 2 root root 1.0K Dec 24 01:41 data/ drwxr-xr-x 2 root root 12.0K Dec 24 01:39 lost+found/ df -h: Filesystem Size Used Available Use% Mounted on tmpfs 213.8M 32.0K 213.8M 0% /dev devpts 0 0 0 0% /dev/pts proc 0 0 0 0% /proc sysfs 0 0 0 0% /sys none 0 0 0 0% /acct tmpfs 213.8M 0 213.8M 0% /mnt/asec tmpfs 213.8M 0 213.8M 0% /mnt/obb none 0 0 0 0% /dev/cpuctl /dev/block/mtdblock4 200.0M 140.9M 59.1M 70% /system /dev/block/mtdblock3 200.0M 95.5M 104.5M 48% /data /dev/block/mtdblock5 41.9M 1.1M 40.7M 3% /cache /dev/block/mmcblk0p2 915.2M 256.7M 609.6M 30% /sd-ext /dev/block/vold/179:1 14.0G 5.2G 8.7G 37% /mnt/sdcard /dev/block/vold/179:1 14.0G 5.2G 8.7G 37% /mnt/secure/asec tmpfs 0 0 0 0% /mnt/sdcard/.android_secure a2sd check: [ ] GREP: Using ROM Busybox. [ ] REBOOT: Using ROM Busybox. [ ] FDISK: Using ROM Busybox. [ ] CAT: Using ROM Busybox. [ ] MKDIR: Using ROM Busybox. [ ] RMDIR: Using ROM Busybox. [ ] CHMOD: Using ROM Busybox. [ ] MOUNT: Using ROM Busybox. [ ] UMOUNT: Using ROM Busybox. [ ] CP: Using ROM Busybox. [ ] RM: Using ROM Busybox. [ ] MV: Using ROM Busybox. [ ] LN: Using ROM Busybox. [ ] MORE: Using ROM Busybox. [ ] MKNOD: Using ROM Busybox. [ ] AWK: Using ROM Busybox. [ ] SLEEP: Using ROM Busybox. [ ] SYNC: Using ROM Busybox. [ ] TEE: Using ROM Busybox. __ _____ | \ | | | | |__/ | Darktremor Apps2SD 2.7.5.3 Beta 4a (2011-01-30) [-] Checkpoint 1: Check for SD Card Fix and Implement. [-] Checkpoint 2: Run Dalvik Heap Program (if exists). [ ] Running Dalvik Heap program... [ ] Setting Dalvik Heap Size to 30 MB [-] Checkpoint 3: Run Set Low Memory Killer Program (if exists). [-] Checkpoint 4: Determine Mount Point. [-] Checkpoint 5: Set Parameter Variables. [ ] GetProp Command = /system/bin/toolbox getprop [ ] SetProp Command = /system/bin/toolbox setprop [ ] Mount Point = /sd-ext [-] Checkpoint 6: Insert CyanogenMod patch. [-] Checkpoint 7: Complete Dalvik Cache Move (if applicable). [-] Checkpoint 8: Resetting Dalvik Cache Partition [-] Checkpoint 9: Switching Davlik Cache to Cache Partition (if applicable) [-] Checkpoint 10: Checking for existence of command parameter [-] Checkpoint 11: Check for a2sd help command [-] Checkpoint 12: Check for a2sd check command [ ] Starting Apps2SD Check Program. Darktremor 2.7.5.3 Beta 4a Apps2SD Status Report =================================================================================== Legend: [✔]=Setting is correct [‼]=Setting is correct, but not optimal. [✖]=Setting is incorrect and needs to be fixed or option is not available. =================================================================================== Block Device - [✔] /dev/block/mmcblk0p2 Mount Point - [✔] /sd-ext Support EXT2? - [✔] Yes Support EXT3? - [✔] Yes Support EXT4? - [✔] Yes Apps - [ ] Linked to SD Card. [ ] No Apps2SD Flag File not found. [✔] Programs run from SD card To run from internal storage, type a2sd remove Private Apps - [ ] Linked to SD Card. [ ] No Apps2SD Flag File not found. [✔] Private Programs run from SD card To run from internal storage, type a2sd remove Dalvik Cache - [ ] Symbolically Linked. [ ] Dalvik to SD flag file found. [✔] Dalvik runs from SD card To run from internal storage, type a2sd nocache To run from /cache partition, type a2sd cachepart Data - [ ] Program Data on Internal Storage. Swap - [ ] Partition not present or no swap support. [✔] Swap does not start. ZipAlign - [✔] Running at boot. To deactivate it, type a2sd nozipalign Dalvik Heap(MB) - [✔] 30m Low Memory Killer Settings - [✔] 2048,3072,4096,6144,7168,8192 Note: Values are in pages. 1 page = 4KB memory. Values represent the following: 1st number = Foreground App 2nd number = Visible App 3rd number = Secondary Server 4th number = Hidden App 5th number = Content Provider 6th number = Empty App [⁇] For a list of commands that you can use with Apps2SD Type: a2sd help While in 'recovery' mode: mount: rootfs on / type rootfs (rw) tmpfs on /dev type tmpfs (rw,mode=755) devpts on /dev/pts type devpts (rw,mode=600) proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) /dev/block/mtdblock5 on /cache type yaffs2 (rw,nodev,noatime,nodiratime) /dev/block/mmcblk0p1 on /sdcard type vfat (rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=07 11,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro) ls -lhAF /: total 118 drwxrwx--x 1 1000 2001 2.0K Dec 30 21:04 cache/ drwxrwx--x 2 0 0 0 Feb 24 2010 data/ -rw-r--r-- 1 0 0 173 Oct 4 2010 default.prop drwxr-xr-x 11 0 0 2.9K Jan 4 01:52 dev/ drwxr-xr-x 2 0 0 0 Sep 8 2010 etc/ -rwxr-x--- 1 0 0 101.3K Jul 9 2010 init* -rwxr-x--- 1 0 0 1.6K Feb 24 2010 init.goldfish.rc* -rwxr-x--- 1 0 0 968 Sep 9 2010 init.rc* dr-xr-xr-x 56 0 0 0 Jan 1 1970 proc/ drwxr-xr-x 3 0 0 0 Feb 24 2010 res/ drwx------ 2 0 0 0 Jun 22 2010 root/ drwxr-x--- 2 0 0 0 Jan 4 01:52 sbin/ drwxr-xr-x 2 0 0 0 Jan 4 01:53 sdcard/ drwxr-xr-x 2 0 0 0 Sep 4 2010 superboot/ drwxr-xr-x 12 0 0 0 Jan 1 1970 sys/ drwxr-xr-x 3 0 0 0 Feb 24 2010 system/ drwxr-xr-x 2 0 0 0 Jan 4 01:52 tmp/ ls -lhAF /system/sd: total 0 -rw-r--r-- 1 0 0 0 Feb 24 2010 empty ls -lhAF /sbin: total 248512 -rwxr-x--x 1 0 0 16.6K Mar 1 2010 Superuser.apk* -rwxr-xr-x 270 0 0 905.8K Aug 31 2010 [* -rwxr-xr-x 270 0 0 905.8K Aug 31 2010 [[* -rwxr-xr-x 270 0 0 905.8K Aug 31 2010 acpid* -rwxr-x--x 1 0 0 114.7K Feb 24 2010 adbd* lrwxrwxrwx 1 0 0 7 Oct 4 2010 app2sd -> apps2sd* -rwxr-x--x 1 0 0 4.0K Mar 27 2010 app2sd.old* -rwxr-xr-x 1 0 0 4.5K Apr 1 2010 apps2sd* (.........................etc....................) ls -lhAF /sd-ext: ls: /sd-ext: No such file or directory df -ha: Filesystem Size Used Available Use% Mounted tmpfs 214.8M 0 214.8M 0% /dev devpts 0 0 0 0% /dev/pts proc 0 0 0 0% /proc sysfs 0 0 0 0% /sys /dev/block/mtdblock5 41.9M 1.1M 40.7M 3% /cache /dev/block/mmcblk0p1 14.0G 5.2G 8.7G 37% /sdcard[/code]recovery.log.txta2sd-sysinfo.txt Link to comment Share on other sites More sharing options...
Guest dabenxiong Posted January 4, 2012 Report Share Posted January 4, 2012 try to update your recovery to Malez 0.6.2 or，you can back up the ext2 partition on computers. just use tours like Ghost. Link to comment Share on other sites More sharing options...
Guest skittleys Posted January 4, 2012 Report Share Posted January 4, 2012 (edited) ...just use tours like Ghost. I don't think that translated correctly...I have no idea what you mean. As for copying the ext partition, I have done that just in case. In theory the symbolic links won't be destroyed since the tree structure will remain the same, but I'm not confident that'll it'll work as planned. And I'll try updating the recovery, but according to the chaneglog, it shouldn't make a difference. ------------------ **update** I installed v 0.6.2, but it made no difference. and this is the output when I try to "repalr" the sdcard: Repair ext filesystem Press HOME/POWER to confirm,I:EVENT received : type 1 value 229 any other key to abort. I:EVENT received : type 1 value 102 Repairing ext filesystem : /sbin/um: line 3: can't create /sys/devices/platform/usb_mass_storage/lun0/file: nonexistent directory .unmounting /system unmounting /sdcard unmounting /data I:EVENT received : type 1 value 102 e2fsck 1.41.6 (30-May-2009) /dev/block/mmcblk0p2: recovering journal Pass 1: Checking inodes, blocks, and sizes .......Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information /dev/block/mmcblk0p2: 281/500856 files (91.1% non-contiguous), 325800/1000018 blocks Ext repairing complete! Edited January 5, 2012 by skittleys Link to comment Share on other sites More sharing options...
Guest siggey Posted January 5, 2012 Report Share Posted January 5, 2012 Malez recovery can't backup ext4 partition. Are you sure that your ext partition is 2? Link to comment Share on other sites More sharing options...
Guest skittleys Posted January 5, 2012 Report Share Posted January 5, 2012 Malez recovery can't backup ext4 partition. Are you sure that your ext partition is 2? I'm 100% sure. See the output of mount in the first post, and also the fact that the error that I get is "ext2 specified but unable to mount the ext2 partition" Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now