Arch Linux

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

[SOLVED] Booting into emergency mode after fresh install, incorrect...

Tl;dr: Had troubles with an arch linux installation on a chromebook. Fstab got messed up and several error messages during booting. WebReflection offered his help and script to try it that way.

Hi all,

Recently I flashed my asus c300m chromebook with John Lewis's custom rom (https://johnlewis.ie/custom-chromebook- … -download/).
I installed arch linux yesterday, but during booting it gives several error messages, finally gets to the point where it says "(1 of 3) a start job is running for dev-disk-by [...]" which runs through 1, 2 and 3 of 3 for 1m30s after which the system gets into emergency mode.

It is probably due to a problem with UUID's (googling the error gave me this clue):
*After generating fstab during the installation, the UUID values in /etc/fstab were the same as lsblk -f', but differed from blkid. Now after rebooting into emergency mode, blkid and lsblk -f give the same UUID's, but differ from /etc/fstab.

*Yesterday I changed the UUID values manually in the fstab file, following the values from blkid. This worked for the 'a start job is running' error, it also booted into non-emergency mode, but a lot of errors remained during booting. Because of the errors I decided to reinstall arch today. But the same thing occurs as yesterday, the start job error and the boot errors.

Any clue on why the UUIDs change and/or how to solve this?

Some potentially important details
-I followed the beginner's guide
-Because the payload doesn't recognize the eMMC of this device (a known bug for baytrail devices https://johnlewis.ie/baytrail-release/) , I have to put the /boot directory on a separate device (an external USB device in my case). After the kernel is loaded, it is possible to use to eMMC, so my / , /home and swap partitions are on the eMMC.

Thanks!

Last edited by tvdbarch (2015-07-28 14:22:57)

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

Apparently this problem was reported just a few days ago. Although I searched the forums I missed that one.

So please ignore this message, I'll head to the other post.

EDIT: the other post didn't give a working solution, so I'd like to continue this thread  -> see message #5

Last edited by tvdbarch (2015-07-27 13:38:48)

respiranto

Member

Registered: 2015-05-15

Posts: 479

Website

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

Could you please provide a link to the relevant thread for the case of somebody else having the same issue but finding only your thread?

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

Could you please provide a link to the relevant thread for the case of somebody else having the same issue but finding only your thread?

Sure, https://bbs.archlinux.org/viewtopic.php?id=200048

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

I cheered too early. After reading through the other post it seems to be a case which is not exactly the same. The OP there is using another script and a GPT partition table.

-The proposed solution in the other topic doesn't work:

genfstab -U -p / > /etc/fstab

The genfstab command isn't found (in emergency mode?).
Edit: Ok, I understand now that this is a script provided with the live arch boot and not some kind of bash command. The more you know...

-WebReflection's problem was caused by:

genfstab saves wrong UIDs in some EFI confguration

This brings me to my next best guess. Yesterday I changed the partition table of the eMMC and the USB flash device to GPT and back to MBR. GPT didn't work with seaBIOS, which I didn't knew and only found out after finishing the installation process. So I had to reinstall and change back to MBR.
During this second installation process I switched to another USB flash device on which I had to install /boot, because I couldn't install GRUB as it was recognizing multiple partition labels. Even though I used parted to change the partition table back to MBR. Google gave different solutions, but it mostly came down to some residue of previously used partition tables.

So my guess: there is some GPT residue left on the eMMC, which causes the wrong UUID's.
Possible solution: remove the residue and reinstall.

My question: does this seem like a reasonable guess and solution? If yes, what kind of residue is still there and how do I delete the residue?

Last edited by tvdbarch (2015-07-27 20:10:07)

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

Ok, this thread is becoming a mess now.

