Not a moment too soon - the hottest day of the year so far, and the WAN network card broke. The old server was slow, noisy, and had a temporary power supply hanging out the side as the old one had recently failed. The new HP Microserver is whisper-quiet, fast, and is now on SME 8.
I turned off the hardware RAID in the BIOS, and the SME 8.0 upgraded the SME 7.6 without any issues. I had originally left it on, thinking I could make use of the hot-swap capabilities without SME even knowing, but that's no great loss.
Last year I did try putting SME on the box as a virtual machine running under some version of VirtualBox. It worked, but I felt it was a bit cludgy - just too many ends that needed to be tied up for it to work, and too many things that could come unstuck. In a corporate environment I'm sure it would be ideal, but I just wanted a simple reliable (and I have been running since e-smith 4.1.2 from the PC Plus cover CDROM, so yeah, I know it "just works") and opted against burying SME under too many layers of virtualization. With SME 8 as the base OS on the server, I am hoping I can run some virtual machines within it for development purposes. Gone are the days when we had to keep setting up separate boxes for each project.
I'll follow your recommendations for upgrading the other SME servers I have out in the field. Before taking out a RAID disk, I would give them a good scan though. I have found in the past that some sectors could go bad on some disks without it being detected by SME, only to be found when you try to migrate to new hardware and find it gets stuck at the same point each time. I don't know if SME 8 monitors these things better and lets you know if any sectors are remapped and which disks are starting to look a bit dodgy.
Thanks for your help, and looking forward to the next 14 years of SME Server!
-- Jason