If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Change Fixboot manually? (Boot Sector was in NTFS but FB change it in FAT)
Hello List,
I was searching for a two days for a solution but my knowledge is to little to be suer so I would be happy for a advice two years ago i install a boot manger , i like it because it looks nice but even in the installation it killed one of my partition so I'll never touch it again and let it on my system because i was afraid that it kill another partition monday i wanted to copy my raid to a new hd and it all went fine except the next day the hd was not found and was labeled as 'hidden hpfs' i remembered that the same was happen last time to the partition which was killed and so it must be the boot manager which made this i try the standard things FIXBOOT was able to say me that the boot sector was wrong and it will fix it BUT IT MAKE A FAT BOOT SECTOR but i was in fact NTFS -now i definitely had enough and kill the boot manager, make a fixmbr and was praying that not much was killed and hallelujah everything was fine, excerpt the new hd which no shows as fat and i have the bad feeling that if i dint make the bootfix first it would also be running so my question -is the data on it totally lost, no change to make make the bootfix undone? and the second -why was the bootmanager interfere with this HD? -is that normal?!? thank for your patience adrian |
#2
|
|||
|
|||
"Adrian A." wrote in message
om... monday i wanted to copy my raid to a new hd and it all went fine except the next day the hd was not found and was labeled as 'hidden hpfs' *What* lists it as hidden HPFS? Was it a PowerQuest program? If it was: This can be caused by 2 things: - The boot sector for an NTFS partition is damaged - The partition table contains an entry pointing to an NTFS partition, but it's pointing to the wrong place i remembered that the same was happen last time to the partition which was killed and so it must be the boot manager which made this But you did not use that anymore? i try the standard things FIXBOOT was able to say me that the boot sector was wrong and it will fix it BUT IT MAKE A FAT BOOT SECTOR but i was in fact NTFS But did or didn't you have it 'fix' it? -now i definitely had enough and kill the boot manager, make a fixmbr and was praying that not much was killed and hallelujah everything was fine, excerpt the new hd which no shows as fat and i have the bad feeling that if i dint make the bootfix first it would also be running Aha, so it seems you did ... Well, I have seen this quite often (Fixboot screwing up an NTFS partition by writing a FAT boot sector onto it), and often it is fixable by copying the NTFS backup boot sector on top of the FAT boot sector. It also requires the partition table to be edited to change the partition back to NTFS, plus probably the size needs adjustment. so my question -is the data on it totally lost, no change to make make the bootfix undone? and the second -why was the bootmanager interfere with this HD? -is that normal?!? No of course it is not normal, still you didn't even mention *what* boot manager ... Kind regards, Joep -- D I Y D a t a R e c o v e r y . N L - Data & Disaster Recovery Tools http://www.diydatarecovery.nl http://www.diydatarecovery.com Please include previous correspondence! DiskPatch - MBR, Partition, boot sector repair and recovery. iRecover - FAT, FAT32 and NTFS data recovery. MBRtool - Freeware MBR backup and restore. |
#3
|
|||
|
|||
"Joep" j o e p @ d i y d a t a r e c o v e r y . n l wrote in message
"Adrian A." wrote in message om... monday i wanted to copy my raid to a new hd and it all went fine except the next day the hd was not found and was labeled as 'hidden hpfs' *What* lists it as hidden HPFS? Was it a PowerQuest program? If it was: This can be caused by 2 things: - The boot sector for an NTFS partition is damaged - The partition table contains an entry pointing to an NTFS partition, but it's pointing to the wrong place How about just what it says: labeled as type 'hidden hpfs' (17h, hidden IFS (NTFS/HPFS)) i remembered that the same was happen last time to the partition which was killed and so it must be the boot manager which made this But you did not use that anymore? i try the standard things FIXBOOT was able to say me that the boot sector was wrong and it will fix it BUT IT MAKE A FAT BOOT SECTOR but i was in fact NTFS But did or didn't you have it 'fix' it? -now i definitely had enough and kill the boot manager, make a fixmbr and was praying that not much was killed and hallelujah everything was fine, excerpt the new hd which no shows as fat and i have the bad feeling that if i dint make the bootfix first it would also be running Aha, so it seems you did ... Well, I have seen this quite often (Fixboot screwing up an NTFS partition by writing a FAT boot sector onto it), and often it is fixable by copying the NTFS backup boot sector on top of the FAT boot sector. It also requires the partition table to be edited to change the partition back to NTFS, plus probably the size needs adjustment. so my question -is the data on it totally lost, no change to make make the bootfix undone? and the second -why was the bootmanager interfere with this HD? -is that normal?!? No of course it is not normal, still you didn't even mention *what* bootmanager ... Kind regards, Joep |
#4
|
|||
|
|||
"Folkert Rienstra" wrote in message
... How about just what it says: labeled as type 'hidden hpfs' (17h, hidden IFS (NTFS/HPFS)) Woow F'Nut, that's a *good* one, I'll give you that! Still, then I'd be interested in *what* displays it as HPFS. PQ products labeling it as HPFS means, they've checked the boot sector and didn't find the NTFS string. Anyway Fixboot screwed up anyway. -- Joep |
#5
|
|||
|
|||
"Joep" j o e p @ d i y d a t a r e c o v e r y . n l wrote in message
- I appologize, I will stop using the stupid F' ... joke. -- Joep |
#6
|
|||
|
|||
Good morning Joep, ---------- insert after writing i should have next time a closer look to other peoples signature especially when the so useful as yours - iRecovery is a great Program and next time when such a thing happen i will buy one, instead going to a friends workplace, where they have easy recovery pro, which seems not of more use in such a situation but a little more expensive -I already formatted the bad NTFS volume, so i can not say which of them get more date, but from a look at the program i would say they'll do both the same good job __________________ monday i wanted to copy my raid to a new hd and it all went fine except the next day the hd was not found and was labeled as 'hidden hpfs' *What* lists it as hidden HPFS? Was it a PowerQuest program? If it was: This can be caused by 2 things: - The boot sector for an NTFS partition is damaged - The partition table contains an entry pointing to an NTFS partition, but it's pointing to the wrong place Yes you guess right, it was in fact the Partition Magic 7 which i had left on my drive from the last time, when a whole partition disappeared I'm pretty sure that its the partition table which was screwed up by the boot manager, because after fixmbr the partition was shown right in place but with the screwed fixboot bootsector it was a little of a Phyrrusvictory i try to fix it with PTEDIT32 which came with PM but only changing the type of the partition seems a little to easy ___________________ and again a insert i think the whole story would be ended here when im using iRecovery, because it seems that program is smart enough to do such things ___________________ i remembered that the same was happen last time to the partition which was killed and so it must be the boot manager which made this But you did not use that anymore? yes yesterday i deinstall it and after deinstalling i had to made a fixmbr to get access to windows (the deinstallation routine seems a little wacky i try the standard things FIXBOOT was able to say me that the boot sector was wrong and it will fix it BUT IT MAKE A FAT BOOT SECTOR but i was in fact NTFS But did or didn't you have it 'fix' it? see below -now i definitely had enough and kill the boot manager, make a fixmbr and was praying that not much was killed and hallelujah everything was fine, excerpt the new hd which no shows as fat and i have the bad feeling that if i dint make the bootfix first it would also be running Aha, so it seems you did ... *gg* again you guess right Well, I have seen this quite often (Fixboot screwing up an NTFS partition by writing a FAT boot sector onto it), and often it is fixable by copying the NTFS backup boot sector on top of the FAT boot sector. It also requires the partition table to be edited to change the partition back to NTFS, plus probably the size needs adjustment. it seems good to have a backup of the boot sector -like in old days I take a look at Partition Magic, if it has this function and will make one, because you never know the 160 GB NTFS partition had with the FAT boot sector a gigantic capacity of 12 MB, but that sure because of the FAT32 limitation but for now i decide that it take to long to change the partition table and because i had no backup up of the boot sector it seems also not helpful i took the hd and drive to a friend which had in his workplace 'easy recovery pro' and with this it was easy to get the data from the ntfs partition back, because the program is so smart that you can say him that its a ntfs partition ___________ but not smart enough to remake the partition table _________ so now i finaley was able to format the hd and after tree days i hoppefully be able to copy my datea to there new home -the friend back there in the workplace also says its a foolish idea to copy the date via dos/directory opus, but i want this time only one partition and i think i remember how secure it is to merge partitions with Partition Magic so my question -is the data on it totally lost, no change to make make the bootfix undone? and the second -why was the bootmanager interfere with this HD? -is that normal?!? No of course it is not normal, still you didn't even mention *what* boot manager ... *gg* your right, i wanted first mention it but before i install it, i had the boot manager from suse which was on linux 7.2 running and it can also be that program screwed up the boot manager because at this time suse 7.2 was brand new and i don't know how gut it deinstall itself its System Commander 7 its a deluxe tool, which was designed to make partition and install OS with it, but maybe it's getting angry with me -I never used it any more and made everything with bare hand have a great time adrian |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
NTFS file system corrupted - cannot boot into XP | mwh7000 | Homebuilt PC's | 12 | September 6th 04 02:26 PM |
corrupted partition table - help needed! | Justin Case | General | 0 | August 3rd 04 09:22 AM |
How Move OS XP from Old to New HD? | Nehmo Sergheyev | Homebuilt PC's | 80 | January 12th 04 05:10 PM |
flashing bios to NTFS any diff than to FAT32 Win XP? | Randyman | Homebuilt PC's | 6 | August 7th 03 06:14 AM |
A7N8X Deluxe Won't Boot from Hard Drives | Dennis | Asus Motherboards | 5 | July 29th 03 07:19 PM |