[Matt Devo]

Can anyone help me here.

My Chromebox wont boot it goes to a black screen and displays the following at the top left corner:

Code:

***Error in check_disks: could not repair filesystem, dropping to debug shell, try to run 'fsck' manually: ***
### Starting debugging shell... type exit to quit ###
sh: can't access tty; job control turned off
#_

Not sure what happened here.

that happened to me once with OpenELEC after an improper shutdown. I just did what it said and ran the fsck utility from the command line. Don't remember the exact parameters offhand though.

Hi Matt,

Just got my box, and your script has helped a lot. Initially I dual booted ChromeOS and Ubuntu, which worked well and was a lot of fun to play around with. Now I'm attempting to install Windows 8.

I first tried to install it after I used your script to dual boot ChromeOS and Ubuntu. I rebooted, entered legacy boot (Ctrl-L), and then hit Esc to go into SeaBIOS's boot menu and select USB boot. I then proceeded to install Windows on the whole disk (deleting all other partitions using the Windows' installer partition tool). It seemed to install successfully, copying over all the files, until it rebooted. Then I did Ctrl-L and selected boot from disc (SSD) and then Windows showed a Windows 8 BSOD (a face) and reported the error "Page Fault in a Non Paged Area" (underscores in between, don't know exact formatting). In the same line, it looked like it said something about "Display" also -- could not read it, it was too blurry. After an automatic restart, Windows boots and shows the error "The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click "OK" to restart the computer, and then restart the installation".

I then recovered ChromeOS and re-downloaded your script and did the standalone coreboot install/update (option 5) and attempted to reinstall Windows, to the exact same result. Any input on how you got Windows to install, and what this error is trying to tell me? Thanks!

sounds like you have an issue with your installation media, as I've never seen that, and I've installed Win8 on the CB a handful of times