Page 1 of 1

Could not find ramdisk image: minimyth-0.23.1-75/rootfs

Posted: Thu Jan 13, 2011 7:29 am
by mx-5
I am seeing the following error during tftp boot:

Code: Select all

....
TFPT prefix: /mythtv/tftpboot/PXEClient/
Trying to load: pxelinux.cfg/default                                ok
Loading minimyth-0.23.1-75/kernel.....
Could not find ramdisk image: minimyth-0.23.1-75/rootfs
boot:
I was successfully able to load 0.23.1-73, but saw this in 0.23.1-74 but didn't bother resolving at the time.

Directory structure of -73, -74, -75 were all the same. If I include NOESCAPE 1, the sequence would repeat like this:

Code: Select all

....
TFPT prefix: /mythtv/tftpboot/PXEClient/
Trying to load: pxelinux.cfg/default                                ok
Loading minimyth-0.23.1-75/kernel.....
Could not find ramdisk image: minimyth-0.23.1-75/rootfs
Loading minimyth-0.23.1-75/kernel.....
Could not find ramdisk image: minimyth-0.23.1-75/rootfs
Loading minimyth-0.23.1-75/kernel.....
.....
Is there something that changed between -73 and -74?

Thanks.

Re: Could not find ramdisk image: minimyth-0.23.1-75/rootfs

Posted: Fri Jan 14, 2011 7:30 pm
by dgabler
Stupid question but is rootfs readable by world or by your tftp proces?

What does your tfptd log look like for requested files? (you may need to add -vv to see what is going on)
-vv gives me things like

Code: Select all

Jan 13 23:03:58 spit in.tftpd[4266]: RRQ from 192.168.2.50 filename pxelinux.cfg/01-00-1a-92-b8-df-4a 
Jan 13 23:03:58 spit in.tftpd[4266]: sending NAK (1, File not found) to 192.168.2.50
Jan 13 23:03:58 spit in.tftpd[4267]: RRQ from 192.168.2.50 filename pxelinux.cfg/C0A80232 
Jan 13 23:03:58 spit in.tftpd[4268]: RRQ from 192.168.2.50 filename ram-minimyth-0.22.0-72/kernel 
Jan 13 23:03:58 spit in.tftpd[4269]: RRQ from 192.168.2.50 filename ram-minimyth-0.22.0-72/rootfs 

Re: Could not find ramdisk image: minimyth-0.23.1-75/rootfs

Posted: Sat Jan 15, 2011 10:27 am
by mx-5
The error I saw was:

Code: Select all

Jan 12 21:52:56 mythtv atftpd[1109]: Requested file to big, increase BLKSIZE
I was using atftpd, which I subsequently found out blksize cannot be changed.

I have now switched over to tftpd and it's working fine now. Thanks!

Re: Could not find ramdisk image: minimyth-0.23.1-75/rootfs

Posted: Sat Jan 15, 2011 11:36 pm
by Pablo
I am glad you got it working.

By the way, if you are willing to jump through a few hoops, you can use HTTP rather than TFTP to transfer all the files except the bootloader (gPXE). See network boot using gPXE.

Re: Could not find ramdisk image: minimyth-0.23.1-75/rootfs

Posted: Sun Jan 16, 2011 12:53 am
by mx-5
Yes, I actually tried to resolve by jumping to gPXE because someone posted that it's faster. Spent much more time on it than I wanted, so I gave up.

Pablo, I think I read the following somewhere...
Unfortunately, there are few guides on the Internet for network boot on a network running the ISC DHCP server, running a Linux TFTP, running the Apache HTTP server and chainloading gPXE. At some point, I should write one.
;)

Re: Could not find ramdisk image: minimyth-0.23.1-75/rootfs

Posted: Fri Jan 21, 2011 4:03 am
by Pablo
mx-5 wrote:Yes, I actually tried to resolve by jumping to gPXE because someone posted that it's faster. Spent much more time on it than I wanted, so I gave up.

Pablo, I think I read the following somewhere...
Unfortunately, there are few guides on the Internet for network boot on a network running the ISC DHCP server, running a Linux TFTP, running the Apache HTTP server and chainloading gPXE. At some point, I should write one.
;)
Yes, I really should do that at some point.