'Drive 1 not found'

tlarkin · 02-19-2008, 04:01 PM

sounds like a bad back up battery for the BIOS and it is resetting back to default, hence the settings have been reset press F1 to continue or DEL for setup.

StrangleHold · 02-19-2008, 04:13 PM

Good idea, thats a possibility.

PC eye · 02-20-2008, 02:02 AM

Quote:

Originally Posted by tlarkin

sounds like a bad back up battery for the BIOS and it is resetting back to default, hence the settings have been reset press F1 to continue or DEL for setup.

Weak battery, failed drive itself, or corrupted boot information. I've run into all three at one time or another with that messsage coming up where XP was involved.

Fortunately the usual 2032 for the number lithium coin sized batteries are a common $2-$3 item found in the calculator/watch or battery section in most retail chains and 24hr. pharmacies.

PC eye · 02-20-2008, 03:21 AM

Quote:

Originally Posted by Cleric7x9

the "drive 1 not found" has nothing to do with windows. its probably that you have your RAID controller turned on without having an array configured or something. please dont do anything with your windows disk, you are just going to mess something up. either see if you can find out what in the BIOS is causing this problem, or just live with it. but i assure you it has nothing to do with your windows

Quote:

Originally Posted by Cleric7x9

what mirror drive? nobody said anything about RAID. i wish we could report incorrect information like we can report spammers.

Does that answer your question? Since computerstu hadn't specified how that system was setup there whether a single OS drive or an array is in use you have to look in both directions.

tlarkin · 02-20-2008, 03:26 AM

well depending on your BIOS depends on the situation. My BIOS, for some retarded reason, by default keeps the SATA controller in RAID mode instead of IDE mode. So, when my battery starts to go out, it will tell me that the disk failed because its trying to boot from a RAID mode, when there is no array set up to begin with.

PC eye · 02-20-2008, 04:52 AM

Even with XP on the more recent build now used after having replaced the first board and reinstalled Windows there I ran into the same error after having not booted in XP for a good period of time for some unknown reason.

I have the present Vista install on an ide drive set as the default while XP sits on a sata model. The last build saw XP on both types there without running into this problem likely from having to reinstall both editions of XP as well as Vista for the multiboot at the time while the board in the previous build ahaaa... it loved batteries!

Besides boot problems try memtest reporting error on defect memory and giving the appearance of a failed cpu! Lately when tossing in a new battery suddenly the fsb can be set to 200mhz on that old board? You never know! But at least with knowing a new battery is going in you expect to be in the bios making any needed changes afterwards from factory defaults.

02-19-2008, 04:13 PM	#12 (permalink)
StrangleHold Diamond Member Join Date: Nov 2005 Location: In a realm of unknown Wonders Posts: 6,848	Good idea, thats a possibility. __________________ NZXT Apollo Athlon 64 X2 5600+ Gigabyte GA MA770 DS3 G Skill DDR2 800 2gb PNY 8800GT Spinpoint F1 500gb. Too bad stupidity isn't painful.

02-20-2008, 04:52 AM	#16 (permalink)
PC eye Diamond Member Join Date: Apr 2006 Location: Inside a pc Posts: 19,005	Even with XP on the more recent build now used after having replaced the first board and reinstalled Windows there I ran into the same error after having not booted in XP for a good period of time for some unknown reason. I have the present Vista install on an ide drive set as the default while XP sits on a sata model. The last build saw XP on both types there without running into this problem likely from having to reinstall both editions of XP as well as Vista for the multiboot at the time while the board in the previous build ahaaa... it loved batteries! Besides boot problems try memtest reporting error on defect memory and giving the appearance of a failed cpu! Lately when tossing in a new battery suddenly the fsb can be set to 200mhz on that old board? You never know! But at least with knowing a new battery is going in you expect to be in the bios making any needed changes afterwards from factory defaults. __________________ Youtube falls short of Google's expectations http://abcnews.go.com/Technology/Ahe...ory?id=5336532 Congress studies how people track your online use http://abcnews.go.com/Technology/Ahe...ory?id=5337932

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Installing a new hard drive with multiple os'es	Ghostnotes	Computer Memory and Hard Drives	5	01-03-2007 02:37 PM
Hard Drive Installation	compdummy	Desktop Computers	2	12-03-2006 02:32 AM
Can't Recognize New Hard Drive, only old hard drive.	PanicByte	Desktop Computers	3	10-28-2006 05:20 PM
Hard Drive Not Recognized???Help!	gsbadbmr	Computer Memory and Hard Drives	5	03-16-2006 02:20 PM
CD-ROM drive not found	Underground_Evo	CD/DVD Technology	3	08-11-2004 10:35 PM

02-19-2008, 04:01 PM	#11 (permalink)
tlarkin VIP Member Join Date: Apr 2006 Location: Kansas City, MO Posts: 5,950	sounds like a bad back up battery for the BIOS and it is resetting back to default, hence the settings have been reset press F1 to continue or DEL for setup.

02-20-2008, 03:26 AM	#15 (permalink)
tlarkin VIP Member Join Date: Apr 2006 Location: Kansas City, MO Posts: 5,950	well depending on your BIOS depends on the situation. My BIOS, for some retarded reason, by default keeps the SATA controller in RAID mode instead of IDE mode. So, when my battery starts to go out, it will tell me that the disk failed because its trying to boot from a RAID mode, when there is no array set up to begin with.