LinuxMCE Forums
General => Users => Topic started by: dcubox1 on April 28, 2010, 07:18:02 pm
-
Ok so im trying to PXE boot a windows machine....
I have followed the steps in the wiki where I take down the MAC address and add the MD in the
admin page.... However when I reboot using PXE the MD still only loads the same stuff "Unable to load..." hiw can i tell if the image is built???
Thanks
P.S. the last line on the PXE boot says:
Unable to locate configuration fileif that helps!
-
Where in the Wiki did you get those instructions? I Pxe boot one of my windows laptop every now and then for use as a mobile MD around the house (most rooms have a cat6 drop) and all i ever did/do is enable pxe booting in the bios and restarted.
Edit: To answer the question in the subject, on my system the initial boot usually takes much longer. In my opinion it takes longer than i would like for the MD's to boot in general but the initial is almost 50% longer. The MD's on my system also hangs on the initial boot, every other boot after that is fine though. IDK if I'm just to impatient but after a hard reboot during the initial boot, it boots up fine and the avwizard starts.
-
http://wiki.linuxmce.org/index.php/PXE (http://wiki.linuxmce.org/index.php/PXE)
I tried to just enable PXE boot but got nothing thats when I started looking at posts and the wiki
EDIT: From digging a bit more I believe it has something to do with the /pxelinux.cfg/default file as it fails at this step and also I do not have this file on the hybrid when i browse to that directory!!?
-
http://wiki.linuxmce.org/index.php/PXE (http://wiki.linuxmce.org/index.php/PXE)
I tried to just enable PXE boot but got nothing thats when I started looking at posts and the wiki
Which Version are you using? If you're using 0810 there's your problem...
"This step is not needed since version 7.04" and "This step is not needed since version 7.04 "
Make sure you have the diskless MD Image...or what ever it's called installed. I'll try and find the link for you but it's in the wiki. When you say "but get nothing" what does that mean? your computer tries to pxe but boots windows instead or starts booting lmce and fails??
-
Make sure you have the diskless MD Image...or what ever it's called installed. I'll try and find the link for you but it's in the wiki.
Is this what I need?:
Run '/usr/pluto/bin/Diskless_CreateTBZ.sh' on the core to created the MD image.
-
Make sure you have the diskless MD Image...or what ever it's called installed. I'll try and find the link for you but it's in the wiki.
Is this what I need?:
Run '/usr/pluto/bin/Diskless_CreateTBZ.sh' on the core to created the MD image.
sorry, i was derailed. Yes, if you're using 0810 and you installed it from the dvd then that is what you need. I couldn't pxe boot my md's until i ran that. It took a good while to complete. I have no clue how long as i was way to impatient to sit around and wait for it, but i waited for while before i left the room.
If i were you and this is a dvd install of 0810, I'd delete the md you manually added, then run this script, then try to pxe boot the md.
-
Ok so I removed the MD from the admin, ran the script( twiddled my thumbs for half an hour), reloaded the router....PXE booted the pc and it ran the diskless setup, then it restarted itself now it is stuck on the following message:
Could not find kernel image:80/vmlinuz
boot:
Any suggestions!!
Thanks for the help
Edit: I deleted the MD using the GUI and rebooted the hybrid, then tried PXE booting again, went through the same process and failed in the exact same way!!! is there something wrong with the kernel???
-
Ok so I removed the MD from the admin, ran the script( twiddled my thumbs for half an hour), reloaded the router....PXE booted the pc and it ran the diskless setup, then it restarted itself now it is stuck on the following message:
Could not find kernel image:80/vmlinuz
boot:
Any suggestions!!
Thanks for the help
Edit: I deleted the MD using the GUI and rebooted the hybrid, then tried PXE booting again, went through the same process and failed in the exact same way!!! is there something wrong with the kernel???
When you say GUI, are you talking about web admin? Did you reset the core after removing the MD?
-
Ya I ment WebAdmin not GUI sorry...Yes I deleted the MD rebooted the core, then tried PXE booting again.
The MD got assigned a differnet ID so insetad of the 80/vmlinuz it was 77/vmlinuzthat was the only difference!!
-
Still having the problem ?
check the soft links on the MD in /usr/pluto/diskless/XX where XX is the MD designation. Mine show.
initrd.img -> /usr/pluto/diskless/53/boot/initrd.img-2.6.27-14-generic
vmlinuz -> /usr/pluto/diskless/53/boot/vmlinuz-2.6.27-14-generic
You may have to manually fix if they are not pointing to the correct kernel boot files.
Everytime I generated a new MD they would point to ...27-7-generic which was wrong.
-
Ya still having the problem, thanks for the suggestion i will give it a go.
May seem like a stupid question but how do you check the kernel version?
-
initrd.img -> /usr/pluto/diskless/53/boot/initrd.img-2.6.27-14-generic
vmlinuz -> /usr/pluto/diskless/53/boot/vmlinuz-2.6.27-14-generic
You may have to manually fix if they are not pointing to the correct kernel boot files.
Everytime I generated a new MD they would point to ...27-7-generic which was wrong.
Ok so I went and checked these 2 files and they are both pointing at the correct kernel....
Tried PXE booting again(just for the fun) and still got the same crappy error :(
-
I'm all out but allow me to take a swing in the dark for a moment. Are you certain the script ran correctly ('/usr/pluto/bin/Diskless_CreateTBZ.sh')? I don't recall if sudo is required or not but i would imagine it would be. I usually just throw sudo in front of commands like that as a general practice. It maybe wrong but i still very much suck at linux... I'm tryin though. Maybe the script errored out some where and you didn't notice, that would mean you have an incomplete image. some of those commands fly past the screen. Good Luck.
-
Ya i ran that script fine, i would never of got this far otherwise...do you know if its ok to just run the script again ?
-
Ya i ran that script fine, i would never of got this far otherwise...do you know if its ok to just run the script again ?
hmm... i don't know dude. I don't see why it would break things if you ran the script again but i don't know for sure. When you run scripts like that doesn't linux just skip over parts that are already done? That's my understanding of how it works, please tell me if I'm wrong.
-
I guess it depends on the script!! I shall give it a go and see if it helps,...one things for sure, it cant make it any worse( ill prob regret them words later!!)
-
Ok so I deleted my MD re-ran
'/usr/pluto/bin/Diskless_CreateTBZ.sh this time it did not get stuck on the kernelproblem i was having but now it runs the setup script every time it boots as in it keeps looping through the setup all the time? Any suggestions!!
-
Ok so I now have a new error on the setup, it gets as far as setting up the AV Wizard and the Message is :
Failed to Setup X with no options to do anything??? is this something I can fix?
-
Reboot the MD, it worked for me.
-
Still having the problem ?
check the soft links on the MD in /usr/pluto/diskless/XX where XX is the MD designation. Mine show.
initrd.img -> /usr/pluto/diskless/53/boot/initrd.img-2.6.27-14-generic
vmlinuz -> /usr/pluto/diskless/53/boot/vmlinuz-2.6.27-14-generic
You may have to manually fix if they are not pointing to the correct kernel boot files.
Everytime I generated a new MD they would point to ...27-7-generic which was wrong.
appologies for bumping on old post but I think I have this problem
the kernel refferences in /usr/pluto/diskless/81/boot dont seem to match my installed kernel
see below
uname -r
2.6.32-02063208-generic
chris@dcerouter:/$ cd /usr/pluto/diskless/81/boot
chris@dcerouter:/usr/pluto/diskless/81/boot$ ls
abi-2.6.27-17-generic initrd.img System.map-2.6.27-17-generic vmlinuz
config-2.6.27-17-generic initrd.img-2.6.27-17-generic vmcoreinfo-2.6.27-17-generic vmlinuz-2.6.27-17-generic
could soemone please give me a step by step how to fix this?
I found a few howtos on changing sym link targets but not sure if thats the right way to fix this, I could be barking up the wrong tree
Thanks
-
what does ls -l /usr/pluto/diskless/81/boot show
-
chris@dcerouter:/usr/pluto/diskless/81/boot$ ls -l /usr/pluto/diskless/81/boot
total 26956
-rw-r--r-- 1 root root 621769 2011-04-22 19:52 abi-2.6.32-02063208-generic
drwxr-xr-x 2 root root 4096 2011-04-22 19:53 backups
-rw-r--r-- 1 root root 112095 2011-04-22 19:52 config-2.6.32-02063208-generic
-rw-r--r-- 2 root root 8479041 2011-04-22 19:52 initrd.img
-rw-r--r-- 2 root root 8479041 2011-04-22 19:52 initrd.img-2.6.32-02063208-generic
-rw-r--r-- 1 root root 1835655 2011-04-22 19:52 System.map-2.6.32-02063208-generic
-rw-r--r-- 2 root root 3999264 2011-04-22 19:52 vmlinuz
-rw-r--r-- 2 root root 3999264 2011-04-22 19:52 vmlinuz-2.6.32-02063208-generic
I've been tinkering in /usr/pluto/diskless/81/boot since my last post
- cp'd over the above files from /boot
- made new symlinks to vmlinuz and initrd.img using "sudo ln initrd.img-2.6.32-02063208-generic initrd.img"
shouldn't the output of ls -l /usr/pluto/diskless/81/boot show where the symlinks point to, did i recreate them incorrectly?
I also couldn't find an equivelant for vmcoreinfo-2.6.27-17-generic in /boot
-
Ok so I got the symbolic links in /usr/pluto/diskless/##/ and /usr/pluto/diskless/##/boot pointing to the correct kernels
I copied over the files from /boot since the correct ones werent in /usr/pluto/diskless/##/boot by default
ls -l reports the following
chris@dcerouter:/usr/pluto/diskless/120/boot$ ls -l
total 26908
-rw-r--r-- 1 root root 508481 2010-03-12 04:56 abi-2.6.27-17-generic
-rw-r--r-- 1 root root 621769 2011-04-23 18:54 abi-2.6.32-02063208-generic
-rw-r--r-- 1 root root 91462 2010-03-12 04:56 config-2.6.27-17-generic
-rw-r--r-- 1 root root 112095 2011-04-23 18:54 config-2.6.32-02063208-generic
lrwxrwxrwx 1 root root 63 2011-04-23 17:58 initrd.img -> /usr/pluto/diskless/120/boot/initrd.img-2.6.32-02063208-generic
-rw-r--r-- 1 root root 8517964 2011-04-23 17:02 initrd.img-2.6.27-17-generic
-rw-r--r-- 1 root root 8479041 2011-04-23 18:54 initrd.img-2.6.32-02063208-generic
-rw-r--r-- 1 root root 1033092 2010-03-12 04:56 System.map-2.6.27-17-generic
-rw-r--r-- 1 root root 1835655 2011-04-23 18:54 System.map-2.6.32-02063208-generic
-rw-r--r-- 1 root root 1074 2010-03-12 04:58 vmcoreinfo-2.6.27-17-generic
lrwxrwxrwx 1 root root 60 2011-04-23 17:58 vmlinuz -> /usr/pluto/diskless/120/boot/vmlinuz-2.6.32-02063208-generic
-rw-r--r-- 1 root root 2252720 2010-03-12 04:56 vmlinuz-2.6.27-17-generic
-rw-r--r-- 1 root root 3999264 2011-04-23 18:54 vmlinuz-2.6.32-02063208-generic
and in /usr/pluto/diskless/120
chris@dcerouter:/usr/pluto/diskless/120$ ls -l
total 84
drwxr-xr-x 2 root root 4096 2011-04-23 16:55 bin
drwxr-xr-x 2 root root 4096 2011-04-23 18:54 boot
drwxr-xr-x 5 root root 4096 2011-04-23 17:00 dev
drwxr-xr-x 126 root root 12288 2011-04-23 17:58 etc
drwxr-xr-x 3 root root 4096 2011-04-23 17:01 home
lrwxrwxrwx 1 root root 63 2011-04-23 18:54 initrd.img -> /usr/pluto/diskless/120/boot/initrd.img-2.6.32-02063208-generic
drwxr-xr-x 15 root root 4096 2011-04-23 16:59 lib
drwxr-xr-x 2 root root 4096 2011-04-23 17:01 media
drwxr-xr-x 3 root root 4096 2011-04-23 16:55 mnt
drwxr-xr-x 2 root root 4096 2010-09-19 10:15 opt
drwxr-xr-x 2 root root 4096 2008-10-20 13:27 proc
drwxr-xr-x 6 root root 4096 2011-04-23 17:58 root
drwxr-xr-x 2 root root 4096 2011-04-23 17:02 sbin
drwxr-xr-x 2 root root 4096 2010-09-19 10:15 srv
drwxr-xr-x 2 root root 4096 2008-10-14 14:02 sys
drwxrwxrwt 3 root root 4096 2011-04-23 17:02 tmp
drwxr-xr-x 12 root root 4096 2011-04-23 16:51 usr
drwxr-xr-x 16 root root 4096 2011-04-23 16:59 var
lrwxrwxrwx 1 root root 60 2011-04-23 18:54 vmlinuz -> /usr/pluto/diskless/120/boot/vmlinuz-2.6.32-02063208-generic
I've re ran diskless.sh, reloaded router, rebuilt media director and through webui (each time having to fix sym links), and rebooted the core but I'm still getting "could not find kernel image" error when I try to PXE boot, see pic.
Its an asus B202 if that helps, up to date bios, I haven't done the r8168 as the wiki said it wasnt needed for 0810. I#ve also checked tftpboot for symlinks but couldnt find any.
Any ideas? Please
P.S. Would it be frowned upon if I reposted this in a new thread?, not sure if this one has gone off topic