I rebooted the system and the error was gone. But my fstab file is empty now (why, I don't know) and only my / partition is mounted.
I'll fiddle around for some time and see what comes up.

WebReflection

Member

Registered: 2014-07-08

Posts: 106

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

installed yesterday on ASUS Chromebox with seaBIOS and specified no UEFI since apparently is not supported.

my installer went up and running quite smoothly without UUIDs problems but in other devices I had to regenerate the /etc/fstab to make it work (through the procedure you already know)

The solution in the other thread was actually to not use /etc/fstab with UEFI since my installer creates a perfectly recognized environment but this won't work for legacy boot.

There is a major difference I see though, my installer is based on Syslinux, you are using GRUB.

If you keep having hard time, you could give archibold a try

$ curl -L -O http://archibold.io/sh/archibold.sh
# be sure to pass the right disk
# if you want the bare minimum ArchLinux installation use GNOME=NO
# if you want GNOME without extras uses GNOME=NOEXTRA
$ DISK=/dev/sda UEFI=NO USER=yourname PASSWD=yourpass GNOME=NO sh archlinux.sh

By default it will create a 2GiB swap, feel free to add SWAP=0 if you don't want it, or any other value.

Without UEFI it will fully erase your disk creating optionally the SWAP partition and the rest will be an ext4 with the system.

If you'll use this installer ( and feel free to go on github to see what it does ) please let me know so I can update the list of known compatible machines ;-)

Best Regards

Last edited by WebReflection (2015-07-27 16:43:13)

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

Thanks!

The more I read your topic and the things I wrote, the more I see that I don't really understand enough, yet. Relatively new to linux etc, but learning.

I wanted to try archibold, but the problem is that I can't install the /boot partition on the internal eMMC because it is not recognized before the kernel is loaded (because this asus is a baytrail device). Because everything is automated in your script I would have to rewrite some parts.
Also tried to install the complete distro on a USB flash device, but here to there are some installation tweaks which I can't perform in the automated installation.

WebReflection

Member

Registered: 2014-07-08

Posts: 106

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

in a non UEFI gpt partitioned disk, you won't need to create a partition a part for the /boot so my script will work because the /boot is there as any other part of the disk.

That means if you have even the whole eMMC disk as ext4 partition, you can use Syslinux and boot without problems. I've used my installer on eMMC partitions too, but it looks like you are stuck with some guide that tells you you should do things in a certain way ... mind sharing that link?

I don't understand otherwise why you have a /boot recognition problem in a legacy, non UEFI, boot.

That being said, I'm not that expert neither, but I've spent quite some time figuring out how to work around gotchas here and there ... the Gizmo 2 board for instance wouldn't boot without specifying UEFI=NO EDD=NO SWAP=0 at installation time ( first bios that needed EDD to be forced to 0 )

Not sure how much I am helping, apologies if I'm rising confusion instead.

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

in a non UEFI gpt partitioned disk, you won't need to create a partition a part for the /boot so my script will work because the /boot is there as any other part of the disk.

That means if you have even the whole eMMC disk as ext4 partition, you can use Syslinux and boot without problems. I've used my installer on eMMC partitions too, but it looks like you are stuck with some guide that tells you you should do things in a certain way ... mind sharing that link?

I don't understand otherwise why you have a /boot recognition problem in a legacy, non UEFI, boot.

That being said, I'm not that expert neither, but I've spent quite some time figuring out how to work around gotchas here and there ... the Gizmo 2 board for instance wouldn't boot without specifying UEFI=NO EDD=NO SWAP=0 at installation time ( first bios that needed EDD to be forced to 0 )

Not sure how much I am helping, apologies if I'm rising confusion instead.

It seems I wasn't clear enough. It's not that during booting the /boot partition itself is not recognized but the eMMC is that which isn't recognized by seaBios. After the kernel is loaded, it is possible to access the eMMC. This issue implies that we have to boot from a separate device.
For some reason or another seaBIOS isn't able to recognize/read from the eMMC in flashed baytrail chromebooks. I'm not sure anyone understands why there is this recognition problem.
John Lewis (link) has been able to provide a fix for many chromebooks without legacy boot (link) and (link2), also (link3). But, as you can read here (link) there are some issues. One of them is the boot issue, getting sound to work isn't easy either.

So, as far as I understand, "Booting from a GPT partitioned drive is not currently supported by SeaBIOS." (source). Although elsewhere (link) it is stated that GPT and seaBios are unrelated. Maybe it is possible to use the protective MBR part of GPT to boot via seaBIOS (see first paragraph under Features). But even then, we would still have the eMMC boot problem.

Thanks for your questions and suggestions, it forces me to get my facts straight, which is great for learning.

Last edited by tvdbarch (2015-07-28 09:51:22)

WebReflection

Member

Registered: 2014-07-08

Posts: 106

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

I haven't read all of them  but in this link it's stated that eMMC won't boot. At this point I wonder if it could make sense to have your system on an SD card and mount the eMMC as extra storage space once booted from such card. Is this an option  or you really want to boot from eMMC 'cause somebody managed to do so?

In latter case I am afraid without an asus c300m there's not much I can do, except pushing (which I've done already) a  slightly modified version of my installer.
This is latest change:

