Re: [Testbed-admins] Can not bring up the first node for a new Emulab site

[Leigh Stoller <stoller@flux.utah.edu>]

> and 'messages' and this GET request get a error code '400' which is
> bad request. Then I looked at newnodecheckin.php and there is a
> required parameter 'role' defined in this file.
>
> So based on what I observed , could I say the old 4.X
> MFS(freebsd47.newnode) is not supported anymore by the current
> emulab software or you want to fix this, or I miss something
> here?

Hmm, the 4.7 newnode code is the same as the 6.2 code; they both
pass the role argument.

The thing to do is set the root password on the MFS, reboot the
node, then log in on the console and run the script by hand.

In the freebsd.newnode/boot directory:

boss> sudo mdconfig -a -t vnode -u 1 -f mfsroot
boss> sudo mount /dev/md1 /mnt
boss> sudo chroot /mnt passwd root
boss> sudo umount /mnt
boss> sudo mdconfig -d -u 1
boss> sudo ./prepare

> PS: The reason why I am using this old MFS because I even can not
> boot the new MFS(freebsd62.newnode) from both of my P3 processor
> machine and Core 2 Duo processor machine.

Sounds like a driver problem. I suspect you will have the same problem
when you to boot the disk images.

Lbs