Author
Topic: 1004: The time has come. (Read 66687 times)

Diskless Setup is failing for everyone. I do not know why. I will investigate.

Good to know I'm not alone there. Not sure if it helps but I then ran the old manual Diskless_CreateTBZ on the core which took the usual x+1 hours and was able to bring up a media director relatively successfully this morning. There was a message that some of the devices did not start correctly but I don't know what that refers to and if it is related.

Ok... so I have fixed diskless for the next batch... but... I don't know if ssh will work between core/moon.

This code is so sticky. Everything interacts with everything, and you touch one piece and get stuck to 14 other pieces.

MD update doesn't seem to be occurring on my end, but I am on a really old unstable image... so... please watch what is going on when you hook your MDs up. SEE if nvidia install is failing, not just a failure to setup x once it tries to load without the driver installed. See if it is updating... when you get a splash screen, hit escape and watch it.

Ta. Incidentally, ssh appears to be working fine in prev (25970) image so hopefully that carries through. So far so good on that image after I ran DisklessCreate. Still haven't tracked down or looked further as far as the "some devices not starting" on the MD.

Mine was the Picture viewer, but after leaving it on overnight and a reload/reboot, it sorted itself out.

Most likely the same for me. Didn't check this morning when I started the MD if it was still reporting that. Incidentally, how did you know it was the picture viewer... because you tried it or because you know where to look to see what didn't sart?

By assumption. When I got the "Some Devices failed to start" message, my screen saver wasnt working. Picture Viewer was allways the last one in the queue just before the orbiter loads. Next morning no error message and a couple of minutes the screensaver started.

I don't know why. They are explicitly installed before the dvd is created.

Running diskless create will definitely fix the md stuff... but part of the point of this is to avoid that. I am trying to get as close to perfect a full install with diskless and everything run and ready. I know 270 was botched. Could use feedback on the latest.

Then installed the Pluto nvidia drivers.Then tried to install nvidia and failedI manually rebooted and still failed to install. If I login to a terminal on the core and SSH to the MD, and just do an apt-get update. Go back to the MD and reboot it the drivers installed. One more reboot after the drivers are installed, AVWizard comes up. So is there anyway you can force an apt-get update before the script tries to install the nvidia drivers?

Anyone else experiencing A very long MD setup, starting with the AVWizard. Took me about 10 minutes to go through the AVWizard, and then at least 45 minutes for sarah to appear, and then another 40 or so minutes to finish to the orbiter. well over 2 hours to setup each md.

The setup can take quite a while, especially if the network itself has some problems. For example, if the switch and the MD don't think they both should use gigabit, some NICs are better than others, i.e. sometimes you only get rates of 1-2MB/s, instead of 20-30MB/s or more.