|
Harddrive problemsdisl (pg. 2)
|
View this Thread in Original format
| Sushipunk |
| quote: | Originally posted by gehzumteufel
it wouldnt matter. it doesnt make sense that the thing has half the drive detected and not the other. sounds like an MBR problem. |
You would probably know more than I would about it, I'm not really sure about this kind of thing. I would think though, that 2 drives on the same computer, both with an OS, would conflict with each other? Maybe a master/slave thing?
Just throwing ideas out. |
|
|
| gehzumteufel |
| quote: | Originally posted by Sushipunk
You would probably know more than I would about it, I'm not really sure about this kind of thing. I would think though, that 2 drives on the same computer, both with an OS, would conflict with each other? Maybe a master/slave thing?
Just throwing ideas out. |
nah cause you could install windows twice, in two different folders, and they would both still boot. this is very stupid since it would cause all sorts of other conflicts (mostly due to the fact that generally you wouldnt ever install the same windows version twice for a dual or multiboot situation) but it is possible.
for some insight the MBR contains partition and filesystem info which is how windows finds this information.
karim: do you have a windows 98 disc? |
|
|
| Sushipunk |
Hi,
Its sushi's gf here (hi!). Sorry to hear about the problem! Its an usual one! I just have couple of questions. Is the drive a SATA drive? If so, it would probably need to be set up using the bios. XP tends not to detect SATA drives correctly until SATA is selected in the bios.
If thats not the prob, you might be able to recover the second partition using powerquest partition magic, by joining the two partitions together.
If the MBR is broken or the partition is corrupted, I use a program called easy recovery pro to recover the data, which works really well. So long as the drive is spinning, I could pretty much guaratee that your data would be recoverable.
Thats all i can think of for now! If you need any more help, let sushi know:) |
|
|
| gehzumteufel |
| quote: | Originally posted by Sushipunk
Hi,
Its sushi's gf here (hi!). Sorry to hear about the problem! Its an usual one! I just have couple of questions. Is the drive a SATA drive? If so, it would probably need to be set up using the bios. XP tends not to detect SATA drives correctly until SATA is selected in the bios.
If thats not the prob, you might be able to recover the second partition using powerquest partition magic, by joining the two partitions together.
If the MBR is broken or the partition is corrupted, I use a program called easy recovery pro to recover the data, which works really well. So long as the drive is spinning, I could pretty much guaratee that your data would be recoverable.
Thats all i can think of for now! If you need any more help, let sushi know:) |
your still off. if it was a driver issue the drive wouldnt show up at all in the drive management at all. its 1 physical drive (hence DISK 1) and its divided into two partitions.
edit: also NEVER again use ERP for MBR corruption. NEVER use anything for MBR corruption. its the easiest fix ever and it takes 2 minutes (most of the time spent finding the media). ALWAYS keep a windows 98 disk around for this reason. for MBR recovery insert a windows 98 disk in and just get to the prompt. once you are at the prompt you type 1 command. fdisk /mbr. this will repair it. |
|
|
| Sushipunk |
| quote: | Originally posted by gehzumteufel
your still off. if it was a driver issue the drive wouldnt show up at all in the drive management at all. its 1 physical drive (hence DISK 1) and its divided into two partitions.
edit: also NEVER again use ERP for MBR corruption. NEVER use anything for MBR corruption. its the easiest fix ever and it takes 2 minutes (most of the time spent finding the media). ALWAYS keep a windows 98 disk around for this reason. for MBR recovery insert a windows 98 disk in and just get to the prompt. once you are at the prompt you type 1 command. fdisk /mbr. this will repair it. |
Yah, I'll nod my head and pretend I know what my gf and you are actually talking about :p I don't know jack about stuff like that.
We still haven't actually established what the problem is here though, and it looks like Karim has run off anyway. |
|
|
| Nrg2Nfinit |
i might as well use dynamic disk in this case.
.. i dont know how it can be an mbr problem.. it was just working today before i transplantedit... |
|
|
| gehzumteufel |
| quote: | Originally posted by Sushipunk
Yah, I'll nod my head and pretend I know what my gf and you are actually talking about :p I don't know jack about stuff like that.
We still haven't actually established what the problem is here though, and it looks like Karim has run off anyway. |
lol
ill say i give her props for knowing what seems like a good bit but shes got some learning to do. :D |
|
|
| gehzumteufel |
| quote: | Originally posted by Nrg2Nfinit
i might as well use dynamic disk in this case.
.. i dont know how it can be an mbr problem.. it was just working today before i transplantedit... |
dont use dynamic disks. they suck. omg i hated it once i did it. i wish i didnt do it the one time i did.
and the reason it seems like the mbr got ed up is cause the one partition is messed up. have you tried restarting? |
|
|
| Sushipunk |
| quote: | Originally posted by gehzumteufel
edit: also NEVER again use ERP for MBR corruption. NEVER use anything for MBR corruption. its the easiest fix ever and it takes 2 minutes (most of the time spent finding the media). ALWAYS keep a windows 98 disk around for this reason. for MBR recovery insert a windows 98 disk in and just get to the prompt. once you are at the prompt you type 1 command. fdisk /mbr. this will repair it. |
Hi, its Sushi's GF again,
What I was trying to get across is that Easy recovery pro is great for recovering the data if it was lost due to a corrupted MBR or some other problem. It would be quicker and probably safer to just recover the data, than re-writing the MBR (which I would not recommend as it can make the problem much worse). I usually recover MBR's using the the FIXMBR command in the recovery console.
Cheers! |
|
|
| gehzumteufel |
| quote: | Originally posted by Sushipunk
Hi, its Sushi's GF again,
What I was trying to get across is that Easy recovery pro is great for recovering the data if it was lost due to a corrupted MBR or some other problem. It would be quicker and probably safer to just recover the data, than re-writing the MBR (which I would not recommend as it can make the problem much worse). I usually recover MBR's using the the FIXMBR command in the recovery console.
Cheers! |
fdisk /mbr is literally a 2 second fix. i can assure its much much faster than recovering any data. i know ive used it before and it works wonders. if the MBR isnt broken then nothing will change.
i was unaware of the fixmbr command from the recovery console though. ill keep that in mind next time.
also ERP is great but use encase. its what the FBI has been using although they are trying to develop an alternative of their own. |
|
|
| Sushipunk |
Sushi's GF (again)
Hey thanks for the windows98 startup disk command. I haven't had windows 98 in years, so I use the XP recovery console. But its good to know another way to fix the MBR.
Just my opinion, but I wouldn't recommend trying to fix the MBR unless the drive owner is fairly certain that the MBR is the problem, as it can totally kill a drive that is already suffering from corruption. Sadly, I learned this from recent experience! If the data is important, I'd grab that first, and then try to diagnose the drive problem. A low level format might fix it (or even just a quick format).
I agree about not converting the drive to dynamic. It would make some files more vulnerable if they were spread across two disks.
(ps. I'd still suggest checking whether the drive is SATA and if it set up correctly in the bios)
Cheers! |
|
|
| gehzumteufel |
| quote: | Originally posted by Sushipunk
Sushi's GF (again)
Hey thanks for the windows98 startup disk command. I haven't had windows 98 in years, so I use the XP recovery console. But its good to know another way to fix the MBR.
Just my opinion, but I wouldn't recommend trying to fix the MBR unless the drive owner is fairly certain that the MBR is the problem, as it can totally kill a drive that is already suffering from corruption. Sadly, I learned this from recent experience! If the data is important, I'd grab that first, and then try to diagnose the drive problem. A low level format might fix it (or even just a quick format).
I agree about not converting the drive to dynamic. It would make some files more vulnerable if they were spread across two disks.
(ps. I'd still suggest checking whether the drive is SATA and if it set up correctly in the bios)
Cheers! |
totally agree he should backup his data anyways. doesnt hurt. i need to get me a new external (well really just get a new 3.5 internal and put it in the case my old external was in. i dropped my old one and it was on so the read/write heads got stuck! :( i was mad) but i have no money for that. got other priorities. |
|
|
|
|
