Questions at bottom in bold (PLEASE skip to the questions at the minimum)So I should install W2K3 Server? OK! Just about exactly 24 hours later, I'm running Windows 2003 Server Standard Edition!
--STARTING with W2K3 Server ENTERPRISE x64--
Thursday, 6:00 PM: Started Major Backup Updates (everything I could)
Thursday, 11:00PM: Backups Finished
Thursday, 11:30PM: Fried Floppy Drive
> Mistakenly plugged cable misaligned (off one pin).
> Amazingly, I took 3 times as much care making sure I didn't block fans, etc....missed the power cable issue!
> Saw a spark, started smelling something
> Didn't want to cut power so waited a bit then decided to before the OS started loading (still Vista at the time)
> Floppy required for RAID drivers
Friday, 1:00 AM: Sick of being unable to boot correct RAID, OS reboots continuously, sick of floppies and extra hassle of opening case each time I want to format (add floppy)
> Plus, the mobo sucks in that it will NOT let me force it to boot the internal RAID so I always have to pull my Promise RAID card and it kinda works but I always run into issues
Friday, 2:00 AM: Decide to use single drive method--MUCH simpler but lose OS redundancy
-- any ideas here to help reduce the danger?
Friday, 5:00 AM: Sick of waiting on Service Pack / update downloads. TIME FOR BED!
Friday, 10:30 AM: Wakeup
Friday, 11:00 AM: Fight with PHP & Apache; simply cannot get PHP working correctly!
Friday, 3:00 PM: Started posting desperate questions on forums
Friday, 7:00 PM: Absolutely fed up, going to try Standard (x86) because Apache & PHP (plus others) are not x64 based so maybe there are conflicts
Friday, 11:00 PM: Completely finished! Completely updated, Apache, PHP, hMailServer, D-Link View Cam, Media Center, Juice Podcast Receiver, Shared Drives, Dynamic Update Client (no-ip), and whatever else I'm forgetting.
This has been one of the most interesting major server overhauls I have ever went through. Not to bore everyone but it's quite difficult to imagine.
We are planning a three family "major" vacation and, since our email is hosted here I had to setup a temporary server and switching meant downtime--and checking email was difficult since Thunderbird profiles are on server (now, down).
Not to mention being up till 5 AM! And destroying a floppy drive--but MORE importantly, I wonder if that could have destroyed more! It appears to not have but several hard drives are on the same cable the floppy was on! Then I was worried something would catch fire. I though: hmm, it's probably fine, I don't smell much. Then I realized that the very high powered fans were blowing over the floppy drive carrying any smell way away from me--so I had no idea how bad it was ... leading me to shut it down immediately.
Luckily the RAID data came right back. When I installed the driver and gave the drive a letter, I double clicked it and got "Access Denied" -- a MUCH more pleasant message than what the message could have said: "This drive is not formatted." So I just took ownership of the drive and it started flipping through all the data--phweww.
So I have some major questions.
I have not tried my MP101's yet but will at some point. I think the 1-track issue won't exist with W2K3 server now.
I was getting around 420 MB/sec read speeds on the array with Vista. I now, testing with the same program, get 60 MB/sec. That is absolutely not pleasant! The 16 drive array performs worse than the OS drive (single drive!) What the heck is going on?! I got the same speeds with both the attempted x64 and the current x86 operating systems.
Any other suggestions for what is in 2K3 Server Standard that I can take advantage of? I'm just using file sharing and general application running/server stuff. What's good that's built into the OS?
Now I just want to go rest...while listening to MC! I was so pleased (mainly this last time around when my work was leading to the finished product) when I opened MC and everything showed up--the server raid array was still perfectly intact!