reboot and select proper boot device problem
Moderator: Thanas
- montypython
- Jedi Master
- Posts: 1130
- Joined: 2004-11-30 03:08am
reboot and select proper boot device problem
My computer currently refuses to boot, telling me to reboot and select proper boot device. I tried ctrl-alt-del to get past, but it just restarts the computer and says the same thing again. How do I solve this?
- General Zod
- Never Shuts Up
- Posts: 29211
- Joined: 2003-11-18 03:08pm
- Location: The Clearance Rack
- Contact:
- montypython
- Jedi Master
- Posts: 1130
- Joined: 2004-11-30 03:08am
- Manus Celer Dei
- Jedi Master
- Posts: 1486
- Joined: 2005-01-01 06:30pm
- Location: I need you to relax your anus.
- montypython
- Jedi Master
- Posts: 1130
- Joined: 2004-11-30 03:08am
- montypython
- Jedi Master
- Posts: 1130
- Joined: 2004-11-30 03:08am
- SCRawl
- Has a bad feeling about this.
- Posts: 4191
- Joined: 2002-12-24 03:11pm
- Location: Burlington, Canada
You could see if the HD is toast by installing it in another computer as a slave, and see if you can read any of the data. (You could also take the opportunity to offload anything important, in case you're worried about losing it.) But yeah, it sounds like the drive is pooched.
(If it turns out that the drive is, indeed, screwed, and there are data you don't wish to lose, then there are data recovery places out there for just such an occasion. I can't speak to the cost effectiveness of this solution.)
(If it turns out that the drive is, indeed, screwed, and there are data you don't wish to lose, then there are data recovery places out there for just such an occasion. I can't speak to the cost effectiveness of this solution.)
73% of all statistics are made up, including this one.
I'm waiting as fast as I can.
I'm waiting as fast as I can.
Professional data recovery on a shagged drive is expensive.
Installing the drive as a slave is a good idea, but it will only recover from a screwed set of boot files, which chkdsk /r or the fixboot command would likely have done anyway. From the report of a damaged volume, it's likely the partition won't show up on any other machine either.
Installing the drive as a slave is a good idea, but it will only recover from a screwed set of boot files, which chkdsk /r or the fixboot command would likely have done anyway. From the report of a damaged volume, it's likely the partition won't show up on any other machine either.
- montypython
- Jedi Master
- Posts: 1130
- Joined: 2004-11-30 03:08am
- General Zod
- Never Shuts Up
- Posts: 29211
- Joined: 2003-11-18 03:08pm
- Location: The Clearance Rack
- Contact:
Did you make sure that the type of HDD is compatible with your current motherboard before purchasing?montypython wrote:Installed it in another computer as a slave to see if data was readable. The drive is detected but no drive letter, can't sense partitions. Haven't used Fixboot yet.
What pisses me off is that this is a brand new Maxtor HDD, just out of the box. To have it go crap like this...
"It's you Americans. There's something about nipples you hate. If this were Germany, we'd be romping around naked on the stage here."
Meh, happens. Got a Hitatchi (I think) once from an otherwise reliable shop with free delivery to my door. Was all happy at the convinience until I plugged it in and its name appeared as a random selection of ASCII non-letter characters. Then had to spend 2 drives to the shop to replace it (once to turn it in, once to get replacement since that wasnt covered by the free delivery). Shit happens...montypython wrote:Installed it in another computer as a slave to see if data was readable. The drive is detected but no drive letter, can't sense partitions. Haven't used Fixboot yet.
What pisses me off is that this is a brand new Maxtor HDD, just out of the box. To have it go crap like this...