[mythtv-users] kernel panic after a fresh install

[Mike Perkins]

On 19/04/14 20:00, Janusz S. Bien wrote:
> Quote/Cytat - mythtv-users-request at mythtv.org (Sat 19 Apr 2014 08:47:14 PM CEST):
>
>>
>> Message: 7
>> Date: Sat, 19 Apr 2014 09:26:21 -0400
>> From: Will Dormann <wdormann at gmail.com>
>> To: Discussion about MythTV <mythtv-users at mythtv.org>
>> Subject: Re: [mythtv-users] Mythbuntu trusty?
>> Message-ID: <5352797D.4090104 at gmail.com>
>> Content-Type: text/plain; charset=UTF-8
>>
>> On 4/19/14, 2:14 AM, Janusz S. Bien wrote:
>>> When I boot in the recovery mode, I also get the flashing LEDs but I see
>>> on the screen the end of some traceback. Should I write it down?
>>
>>
>> Yes, or just take a picture and post it online.   It's a kernel panic.
>> Could be something like bad hardware (flaky RAM - testable with
>> memtest86), or a bad driver.
>
> RAM is OK, the problem seems to be specific to the external disk used for
> Mythbuntu.
>
> The relevant message is:
>
> Failed to execute /init
> Kernel panic - not syncing: No init found
>
> I've noticed that a similar problem was reported e.g. 9 days ago
>
> http://askubuntu.com/questions/445958/unable-to-boot-ubuntu-12-04-after-new-installation
>
>
> and using Boot-Repair was recommended.
>
> I have done it but I was surprised by the question:
>
> FlexNet detected. Please backup your data before this operation. Do you want to
> continue?
>
> and I answered "No". Should I say "Yes"? I have no idea why I have FlexNet on
> this computer. Originally it came with Vista which I downgraded to XP - can this
> be the reason?
>
> The output of Boot-Repair is available at
>
> http://paste.ubuntu.com/7284541/
>
> Mythbuntu is on sdc2 (other systems on sdc have been installed when the disk was
> in a different computer, so the boot configuration is probably not valid).
>
> I will appreciate your help.
>
> Best regards
>
> Janusz
>
The flexnet messages are a pain. Basically they indicate that someone (probably 
the disk manufacturer) has placed a non-standard value in one specific byte in 
the boot sector. You can safely ignore this. There are ways of overwriting this 
value so that the message is suppressed.

-- 

Mike Perkins