Incredibly long boot time

[Wolfley-Matt]

No matter which time it is starting up, the Chrome OS screen sits for several minutes before successfully loading the OS. The process I've followed several times with various images all resulting the same way. The OS functions great once it's loaded, even wake up is snappy. I'm using Eve and Caroline on a Yoga 2 Pro i7 - any other info I can provide I will.

[imperador]

Which of the three methods did you use?

[Wolfley-Matt]

Method 2 with script automation - sorry about that.

On Sat, Nov 24, 2018, 7:41 PM Cristoffer <notifications@github.com wrote:

Which of the three methods did you use?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/imperador/chromefy/issues/7#issuecomment-441410899, or mute the thread https://github.com/notifications/unsubscribe-auth/AFXCdrZuNbdjX822yKmjT-WEqxaIIlMfks5uygNxgaJpZM4YxoWW .

[imperador]

Show me your lsblk.

And also, try to generate an img for it with Method 1 and boot it from an usb stick

[Wolfley-Matt]

https://photos.app.goo.gl/3mLYp6VQKqmUZSMVA

I made /dev/sda3 larger than 4 gb to see if that mattered so that's why it's as big as it is. I didn't know what would help and what wouldn't matter. I'm trying the img generation from method 1 now.

[imperador]

On USB it took that much to boot?

[Wolfley-Matt]

I'm trying that method now, I'll report back.

On Sun, Nov 25, 2018, 1:25 PM Cristoffer <notifications@github.com wrote:

On USB it took that much to boot?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/imperador/chromefy/issues/7#issuecomment-441470054, or mute the thread https://github.com/notifications/unsubscribe-auth/AFXCdirAschVVa_OQ34feQXeSzy5tFZEks5uyvyugaJpZM4YxoWW .

[Wolfley-Matt]

Etcher tells me the image isn't bootable - chromium.img - and I've skipped warnings and it does not boot as warned. Thoughts?

**I did want to add that I was looking over the script and I noticed there were two successful completion messages - I get the message "ChromeOS installed, you can now reboot" when finishing Method 1. This could be my issue as I'm not getting the "ChromeOS image created: this is for personal use only, distribute at your own risk" message.

[imperador]

Which img are you using as recovery?

[Wolfley-Matt]

I am using eve.bin, and I grabbed the updated version of the script and it ran successfully but when I boot the image it hangs at login as if I didn't include caroline.bin even though I did add it. Boot is faster but then I'm stuck at Please Wait on login.

On Mon, Nov 26, 2018, 4:06 AM Cristoffer <notifications@github.com wrote:

Which img are you using as recovery?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/imperador/chromefy/issues/7#issuecomment-441601737, or mute the thread https://github.com/notifications/unsubscribe-auth/AFXCdtVosihX_CqbefASZiT8h0ozjQNPks5uy8svgaJpZM4YxoWW .

[imperador]

This last problem is while booting from USB? Can you access shell through CTRL + ALT + F2?

[Wolfley-Matt]

I can access shell yes, and the last problem is while booting from USB after creating the image as directed in Option 1.

[Wolfley-Matt]

imperador, I went ahead and went to a different recovery image to get past the issue with logging in. The recovery I used was samus this time. After getting through and entering shell, my installation crashes at:

Installing partition 1 to /dev/sda Installing the stateful partition... mount: wrong fs type, bad option, bad superblock on /dev/loop6, missing codepage or helper program, or other error umount: /tmp/install-mount-point: not mounted localhost /home/chronos/user #

[Wolfley-Matt]

Sorry to report back that no method works without the long boot time. I will include that, as someone else mentioned, this is an SSD and not an HDD. I have no way of doing an HDD in this machine, so I was not able to test the success of an HDD.

[djhardrich]

Running into this as well, install method 1, image made with Eve/Caroline/ATB Vanilla, all r69 running on an m3 6y30 (Skylake). Weird thing is every once in a while it will boot in less than 4 seconds, where it normally takes 2-5+ mins... This is on an m.2 SSD, feels like something is triggering a FS integrity check on boot?

[Wolfley-Matt]

I wanted to report that I was successfully able to get this working with the following combination of items:

I followed method #2. I used FydeOS as my base, and installed it to my SSD. I used samus.bin as my recovery (caroline was not needed). So far, booting is immediate and I have rebooted several times to be sure. Everything appears to be working, although Samus appears to not have Linux support yet.

I will note that no matter how I flashed eve and caroline, I was never able to log in until I went with JUST samus. It was still on v69, I will test v70 as soon as possible.

[Wolfley-Matt]

I have successfully installed v70 as well and all is working except Linux App function. The container never starts.

[imperador]

@Wolfley-Matt no luck with method 1? Even with the Grub fix?

[Wolfley-Matt]

Sadly no, not until I used FydeOS as my base did anything boot correctly.

[imperador]

Note: Problably related to the the fact that we are resizing partitions on loop devices

[imperador]

@Wolfley-Matt does it only happen with method 1?

[imperador]

Try to press CTRL + ESC + ENTER when the logo appears to see if it boots faster

[fatihbalsoy]

@imperador I have this same issue (5 minutes to boot) on my Dell Inspiron 11 3138 with v71 (eve and caroline) and, for some reason, holding the right arrow key let it boot faster (almost 5-8 seconds).

[kiwisibk]

Try to press CTRL + ESC + ENTER when the logo appears to see if it boots faster

This worked perfectly for me! Booted up in a few seconds after Google logo... Thanky you so much!!! :)

[Xelfmade]

imperador, I went ahead and went to a different recovery image to get past the issue with logging in. The recovery I used was samus this time. After getting through and entering shell, my installation crashes at:

Installing partition 1 to /dev/sda Installing the stateful partition... mount: wrong fs type, bad option, bad superblock on /dev/loop6, missing codepage or helper program, or other error umount: /tmp/install-mount-point: not mounted localhost /home/chronos/user #

I've exactly the same error with Ubuntu as base. Could you please name me the right fs type I should format my SSD?

[intdel]

Try to press CTRL + ESC + ENTER when the logo appears to see if it boots faster

This worked perfectly for me! Booted up in a few seconds after Google logo... Thanky you so much!!! :)

What exactly does the short cut do?

[downwa]

Try to press CTRL + ESC + ENTER when the logo appears to see if it boots faster

This worked perfectly for me! Booted up in a few seconds after Google logo... Thanky you so much!!! :)

What exactly does the short cut do?

For me, pressing any key, such as SHIFT, or CTRL, or even the mouse, will do the trick. I think it may be waiting to detect an input device unless some input is given.

[rockguy40]

Signed up to say, same problem ~5 min to boot, solved by ctrl esc enter. Is there a more permanent fix so I don't have to do that at every boot?

More details: lulu+caroline+latest daily Arnold the bat. (Inspiron 5378, 7th gen, crucial sata ssd). Did not happen when booting from usb. I used method #1