First time posting here, but then again I never had this type of issue.
You may want to grab a coffee or favorite drink
while you read this story.
Background story: I added 2 WD HDD, 1x1TB and 1x 2TB drive. Both NTFS for Movies and Music sharing. I use TWONKY server software for the shares. This allows me to pull the drives whenever I want to move to another system if needed. This avoids having to manually transfer all files to another drive before safely removing the hard drives. Unfortunatly my 2TB HDD is 95% full. Time to upgrade. But wait, I noticed that I am not using the full capacity of the original 2x 500GB drives. In fact the OS is only using 20GB to run.
Change out Main HDD's option to a smaller Primary drive (C:):So I figured if I put in a blank HDD is slot 1 (bottom slot) then I should be able to scrub the system and reinstall onto a blank drive. No problem right? Then I can put TB HDD's in plus reformat the one 500GB HDD and now I have more space.
The Problems:
I didn't realize it was ok to put in a blank primary drive, and rest to factory setup via pushing the little button in, plus launching the recovery software on my main system and connect via network. What I figured was this was no diff than a regular system. I guess not.
My scrub setup steps:
1) Remove all drives
2) Open MSS and connect my KVM cable (connecting my Monitor, Keyboard, Mouse)
3) Connect my USB-CDROM and insert the Official HP PC Restore Disc v1.0 (Solid Green CD)
4) Boot to CD and reinstall OS to blank HDD
But that did not happen. So I figured that I needed to get into BIOS setup and tell the boot order that the USB-CDROM was first on the list.
But that did not happen. It booted to the SMI setup and some strange Windows boot up started and then BSOD.
This happened 3 times. Finally the SMI fully booted and it showed the CD Recovery window... (a small window with a checklist of things to setup), then a DOS screen (windowed) popped up and showed that all drives (C-E) were not found, but it showed that my HDD device and that it was compatable and ok to install. Then it sat there doing nothing.
I closed the DOS window, and the system shutdown and rebooted. I let this happen 5 times.
I realized that this wasn't right and I thought it was not booting properly. I then went back to the BIOS and selected the Optimized Defaults BIOS. When I selected this, the SMI USB-Disk disappeared from the Boot order. Then nothing was booting, it just sat there.
I got online, and came here to search for options. and after reading alot I realized I should just select the proper recovery option. I'm running Win7 64Bit. The HP software didn't like my OS, I grabbed the official MS connector software for 64Bit, but after installing the connector software it tried to connect to the server to download the rest of the software. (how stupid is that,
in the name of all things holy, who decided that I can not download the software without the server?) So I put the original Boot HDD's back into the MSS so my system can connect to downlaod and install the 64bit Connect software. But it could not find the server.
I can ping the server, and can view the shared drive, I can even RDP into it. But that software still can not see it. Now I have to manually move the setup files to my Win7 desktop then install. The connector software is now installed and I can see the server. all is well.
But wait, I still did not scrub my new HDD. I take the Original HDD's out and put the new HDD back in. And it will not boot. So now I start the system, wait for the lights to blink Blue/Red and I use a paperclip and hold the restore button until it starts to blink blue. Remember I am still able to watch everything via KVM. I see the "
SiS191 PXE BootROM v0.7 USE BEV/BBS" setup and it starts looking for DHCP. Is dispalys the MAC address and the GUID. So now I start the recovery software to connect to the server. Nothing happens. and the PXE BootROM stops stating... "
PXE-E53: No boot filename recieved" "
PXE-M0F: Exiting SiS191 PXE BootROM." And my restore software says it can not find the server.
I read troubleshooting for this. I made sure Firewalls were shut down, Port addressing was open for the software, I even connected the MSS directly to the Win7 system. Nothing. So I went to the wife's Vista 32Bit laptop and tried. still nothing. I continue to get the same results over and over.
I thought I'll try the SMI option and allow it to boot back into that. But now it's not in the BIOS. I now go back into the server BIOS and Load the Fail-Safe Defaults. Sure enough the SMI USB-Disk Boot option has returned. Alright now I'll boot into that, right? NOT... What happens next is the system boots and I see all the drive infor plus the IRQ info at the bottom of the screen the cursor is blinking onder the "Verifying DMI pool Data ............." (this is a normal boot) but it just sits there. I go back into the BIOS and make changes to the Fail-Safe Defaults... I enabled the selection for the USB 2.0 support (BIOS Menu options - Integrated Peripherals/SIS OnBoard PCI Device/USB 2.0 support) for good messure I also enabled USB Keyboard and Mouse support) Looking back now... If I make this selection the SMI USB Disk removes itself from the Boot order. So I can't have that happen, I need to make sure the SMI is still working. I power up the MSS and do nothing. I let the lights blink Red/Purple... this happens for a bit of time, then the light sits solid Red.
So I say the heck with this, I'll just put the original system HDD's back in. I do that and it boots up.
I notice that the second 500GB is not being used for anything No drive (E:) is even on it. so I tell the system (via connector software) to remove this HDD. All goes well and I remove it. I boot up the MSS and now it only has the one system HDD. Seems ok.
Not wanting to give on my blank HDD to be the smaller system drive, I read more on this forum and try a few different things. Changing the BIOS defualts a few times trying to boot from the USB-CDROM, or boot via network or boot Via SMI. Nothing.
New Problem:I gave up and put the original HDD back in, and it tries to boot. It stops right at the beginning, big grey bar across the bottom. I realize through trial and error that it does not like to boot with anything plugged into the USB ports. I discovered this as I was logged into the MSS via KVM (not RDP) It seems if I plug in anything USB storage device the system freezes (crashes)
. I tried the USB-CDROM, and other USB jump drives I have.
So now, in order to boot to the original system HDD I have to set the BIOS to Optimized Defaults so that the SMI is not in the boot up order. As I mentioned if the Original HDD boots up and it sees the SMI USB it stops before it even loads. This does not help that with the SMI Boot disk not loaded and that I can not view the SMI drive as it's not available. So I can not go into the SMI drive to save those files to a USB stick in order to boot from. The system will not boot if the SMI USB Disk is present in the BIOS.
I thought if I can get somebody on here to send me the SMI files and put it on a jump drive, I could force it to boot that way, but with all this USB boot stoppages happening, I have no idea if that will even work now.
It's worth a try. Anybody have the SMI files they can send me? Plus instuctions to make my USB Jump drive bootable with those files?
Now that you're up to speed on my situation.... Anybody want to help me out?
If I need to, I can put the original HDD in and have the system up and running again, but I know the moment I put any USB drive in, the MSS crashes.
It should not be like this and it just bugs me.
Thnx in advance