[debian-lan-devel] Kernel panicked when trying to install mainserver from newest debian-lan iso

Franklin Weng franklin at goodhorse.idv.tw
Tue Mar 4 14:16:53 UTC 2014


2014-03-04 18:32 GMT+08:00 Andreas B. Mundt <andi.mundt at web.de>:

> Hi Franklin,
>
> On Tue, Mar 04, 2014 at 02:39:25PM +0800, Franklin Weng wrote:
> >
> > I downloaded 0302 version of debian-lan iso and used unetbootin to write
> it
> > into a USB.
> >
> > I booted with that USB and choose to install mainserver.
> >
> > However when booting the kernel panicked.  Here is the console output (I
> > key it since no screenshot could be taken)
> >
> > Begin: Running /scripts/live-realpremount ... done.
> > mount: mounting /live/medium/live/filesystem.dir on
> > /live/rootfs/filesystem.dir failed: Invalid argument
> > umount: can't umount /live/overlay: Device or resource busy
> > done.
> > Begin: Configuring fstab ... done.
> > Begin: Preconfiguring networking ... done.
> > Begin: Running /scripts/init-bottom ... done.
> > switch_root: can't execute 'sbin/init': Input/output error
> > [   6.725344] Kernel panic - not syncing: Attempted to kill init!
> > [   6.725416] Pid: 1, comm: busybox Tainted: G         C   3.2.0-4-amd64
> #1
> > Debian 3.2.54-2
> > [   6.725499] Call Trace:
> > [   6.725568]  [<ffffffff8134943b>] ? panic+0x95/0x1a2
> > [   6.725638]  [<ffffffff81049d7f>] ? do_exit+0x95/0x713
> > [   6.725705]  [<ffffffff8104a67d>] ? do_group_exit+0x74/0x9e
> > [   6.725773]  [<ffffffff8104a6b6>] ? sys_exit_group+0xf/0xf
> > [   6.725040]  [<ffffffff81354d92>] ? system_call_fastpath+0x16/0x1b
> >
> > I tried two USB drive and had the same result.
>
> Hm, I am just trying the iso image and it works fine here
> (virt-manager/kvm).  To make sure we talk about the same image:
>
> $ md5sum debian-lan_wheezy_20140302_amd64.iso
> 1538265b146d1ed4601e94c151883a92  debian-lan_wheezy_20140302_amd64.iso
>
> I am not familiar with unetbootin, could something have gone wrong
> there?  Can you try the iso without unetbootin, perhaps in a virtual
> machine?  As the panic happens right at the start, you even don't need
> to provide a virtual disk, just see if it passes where the panic
> happens and starts FAI, I just used to test:
>
>         $ kvm -cdrom debian-lan_wheezy_20140302_amd64.iso
>
> It boots fine and fails when trying to partition disks of course.
>
> Can you check if it's a hardware issue, by booting on some other machine?
> That's what comes to my mind to explore the issue, perhaps it helps.
>
> Keep us up to date if you can figure out more.
>
> Best regards,
>
>      Andi
>

Hi,


I tried some and here are the result:

1. Using the same USB stick it failed on two laptops and one PC.
2. It succeeded to boot in VirtualBox.

So I guess that there was something wrong while making bootable USB.

I'll check some more tomorrow and give you the result.


Franklin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/debian-lan-devel/attachments/20140304/cbb993dc/attachment.html>


More information about the debian-lan-devel mailing list