MD setup: no route to host

[hjklhjklhjkl]

When I attempt to netboot my md it gets stuck on the following:

/scripts/fs-premount ...
Done.
connect: No route to host
read: no route to host
read: no route to host
read: no route to host
and then it just keeps repeating.

What am I doing wrong here?  Am I missing something?

[totallymaxed]

When I attempt to netboot my md it gets stuck on the following:

/scripts/fs-premount ...
Done.
connect: No route to host
read: no route to host
read: no route to host
read: no route to host
and then it just keeps repeating.

What am I doing wrong here?  Am I missing something?

Your NIC has not been detected and is therefore not supported.

All the best

Andrew

[hjklhjklhjkl]

I am useing a brand new Intel Pro/1000 8390MT Gigabit pci network card.  Is this card really not supported, with no workaround?  If so then is there a few cards that for sure are supported gigabit cards?

[totallymaxed]

I am useing a brand new Intel Pro/1000 8390MT Gigabit pci network card.  Is this card really not supported, with no workaround?  If so then is there a few cards that for sure are supported gigabit cards?

Support for your card is not in the initramfs that is used to pxe boot an MD...see;

http://wiki.linuxmce.org/index.php/Unrecognized_NIC

http://wiki.linuxmce.org/index.php/Automatic_diskless_boot_of_media_directors#Other_Network_Cards

http://wiki.linuxmce.org/index.php/Automatic_diskless_boot_of_media_directors

The route to supporting your card below is more complex to achieve...but worth a look;

http://wiki.linuxmce.org/index.php/GRUB_PXE_network_boot

Andrew

[hjklhjklhjkl]

So is there a list of gigabit network cards that will automaticly work with no problems?  I can't seem to find any.  Thank you so much for your help.  I am new to linux and appreciate your guidance.

[colinjones]

Not really, it is all down to what is in the 0710 standard initramfs boot image, not really a LMCE thing at all. Because pretty much any NIC that has a Linux driver compatible with 0710 can be added into the initramfs image by following the first link Totallymaxed gave you, so its not really a static thing.

