Source of "Installation Unsuccessful" errors

[Guest jmmL]

I get a lot of "installation unsuccessful" errors on my pulse. They are always fixed by running the repair ext option in the custom recovery image.

I would like to know:

1. The cause of these errors.
   
2. The command(s) that the repair option runs (I assume it's running fsck in some form).
   

It seems to be that each time I mount my sdcard on my PC through the pulse, that after this I will be unable to install apps properly. I have a suspicion that perhaps ubuntu isn't unmounting them correctly (although I do make sure to click "eject" in nautilus before then toggling USB on the pulse itself).

[Guest BigBearMDC]

I get the same errors too everytime i restart my Pulse.

It would be great if somebody could integrate the ext repair into the bootloader.

Greetings,

BigBearMDC

[Guest Bigsy]

Mounting/unmounting in linux/windows is fine on my pulse, but as said a reboot always needs me to repair the ext partition. Pretty annoying tbh as I like to turn it off at night.

[Guest Neron]

I get the same errors too everytime i restart my Pulse.

It would be great if somebody could integrate the ext repair into the bootloader.

Greetings,

BigBearMDC

I think we need to ask Paul to see if its possible to include in his new rom?

[Guest Jan M]

It seems to be that each time I mount my sdcard on my PC through the pulse, that after this I will be unable to install apps properly. I have a suspicion that perhaps ubuntu isn't unmounting them correctly (although I do make sure to click "eject" in nautilus before then toggling USB on the pulse itself).

i noticed this in my logcat when mounting the SD card through USB:

[ 01-08 10:45:21.367 987:0x3db W/vold ]

umount:v->mount_point = /sdcard, rc = 0, errno = 2

errno 2 is probably:

EBUSY target could not be unmounted because it is busy.

Edit: I'm not getting the installation unsuccessful error though...only if I reboot

Edited January 8, 2010 by Jan M

[Guest Casper-vH]

Always get the error after rebooting. And I almost never remember to load recovery first after my phone shut down because my battery died or whatever.

So *BUMP* because its getting annoying!

EDIT

Does this still happen in beta 1.7?

Edited January 9, 2010 by Casper-vH

[Guest jmmL]

Always get the error after rebooting. And I almost never remember to load recovery first after my phone shut down because my battery died or whatever.

So *BUMP* because its getting annoying!

EDIT

Does this still happen in beta 1.7?

Still happens in 1.7 RC1, and it's dead annoying!

I assume that "repair ext" actually runs something like

e2fsck -p

perhaps with an "-n" flag just to be safe. It would be nice if this could be run on every boot somehow, as a workaround if the root cause can't be identified. It's pretty quick and would save a lot of time rebooting and repairing.

Edited January 10, 2010 by jmmL

[Guest xangma]

Still happens in 1.7 RC1, and it's dead annoying!

I assume that "repair ext" actually runs something like

e2fsck -p

perhaps with an "-n" flag just to be safe. It would be nice if this could be run on every boot somehow, as a workaround if the root cause can't be identified. It's pretty quick and would save a lot of time rebooting and repairing.

Include it in the init.rc?

[Guest klutsh]

I cant find where I would place it inside init.rc

and is the correct command

e2fsck -p /dev/block/mmcblk0p1

Edited January 10, 2010 by klutsh

[Guest xangma]

I cant find where I would place it inside init.rc

and is the correct command

e2fsck -p /dev/block/mmcblk0p1

Init.rc launches certain scripts/services on start up. Surely e2fsck is just a script or something in the bin folder?

EDIT: In fact, it's in system/xbin .... and so is chmod. Soooooooo this means you should just chuck it in your init.rc and see what happens me thinks =]

Edited January 10, 2010 by xangma

[Guest BigBearMDC]

I pasted it between

#create WIFI filesystem structure

and

# basic network init

lets see what happens :)

Greetings,

BigBearMDC

[Guest xangma]

I pasted it between

and

lets see what happens :)

Greetings,

BigBearMDC

It has to be run before the filesystem is mounted, just by the way.

Edited January 10, 2010 by xangma

[Guest BigBearMDC]

It has to be run before the filesystem is mounted

Thanks!

Saves me a lot of trouble :)

Greetings,

BigBearMDC

[Guest xangma]

Thanks!

Saves me a lot of trouble :)

Greetings,

BigBearMDC

Yeah can't find where to put it. It just freezes on startup for me.

EDIT: Thinking about, the nandroid recovery program must have the SD card mounted (fair enough maybe not the custom made ext partition). Maybe try putting it at the end of the init.rc file? Obviously do a backup first.

Also, I found it very difficult (as in I couldn't) edit the init.rc without unpacking the boot.img and editing it through the ramdisk.

Edited January 10, 2010 by xangma

[Guest BigBearMDC]

Thats what i thought.

the SD-Card must be mounted some way...

Thats why i wanted to execute the command after the mounting operations..

Anyway im just setting up my whole Andriod developiong envoiroment so it will takes a further few minutes until i can repack the boot.img...

Greetings,

BigBearMDC