That machine has an option to boot from LAN you said correct? The other thing is if you are on R5F1 I think there was an issue with the diskless script if you check the wiki I think it has a link to download the newest version.

_________________
Marty

Long live Myth and Knoppmyth!!!!!

I'm using R5F27
Mobo: K7T Turbo Limited Edition
NIC: DLink 530-TX+ (I think...)

As noted, is there something I need to change on my DLink (DI-524) router?

EDIT: This is actually the second motherboard I've tried. The first was a Gigabyte GA-60XET w/a DLink D-528 nic.

_________________
"The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me

KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb

Yeah your backend is now your DHCP server (gives the ips out). If your frontend got an IP from the router then it didn't get the info where to boot from.

Sounds like both the BE and the router are doing DHCP. Disable DHCP on the router.

As for the guy not understanding installing a remote on a diskless FE:
The FE mounts it's drives from the server. It does have "drives" (it's own files) they just happen to be on another server. So you can change files and they will still exist when you reboot.

You are not running the entire system from within RAM.

Disabled DHCP on my router, re-ran the diskless frontend script. Deleted the nfsroot. Ran it again, still the same problem. It happens almost instantly, like it's not even trying to boot from the LAN...? Though, there's no disks hooked up or setup in the bios, the ONLY boot device is LAN.

DHCP was working, as my laptop still got an address.

_________________
"The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me

KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb

Ok, one step at a time.

Firstly make sure that it's actually trying to get an IP address from the DHCP on your server (backend).

/var/log/syslog on your backend will show you the details of when your frontend tries to query for an IP. Something along the lines of;



Where bart is my server name. 00:01:6c:ab:b9:08 is the MAC address of the client (frontend). 192.168.0.205 is the IP the server is giving the client.

If you don't see this before you get DISK BOOT FAILURE, then you're not quite set for booting from DHCP. Also you should see something like "PXE BOOT ROM...." right before it would normally boot up your OS.

1) Ensure you have boot method as LAN in your BIOS, and also that your BOOT ROM is enabled in your BIOS.
2) Ensure that the dhcpd3 daemon is running.

Oddly, it never says "PXE BOOT ROM...", and while I have the First Boot Device set to LAN, I can't find an option to enable BOOT ROM in the Bios.

It's an Award Bios if that matters.

This is the exact motherboard http://www.msicomputer.com/product/deta ... imited.htm

_________________
"The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me

KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb

Interesting...it appears my NICs dont' support PXE Booting...they need an optional PXE Boot Rom chip...it would seem. Now...where can i get a NIC with this.

_________________
"The amount of time needed to solve a problem is inversely proportionate to the complexity of the solution" -- Me

KM: R5.5
CPU: Athlon 3800+
Vid: nvidia 7300GT
Snd: Chaintech av-710
Tuner: PVR150
HD: 1000gb sata + 750gb sata + 500gb usb

Anytime's a good time for a motherboard upgrade!

Seriously, here is Aus it only seems the the higher end (read more expensive) PCI NIC's have this. Whereas it's standard on most (if not all) onboard NICs these days.

Is there a way to set this up while keeping my router as the DHCP server? Maybe assign static IPs to the diskless FEs? Possibly run this script, undo the DHCP part, and somehow "point" to the FEs by hardcoding their IPs?

I am a little nervous about turning off the DHCP server in my router. I Have AT&T u-verse and if I screw anything up or if my BE ever went down I would lose TV as well and then everyone would be yelling at me. But aside from this, I'd feel more comfortable leaving the router as the DHCP server, less like to 'break' etc etc.

_________________
Paul O'Flynn

If you already have another device on your network setup to do DHCP edit the knoppmyth_diskless_frontend.bash script and find the spot that has the defaults for the DHCP server settings. Insert a # in front of the allow booting line. So it will now look like this.

# allow booting;

Now the DHCP server on the Knoppmyth box will only respond to bootp or PXE boot requests not normally booting DHCP request.

_________________
Marty

Long live Myth and Knoppmyth!!!!!

I just found this on the wiki and my answer was right in there, but thanks for the prompt reply!

I'm going to assume that the script that shipped with R5F27 does not need updating, please let me know if I'm wrong. Will be trying this tomorrow morning..

Thanks,

Paul


http://www.knoppmythwiki.org/index.php? ... ssFrontend

_________________
Paul O'Flynn

Correct it does not. I meant to add that to the wiki awhile ago but just forgot to. So when I saw your post it reminded me to go add it in case anyone else has the same question.

_________________
Marty

Long live Myth and Knoppmyth!!!!!

I seem to have done something goofy to my backend. I ran the script and selected a ip range of 192.168.1.30 192.168.1.36

Now my backend takes 15 minutes to boot up. It spends the majority of its time doing IPRequests, IPDiscovery, and IPOffer. This cycle seemede to repeat about 20 times before it finally moved on. It then finished booting normally.

Any idea why it would do this?

_________________
LINHES 8.6.1 BE/FE - MSI K9N6SGM-V with AMD A64 X2 4600+, 4GB Ram. 1.5TB WD. HDHR Prime. Nvidia GT210. MCE remote.
FrontEnd - Dell Vostro 400 3.0GHz Core2Duo NVidia GeForce210. MCE Remote

I have a R5F27 backend working out of the way in a basement cabinet. The frontend is running on a Shuttle by the TV.

I used the knoppmyth_diskless_forntend.bash, and reset the Shuttle to boot over the LAN. It came right up and all seemed to work fine, except for the the MCEUSB remote control. Nothing I have tried seems to work. The only thing that I see that I question is that the USB receiver shows as Bus 001, Device 002 when diskless, and Bus 001 Device 003 when booting from the disk.

I'd like to get this working diskless (and reclaim the drive).

Any suggestions?

_________________
Charlie

have you tried to run the remove reconfigure program on the client. I don't remember the command but I think it is the upgrade instructions.

_________________
Marty

Long live Myth and Knoppmyth!!!!!