|
kvelland
|
 |
« on: March 14, 2011, 10:00:22 am » |
|
I can't find any PXE boot options in my BIOS. And can only choose from booting from CDROM or HDD.
Is there any other way to install a MD than to use a netboot. Or is it possible to netboot this computer? Another nic?
|
|
|
|
|
Logged
|
|
|
|
purps
NEEDS to work for LinuxMCE
Posts: 1269
If it ain't broke, tweak it
|
|
« Reply #1 on: March 14, 2011, 10:15:34 am » |
|
I would be surprised if that board doesn't have PXE. Check there's not an option saying "LAN" or "ROM", just enable anything that looks network related (making a note of what you have done!). If it really doesn't have PXE boot capabilities, there are other options. You can either buy a NIC that does support it, perhaps using it with a 90 degree riser if you care about MD flatness. Or, you can generate your own network boot image http://www.rom-o-matic.net/. You can use a CD, floppy, or even USB I believe. Provide a bit more information about your hardware/BIOS as well please. Cheers, Matt. |
|
|
|
|
Logged
|
|
|
|
|
posde
|
|
« Reply #2 on: March 14, 2011, 10:41:06 am » |
|
In the BIOS, go to
* Advanced
* Chipset Configuration and enable Onboard LAN
After that
* Advanced
* ACPI Configuration
* Onboard LAN power on
|
|
|
|
|
Logged
|
|
|
|
|
JoakimL
|
|
« Reply #3 on: March 14, 2011, 10:36:43 pm » |
|
I use an Asrock 330 ION as MD; PXE boot works perfectly. Remember to disable the WLAN in the BIOS.
/Joakim
|
|
|
|
|
Logged
|
|
|
|
|
|
|
kvelland
|
|
« Reply #5 on: March 15, 2011, 10:22:59 am » |
|
In the BIOS, go to
* Advanced
* Chipset Configuration and enable Onboard LAN
After that
* Advanced
* ACPI Configuration
* Onboard LAN power on
Thank you man, great description, it works |
|
|
|
|
Logged
|
|
|
|
|
kvelland
|
|
« Reply #6 on: March 15, 2011, 10:33:19 am » |
|
The first problem is solved.
This is the next one, added attachment.
The core is just default setup, I reach the core from the internal network, the DHCP server is working, there is no other DHCP server running.
Any idea
|
|
|
|
|
Logged
|
|
|
|
|
sambuca
|
|
« Reply #7 on: March 15, 2011, 11:08:57 am » |
|
Did you run /usr/pluto/bin/Diskless_CreateTBZ.sh on your core? It creates the inital boot image for MDs.
best regards,
sambuca
|
|
|
|
|
Logged
|
|
|
|
|
kvelland
|
|
« Reply #8 on: March 21, 2011, 11:53:48 am » |
|
I did it now, and it is pxe booting.
Everything looks good untill it says "we announced ourself to the router", then it runs some scripts and then:
reebooting stopping all md deveices.
Then it reboots and goes into this same loop again.
|
|
|
|
|
Logged
|
|
|
|
|
kvelland
|
|
« Reply #9 on: March 21, 2011, 12:00:17 pm » |
|
btw.. Great having this forum, help is really appreiciated
|
|
|
|
|
Logged
|
|
|
|
purps
NEEDS to work for LinuxMCE
Posts: 1269
If it ain't broke, tweak it
|
|
« Reply #10 on: March 21, 2011, 12:17:50 pm » |
|
Is it a kernel panic? Did you have to do anything to get the NIC recognized?
Cheers,
Matt.
|
|
|
|
|
Logged
|
|
|
|
|
kvelland
|
|
« Reply #11 on: March 22, 2011, 07:34:42 am » |
|
I canīt see any messages about kernel panic. The NIC did work after I just enabled it in BIOS. No additional actions.
It just restarts with the messages quoted earlier.
|
|
|
|
|
Logged
|
|
|
|
|
l3mce
|
|
« Reply #12 on: March 22, 2011, 10:21:41 am » |
|
Just out of curiosity:
1. Did you interrupt it the first time it announced itself to the router, because it just hung there and didn't seem to be doing anything? Because it was doing things.
2. In web admin under "Media Directors" did it make one (should be two there now, 1st the hybrid, and second the MD)? If not, run /usr/pluto/bin/Diskless_CreateTBZ.sh again.
If so delete it, run /usr/pluto/bin/Diskless_CreateTBZ.sh again, then boot and do not interrupt it.
|
|
|
|
|
Logged
|
I never quit... I just ping out.
|
|
|
|
kvelland
|
|
« Reply #13 on: March 22, 2011, 09:36:40 pm » |
|
I did not interupt it and it did not make an ekstra MD.
I run the /usr/pluto/bin/Diskless_CreateTBZ.sh command again.. Booted, same thing happens..
Anybody?
|
|
|
|
|
Logged
|
|
|
|
|
kvelland
|
|
« Reply #14 on: March 24, 2011, 10:51:57 pm » |
|
The weird thing is.. I just tested with another PC and everything worked fine. So the problem is with the Asrock. Any ideas?
|
|
|
|
|
Logged
|
|
|
|
|
