Root sd-ext - fails to create

[critusodem]

Phone: LG Optimus Slider

Installed:
GingerKernel 2.6.35.7 v07.1
Mobster Rom v1.3

Objective:
Install A2SD to deal with this inane low internal memory nonsense

Using:
How to Partition an SD Card and Install Darktremor Apps2SD on Android Smart Phone? ~ Handy Information

At:
5. Reboot your device and open a terminal emulator or shell commander and type in the following command to make sure that your second partition (aka sd-ext partition) is mounted at boot.
mount | grep sd-ext
You should see the following code:
/dev/block/mmcblk0p2 on /sd-ext type ext3 (rw,noatime,nodiratime,barrier=1,nodelalloc,data=ordered)

When I enter:
su
mount | grep sd-ext

It yields no results (goes to the next time).

Going into the log from the recovery interface provides this:

Formatting /sd-ext...
I: Set boot command ""
Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Done.
mtd: successfully wrote block at c7de400000000
I:Set boot command ""


I did the option step as well:
Format your sd-ext from mounts and storage>>fromat /sd-ext


Any ideas?
Thanks and what not.

-Chris

Recovery.log

Starting recovery on Sun Jan 6 00:00:04 1980
framebuffer: fd 4 (320 x 480)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /sd-ext auto /dev/block/mmcblk0p2 (null)
8 /system yaffs2 system (null)

W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
E:Bad boot message
"recovery
"
Fixing execute permissions for /cache
mtd: successfully wrote block at c7de400000000
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_gelato-eng 2.3.7 GINGERBREAD eng.bobzhome.20111114.211246 test-keys
ro.build.version.incremental=eng.bobzhome.20111114.211246
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Mon Nov 14 21:14:56 EST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=bobzhome
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_gelato
ro.product.device=gelato
ro.product.board=gelato
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=gelato
ro.build.description=full_gelato-eng 2.3.7 GINGERBREAD eng.bobzhome.20111114.211246 test-keys
ro.build.fingerprint=Android/full_gelato/gelato:2.3.7/GINGERBREAD/eng.bobzhome.20111114.211246:eng/test-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=normal
ro.baseband=msm
ro.carrier=VirginMobile
ro.bootloader=6170
ro.hardware=gelato
ro.revision=0
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at c7de400000000
I:Set boot command ""

Using the mount command once the phone is booted up:

$ export PATH=/data/local/bin:$PATH
$ su
# mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock6 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock7 /data yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock9 /persist yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
#

 

[Mobstergunz]

It depends if the kernel supports apps to ext which I'm not sure if Ginger kernel does..... you can also try minitool partion wizard for any east way to partion your SD card I also recommend ext2

 

[jcole20]

To be honest, I'd think Drew would be smart enough to enable A2SD at a kernel level in the slider with Gingerkernel. I'd partition via CWM if I were you. And I agree with Mobstergunz in that ext4 will put more strain on your sd because of ext4's journaling. But, in the end, sd-cards are rather inexpensive and this isn't a high dollar device. I still recommend people use CWM and just make an ext4 partition. It's simpler and in the long-run the majority of people probably wont see any strain from the ext4 partition. If you do have the know-how to format to ext2 using busybox and adb or a terminal, then by all means go with ext2.

 

[AndyOpie150]

The previously mentioned Utility...QtADB will save all the contents of the sd card, partition the sd card up to 2GB, then transfer back all the contents of the sd card. It will also allow you to pick the format of the partition to one of these: FAT32, ext.2, ext.3 and ext.4.
You must have a working CWMod recovery or a modified version. There is a lot more it will do, but in this context ^ that's all that needs mentioning.