> Author: Andy Smith
> Date: 2015-11-11 04:38 -000
Hi Andy.
Thanks for the help, I do appreciate that Bitfolk is a service for
real geeks and that support for installations is not part of the deal.
Your support is one of the reasons why Bitfolk is special :)
> I'm sorry to see
> you're having problems. Here's an asciicast I just made of me
> installing Ubuntu 14.04 i686 on the same host that you're on:
>
> https://asciinema.org/a/ckiwp5sm75kbll77wj3r23myt
I watched the asciicast and what you did is pretty well what I did.
The main difference was the partitioning. When I did the first and
subsequent installs the partitions were already there and I just
labelled and formatted them. You deleted everything and started from
scratch.
The other difference is that for the first and last attempts I took
the LAMP and encryption options. These two installations both booted
but with error messages and I was unable to ssh into them. It is
running like that now. The installations without those options would not boot.
>
>I suspect what has happened to you is that somehow grub-pc (GrUB 2.x)
> has become installed. Only grub-legacy is supported at the moment¹,
> but the self-installer is not meant to leave you with grub-pc, so it's
> still a bug.
I hate GrUB2 :) I always had the feeling that it was designed for and
by enterprise users. On your screencast you were offered a grub boot
menu. I did not see this on mine.
> The other thing it might be is that I see you have a quite interesting
> partition layout.
I mentioned this above. I am happy to do another install deleting the
partitions and doing exactly what you did.
> broken install still exist, for me to examine?
Yes. It is running. I will not touch it until you have given me the
all clear. I am happy to give you my login details.
> Depends what "could not log in" means. :) >
I tried to ssh to the IP address and received an instant 'connection
refused'. It did not respond to ping.
The strange thing is that I just tried again, received a response to
ping and to ssh:
$ ssh zaphod@85.119.83.139
zaphod@85.119.83.139's password:
Permission denied, please try again.
I typed in the password very carefully three times and checked that
the caps lock were not on.
> You should have seen a block of text printed before the login prompt
> which tells you what the (randomly-generated) credentials are.
I did see the instructions but there was no block of text telling me
the credentials. I suspect that it disappeared because I touched
something but left the login prompt. I am not a screen user and it
took me longer than it should to escape from the login prompt :( Once
I did that I did succeed in logging in to the rescue environment.
>
> Did yours not look like that? If it did, then clearly this is still
> too confusing.
It did and it was confusing to someone who is not used to screen. I
did control + a k to kill the session but it returned to the same
login screen when I made a fresh connection. It was later that I found
contol + ] that returned me to the Xen shell. Later I saw that on the
initial screen it tells about control + ] but it was not visible when
I needed it.
> Do you have any suggestions on how to make this
> clearer?
Maybe a 'how to get out of here if your login fails' hint at the login
screen? I guess the typical Bitfolk customer would not need that sort
of help.
Thanks again.
Steve