# temporary hack to test boot from SD
# and system in the EMMC
# needed to be done upfront:
#   1. create a primary ext4 partition in /dev/emmcblk0
#   2. mkfs.ext4 /dev/emmcblk0p1
#   3. specify such partition before running this installer
if [ "$EXP_USE_EMMC" != "" ]; then
  sudo mount $EXP_USE_EMMC archibold
  sudo mkdir -p "archibold$SYSLINUX_ROOT"
  sudo mount $ROOT "archibold$SYSLINUX_ROOT"
else
  sudo mount $ROOT archibold
  if [ "$UEFI" != "NO" ]; then
    sudo mkdir -p "archibold$SYSLINUX_ROOT"
    sudo mount $EFI "archibold$SYSLINUX_ROOT"
  fi
fi

Basically I've modified it in a way that Syslinux will use the SD card to boot the OS, but will try to use the eMMC as disk. I have no idea if this can possibly work but it was easy to hack change.

What you need to do now is to create a partition in your eMMC and pass it through.

# find where is the eMMC
$ lsblk
# let's say it's in /dev/emmcblk0
$ fdisk /dev/emmcblk0
# to create a Linux ext4 partition of the whole disk
# press in this sequence (will erase your partition)
o
n
p
enter, enter, enter
w
q
# download my installer
$ curl -L -O http://archibold.io/sh/archibold.sh
# now try to install it via an SD card, let's say /dev/sdb
# PLEASE NOTE DISK points to the SD card while EXP_USE_EMMC should point to the **partition**
$ USER=yourname PASSWD=yourpass GNOME=NO UEFI=NO SWAP=0 DISK=/dev/sdb EXP_USE_EMMC=/dev/emmcblk0p1 sh archibold.sh

Accept and go through the installation with fingers crossed.

Please note this will erase both the SD card and the eMMC with two ext4 partitions.

If this works, we can discuss later on how to put a swap in the eMMC. If this work, you should also be capable in the future, whenever the boot from eMMC would be available, to copy /boot to a local eMMC folder, umount it, re-copy back to the eMMC the boot content,  re-generate the fstab, and live hackily ever after.

If none of this works, I'm afraid I've exhausted all my knowledge.

Best Regards

Last edited by WebReflection (2015-07-28 11:00:17)

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

...to have your system on an SD card and mount the eMMC as extra storage space once booted from such card.

This surely is a possibility. To make sure: what I do now is put / and /home on the eMMC and the /boot on a USB flash device. After booting I can remove the /boot device safely and continue to work.
SD cards also work, but seaBIOS is also picky on them. I tried the few I have at home, but neither of them worked. They just won't be listed on early startup, so I use a working usb flash device.

As far as I know, nobody managed yet to boot a non-ChromeOS distro from the eMMC on a baytrail device. And I'm completely fine with the workaround.

I'll try your modified right now. As far as I can tell this is something that should work and has worked before when I installed Fedora 22 and Linux Mint 17.2 on this device.

