After letting the problem sit for a couple of days I decided to get a FreeBSD LiveCD and see what I could.
After many searches to learn how to setup the system to mount the ad0s1a filesystem to see the information that was on my hard drive. I finally got it mounted. I wanted to see the /etc/fstab file.
The reason I whated to see what was in it was that I noticed (a little closer) that what I typed as the display contained an error in the syntax. I am referring to the line that had -- da0s1 -- it was typed correctly as that was how it was printed on the screen. But is incorrect as it should have read "ad0s1" so I wanted to see how it read in the /etc/fstab file.
What I found was that my /etc/fstab file contained NOTHING; it was empty, not even a cdrom filesystem line.
As I mentioned this was the second time after installing PC-BSD that I got that error. So I can state to you TerryP you where correct to have me check the fstab file. And thank you Charles for writing it up as a bug I would not have done so as I do/did not have any information as to what the problem was. Now I know the problem. But the second questiion comes as to. What causes the /etc/fstab file to be erased/purged???
To answer your directions to type in a ? for more information. The PC does not respond to any keyboard input. The three finger salute does nothing, the only thing I can do is press the reset switch to get the system moving again. I will check some other things here also should I have another hang after an install.
Since I do not know the BSD syntax for entering the information of my hard drive partioning into fstab, and deciding it would be better and faster for now to do another reinstall I did so. After the reinstall the first thing I did was copy /etc/fstab to /etc/fstab_bkup_after_install and secondly was backup the whole PC-BSD partition.
Should I have another hang like before I will see what is wong as best possible. If the fstab file is empty again I will have something to restore from.
I will try and monitor what I did before a reboot (a system update ....) and should I then get another error that my system is corrupt I can then come back with hopefully more information as to what might be causing the fstab file to becone empty.
Again thank you for your replys as I have some direction on what to look for and how to do it. (I copied your directions Terry). Should I get another hang like this again I hope to have more information for a solution to the problem.
I ask this question seeking your opinions. How would you rate PC-BSD compared to FreeBSD or NETBSD or another flavor of BSD?? I know PC-BSD has a FreeBSD foundation. Since I want to find a better replacement for Windows. Would I be better off going, to say, FreeBSD and using and learning it instead of PC-BSD??
Again thank you.