[Matt Devo]

Yeah, the usb drives with all my movies and music are formatted NTFS. It's weird, in XBMC for the drives that do get recognized some of the time a message will pop up saying it was mounted but it's nowhere to be found. If I reboot sometimes it'll show up then, sometimes it will just do the same thing saying it mounted the drive but it won't show up. It seems like it's similar to problems other people were having in other comments where they mentioned certain usb drives or sticks were working and others not working.

Do you know of any walkthroughs of how to reflash the rom with the method you described? Thanks for any help.

I think the issue you are having is completely unrelated to what others are seeing, but I could be wrong.

OpenELEC should actually automount NTFS drives as read-only, so if not then there's an issue somewhere. Are the drives in question USB flash drives? or external hard drives? If the latter, are they bus-powered or externally powered? USB2 or USB3?

Re-flashing the stock firmware will not let you run OpenELEC as-is, since the stock legacy BIOS/SeaBIOS is pretty hosed. You could re-flash the stock firmware, then manually update just the legacy BIOS portion (with the original fixed version from John Lewis), but even then you'd still need to re-install OpenELEC with my old custom build, as the bootloader (syslinux) included with the official OE distribution is not compatible (due to a bug in the stock firmware/SeaBIOS). And even then there's no guarantee that your drives would work, as the original SeaBIOS update didn't support USB3 drives at all.

[teki4u]

Hey guys I have an external HP my passport HDD 1tb that contain movies and it does mount all the time but now when I want to copy files from that HDD to my PC or another external HDD it stops to 0kbps after 19% or so it may vary. I have let it rest for few days to try again but same thing. Does anyone know a trick or something for it to work.

I wanted to open the thing but I couldn't , I need my 1tb of movies

[stewartgp]

Count me as another stuck on the 'Booting from Hard Disk...' stage after completing the dual boot ChromeOS/OE setup.

If it helps I set my OE partition size as 9GB, opted for a 1s boot delay defaulting to OE and was doing a completely fresh install... will try and go through it again I guess, see if it makes any difference...

[Matt Devo]

Count me as another stuck on the 'Booting from Hard Disk...' stage after completing the dual boot ChromeOS/OE setup.

If it helps I set my OE partition size as 9GB, opted for a 1s boot delay defaulting to OE and was doing a completely fresh install... will try and go through it again I guess, see if it makes any difference...

sent you a PM. Hit me up on google chat/hangouts so I can walk you thru a few things and see what's going on

[Roffy]

Count me as another stuck on the 'Booting from Hard Disk...' stage after completing the dual boot ChromeOS/OE setup.

I set partition size of 8GB, 1s boot delay defaulting to OE and was doing a completely fresh install as well.

[denrock]

I think the issue you are having is completely unrelated to what others are seeing, but I could be wrong.

OpenELEC should actually automount NTFS drives as read-only, so if not then there's an issue somewhere. Are the drives in question USB flash drives? or external hard drives? If the latter, are they bus-powered or externally powered? USB2 or USB3?

Re-flashing the stock firmware will not let you run OpenELEC as-is, since the stock legacy BIOS/SeaBIOS is pretty hosed. You could re-flash the stock firmware, then manually update just the legacy BIOS portion (with the original fixed version from John Lewis), but even then you'd still need to re-install OpenELEC with my old custom build, as the bootloader (syslinux) included with the official OE distribution is not compatible (due to a bug in the stock firmware/SeaBIOS). And even then there's no guarantee that your drives would work, as the original SeaBIOS update didn't support USB3 drives at all.

Hey Matt,

The drives I'm using are those usb external hard drives that are 1 or 2 terabytes each and powered by the usb port. I also have a powered usb hub that I use when I want to have a bunch of the drives connected at once. They're mostly USB2 drives. One of them is a USB3. The USB3 pretty much works most of the time. A couple of times it didn't show up when I turned on the system and had to reboot and then it appeared. But the USB2 drives are the problem. Some of them work some of the time and others don't work at all. I've tried them plugged directly into the chromebox and also through the powered usb hub but it's the same results. And I use all these same drives on another XBMC box I have (an android based xbmc box) and they all work fine there so something's going on with this chromebox configuration for me.

Since I don't think I'll be able to use this setup until I get all USB3 drives I just wanted to flash the stock firmware to turn this back into a regular chromebox right now, not to try to use openelec with the original firmware or anything like that. So if you know any guides for flashing the backup that your script made, let me know. Thanks.

[Kietunes]

Hi Matt,

Firstly apologies, I've tried everything I think of to sort the issue but I just haven't had any joy.

I followed the instruction in the original post, I made sure I followed the Device Prep section, downloaded & ran the script no problem.

I was then able to install the Coreboot firmware, I didn't backup a copy as I had already done so using the ChromeOS Recovery Tool.

