Hello Everyone,
I'm having some trouble booting MDs in 810.
The diskless setup script runs & creates the MD correctly, MD reboots, installs needed packages etc.
But the problem starts when the boot process gets to "Starting periodic command scheduler crond [OK]"
It doesn't go any further, no matter how long I leave it.
I have tried booting 4 MD candidate PCs, 2 of which worked with 710.
Any suggestions would be greatly appreciated.
Regards,
Josh
Hi,
Did you ever get this solved?
I'm having the same problem on the latest Alpha2 Release of 810.
Changed the Architecture to i386, rebuilt the image.
MD Boots fine, but then hangs at starting cron.
Any help or pointers would be appreciated.
P.S. MD System is Zotac GeForce 9300 board.
Cheers,
Quote from: filberuk on August 24, 2009, 11:53:23 AM
Hi,
Did you ever get this solved?
I'm having the same problem on the latest Alpha2 Release of 810.
Changed the Architecture to i386, rebuilt the image.
MD Boots fine, but then hangs at starting cron.
Any help or pointers would be appreciated.
P.S. MD System is Zotac GeForce 9300 board.
Cheers,
are you using the Zotac 230?
Hi Guys,
Any resolution to this? I am getting the same problem with 2 EPIA boards, and one kt3 ultra/nvidia 5500, all three worked with 7.10. I started a post here: http://forum.linuxmce.org/index.php?topic=8835.0 but haven't gotten much farther.
DoTheDog
I had an issue this morning adding a new MD to my setup, I created trac ticket http://trac.linuxmce.org/trac.cgi/ticket/333 on my issue. Not sure it's the exact same problem as described above but check it out to see if it helps.
Anyone have any ideas on this, its the only thing keeping me from using the system now.
A couple of people had suggested it was the video card causing this problem.
Today I purchased a 9400GT & tried that, but it made no difference.
Also did a clean install of the core.
lemming,
Any resolution on this? The other thing I am seeing is that when it stops at "Starting crond" I can ctl-alt-F2 to a tty, I can input a user but it never prompts for a password. Are you getting this as well? I also saw that WhateverFits seems to be having the same issue (http://forum.linuxmce.org/index.php?topic=8757.msg59297#msg59297) though I couldn't find a post for any resolution. This is driving me a little crazy... Please post if you get anywhere.
Thanks,
DotheDog
No Solution yet.
Yes, I'm having the same problem you are on every PC I've tried as an MD.
Hi,
Are you running nvidia cards in each MD?
When you look at the xorg.conf (from the core at /usr/pluto/diskless/XX/etc/X11) are you using nvidia, nv or vesa as the driver?
I'm running 8600GT cards in all.
I bought a 9400GT to see if that helped.
They are using the nvidia driver, out of curiosity I changed to vesa, didn't help.
Hi,
Was your Core running 180.11 when you set up the MD's? KDE Desktop.Applications>Settings open NVIDIA X Server Settings.
I will have a look when I get home, but its running whatever is included in the latest alpha
Hi,
O.K. two things then...
Did you try nv as the driver - you tried vesa...
...and did you set the hardware driver up for the video card to run the 180.11 driver back in Kubuntu before you installed LMCE?
That's what I normally do.
Hi Guys
I got two new ION and I had endless problems with My MD's For some reason the core just install the 180.11 driver..
I had to go and remove the driver like atp-get remove nvidia-glx-* and also removed the nvidia-180- restricted drivers.
Than after that I installed the Nvidia driver that I downloaded.. I had to reset my root password on the MD and then telinit 3 and then sh NVIDIA.........
this gave me a "X Failed to start" and all I did is created an xorg.conf file and bam everything worked..
I don't know if this will help any of you but it help me..
Chris
I haven't tried that, I will try it when I get home, thanks.
So which should they use nv or nvidia?
Hi,
The driver should be nvidia for your video cards but if you have an older version (96 legacy) loaded you would run nv.
If the 180.11 is running in the NVIDIA X server settings you might need to try installing the 185 variant of the drivers.
lemming86_au,
Did the video driver make a difference? I have had 3 different motherboards not start with the same symptoms (kt3 ultra/e1000/gf8500, via epia, atom330/rtl8111c/i945). I have actually gotten it past the starting chrond but now it is hanging at starting NIS services. Please post if you get past this.
DoTheDog
I had what appears to be the same problem. If you hit Control-F12 (IIRC) then you get a list of recent messages from the system. The very last one I get is about the network card changing state. Network cards changing their connection state on a network boot is not a good thing. I got this when I updated my media director and it pulled some update from Ubuntu that broke this for me. I'm still trying to figure out what package.
Whateverfits,
Did you ever get it figured out? I actually got an atom330 board to run. But when I tried to get the second one running I end up getting this:
Oct 1 21:55:01 moon61 NetworkManager: <info> (eth0): carrier now ON (device state 1)
Oct 1 21:55:01 moon61 nm-system-settings: SCPlugin-Ifupdown: init!
Oct 1 21:55:01 moon61 anacron[6353]: Jobs will be executed sequentially
Oct 1 21:55:01 moon61 kernel: [ 0.905038] domain 0: span 1,3 level SIBLING
Oct 1 21:55:01 moon61 nm-system-settings: SCPlugin-Ifupdown: update_system_hostname
Oct 1 21:55:01 moon61 kernel: [ 0.905043] groups: 3 1
Oct 1 21:55:01 moon61 kernel: [ 0.905050] domain 1: span 0-3 level CPU
Oct 1 21:55:02 moon61 nm-system-settings: SCPluginIfupdown: guessed connection type (eth0) = 802-3-ethernet
Oct 1 21:55:02 moon61 kernel: [ 0.905055] groups: 1,3 0,2
Oct 1 21:55:02 moon61 kernel: [ 0.905284] net_namespace: 840 bytes
Oct 1 21:55:02 moon61 kernel: [ 0.905284] Booting paravirtualized kernel on bare hardware
Oct 1 21:55:02 moon61 kernel: [ 0.905284] Time: 21:52:58 Date: 10/01/09
Oct 1 21:55:02 moon61 nm-system-settings: SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, autoconnect:0, id:Ifupdown (eth0), uuid: 681b428f-0000-0000-0000-000039000000
Oct 1 21:55:02 moon61 kernel: [ 0.905284] NET: Registered protocol family 16
Oct 1 21:55:02 moon61 nm-system-settings: SCPlugin-Ifupdown: addresses count: 1
Oct 1 21:55:02 moon61 kernel: [ 0.908120] EISA bus registered
Oct 1 21:55:02 moon61 nm-system-settings: SCPlugin-Ifupdown: No dns-nameserver configured in /etc/network/interfaces
Oct 1 21:55:02 moon61 kernel: [ 0.908123] ACPI: bus type pci registered
Oct 1 21:55:02 moon61 nm-system-settings: SCPlugin-Ifupdown: autoconnect
Oct 1 21:55:02 moon61 kernel: [ 0.908203] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory Controller Hub without MMCONFIG support.
Oct 1 21:55:02 moon61 nm-system-settings: SCPluginIfupdown: management mode: unmanaged
Oct 1 21:55:03 moon61 kernel: [ 0.910017] PCI: Using configuration type 1 for base access
Oct 1 21:55:03 moon61 kernel: [ 0.916547] ACPI: EC: Look up EC in DSDT
Oct 1 21:55:03 moon61 nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/net_00_1c_c0_c9_2b_e3, iface: eth0): well known
Oct 1 21:55:03 moon61 /USR/SBIN/CRON[6582]: (root) CMD (/usr/sbin/ntpdate dcerouter &>/dev/null)
Oct 1 21:55:03 moon61 kernel: [ 0.923568] ACPI: Interpreter enabled
Oct 1 21:55:03 moon61 nm-system-settings: Ifupdown: get unmanaged devices count: 1
Oct 1 21:55:03 moon61 kernel: [ 0.923623] ACPI: (supports S0 S1 S3 S4 S5)
Oct 1 21:55:03 moon61 nm-system-settings: SCPlugin-Ifupdown: (153420008) ... get_connections.
Oct 1 21:55:03 moon61 NetworkManager: <info> (eth0): device state change: 1 -> 2
Oct 1 21:55:03 moon61 kernel: [ 0.923817] ACPI: Using IOAPIC for interrupt routing
I believe that is the same "state change" you mention in your previous post? I really wish I knew what the voodoo magic to get this to boot is. The funny thing is, the one that actually boots (exact same atom 330 board) won't boot consistently, it usually boots up on the second or third try...
I have tried compiling the latest r8168 driver from realtek (it uses it for boot), added Driver "intel" to my xorg.conf file (its an intel i945), added dns-nameserver 192.168.80.1 to /etc/network/interfaces (because it complained about that), changed architecture from amd64 to i386, and none of it seems to help. If you have had any progress please let me know.
Thanks,
DoTheDog
<info> (eth0): device state change: 1 -> 2
Yeah, that looks familiar. No, I never figured it out since I got it working, updated just the pluto/linuxmce stuff, ignored the core Ubuntu updates, and all is working then I started back to college and have had no time to monkey with it. I'll probably have LOTS of time in December between semesters to test this out and get more detail. My current belief is it was one of the packages (from Ubuntu, not linuxmce) that has to do with the networking stack, not the drivers or kernel itself. I upgraded all my packages except the kernel once and still got the problem.
I have a large list to go through and I have to reboot every time to test so it takes a while. I plan on doing a binary search for it. Upgrade half the list. Reboot. Fail? Rebuild and cut that list in half again. Of course, I don't know what do do once I find the package! :)
Whateverfits, So how did you "ignore the core Ubuntu updates". Did you do this on the Core or on the MD? Did you just comment out the ubuntu sources in the your apt sources? Let me know. I would love to get these things working.
Dothedog
Ok Guys, I think I solved this:
since you can't boot into a tty when you get this, I did a chroot
sudo chroot /usr/pluto/diskless/<moon#> /bin/bash
update-rc.d -f NetworkManager remove
reboot MD
Apparently there is a bug in NetworkManager in Intrepid that has a problem with static IP addresses. You don't need NetworkManager if you are only using static ips.
Please try this and let me know if it works.
Dothedog
Dothedog: You legend!
I was getting the (eth0): device state change: 1 -> 2 as well, but removing NetworkManager as you suggested has fix the problem!
Regards,
Josh
lemming86_au,
I'm glad it worked for you. I just marked this one solved :) I am surprised more people don't have this issue. I had the same thing happen on 4 different ethernet cards, so I figured it wasn't a hardware driver issue. Took a lot of googling but I'm glad we got it figured out.
Dothedog
dothedog, I ignored the other updates by manually running apt-get update packagenamehere on my MD.
But I guess that doesn't matter any longer since disabling NetworkManager worked perfectly! Thanks!
Quote from: dothedog on October 03, 2009, 04:14:05 AM
Ok Guys, I think I solved this:
since you can't boot into a tty when you get this, I did a chroot
sudo chroot /usr/pluto/diskless/<moon#> /bin/bash
update-rc.d -f NetworkManager remove
reboot MD
Apparently there is a bug in NetworkManager in Intrepid that has a problem with static IP addresses. You don't need NetworkManager if you are only using static ips.
Please try this and let me know if it works.
Dothedog
dothedog,
The process you describe here, is it to enable MD to PXE? I have a problem with my two Zotac boards (330 and 230), with both reporting the same error while trying to go through the initial steps of network booting for the first time. Both PCs reboot after about 10 to 15 seconds, occasionally reporting that they "cannot connect to router". Do I have to change something on the Core?
Sorry for the novice question,
Lev
Levster,
The "cannot connect to router" is a different issue than what is being discussed here, but I have noticed some other topics in the forum discussing it.
I believe there is a temp fix in this topic - http://forum.linuxmce.org/index.php?topic=8939.0
Regards,
Josh
Josh,
Thanks.
I was able to push myself a bit further with "/usr/pluto/bin/startup-script.sh", but am now stuck on "diskless setup failed" message.... :-\ ???
Quote from: levster on October 15, 2009, 06:06:51 AM
Josh,
Thanks.
I was able to push myself a bit further with "/usr/pluto/bin/startup-script.sh", but am now stuck on "diskless setup failed" message.... :-\ ???
yup me 3. :)
allegedly if you add a closing quote to the end of the last line in /etc/pluto/bin/files.d/fstab-diskless it should fix that.
I added a quote to /usr/pluto/bin/files.d/fstab-diskless on the core, which got me through to the AVWizard.
Quote from: davegravy on October 15, 2009, 06:30:36 PM
allegedly if you add a closing quote to the end of the last line in /etc/pluto/bin/files.d/fstab-diskless it should fix that.
Can you please "spell it out"? I am sorry, but I am rather of a novice at this and need a little extra help... ??? Where do I add a "closing quote"?
Thanks,
Lev
On the core, open a prompt and edit the file in nano:
sudo nano /usr/pluto/bin/files.d/fstab-diskless
Move to the last line with text on it (line 28). It should look like this:
mkdir -p "${Parm_RootLocation}/var/spool/asterisk
Add a double-quote to the end so it looks like this:
mkdir -p "${Parm_RootLocation}/var/spool/asterisk"
Save and exit nano ([Ctrl]+X then Y then [Enter]). Then reboot your MD and see if it worked ...
If not, the MD may also be missing a hosts file. I had created one as part of troubleshooting before I did this step, so I'm not clear whether that's a required step for the workaround or not.
Quote from: jthodges on October 15, 2009, 08:58:02 PM
On the core, open a prompt and edit the file in nano:
sudo nano /usr/pluto/bin/files.d/fstab-diskless
Move to the last line with text on it (line 28). It should look like this:
mkdir -p "${Parm_RootLocation}/var/spool/asterisk
Add a double-quote to the end so it looks like this:
mkdir -p "${Parm_RootLocation}/var/spool/asterisk"
Save and exit nano ([Ctrl]+X then Y then [Enter]). Then reboot your MD and see if it worked ...
If not, the MD may also be missing a hosts file. I had created one as part of troubleshooting before I did this step, so I'm not clear whether that's a required step for the workaround or not.
Thank you, jthodges!
I will try this and let you know if it works. Also, if the diskless MD is booting with out a disk, how would you append the host file on it?
Lev
I appended the file:
sudo nano /usr/pluto/bin/files.d/fstab-diskless
and verified it. The MD is still not booting past the Diskless setup failed. So, how would I correct the MD's host file?
Lev
Well, if it comes to that you access the MD's tree in the /usr/pluto/diskless/# directory (where # is your MDs device ID). So something like this to create/edit your hosts file:
sudo nano /usr/pluto/diskless/80/etc/hosts
You'll want that file to include this line:
192.168.80.1 dcerouter
But like I said, only if it comes to that - this file is supposed to be generated automatically, and if this is necessary it means that the closing quote isn't the whole story for this issue. In that case it might be safer to wait and get the official fix before you create your MDs.
Edit: Just saw your latest post. If you decide to proceed, you can try the hosts file fix. But I'm really out of my depth as far as the MD creation process, and just repeating what possy walked us through in IRC. You may want to drop in there for help or wait for the official fix.
thanks that worked like a hooker in vegas!!!!!!!
I checked both the Core and MD and neither has anything in those files. Which should I change?
This was the fix I was looking for (adding a closing quote to the end of the last line in /etc/pluto/bin/files.d/fstab-diskless) in testing beta810. Big thanks. I had tried booting five different MDs and all returned the "failed" message.
I am having the same issue with "Failing to Setup X" I have tried changing the drivers listed in the MD's xorg.conf. None seem to be able to get past that part. is there an answer on this yet?