Database Info

[Q] CyanogenMod 6.3.0 link2sd

Anyone get link2sd working with the latest CyanogenMod 6.3.0 from Moize yet?
Tried reformatting, keep running into the Mount script error.
"Mount script cannot be created.
mount: mounting/dev/block/vold/179:2 on /data/sdext2 failed: No such device"
For quick reference, it was working on Khalpower's EpicSteelBlue rom. I can't seem to get SU to run in adb shell either...
Any workarounds would be appreciated!
(I don't have enough posts to post in the main development thread yet.)

Can you run these commands (either in adb shell or terminal):
Code:
su
fdisk -l /dev/block/mmcblk0 > /sdcard/fdisk.txt
and then post the contents of /sdcard/fdisk.txt ?

I will try as soon as I get back home.
Restored my backup since I need to be heading out for now.

Back. Here are the contents of fdisk.txt.
Code:
Disk /dev/block/mmcblk0: 16.5 GB, 16574840832 bytes
255 heads, 63 sectors/track, 2015 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1689 13566861 b Win95 FAT32
/dev/block/mmcblk0p2 1690 1885 1574370 83 Linux
/dev/block/mmcblk0p3 1886 2015 1044225 82 Linux swap
The native app2ext works, but I can't enable link2sd for some reason.

Raydonn said:
Back. Here are the contents of fdisk.txt.
Code:
Disk /dev/block/mmcblk0: 16.5 GB, 16574840832 bytes
255 heads, 63 sectors/track, 2015 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1689 13566861 b Win95 FAT32
/dev/block/mmcblk0p2 1690 1885 1574370 83 Linux
/dev/block/mmcblk0p3 1886 2015 1044225 82 Linux swap
The native app2ext works, but I can't enable link2sd for some reason.
Click to expand...
Click to collapse
Can you try making an empty /sd-ext/link2sd directory and reboot? Or have you done that already?

Mioze7Ae said:
Can you try making an empty /sd-ext/link2sd directory and reboot? Or have you done that already?
Click to expand...
Click to collapse
I've tried that.
Link2sd won't recognize it for some reason on this rom.

I found some bugs in the link2sd init.d script. A hotfix can be found here:
http://forum.xda-developers.com/showpost.php?p=16757523&postcount=408

Thanks, link2sd is working now.
But there seems to be another problem I'm running into. I can't seem to get the system to mount anything but ext2.
So ext2? Link2sd and root explorer sees the sd-ext fine and reports the size, etc.
ext3 and ext 4? Unable to mount.
Perhaps there's something I'm overlooking, but I've reformatted the SD card several times now to no avail.

Try to manualy mount like:
mount /dev/block/mmcblk0p2 /sd-ext -t ext4(3) and reboot.

fjfalcon said:
Try to manualy mount like:
mount /dev/block/mmcblk0p2 /sd-ext -t ext4(3) and reboot.
Click to expand...
Click to collapse
Hmm, tried that.
Getting the error message
"mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such device" for ext3.
"mounting /dev/block/mmcblk0p2 on /sd-ext failed: Invalid argument" for ext4.

ls /system/lib | grep ext
show input...

fjfalcon said:
ls /system/lib | grep ext
show input...
Click to expand...
Click to collapse
Code:
libext2_blkid.so
libext2_com_err.so
libext2_e2p.so
libext2_profile.so
libext2_uuid.so
libext2fs.so

Are you sure that u usyng cm 6.3.0?
Cause it has already build-in modules for ext4.
http://www.multiupload.com/VHPFIMOJTR
apply that update again, you don't need to make any wipes.(or just wipe cache...)

Hmm, tried updating/installing again.
Still no luck. Same results.
Does it matter that I skipped 6.1.2 and went straight to 6.3.0? Although that doesn't make much sense since you said 6.3.0 included the modules for ext4.
I also see ext2.ko, ext3.ko, ext4.ko in system/lib/modules so I assume it's all there.

Small update.
I don't know why, but link2sd is working now and apparently with ext4.
Maybe it's because I installed cm6.1.2 and then applied cm6.3.0 overtop it? I didn't factory wipe though, but it still works.
Or maybe it's because I used the new OR to update my ext2 to ext4 instead of fresh formatting it to ext4?
Or maybe the latest version of link2sd fixed ext4 support? I don't know.
But anyhow, thanks for all the help and the great ROM.

Raydonn said:
Or maybe it's because I used the new OR to update my ext2 to ext4 instead of fresh formatting it to ext4?
Click to expand...
Click to collapse
Probably this one. The ext4 update in the OR uses known-working ext4 options. I think there are some features that desktops turn on by default when formatting ext4 that don't work with our kernel. My guess is it's largefile support, but I haven't tested tested that hunch.

A2SD, partitioning and Nand Switching (internal to external) for Optimus 3D

Please someone more experienced than me check the prosedure!!! Till I remove this line go with extreme caution
I have an enormous amount of applications inherited from the partition-able optimus 2x. I got optimus 3D as an upgrade but I couldn’t intall not even half of them. So I was trying to find ways to repartition /data as I had done with optimus 2x but with no success.
Then I got an idea... why not A2SD style? So it begins
Disclaimer: Have in mind that I’ve done nasty stuff which could brick the phone badly. I take no responsibility for breaking your phone even if you follow my guide perfectly. I am no developer and I can make mistakes so please don’t continue if you don’t understand what I am telling you to do. Also be careful since I dont know how future lg updates will react
My composition is: Thiaiz Rom V0.1, clockworkmod touch, rooted ofc and I have installed most drivers found on this forum for o3d.
Before you begin get a backup of your internal memory, sd card, titanium backup and nand backup to a pc. You WILL loose internal memory data. The rest just to be safe....
Drawbacks: Your internal memory will be around 2-3gbs smaller and wont be able to be mounted to the pc. You could brick your phone.
While all these can be done with a cwm zip script I did it manually. Also since my phone works fine know and my time is short I dont really want to go to the reformating coping restoring backups again. This means that while I write this guide I dont actually run these command only checking them if they are correct.
Lets start.
First shutdown your phone. Open it to recovery by pressing down button and power for 7-8 seconds. Release when you see LG logo. While in recovery connect your device with the pc with a usb cable. Open command prompt on your windows pc and do a
adb shell
Now you are probably ready to send commands. If not use a guide like this http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
at the shell do a
Code:
# cd /dev/block
#ls
you will see all your partitions. mmcblk0 is the internal memory and mmcblk1 is the sd card.
Code:
# parted mmcblk0
(parted) print
now you see the partitions
You should see something like this
Code:
Number Start End Size File system Name Flags
1 131kB 262kB 131kB x-loader
2 262kB 393kB 131kB nv1
3 393kB 524kB 131kB nv2
4 524kB 1049kB 524kB u-boot
5 1049kB 11.5MB 10.5MB kernel
6 11.5MB 22.0MB 10.5MB recovery
7 22.0MB 651MB 629MB ext3 system
8 651MB 1725MB 1074MB ext3 userdata
9 1725MB 1859MB 134MB fsswap
10 1859MB 1926MB 67.1MB ext3 cache
11 1926MB 1928MB 2097kB ext3 lgdrm
12 1928MB 1929MB 1049kB divxkey
13 1929MB 1950MB 21.0MB fota
14 1950MB 1955MB 4194kB ext3 misc
15 1955MB 7944MB 5989MB fat32 msftres
we are going to work on partition 15 starting by deleting it. Be very carefull here what you delete
Code:
(parted) rm 15
now we want to create 2 more partitions. The 1955-4944 and 4944-7944 will give you around 3gb for apps and 3gb for internal memory. Tweak it at your needs but always follow the numbers. I meant if your print gave you this output
Code:
15 1955MB 7945MB 2989MB fat32
use 7945 and not 7944
Code:
(parted) mkpartfs primary fat32 1955 4944
(parted) mkpartfs primary ext2 4944 7944
now the command print should give you two more partitions
Code:
15 1955MB 4944MB 2989MB fat32 msftres
16 4944MB 7944MB 3000MB ext2
quit parted to update the ext2 to ext3
Code:
(parted) quit
#mke2fs /dev/block/mmcblk0p16
#tune2fs -j /dev/block/mmcblk0p16
Now our phone is ready for A2SD. Reboot the phone.
After finish rebooting continue via adb or terminal (I used terminal because I was in a 3 hours trip with bus ) and es file explorer with root and rw options on
we need to tweak /etc/vold.fstab to change the mount points. You can change it with es file explorer
My file is:
Code:
dev_mount sdcard /mnt/sdcard auto /devices/platform/mmci-omap-hs.0/mmc_host/mmc1
dev_mount extsdcard /mnt/sdcard/_ExternalSD 15 /devices/platform/mmci-omap-hs.1/mmc_host/mmc0
then we need to create the mount point for our new partition. I did it at /mnt/a2sd but you can do it anyware including the standard /system/sd
Code:
#mkdir /mnt/a2sd
#mkdir /mnt/emmc
now we need to mout our new partition everytime the system starts. I opened /etc/init.d/thiaizSDbooster and added few lines
Code:
mkdir /mnt/a2sd
mount -w /dev/block/mmcblk0p16 /mnt/a2sd
mkdir /mnt/emmc
mount -w /dev/block/mmcblk0p15 /mnt/emmc
ln -s /mnt/a2sd/data/app /data/app
ln -s /mnt/a2sd/data/data /data/data
dont forget to make the correct permitions again after the edit
now you need to mount the new partition to your mount point
Code:
#mount -w /dev/block/mmcblk0p16 /mnt/a2sd
and copy the data files you will link there
Code:
#cp -a /data /mnt/a2sd
now careful youll delete the /data/app and /data/data from /data
Code:
#rm -r /data/app
#rm -r /data/data
and create the links
Code:
#ln -s /mnt/a2sd/data/app /data/app
#ln -s /mnt/a2sd/data/data /data/data
Reboot the phone and you are ready to go!
To mount the sd card to the pc you will need an app from market https://market.android.com/details?id=com.rafoid.multimountsdcard.widget.free
Look atached images for what you get

want to give it a try but I need to know if there is a way to revert back if anything goes wrong. Will a restore of a previous backup return things to normal?or flashing a kdz? thanx anyway.any try to improve our phones is worth praize...

jimakos29 said:
want to give it a try but I need to know if there is a way to revert back if anything goes wrong. Will a restore of a previous backup return things to normal?or flashing a kdz? thanx anyway.any try to improve our phones is worth praize...
Click to expand...
Click to collapse
Make a nand back-up in another sd card, if you re lucky and can still boot upto recovery then you can restore or you can boot to download mode. Last resort will be to flash a bin or kdz file then restore your nand back up.
I bricked my phone 5 times in one month 2 times in 1 day. I still figured how to restore, just relax and think before you do crazy stuff, all the answers are in XDA.
---------- Post added at 04:44 AM ---------- Previous post was at 03:49 AM ----------
@orlox tested it and gives me phone memory damage, forgot to pull the logs and do some ss, well anyways I won't be doing this one, I was setting up for the s2e and link2sd stuff -- that one is not that risky.

mtvtitan said:
tested it and gives me phone memory damage, forgot to pull the logs and do some ss, well anyways I won't be doing this one, I was setting up for the s2e and link2sd stuff -- that one is not that risky.
Click to expand...
Click to collapse
The "damage part" is because you probably didnt change the vold file. Its not something to worry. After you tell vold what partition to mount (15) it will be ok

orlox said:
The "damage part" is because you probably didnt change the vold file. Its not something to worry. After you tell vold what partition to mount (15) it will be ok
Click to expand...
Click to collapse
I figured that one...

have you finished the guide? all ok?

orlox said:
have you finished the guide? all ok?
Click to expand...
Click to collapse
not yet, got other stuff in hand... i'll try to report tom* its already 2am here and have work at 4am -- cooked.

I made a mistake somewhere and am stuck. Can't sleep now, I'll have to figure this thing thorough.
---------- Post added at 07:20 AM ---------- Previous post was at 07:12 AM ----------
btw you can try this --> install link2sd let it install the script needed to mount 2nd sd part, then edit it (init.d folder)
--> add this before mounting sdext2
sleep 2
mkdir /sd-ext
sleep 2
--> then after mounting sdext2 insert this
sleep 2
mount -o bind /data/sdext2 /sd-ext
-----------------------------------------
install s2e
move dl cache (dont move any apps, let link2sd do that)
reboot.
----------------------------------------------
works with thiaz boot image only
the risk is low and would not probably brick your phone but try it at your own risk (disclaimer) --> this is generic, do your mods.
any problems will discuss after I unbrick my phone lol.

Generic scripts are not working well. I was trying with dark tremors first. I think manual is safer. Also Someone may want to partition sd instead of nand. Its safer but I think its a waste of space.
The good thing is that parted works so we don't need a tool like nvflash. Also /data had a limit at 2GB I think. With a2sd there is no limit.

CWM Loop, fast support apprecciated

Hello guys,
I recently installed CWM on my GoClever device.
Booting into recovery from Android using ROM Manager didn't work, so I tried
Code:
su "echo -n boot-recovery | busybox dd of=/dev/block/nandf count=1 conv=sync; sync; reboot"
And I booted in CWM right after it rebooted
but when I tried to boot the device back to Android, it booted to CWM.
Also the CWM is unable to mount any of the directories.
Code:
CWM-based Recovery v6.0.1.2
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't mount /open/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
ADB should work I guess
Could anyone help me please? I guess it's not hard to fix this, probably some file modifying, but I don't really know what exactly to do... :/
EDIT: A recovery image that boots into Android instead of recovery would be a neat solution, but I'm not sure if it's possible
LAST EDIT [SOLVED] :
hajdulak said:
So I flashed an officcial firmware from this thread:
http://forum.xda-developers.com/showthread.php?p=36674128
Using this method:
http://www.goclever.com/manuals/update_a93_en.pdf
Didn't know the img contained a recovery image. Thank you XDA, for being helpful again
I really appreciate it
-> [SOLVED] pretty please
Click to expand...
Click to collapse
Well, i guess A13's will never get some solid support... At least I got my 10 posts... Weeee!

Guys, what's with all the views and no answers?
After some googling, I found out it's quite a frequent issue, but none of the googled threads helped in any way... Damn it...
Also, A13 devices have SOOOOO low support...
And an important thing
I got a dumped stock recovery img on the /sdcard/, just need to know if I can flash it and how to flash it using ADB, I'm quite afraid of doing anything now

Soooo...
When the device is plugged in, it identifies itself as "MID08"
Seems i installed a wrong recovery image
Now I need drivers for my TAB, as it can't appear in the
Code:
adb devices
menu... :/

If anyone can really help, this is a list of my blockdevices:
Code:
loop0 loop1 loop2 loop3 loop4 loop5 loop6 loop7 nandf ram0 ram1
And this is my fstab
Code:
/dev/block/nandh /cache ext4 rw
/dev/block/nande /data ext4 rw
/dev/block/nandi /emmc auto rw
/dev/block/nandd /system ext4 rw
/dev/block/mmcblk0p1 /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw
And this is recovery.fstab
Code:
# mount point fstype device
/boot emmc /dev/block/nandc
/cache ext4 /dev/block/nandh
/data ext4 /dev/block/nande
/emmc auto /dev/block/nandi /dev/block/nandi1
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/nandd
/recovery emmc /dev/block/nandg
Also when I try to cd to some dirs i get can't cd to XXX
I guess there's some script that does the mounting stuff, but I still don't know what it is... I just need to access my sdcard and get the recovery image outta there...

So I flashed an officcial firmware from this thread:
http://forum.xda-developers.com/showthread.php?p=36674128
Using this method:
http://www.goclever.com/manuals/update_a93_en.pdf
Didn't know the img contained a recovery image. Thank you XDA, for being helpful again
I really appreciate it

Clean Your File Systems!

Ok, lately we have had a rash of errors and undesired performance. In my opinion, this is unacceptable... So I am trying to fix it. Now, I can't fix every issue, but boy can I sure help most of them...lol
So let's get started. We will call this:
The File System Cleaner
Linux has a few tools for us to see if we have a "Dirty" or "Clean" filesystem.
They are tune2fs, e2fsck, and fsck_msdos.
Now, you can't use all of them for every file system or partition (we will refer to them all as partitions from here on out). Each one works on certain filesystems. For example, e2fsck works on ext type partitions where fsck_msdos works on vfat type partitions, and tune2fs only works on large partitions.
While tune2fs is a tool that gives detailed information about a partition, it can still give us an idea on where we stand on those larger partitions as well as change certain options/features on that partition such as journaling, mount point, mount as rw or ro, etc. But the biggest thing we are going to focus on is 1 line:
Code:
Filesystem state
If you run tune2fs and the filesystem state is anything other than clean, you have some sort of gremlin floating about it and it needs to be fixed. Now what about those partitions in which we get these errors:
t
Code:
tune2fs 1.41.11 (14-Mar-2010)
tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p4
Couldn't find valid filesystem superblock.
1|[email protected]:/ # tune2fs -l /dev/block/mmcblk0p28
tune2fs 1.41.11 (14-Mar-2010)
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0p28
Couldn't find valid filesystem superblock
It doesn't mean that they are corrupt. It means they are either not in a format that tune2fs can read or they are not a large partition.
So for those partitions that are not compatible with tune2fs, we can use fsck.
The fsck works much like scan disk and defrag in windows. It scans the partition for several different things like bad blocks, missing/corrupt information, etc. Although you can run tune2fs on any large partition whether it is mounted or not, you DO NOT want to fsck ANY partition that is mounted or it WILL result in TOTAL data LOSS! You have been warn!
Keep in mind all this information is at your own risk, but know that I have been using this for quite some time and it hasn't failed me yet. But then again, I follow my instructions to a TEE, as you should as well...
So, here's how we use all this.
First make sure you have adb installed on your computer
To be safe, boot into recovery, plug your phone into your computer and start adb shell
Now type:
Code:
mount /system
cp /system/bin/tune2fs /tmp
cp /system/bin/e2fsck /tmp
cp /system/bin/fsck_msdos /tmp
chmod -R 777 /tmp
cd tmp
Now that our tools are set, we can now begin cleaning house.
First and most important, make sure you umount ALL partitions.
I personally unmount them manually via mounts and storage in CWM.
In terminal (with adb running) type:
Code:
./tune2fs -l <partition>
./e2fsck <partition>
./fsck_msdos <partition>
**NOTE**If you have an error "/sbin/sh: <command>: not found" when executing one of these commands simply mount /system and copy to tmp, and chmod 777 again.**
For more information on the commands, run <command> -h. here you will see additional options for that command.
Now, I didn't break down which partitions work with tune2fs, but /system, /data, and /cache can be scanned with tune2fs.
However, I did break as to what partitions need which fsck command to be cleaned.
Code:
e2fsck
|mount point| |Filesystem type|
/dev/block/mmcblk0p21 /efs
/dev/block/mmcblk0p24 /system
/dev/block/mmcblk0p25 /data
/dev/block/mmcblk0p26 /cache
/dev/block/mmcblk0p27 /tombstones
/dev/block/mmcblk1p2 unknown
Code:
fsck_msdos
|mount point| |Filesystem type|
/dev/block/mmcblk0p4 fsinfo
/dev/block/mmcblk0p13 /system/etc/firmware/misc
/dev/block/mmcblk0p17 /system/etc/firmware/misc_mdm
/dev/block/mmcblk0p28 emmc
/dev/block/mmcblk1p1 /sdcard
Example:
Code:
/tmp # e2fsck /dev/block/mmcblk0p24
e2fsck 1.41.12 (17-May-2010)
/dev/block/mmcblk0p24: clean, 4220/38320 files, 93625/153088 blocks
This should resolve many of your laggy performance and random reboot issues. As well as the issue of freezes after a reboot.
If you are a flash addict, tuning your partitions between flashes my be a GREAT idea...
If you do not have those binaries in your ROM, let me know and I will upload them here...
Now, there is a little more destructive way to clean a partition, and that is to reformat it. Most of us format /system /cache and dalvik in CWM before flashing, but sometimes that isn't enough. All CWM does is erase the files/folders contained in one of those partitions.
Here's how we do a complete reformat:
Reboot to recovery, plug phone in and start adb shell
Type:
Code:
mount /system
cp /system/bin/make_ext4fs /tmp
chmod 777 /tmp/make_ext4fs
mount <system, data or cache partition>
./make_ext4fs <partition>
This only works with ext4 partitions, so use it ONLY on these:
Code:
/dev/block/mmcblk0p24 /system
/dev/block/mmcblk0p25 /data
/dev/block/mmcblk0p26 /cache
I know there are other ext partitions, like tombstone and efs, but DO NOT use this command on them. You may BRICK or damage your device. I will say this again, ONLY DO THIS on data, cache, system!
**NOTE** If you format system partition, you WILL have to flash your ROM and Gapps again...

I have not had windows on this pc for over 2 years now and I think ADB is MS only right? I do flash a lot but I normally run ultimate kernel cleaning script and plus run the wipes a couple times myself and sumtimes format cache partitons before I install a new rom.... I like to make sure I do most I can to clean before I flash...and I always run the LZ kernel Cause its AWESOME!! but I guess my question is how can I look to see if my partitons need to be cleaned.. on AOKP with LZ kernel at moment and it is smooth fast and no bugs or reboots. is there a way to vew the partitions with ubuntu 12.04? or dose ubuntu even need ADB... linux seems very good at haveing the right drivers and software already available without installing to many extras.
not even sure your a linux desktop user but thought I would go ahead and ask.
Many thanks for everything

woodyjlw said:
I have not had windows on this pc for over 2 years now and I think ADB is MS only right? I do flash a lot but I normally run ultimate kernel cleaning script and plus run the wipes a couple times myself and sumtimes format cache partitons before I install a new rom.... I like to make sure I do most I can to clean before I flash...and I always run the LZ kernel Cause its AWESOME!! but I guess my question is how can I look to see if my partitons need to be cleaned.. on AOKP with LZ kernel at moment and it is smooth fast and no bugs or reboots. is there a way to vew the partitions with ubuntu 12.04? or dose ubuntu even need ADB... linux seems very good at haveing the right drivers and software already available without installing to many extras.
not even sure your a linux desktop user but thought I would go ahead and ask.
Many thanks for everything
Click to expand...
Click to collapse
Yeah, I'm completely windows free too...YAY! lol
You still need to install the adb binary/command and put it in your path. The good news is, it's very simple in Linux, unlike wincrapdows...
And then just follow the tutorial to check your partitions...

[Q] Adb shell/terminal

what exactly does adb shell mount do?
Edit: When I input
mount -t ext4 /dev/block/mmcblk0p25 /data
I get the output
mount: Invalid argument
Edit: I made a new ext2 filesystem in mmcblk0p25, how can I mount it?

Syreth said:
what exactly does adb shell mount do?
Click to expand...
Click to collapse
It allows you to mount partions on your phone such as /system so you can edit stuff in that partion (that's why I read)

A_Bunny said:
It allows you to mount partions on your phone such as /system so you can edit stuff in that partion (that's why I read)
Click to expand...
Click to collapse
I tried to mount -t ext4 dev/block/mmcblk0p25 /data and I got mount: Invalid arguement...

probably you should check your filesystem mmcblk0p25
>if it doesnt exist, create one using mkfs
>if it is corrupted, check & repair it using fsck

samsungrockz said:
probably you should check your filesystem mmcblk0p25
>if it doesnt exist, create one using mkfs
>if it is corrupted, check & repair it using fsck
Click to expand...
Click to collapse
I don't have those commands..

Nevermind, I have e2fsck, but e2fsck -pcfv /dev/block/mmcblk0p25 gives the output
e2fsck -pcfv /dev/block/mmcblk0p25
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
25
/dev/block/mmcblk0p25:
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>.

EDIT