(2015-06-05, 00:13)dumb1 Wrote: Hello,
First post. I tried searching but can't seem to find any topics on my issue. Installed openelec and kodi on a Asus Chromebox in a dual boot configuration. Love the setup but out of nowhere I booted the Chromebox up and get this message. "Error in check_disks: could not repair filesystem, dropping to debugging shell, try to run fsck manually Starting debugging shell... type exit to quit ### can't access tty: job control turned off." Can someone please help me repair my openelec install? I do not know linux hence the username I chose. Weird thing is i can boot to Chrome OS with no problems so somethings has to be wrong with the Openelec partition. Also not sure if this is related or not but we did have a power surge a few nights ago I don't know if that is coincidence or what. I don't know how to run that fsck command either.

Please Help and TIA!

(2015-06-05, 00:13)dumb1 Wrote: Hello,
First post. I tried searching but can't seem to find any topics on my issue. Installed openelec and kodi on a Asus Chromebox in a dual boot configuration. Love the setup but out of nowhere I booted the Chromebox up and get this message. "Error in check_disks: could not repair filesystem, dropping to debugging shell, try to run fsck manually Starting debugging shell... type exit to quit ### can't access tty: job control turned off." Can someone please help me repair my openelec install? I do not know linux hence the username I chose. Weird thing is i can boot to Chrome OS with no problems so somethings has to be wrong with the Openelec partition. Also not sure if this is related or not but we did have a power surge a few nights ago I don't know if that is coincidence or what. I don't know how to run that fsck command either.

Please Help and TIA!

Quote:OpenELEC Fails to boot:

If the OS isn't shutdown cleanly, sometimes a filesystem check (fsck) will be automatically performed. In some cases, the automatic repair is unsuccessful, and an error will show:

***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
#_


In this case, simply run fsck manually as instructed, using the following commands, hitting [enter] after each:

For a standalone setup:

fsck /dev/sda1
fsck /dev/sda2


For a dual-boot setup:

fsck /dev/sda6
fsck /dev/sda7


After the fsck is run, type 'reboot' then hit [enter] and the system should boot normally.

(2015-06-05, 03:08)Matt Devo Wrote: update 2015-06-04
------------------------------------------------------------------
- further improved dual boot / boot options menu
- tweaked fan speeds/temp thresholds for coreboot firmware for Haswell ChromeBoxes
- synchronized coreboot and SeaBIOS to latest upstream codebases

(2015-06-05, 13:04)BoxFreak Wrote:

(2015-06-05, 03:08)Matt Devo Wrote: update 2015-06-04
------------------------------------------------------------------
- further improved dual boot / boot options menu
- tweaked fan speeds/temp thresholds for coreboot firmware for Haswell ChromeBoxes
- synchronized coreboot and SeaBIOS to latest upstream codebases

Do you think this could help my noise-problem?

There´s no possibility for user to change fan -settings with coreboot?

(2015-06-06, 02:38)fvlserevere Wrote: I'm feeling curious about which bootloader is downloaded and installed onto USB?

(2015-06-06, 02:46)Matt Devo Wrote:

(2015-06-06, 02:38)fvlserevere Wrote: I'm feeling curious about which bootloader is downloaded and installed onto USB?

syslinux 5.10, since the OpenELEC default (syslinux 6.0.x) doesn't play nicely with the stock firmware; it's the same as used for a dual boot OE setup.

(2015-06-06, 11:53)magy77 Wrote: Whats the problem here?

(2015-06-06, 14:44)movie78 Wrote: Does anybody have a problem playing this file?

Click on the picture to Download