Re: [bitfolk] Xen problem: can't boot after update to Debian…

Top Page
Author: John Morgan Salomon
Date:  
To: Andy Smith
CC: users
Subject: Re: [bitfolk] Xen problem: can't boot after update to Debian Wheezy

Reply to this message
gpg: Signature made Sat Jul 5 17:54:56 2014 UTC
gpg: using DSA key 60DA875FEEE04EB1
gpg: Can't check signature: No public key
Hi Andy,

thanks, that solved it (at least my Grub problems, it’s still not booting but that’s an issue with a startup script somewhere).

Much appreciated.

Best,

-John

On 5Jul 2014, at 01:32, Andy Smith <andy@???> wrote:

> Hi John,
>
> On Sat, Jul 05, 2014 at 12:32:40AM +0200, John Morgan Salomon wrote:
>> kernel     /boot/vmlinuz-3.2.0-4-686-pae root= ro 

>
> The "root=" part is not valid; it's specifying nothing for the root
> filesystem device. Your old menu.lst file probably the info you
> need. There is a line somewhere in the file that starts with:
>
> # kopt=...
>
> That is where you put such options as the "root=" business that will
> be present in every entry. update-grub reads that line and creates
> the entries from it.
>
> For example, one of my wheezy VMs has this:
>
> # kopt=root=UUID=5658a3af-0344-4bc4-8ba6-4ca2cc6cf429 ro console=hvc0
>
> The "root=" part should be the block device that has your root
> filesystem on. Yours will be either /dev/xvda or /dev/xvda1. I
> generally recommend using the UUID of the filesystem, that way if
> the device name changes then things still work.
>
> From the rescue VM you can see with
>
> $ cat /proc/partitions
>
> whether you have a partitioned disk or not (if there's an xvda1 it's
> partitioned). But I can save you some time and tell you that you
> don't. Therefore your root filesystem is on /dev/xvda.
>
> You can tell the UUID using:
>
> $ sudo tune2fs -l /dev/xvda | grep UUID
>
> but I can save you some time and tell you:
>
> Filesystem UUID:          8a67d497-9377-48b8-910e-b979c6f405e0

>
> So your kopt line should be:
>
> # kopt=root=UUID=8a67d497-9377-48b8-910e-b979c6f405e0 ro console=hvc0
>
> Once you have edited that into the file
>
> $ sudo update-grub.
>
> I suspect it will then boot.
>
> Cheers,
> Andy
>
> --
> http://bitfolk.com/ -- No-nonsense VPS hosting
> _______________________________________________
> users mailing list
> users@???
> https://lists.bitfolk.com/mailman/listinfo/users