If you can find a Linux driver for your NIC that is compatible with 2.6.22-14 version of the kernel (the vendor's web site will tell you this info), then you can download that driver, and follow that article to rebuild the boot images (both the initial/default boot image used for an MD when the core has never seen it before, for building the initial image; and also the ongoing initramfs image used for all subsequent boots once the MD has been set up). As long as you rebuild those images, it will boot just fine with the current hardware.

Failing that, the standard boot image is just an archive file, expanded into a temporary RAM disk during boot, so I suppose you could use a tool to open that archive file, and find out what drivers are in there and choose one of those NICs... seems a lot of work though, when you could just concentrate on refreshing the archive with the required driver....

[hjklhjklhjkl]

Ok so what is the text editor in kubunu to use to modify those files?  Also, how do I untar the linux driver files and where do I put them on my core's system? 

[colinjones]

I would use joe, you need to install it though....

sudo apt-get install joe

then:

sudo joe <filename>

tar xvvf <filename>

It will untar them into a folder under the current directory. Likely they are not compiled if they are tarred, so you will need to compile them for your system... read the readme or whatever doco that comes with it. Usually it is a case of something like:

./configure
make
make install

... to compile and install them. Ideally, see if the manufacturer provides a pre-compiled installable for your architecture and kernel... that way you won't have to compile and install manually.

[hjklhjklhjkl]

ok so I am attempting to go through the steps from here:
http://wiki.linuxmce.org/index.php/Unrecognized_NIC
I got through the first step and edit, but when I get to rebuilding the initial ramdisk I get the following when I try both of the recommended steps:

File /etc/initramfs-tools-interactor/modules saved
linuxmce@dcerouter:~$ /usr/pluto/bin/Diskless_BuildDefaultImage.sh
cp: cannot create regular file `/tftpboot/default/vmlinuz': Permission denied
/usr/pluto/bin/Diskless_BuildDefaultImage.sh: line 6: mkinitramfs: command not f                             ound
/usr/pluto/bin/Diskless_BuildDefaultImage.sh: line 15: /tftpboot/pxelinux.cfg/de                             fault: Permission denied
linuxmce@dcerouter:~$ mkinitramfs -d etc/initramfs-tools-interactor/ -o /tftpboot/default/initrd
Command 'mkinitramfs' is available in '/usr/sbin/mkinitramfs'
The command could not be located because '/usr/sbin' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative priviledges associated with your user account.
bash: mkinitramfs: command not found
linuxmce@dcerouter:~$

What am I missing here?

Also, when I install the driver for the new nick, does it matter where or what directory I install it into?

[totallymaxed]

ok so I am attempting to go through the steps from here:
http://wiki.linuxmce.org/index.php/Unrecognized_NIC
I got through the first step and edit, but when I get to rebuilding the initial ramdisk I get the following when I try both of the recommended steps:

File /etc/initramfs-tools-interactor/modules saved
linuxmce@dcerouter:~$ /usr/pluto/bin/Diskless_BuildDefaultImage.sh
cp: cannot create regular file `/tftpboot/default/vmlinuz': Permission denied
/usr/pluto/bin/Diskless_BuildDefaultImage.sh: line 6: mkinitramfs: command not f                             ound
/usr/pluto/bin/Diskless_BuildDefaultImage.sh: line 15: /tftpboot/pxelinux.cfg/de                             fault: Permission denied
linuxmce@dcerouter:~$ mkinitramfs -d etc/initramfs-tools-interactor/ -o /tftpboot/default/initrd
Command 'mkinitramfs' is available in '/usr/sbin/mkinitramfs'
The command could not be located because '/usr/sbin' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative priviledges associated with your user account.
bash: mkinitramfs: command not found
linuxmce@dcerouter:~$

What am I missing here?

Also, when I install the driver for the new nick, does it matter where or what directory I install it into?

You need to follow that page very carefully... you must use the 'sudo' command otherwise you do not have correct privileges to make the changes you need to make.

Andrew

[hjklhjklhjkl]

ok, thanks!  So I am now on the last step of that page and am stuck, here is what I have done and where I am stuck:

linuxmce@dcerouter:/usr/pluto/diskless/43/etc$ cd /usr/pluto/diskless/
linuxmce@dcerouter:/usr/pluto/diskless$ chroot 43
Command 'chroot' is available in '/usr/sbin/chroot'
The command could not be located because '/usr/sbin' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative priviledges associated with your user account.
bash: chroot: command not found
linuxmce@dcerouter:/usr/pluto/diskless$ sudo /usr/sbin/chroot
/usr/sbin/chroot: missing operand
Try `/usr/sbin/chroot --help' for more information.
linuxmce@dcerouter:/usr/pluto/diskless$ sudo chroot 43
root@dcerouter:/# depmod
root@dcerouter:/# cd/boot
bash: cd/boot: No such file or directory

what am I missing now?

[UNi]

You need a space for that command:

cd /boot

You can also type "sudo -s" before you start the commands so you don't have to put sudo in front of every one.

-UNi

[hjklhjklhjkl]

ok, so I followed the steps in the following wiki page:

http://wiki.linuxmce.org/index.php/Unrecognized_NIC

It seems though that that did not solve my NIC problem on my MD.  I now get the following when I attempt to netboot my media director:

pxe-m0f: No DHCP or proxyDHCP offers were received.
PXE-M0F:  Exiting Intel Boot Agent.

Could some one help me?  I have been trying to get this MD to work for weeks now and have been held up by this NIC problem the whole time!!

[totallymaxed]

ok so I am attempting to go through the steps from here:
http://wiki.linuxmce.org/index.php/Unrecognized_NIC
I got through the first step and edit, but when I get to rebuilding the initial ramdisk I get the following when I try both of the recommended steps:

File /etc/initramfs-tools-interactor/modules saved
linuxmce@dcerouter:~$ /usr/pluto/bin/Diskless_BuildDefaultImage.sh
cp: cannot create regular file `/tftpboot/default/vmlinuz': Permission denied
/usr/pluto/bin/Diskless_BuildDefaultImage.sh: line 6: mkinitramfs: command not f                             ound
/usr/pluto/bin/Diskless_BuildDefaultImage.sh: line 15: /tftpboot/pxelinux.cfg/de                             fault: Permission denied
linuxmce@dcerouter:~$ mkinitramfs -d etc/initramfs-tools-interactor/ -o /tftpboot/default/initrd
Command 'mkinitramfs' is available in '/usr/sbin/mkinitramfs'
The command could not be located because '/usr/sbin' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative priviledges associated with your user account.
bash: mkinitramfs: command not found
linuxmce@dcerouter:~$

What am I missing here?

Also, when I install the driver for the new nick, does it matter where or what directory I install it into?

Out of interest what driver did you add to /etc/initramfs-tools-interactor/modules

If you did not add the e1000 driver then you will not get a usable initramfs for your NIC.

Andrew

[hjklhjklhjkl]

You are correct, I added the e1000 driver.  That is why I am so confused.