nufcforeva Posted June 3, 2005 Posted June 3, 2005 Hi all I have a problem where when installing from RIS when it tries to format the hard drive it fails with an error saying hard drive might be damaged but seems to work fine installing from a CD. Has anyone seen this before
ixion Posted September 14, 2005 Posted September 14, 2005 nope, sure you using the same raid/sata drivers in the two installation media's?
InTheWayBoy Posted September 14, 2005 Posted September 14, 2005 Is the computer a Dell or some other major manufacturer? If so, then you might need to blank out the HD before hand. Many of the OEMs are including hidden partitions on their systems now, and I had a similar issue with RIS before I manually erased the hidden partitions.
homolka Posted September 22, 2005 Posted September 22, 2005 No need to erase a Dell manually. All of our hundreds machines went through RIS without any problems.Daniel
InTheWayBoy Posted September 22, 2005 Posted September 22, 2005 No need to erase a Dell manually. All of our hundreds machines went through RIS without any problems.Daniel<{POST_SNAPBACK}>Well mine didn't...just something to watch out for.
cluberti Posted October 21, 2005 Posted October 21, 2005 Ironically, that error message is usually an error with the NIC drivers rather than the hard disk (go figure). Make sure that you've integrated the latest drivers for the NIC you're using to PXE boot the machine into the i386 source of your RIS install (as per http://support.microsoft.com/?kbid=315279). That should fix it.
Generic Posted October 21, 2005 Posted October 21, 2005 I myself was just having that issue about 20mins ago. I had made a copy of our production image (so I could test the integrated patches in a non-production environment) when I started getting that same error. Don’t know if this will help or not but I made sure that I had no spaces in the directory name of the image. For instance:Windows.XP.SP2.ProductionThe test image that I was using was in a directory calledCopy Of Windows.XP.SP2.ProductionAfter I renamed the directory I restarted the services (all 4) and that seemed to have corrected my problem.Hope that helps a little.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now