error 17? [wont boot]

[monstercameron]

hi, I have seen having error 17 when I try to boot from a 64gb ssd through usb. I formatted it in fat32 [I tried ext3 under ubuntu but was getting filesystem errors] then I formatted in ext through the androidx86 liveusb. i used the install grub and read/write /system options but when I go to boot off this device it throughs error 17. The work around for me has been to reinstall androidx86 without formatting the ssd[keeps all user data] then use the option to boot into it at the end. is there any way to fix this? also the /system folder doesnt give me write permissions, is there a workaround for this aswell?

[Masaki Muranaka]

Hello,

Error 17 is reported by GRUB bootloader. It means GRUB is booted up but can't find linux kernel.

Your SSD may be something broken.

I recommend you to try formatting ext3 under Ubuntu as the first step.

You know, Ubuntu users are more than Android-x86 users.

So you'll find your solution out more easily if you treat this issue as Ubuntu's 

2013/8/28 monstercameron <mr.e.c...@gmail.com>

hi, I have seen having error 17 when I try to boot from a 64gb ssd through usb. I formatted it in fat32 [I tried ext3 under ubuntu but was getting filesystem errors] then I formatted in ext through the androidx86 liveusb. i used the install grub and read/write /system options but when I go to boot off this device it throughs error 17. The work around for me has been to reinstall androidx86 without formatting the ssd[keeps all user data] then use the option to boot into it at the end. is there any way to fix this? also the /system folder doesnt give me write permissions, is there a workaround for this aswell?

--
You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/groups/opt_out.

--
--
Masaki Muranaka
Monami-ya LLC, Japan.

[tue...@hotmail.com]

I have found there are problems with jb-x86 not cleanly unmounting writable filesystems at reboot/shutdown, resulting in various corruption errors (grub errors 17 and 21, ext3 invalid journal superblock etc.). I tracked the problem to platform/system/core/libcutils/android_reboot.c in the remount_ro_done() function: it is meant to ensure all block-device filesystems have been remounted as read-only (and had their block caches flushed) by comparing the names of each mounted device to "/dev/block*", but due to the way android_x86 boots the devices are mounted from /dev instead of /dev/block so they don't get matched and the reboot process doesn't wait for them to properly unmount.

[monstercameron]

I just formatted to ext3 in ubuntu, then on the install I skipped the formatting part and it seems to be ok...now for root...

[Masaki Muranaka]

Hi Monstercamereon,

> I tried ext3 under ubuntu but was getting filesystem errors

You wrote "I tried ext3 under ubuntu but was getting filesystem errors" at the first.

Which is your status? you could format your drive as ext3 on your Ubuntu, or not?

Possibly it's not caused by your drive if you could format on Ubuntu.

But reported by Tueidj or other things.

2013/8/28 monstercameron <mr.e.c...@gmail.com>

I just formatted to ext3 in ubuntu, then on the install I skipped the formatting part and it seems to be ok...now for root...

On Tuesday, August 27, 2013 6:52:10 PM UTC-4, monstercameron wrote:

hi, I have seen having error 17 when I try to boot from a 64gb ssd through usb. I formatted it in fat32 [I tried ext3 under ubuntu but was getting filesystem errors] then I formatted in ext through the androidx86 liveusb. i used the install grub and read/write /system options but when I go to boot off this device it throughs error 17. The work around for me has been to reinstall androidx86 without formatting the ssd[keeps all user data] then use the option to boot into it at the end. is there any way to fix this? also the /system folder doesnt give me write permissions, is there a workaround for this aswell?

--

You received this message because you are subscribed to the Google Groups "Android-x86" group.
To unsubscribe from this group and stop receiving emails from it, send an email to android-x86...@googlegroups.com.
To post to this group, send email to andro...@googlegroups.com.
Visit this group at http://groups.google.com/group/android-x86.
For more options, visit https://groups.google.com/groups/opt_out.

[Raymone Fagan]

I had the same issue you have to delete the partition (with a windows cd) and create the new partition with the liveusb android installation, at least thats how  i got mine to work on my MSI Windpad 110w

On Aug 27, 2013 6:52 PM, "monstercameron" <mr.e.c...@gmail.com> wrote:

hi, I have seen having error 17 when I try to boot from a 64gb ssd through usb. I formatted it in fat32 [I tried ext3 under ubuntu but was getting filesystem errors] then I formatted in ext through the androidx86 liveusb. i used the install grub and read/write /system options but when I go to boot off this device it throughs error 17. The work around for me has been to reinstall androidx86 without formatting the ssd[keeps all user data] then use the option to boot into it at the end. is there any way to fix this? also the /system folder doesnt give me write permissions, is there a workaround for this aswell?

--

[monstercameron]

I tried a few times prior but now it works, I think maybe the ext3 option on the liveusb is broken.

[tue...@hotmail.com]

The ext3 option isn't broken, the volume just isn't being unmounted cleanly. Try rebooting a few times and your drive will most likely end up with a corrupted journal. The only reason it's more likely to happen after formatting with the installer (instead of formatting with something else) is because it doesn't set a default journal data mode (writeback/ordered) and the kernel defaults to writeback.

[Masaki Muranaka]

Hello Tueidj, Monstercameron and others,

I agree with Tueidj opinion if this issue is caused by software.

I look into repos. The most suitable is adding /etc/mdev.conf and using /dev/block/.

I'm going to fix them. Stay tuned.

2013/8/29 <tue...@hotmail.com>

[Masaki Muranaka]

Hi Tueidj and Chih-Wei,
I sent a patch to new installer to this group a few minutes ago. Could
you review it?
Thanks,

2013/8/29 Masaki Muranaka <mon...@monami-ya.jp>:

[Tian Xuan Liu]

I have the same problem here.

Asus K53 Intel i5 750gb HDD

[dscm]

what tue...@hotmail.com said has been correct for me for about a year now....

anytime I get an Error 17(which is seldom now) I use my gparted USB flash drive and

format my partition(ext3) with it.....then install android-x86 BUT DO NOT FORMAT the already formatted partition.....

it corrupted as he said...remove the partition then format with something else using ext3