perhaps I need to make this more clear in the OP/script. The recovery media created by the Google ChromeOS Recovery Tool will allow you to restore the ChromeBox provided you are running the stock firmware. The Recovery button operation/function is part of the stock firmware. Without it, the recovery media is useless. That's why you need to back up your stock firmware.

Now, the stock firmware is also contained within the recovery media image, but it's a bit of a pain to extract it, and it's not an exact copy since it doesn't contain your unique serial number, etc. But it's enough to get the box back running ChromeOS.

Hmm sounds like I made myself a bit of a problem by not making a copy during the installation process. Could you possibly point me in the direction of an explanation of how to extract the stock firmware from the recovery media image and/or how to reflash this?

Thanks again Matt, loving my Chromebox currently, it's so much smoother/slicker than my old HTPC

[Matt Devo]

Hmm sounds like I made myself a bit of a problem by not making a copy during the installation process. Could you possibly point me in the direction of an explanation of how to extract the stock firmware from the recovery media image and/or how to reflash this?

Thanks again Matt, loving my Chromebox currently, it's so much smoother/slicker than my old HTPC

it's not that big of a deal honestly. Extracting the stock firmware from the recovery image is a massive pain unless you're really linux savvy. I'll probably end up posting a download link and instructions in the OP at some point, not sure about integrating it into the script though. If you have OE running and are happy there's no need for it at this point anyway

[Kietunes]

Thanks,

I'm happy but considering possibly running it as a Dual Boot in the future (looking at running ChromiumOS from usb for the moment, which I presume is possible?).

I guess I just wanted to have it in the even that I do want to go back to having ChromeOS on the box itself.

I'll keep my eyes peeled for any further info

[Matt Devo]

Thanks,

I'm happy but considering possibly running it as a Dual Boot in the future (looking at running ChromiumOS from usb for the moment, which I presume is possible?).

I guess I just wanted to have it in the even that I do want to go back to having ChromeOS on the box itself.

I'll keep my eyes peeled for any further info

dual booting ChromiumOS is the easiest way, it's what I do to test script updates and/or firmware updates

[jerndl]

Matt, I ran an early version of you script a couple of week ago (before the Coreboot firmware update). So I guess I am still using the original firmware. I am using a single boot to Openelec (4.0.2). Currently I am not having any specific problems. Is there any reason I should go back a re-run your script to update the firmware? Thanks and a great job putting all this information together. So far I am very happy with the Chromebox/Openelec setup. I have a single 4TB WD MyBook external USB 3.0 drive to store my media. I went ahead and added an extra 4GB of ram (even though I don't think I needed to). I am also using this unit to serve SMB shares to 3 other XBMC "clients" and have had no trouble. I was pleasantly surprised that the Chromebox / external drive combo seem to sleep/wake automatically. So far everything is working much better that the with previous Windows 8 PC/service that was used for the same purpose.Thanks again.

Jay

[teki4u]

which version of chromium os are you using, i tried latest weekly and is not booting tried several times with a micro sdcard in a card reader, gets recognized in xubuntu but after restart or shutdown it doesnt boot from it, always boot to hard disk. What should i do. Thing is i only have a 2gb usb stick and the image is larger than that and i dont have another stick to try yet. Thanks in advance

[Matt Devo]

Matt, I ran an early version of you script a couple of week ago (before the Coreboot firmware update). So I guess I am still using the original firmware. I am using a single boot to Openelec (4.0.2). Currently I am not having any specific problems. Is there any reason I should go back a re-run your script to update the firmware?

nope, if it's working well, no reason to change it. I'm curious what you mean about sleep/wake working properly though. With the stock firmware, suspending OpenELEC will just shut it down, not actually suspend it

which version of chromium os are you using, i tried latest weekly and is not booting tried several times with a micro sdcard in a card reader, gets recognized in xubuntu but after restart or shutdown it doesnt boot from it, always boot to hard disk. What should i do. Thing is i only have a 2gb usb stick and the image is larger than that and i dont have another stick to try yet. Thanks in advance

I'm using this one: http://chromium.arnoldthebat.co.uk/daily...101.img.7z

Download the file, extract with 7zip, then use Win32diskimager to write the image to a USB or SD card. It needs to be at least 4GB.

Also, FYI, you will always see the 'Booting from Hard Disk' text even when booting from USB, as SeaBIOS only distinguishes between hard disks, floppy disks, and cd/dvdrom disks.

[Searlan]

Hey Matt, is there a significant difference between v1.1 and 2.0 of the script? I updated using v1.1 a few weeks ago, but in v2.0 the release notes said "updated Coreboot firmware".

Thanks

[Matt Devo]

Hey Matt, is there a significant difference between v1.1 and 2.0 of the script? I updated using v1.1 a few weeks ago, but in v2.0 the release notes said "updated Coreboot firmware".

Thanks

there's a big difference in the script menu/layout, but the changes to the firmware are minimal, and no need to update. If there's a major update or bug fix I'll be sure to publicize it