Edit: If I look at my previous post, there are hell of a lot links in there. Of course you didn't read them all, I just wanted to provide some more reliable sources.

Last edited by tvdbarch (2015-07-28 11:29:28)

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

I haven't read all of them  but in this link it's stated that eMMC won't boot. At this point I wonder if it could make sense to have your system on an SD card and mount the eMMC as extra storage space once booted from such card. Is this an option  or you really want to boot from eMMC 'cause somebody managed to do so?

In latter case I am afraid without an asus c300m there's not much I can do, except pushing (which I've done already) a  slightly modified version of my installer.
This is latest change:

# temporary hack to test boot from SD
# and system in the EMMC
# needed to be done upfront:
#   1. create a primary ext4 partition in /dev/emmcblk0
#   2. mkfs.ext4 /dev/emmcblk0p1
#   3. specify such partition before running this installer
if [ "$EXP_USE_EMMC" != "" ]; then
  sudo mount $EXP_USE_EMMC archibold
  sudo mkdir -p "archibold$SYSLINUX_ROOT"
  sudo mount $ROOT "archibold$SYSLINUX_ROOT"
else
  sudo mount $ROOT archibold
  if [ "$UEFI" != "NO" ]; then
    sudo mkdir -p "archibold$SYSLINUX_ROOT"
    sudo mount $EFI "archibold$SYSLINUX_ROOT"
  fi
fi

Basically I've modified it in a way that Syslinux will use the SD card to boot the OS, but will try to use the eMMC as disk. I have no idea if this can possibly work but it was easy to hack change.

What you need to do now is to create a partition in your eMMC and pass it through.

# find where is the eMMC
$ lsblk
# let's say it's in /dev/emmcblk0
$ fdisk /dev/emmcblk0
# to create a Linux ext4 partition of the whole disk
# press in this sequence (will erase your partition)
o
n
p
enter, enter, enter
w
q
# download my installer
$ curl -L -O http://archibold.io/sh/archibold.sh
# now try to install it via an SD card, let's say /dev/sdb
# PLEASE NOTE DISK points to the SD card while EXP_USE_EMMC should point to the **partition**
$ USER=yourname PASSWD=yourpass GNOME=NO UEFI=NO SWAP=0 DISK=/dev/sdb EXP_USE_EMMC=/dev/emmcblk0p1 sh archibold.sh

Accept and go through the installation with fingers crossed.

Please note this will erase both the SD card and the eMMC with two ext4 partitions.

If this works, we can discuss later on how to put a swap in the eMMC. If this work, you should also be capable in the future, whenever the boot from eMMC would be available, to copy /boot to a local eMMC folder, umount it, re-copy back to the eMMC the boot content,  re-generate the fstab, and live hackily ever after.

If none of this works, I'm afraid I've exhausted all my knowledge.

Best Regards

Update: The GNOME=NO made the installation process much faster already!

The problem is that the bootloader can't locate /boot/vmlinuz-linux (no such file or directory). I booted back into live arch and checked, vmlinuz-linux is there.
Edit: now that I think of it, this MIGHT also have been the case when I did a full install to a usb flash device yesterday. It got into the bootloader menu, but after choosing the only option available, the only thing that came up was a fancy archibold sreen. So it might be the case that it couldn't find the kernel image either but that it didn't output it to the screen.
When I check the eMMC, then I notice that there wasn't anything new written to it. So I might have done something wrong with selecting the right device, or your script goes wrong somewhere. I'll reinstall.

Last edited by tvdbarch (2015-07-28 12:02:55)

WebReflection

Member

Registered: 2014-07-08

Posts: 106

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

OK ... this is a huge step forward

fancy archibold sreen

that means the installation worked, but that syslinux/syslinux.cfg should point to / and not to /boot

try to modify that, mount the USB and sudo vi syslinux/syslinux.cfg

it should look like this (note there is no /boot)

TIMEOUT 20
PROMPT 0
DEFAULT arch

