Page 1 of 1

Can't get thru "init"

Posted: Sat Jul 28, 2012 9:04 pm
by JoeHenley
Hi,

I'm trying to install MM 0.25.0-81b5 using PXElinux NFS boot via a server running Fedora Core 16 and Myth 0.25 (from atrpms ver 286).

I can get past the dhcp part, then screen goes blank for a few seconds. Then I get error messages ending in a "panic." It appears to be running in /tftpboot/minimyth-0.25.0-81b5/sbin/init when it occurs. The first few error messages are:
mount: none has wrong device number or fs type unionfs not supported
mkdir: can't create directory 'initrd'; read only file system
pivot-root: No such file or directory
mkdir: can't create directory '/etc/'; read only file system
Then I get a few more messages and then the panic and the trace.

Any thoughts or suggestions appreciated. Thanks!

Joe Henley

Re: Can't get thru "init"

Posted: Sun Jul 29, 2012 4:36 pm
by Pablo
Could you try with the latest MiniMyth version (81)?

How much memory for the initrd is allocated on the boot line (ramdisk_size=?)?

Re: Can't get thru "init"

Posted: Sun Jul 29, 2012 9:17 pm
by JoeHenley
Hi Pablo,

Thanks for the quick response!
How much memory for the initrd is allocated on the boot line (ramdisk_size=?)?
Ummm, I don't have a ramdisk_size parameter on my boot line. My pxelinux.cfg file has:
--------------------------- snip --------------------------------
DEFAULT minimyth-nfs
NOESCAPE 1
DISPLAY messages
# TIMEOUT 5
LABEL minimyth-nfs
KERNEL minimyth-0.25.0-81b5/kernel
APPEND ro root=/dev/nfs ip=dhcp nfsroot=192.168.1.200:/tftpboot/minimyth-0.25.0-81b5 pci=nomsi hpet=disable i8042.noaux
------------------------ sni -------------------------------
The FE has 2 GB memory.
Could you try with the latest MiniMyth version (81)?
Certainly. I'm running MythTV ver 0.25 (atrpms sub ver 286) in the BE. I can't recall the "rule" on MythTV BE/FE database versions, will 0.25 BE be OK with 0.25.2 FE?

Thanks!

Joe Henley

Re: Can't get thru "init"

Posted: Mon Jul 30, 2012 11:03 pm
by JoeHenley
Hi Pablo,

I dug around and it looked like it was OK to run a 0.25.2 BE against a 0.25 FE. So I gave it a shot; I loaded MM ver 0.25.2-81.

As before, it got past the dhcp part (and I think it gets past loading pxelinux), then the screen went blank, then a few seconds later it paniced. But the message is abit different:
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown block (2,0)
PID: 1, Comm: swapper/0 Not tainted 3.4.6 #1
Call Trace: yada yada

Thoughts, suggestions?

Thanks again for all your help!

Joe Henley

Re: Can't get thru "init"

Posted: Mon Aug 13, 2012 7:54 pm
by JoeHenley
Hi all,

My bad. Turns out that this problem stems from a typo on my part. Once I discovered and corrected it, the problem went away. Sorry for the false alarm.

Joe Henley