On 2/10/2016 11:10 AM, Ben Hutchings wrote:
> Which boot loader are you using?
Grub 2.
> diffoscope (https://try.diffoscope.org/) agrees with that.
>
> This works for me:
>
> kvm -m 1G -kernel /boot/vmlinuz-3.16.0-4-amd64 -initrd initrd.img-3.16.0-4-amd64.broken
Huh. This is only making me more confused. The .broken initrd image
consistently gives me "no cpio magic" panics.
The machine is a VirtualBox VM. Perhaps I can produce a small VM image
that reproduces the problem. Since the failure is in loading the
initrd, an image with just a /boot volume should be sufficient to
reproduce this specific failure.
> Of course the initramfs can't find your root device, but it eventually
> drops to a rescue shell. Which I can't use because... is that
> Dvorak layout?
It is.
--
Chris Howie
http://www.chrishowie.com
http://en.wikipedia.org/wiki/User:Crazycomputers
If you correspond with me on a regular basis, please read this document:
http://www.chrishowie.com/email-preferences/
PGP fingerprint: 2B7A B280 8B12 21CC 260A DF65 6FCE 505A CF83 38F5
------------------------------------------------------------------------
IMPORTANT INFORMATION/DISCLAIMER
This document should be read only by those persons to whom it is
addressed. If you have received this message it was obviously addressed
to you and therefore you can read it.
Additionally, by sending an email to ANY of my addresses or to ANY
mailing lists to which I am subscribed, whether intentionally or
accidentally, you are agreeing that I am "the intended recipient," and
that I may do whatever I wish with the contents of any message received
from you, unless a pre-existing agreement prohibits me from so doing.
This overrides any disclaimer or statement of confidentiality that may
be included on your message.
Attachment:
signature.asc
Description: OpenPGP digital signature