(2016-09-08, 05:02)Boulder Wrote: Maybe you should boot a live Linux distro from a USB stick and test if you have the same issue there. It would rule out the Chromebox hardware.

(2016-09-08, 06:37)Matt Devo Wrote:

(2016-09-08, 05:35)A2K81 Wrote: I'd be happy to. Not sure I quite know how to go about that though!

download the Ubuntu 16.04 ISO. Use Rufus (assuming using a Windows machine) to write the ISO to USB. Power off Chromebox, insert USB, power on, press ESC for boot menu when prompted, select USB device.

(2016-09-12, 02:14)Matt Devo Wrote:

(2016-09-12, 02:02)A2K81 Wrote:

(2016-09-09, 07:53)nickr Wrote: Yes, SSH into your chromebox.

I can't SSH into the chromebox when this happens, it just times out on me.

I'd really recommend booting a Linux live USB as suggested earlier to determine if hardware or software issue. Either that, or backup your exiting LE config to USB and do a Soft Reset via the LE control panel

(2016-09-12, 01:37)Matt Devo Wrote:

(2016-09-12, 01:29)samurai_k Wrote: Update, I finally was able to get to terminal using another technique. The following is what I did (as this is not documented in the wiki)

1. Boot up ChromeOS
2. Establish a network connection
3. Login as Guest
4. Hit [CTRL+ALT+T] This will launch Crosh in the browser.
5. Type in the command: Shell

This allowed me to finally get to the terminal where I could run the script...

that was going to be my next suggestion. The reason it's not documented in the wiki is because it's potentially problematic for some of the script functions, due to ChromeOS automatically mounting inserted USB/SD media. This can disrupt or cause a failure when backing up the stock firmware and/or creating the LibreELEC install media

(2016-09-12, 02:51)A2K81 Wrote: Based on my last post, do you think I should do a soft reset?

(2016-09-12, 07:38)seamus_butler Wrote: i first upgraded legacy bios using you webpage and used option 3 to put onenelec on
sd card .

the chromebox wouldnt boot via sd card.

I then tried johnlewis.ie legacy rom , still the chromebox didnt boot from sd card .

i accidentally restored origional bios by following some guide on the net.

i intended to do a bios backup , but dont know how ?

I just want it that I can try out different os by booting from sd card or usb

so where do i go from here ?

what size of donation is required ?

(2016-09-12, 08:16)seamus_butler Wrote: how do i backup bios to sd card ?

is that johnlewis.ie script any good ?

i will try it again but want to avoid bricking chromebox.

(2016-09-12, 09:35)seamus_butler Wrote: so its okay to try option 1 and a few days later option 2 with the Kodi E-Z Setup ?

thanks again.

(2016-09-13, 08:14)seamus_butler Wrote: i just want to make sure if I mess around with option 1 or 2 .......there isnt any problem
turning back system to chrome os 'triicky'

(2015-11-18, 12:08)lancastrian Wrote:

(2015-11-18, 10:56)McButton Wrote: On my Chromebox, I notice that it doesn't always keep an external drive connected. I had a 2TB that would disco then reconnect, and my 6 does now too. I've used 4 different cables and 3 of the 4 ports. All the same issue. Also, when it idles for long periods of time, upon turning the system back on, it's no longer accessible, though it is clearly on.

Any ideas? I read somewhere about the USB 3.0 having some sort of power save mode that may disconnect and not allow a reconnect. Whether it's a temp or total disconnect, a reboot always fixes it. It's pretty annoying.

I had an issue writing to a portable HDD when connected to my Chromebox's USB 3.0 ports (it would disconnect/fail mid-transfer). In the end the workaround was attaching it via a cheap USB 2.0 hub - not as quick, but it worked, suggesting the problem was USB 3.0 related.

It's a strange one, because I connected the same drive directly to my dad's Chromebox - an identical HP CB1-030na with the exact same version of OpenELEC (and even the same add-ons) - without any issues whatsoever.

Another possible option, and one I've since taken, is to attach your HDD directly to your router (or NAS if you have one) and have your Chromebox retreive the files across your network. This also means you can access the files from other devices when your Chromebox is not switched on.

(2015-11-18, 21:00)Matt Devo Wrote:

(2015-11-18, 20:48)McButton Wrote: Weird. I have a 2.0 hub, but wouldn't it still disco since it's routing through the chromebox 3.0? I have all my files on my cloud too. The drive is a backup. Cloud would be easier, but I don't want buffering. It's usually really good, but I'd rather keep it more of a stable source.

If I could access the 3.0 to ensure it always stayed live, I'd be set. I'll try the 2.0 route. It doesn't need to be faster to play my VIDS and all I transfer to it is from my laptop through the network.

No, since it forces the xhci controller into ehci/USB 2.0 mode