SAY
SAY
SAY
SAY
SAY
SAY
SAY
SAY
SAY
# the archibold fancy thing
SAY
SAY
SAY
SAY

LABEL arch
      LINUX /vmlinuz-linux
      INITRD /intel-ucode.img,/initramfs-linux.img
      # whatever you have here ... it's OK

If that will work is of course because if you have only the bootable USB stick available, that won't possibly work as /boot folder 'cause it hasn't been mounted yet.

I should have thought about it, apologies for any inconvenient. I will update the script to fix this issue.

Last edited by WebReflection (2015-07-28 12:10:10)

WebReflection

Member

Registered: 2014-07-08

Posts: 106

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

update I've just pushed the patched version that will look for / instead of /boot ... I am  pretty sure that will solve your problems, because you have a running Syslinux initialization from your stick, and that is already in the right disk and it's working.

You should just follow the exact same procedure you've followed before, this time archibold.sh will create the right config

Hope this helped.

Best Regards

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

OK ... this is a huge step forward

fancy archibold sreen

that means the installation worked, but that syslinux/syslinux.cfg should point to / and not to /boot

try to modify that, mount the USB and sudo vi syslinux/syslinux.cfg

it should look like this (note there is no /boot)

TIMEOUT 20
PROMPT 0
DEFAULT arch

SAY
SAY
SAY
SAY
SAY
SAY
SAY
SAY
SAY
# the archibold fancy thing
SAY
SAY
SAY
SAY

LABEL arch
      LINUX /vmlinuz-linux
      INITRD /intel-ucode.img,/initramfs-linux.img
      # whatever you have here ... it's OK

If that will work is of course because if you have only the bootable USB stick available, that won't possibly work as /boot folder 'cause it hasn't been mounted yet.

I should have thought about it, apologies for any inconvenient. I will update the script to fix this issue.

This worked. Now it's stuck at "Booting the kernel."
I was mistaken before, this is were I got stuck yesterday. I'm starting to mingle things together in my head. Although I saw that fancy screen, but where I don't remember.

WebReflection

Member

Registered: 2014-07-08

Posts: 106

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

OK, little steps ... so if you want to see what's going on you can edit syslinux/syslinux.cfg and remove quiet splash loglevel=0 console=tty2

you will be probably once again in panic mode ( after a minute and a a half, use the password you specified during installation ).

But then, with your USB-boot stick in, and verifying that your eMMC is available, you can mount the USB to the /boot folder

# mount the partition, not the entire disk
mount /dev/usbstick1 /boot

and after that

genfstab -U -p / >/etc/fstab

you can have a look there and try to understand if it looks OK ... type

reboot

and let us know

Last edited by WebReflection (2015-07-28 12:34:05)

WebReflection

Member

Registered: 2014-07-08

Posts: 106

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

watch out I copied and pasted `rw quiet splash loglevel=0 console=tty2` it shoukld have been `quiet splash loglevel=0 console=tty2` sory for the mess

WebReflection

Member

Registered: 2014-07-08

Posts: 106

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

FWIW I've actually added BOOT_LOUDLY flag in the list of configurable options and that will take care of NOT adding `quiet splash loglevel=0 console=tty2` to the config

Last edited by WebReflection (2015-07-28 12:45:18)

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

It goes a few lines further than "Booting the kernel" into a recovery shell. But it is looking for /dev/sdb1 and can't find it. Or I messed something up and it is dependent on my other usb device where the live arch iso is. But more probable is that when I ran your script the /boot usb device was named /dev/sdb1 and now sda1.
Update: I inserted both USBs but the arch-iso usb first so the /boot usb got recognized as sdb1.

Now it gives in the recovery shell the error that /sbin/init doesn't exist and that I'm on my own now. After which it continues to a black screen where it is stuck. This black screen showed up several times, completely at random the last 10 or so times I was in the recovery shell. Only way out is holding the power button for several seconds.

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

