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
|
|||
|
|||
ntfs changes to raw filesystem
I have a problem, and I have not found any good working solution for this.
I was running windows XP (installed it 2 months ago) on my service computer on our technical department. Windows downloaded updates, rebooted the PC at night (this was before I found the option to disable this in gpedit.msc) but when I checked the PC in the morning, my 2x250GB RAID disk (which was in NTFS) was not recognized. So I immediatly used system restore to go back, but it didn't help. I had to reinstall my raid driver (sillicon image 3114) and then the harddisk showed up again in my computer. But the filesystem was changed to RAW file system, and is not readable. Whenever I click the drive, windows gives me an error that the location is not connected or not available. So I tried my datarecovery software (Partition Table Doctor), and booted with the recovery CD, which could read my drive and see all my files. (so everything is still on there, but not readable in windows) Also if I try a ntfs reader, it can still find the drive. I tried already to repair the partition table, and also the MBR. But none helped. I'm sweating more and more, hence there are a lot of backups which belong to my customer's PC's on the drive. (almost all 500GB are used) Do you by any chance know if this could occur with a damaged register key? Or is there a way to convert it back, so it's readable in windows again? I've found some more of these similar problems, but the only "semi-"working solution is to connect new drives, copy it all on a windows 98 PC, and then repartition the original drive, and copy everything back. But that's takes so much time, because then I first have to install win98, copy all the data, replug my xp drive, and copy all the data back. I think there is an easier way for this, but I don't know which way. by the way, I tested both RAID disks with the WD utility, and the drives are both 100% ok. (according to this utility) |
Ads |
#2
|
|||
|
|||
ntfs changes to raw filesystem
OcinO wrote:
I have a problem, and I have not found any good working solution for this. I was running windows XP (installed it 2 months ago) on my service computer on our technical department. Windows downloaded updates, rebooted the PC at night (this was before I found the option to disable this in gpedit.msc) but when I checked the PC in the morning, my 2x250GB RAID disk (which was in NTFS) was not recognized. So I immediatly used system restore to go back, but it didn't help. I had to reinstall my raid driver (sillicon image 3114) and then the harddisk showed up again in my computer. But the filesystem was changed to RAW file system, and is not readable. Whenever I click the drive, windows gives me an error that the location is not connected or not available. So I tried my datarecovery software (Partition Table Doctor), and booted with the recovery CD, which could read my drive and see all my files. (so everything is still on there, but not readable in windows) Also if I try a ntfs reader, it can still find the drive. I tried already to repair the partition table, and also the MBR. But none helped. I'm sweating more and more, hence there are a lot of backups which belong to my customer's PC's on the drive. (almost all 500GB are used) Do you by any chance know if this could occur with a damaged register key? Or is there a way to convert it back, so it's readable in windows again? I've found some more of these similar problems, but the only "semi-"working solution is to connect new drives, copy it all on a windows 98 PC, and then repartition the original drive, and copy everything back. But that's takes so much time, because then I first have to install win98, copy all the data, replug my xp drive, and copy all the data back. I think there is an easier way for this, but I don't know which way. by the way, I tested both RAID disks with the WD utility, and the drives are both 100% ok. (according to this utility) This is not the first time this has happened after a windows update! http://www.z-a-recovery.com/art-raw-filesystem.htm Hope this helps. -- Mike Pawlak |
#3
|
|||
|
|||
ntfs changes to raw filesystem
By the way, I just thought of something. When I check the disk management,
the drive doesn't show up at all! That's also a strange thing. I will try your solution in a few hours, since now I'm not near the system. I'll come back to you if it worked. Thanks in advance, Nico Buma. "MAP" wrote: OcinO wrote: I have a problem, and I have not found any good working solution for this. I was running windows XP (installed it 2 months ago) on my service computer on our technical department. Windows downloaded updates, rebooted the PC at night (this was before I found the option to disable this in gpedit.msc) but when I checked the PC in the morning, my 2x250GB RAID disk (which was in NTFS) was not recognized. So I immediatly used system restore to go back, but it didn't help. I had to reinstall my raid driver (sillicon image 3114) and then the harddisk showed up again in my computer. But the filesystem was changed to RAW file system, and is not readable. Whenever I click the drive, windows gives me an error that the location is not connected or not available. So I tried my datarecovery software (Partition Table Doctor), and booted with the recovery CD, which could read my drive and see all my files. (so everything is still on there, but not readable in windows) Also if I try a ntfs reader, it can still find the drive. I tried already to repair the partition table, and also the MBR. But none helped. I'm sweating more and more, hence there are a lot of backups which belong to my customer's PC's on the drive. (almost all 500GB are used) Do you by any chance know if this could occur with a damaged register key? Or is there a way to convert it back, so it's readable in windows again? I've found some more of these similar problems, but the only "semi-"working solution is to connect new drives, copy it all on a windows 98 PC, and then repartition the original drive, and copy everything back. But that's takes so much time, because then I first have to install win98, copy all the data, replug my xp drive, and copy all the data back. I think there is an easier way for this, but I don't know which way. by the way, I tested both RAID disks with the WD utility, and the drives are both 100% ok. (according to this utility) This is not the first time this has happened after a windows update! http://www.z-a-recovery.com/art-raw-filesystem.htm Hope this helps. -- Mike Pawlak |
#4
|
|||
|
|||
ntfs changes to raw filesystem
It did not work
Do you by any chance know another way? I also tried the ptedit file (this one recognizes the disk, but with a new partition table or mbr still no change) And the ptedit32 file (this one only sees my non-raid disk(s), and not the one I would like to get back) Thanks. Nico. "OcinO" wrote: By the way, I just thought of something. When I check the disk management, the drive doesn't show up at all! That's also a strange thing. I will try your solution in a few hours, since now I'm not near the system. I'll come back to you if it worked. Thanks in advance, Nico Buma. "MAP" wrote: OcinO wrote: I have a problem, and I have not found any good working solution for this. I was running windows XP (installed it 2 months ago) on my service computer on our technical department. Windows downloaded updates, rebooted the PC at night (this was before I found the option to disable this in gpedit.msc) but when I checked the PC in the morning, my 2x250GB RAID disk (which was in NTFS) was not recognized. So I immediatly used system restore to go back, but it didn't help. I had to reinstall my raid driver (sillicon image 3114) and then the harddisk showed up again in my computer. But the filesystem was changed to RAW file system, and is not readable. Whenever I click the drive, windows gives me an error that the location is not connected or not available. So I tried my datarecovery software (Partition Table Doctor), and booted with the recovery CD, which could read my drive and see all my files. (so everything is still on there, but not readable in windows) Also if I try a ntfs reader, it can still find the drive. I tried already to repair the partition table, and also the MBR. But none helped. I'm sweating more and more, hence there are a lot of backups which belong to my customer's PC's on the drive. (almost all 500GB are used) Do you by any chance know if this could occur with a damaged register key? Or is there a way to convert it back, so it's readable in windows again? I've found some more of these similar problems, but the only "semi-"working solution is to connect new drives, copy it all on a windows 98 PC, and then repartition the original drive, and copy everything back. But that's takes so much time, because then I first have to install win98, copy all the data, replug my xp drive, and copy all the data back. I think there is an easier way for this, but I don't know which way. by the way, I tested both RAID disks with the WD utility, and the drives are both 100% ok. (according to this utility) This is not the first time this has happened after a windows update! http://www.z-a-recovery.com/art-raw-filesystem.htm Hope this helps. -- Mike Pawlak |
#5
|
|||
|
|||
ntfs changes to raw filesystem
OcinO wrote:
It did not work Do you by any chance know another way? I also tried the ptedit file (this one recognizes the disk, but with a new partition table or mbr still no change) And the ptedit32 file (this one only sees my non-raid disk(s), and not the one I would like to get back) Thanks. Nico. Do you by any chance know another way? Sorry no I don't. Good Luck -- Mike Pawlak |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
FAT32 is for file storage, NTFS is for windows installation? | [email protected] | General XP issues or comments | 22 | June 9th 06 07:00 PM |
Cloning NTFS & FAT32 | SeaSpeeder | Networking and the Internet with Windows XP | 2 | November 29th 04 10:42 PM |
HELP: NVTV CAD, NTFS FILESYSTEM | Enry | Hardware and Windows XP | 1 | November 14th 04 03:55 PM |
XP - Disk Defragmentor vs Diskeeper | Prabhat | Performance and Maintainance of XP | 32 | October 6th 04 08:33 AM |
Converting from Fat32 to NTFS | General XP issues or comments | 9 | September 10th 04 12:07 PM |