...When I check the eMMC, then I notice that there wasn't anything new written to it. So I might have done something wrong with selecting the right device, or your script goes wrong somewhere. ...

What do you think about this? Mounting the eMMC in live-arch tells me that nothing new has been written to the eMMC after the last installation with your script. Some files I created yesterday are still there.

EDIT: I think I forgot to format (mkfs.ext4 /dev/mmcblk0p1, onlly fdisk) the created partition, which would explain this.

Last edited by tvdbarch (2015-07-28 13:03:58)

WebReflection

Member

Registered: 2014-07-08

Posts: 106

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

try to follow these instructions again, there are few little changes so please read carefully ( added BOOT_LOUDLY as well )

# find where is the eMMC
$ lsblk
# let's say it's in /dev/emmcblk0
$ fdisk /dev/emmcblk0
# to create a Linux ext4 partition of the whole disk
# press in this sequence (will erase your partition)
o
n
p
enter, enter, enter
w
q

# CHANGE
# you need to format the eMMC **partition**
mkfs.ext4 /dev/emmcblk0p1
# see the p1 at the end? not sure you have just 1 or p1
# but that is the partition

# download my installer
$ curl -L -O http://archibold.io/sh/archibold.sh
# now try to install it via an SD card, let's say /dev/sdb
# PLEASE NOTE DISK points to the SD card while EXP_USE_EMMC should point to the **partition**
# CHANGE added alos BOOT_LOUDLY=1
$ BOOT_LOUDLY=1 USER=yourname PASSWD=yourpass GNOME=NO UEFI=NO SWAP=0 DISK=/dev/sdb EXP_USE_EMMC=/dev/emmcblk0p1 sh archibold.sh

Once you reach the "congratulations" part, try to write

ls archibold

where archibold is the folder with the mounted eMMC and the mounted USB

You should have the list of all archlinux files in there, and you could also verify directly if the archibold/boot/syslinux/syslinux.cfg file has the right path for the initram which is / and not /boot

just

cat  archibold/boot/syslinux/syslinux.cfg

if everything looks fine, try to reboot and tell us what happens ( you probably will need again to go to the panic mode annd regenerate the genfstab and verify it )

If nothing works again I really don't know where else could be the problem and I'd suggest to simply install everything into a USB stick

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

Right after installation, the eMMC was not mounted, the usb was mounted on /root/archibold

The syslinux.cfg file still used /boot instead of /. I changed that.
Rebooting gave again the "loading /vmlinuz-linux failed" error. So I went back into the live-arch. Now it looks like the system is completely installed on the usb device. Don't know what went wrong but it surely has something to do with the eMMC partition not being mounted. I'll reinstall.

EDIT: I changed the syslinux.cfg file back to /boot instead of / and now the system booted!

Last edited by tvdbarch (2015-07-28 13:45:48)

WebReflection

Member

Registered: 2014-07-08

Posts: 106

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

yes, if you use only the USB disk and you don't use the EXP_USE_EMMC you should have automatically the /boot folder working because everything will run from the USB stick, which is the initial suggestion.

I am very sorry I cannot help further with this, I wish I had that machine to try myself.

Best Regards

tvdbarch

Member

Registered: 2015-07-27

Posts: 18

Re: [SOLVED] Booting into emergency mode after fresh install, incorrect...

yes, if you use only the USB disk and you don't use the EXP_USE_EMMC you should have automatically the /boot folder working because everything will run from the USB stick, which is the initial suggestion.

I am very sorry I cannot help further with this, I wish I had that machine to try myself.

Best Regards

As far as I know I did use the EXP_USE_EMMC variable when calling your script.

I'm glad we've got it working on a USB device already. Yesterday that didn't work.

I'll see what I'll do from here. Thank you very much!!

EDIT: after another reinstall I have to conclude that I miss typed something before when calling your script, now everything was as planned after installation, except for booting Gets into emergency mode again and continues to the black screen.

Last edited by tvdbarch (2015-07-28 14:15:41)