Re: Cannot Access NTFS Stripe Set ... NT4 or NT5 - FOLLOWUP
From: LockPinZ (NO-EMAIL_at_ADDRESS.INFO)
Date: 06/03/04
- Next message: Harry L.: "dfs, frs read only for access databases"
- Previous message: Thomas Åhlstedt: "NT4 Print diver on Windows 2003 server"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 3 Jun 2004 06:47:54 -0400
2 months later - no answers 2 this question - so much for the Guru's
Problem solved using QUETEK's "File Scavenger". After checking some other
vendors, QUETEK's product came out ON TOP as it not only recovered every
file INTACT, it also recovered the existing directory structures, attributes
and security settings. In comparison to other data disasters experienced
here, File Scavenger worked like a breeze as it identified everything.
Several other well known "NTFS" recovery programs refused to find file ONE,
never mind the directory structure. They know who they are, as I have taken
the liberty to inform them of their failure in recovering simple data.
ANYONE who is responsible for DISASTER DATA RECOVERY (yeah, all you I.T.
tech wanna be's too) QUETEK's "File Scavenger" is by far the best software
recovery tool as long as the PC can access the disk(s). It has recovered
files from re-formatted disks (quick), broken stripes and disk crashes. No
other recovery product I have used has come close to the ease of use and
recovery ability. The cost is absolutely a bargain compaired to those OTHER
guys who charge THOUSANDS and deliver NOTHING.
I hope this information is used for your benefit - good luck!
LockPinZ
"LockPinZ" <NO-EMAIL@ADDRESS.INFO> wrote in message
news:O#cyCcnGEHA.3012@TK2MSFTNGP12.phx.gbl...
> Cannot access NTFS Stripe set from windows but CAN access and verify with
> chkdsk
>
> After moving a stripe set (2 disks and controller) from a NT Server (sp6a)
> to W2K (sp4), disks worked fine. Shared this stripe set the same as it
was
> in the server. Something went wrong. During a FTP transfer, W2K crashed
> and reset. After this the disks were disconnected. Examination with Disk
> Manager showed them as 2 independent disks. Immediately shut down PC,
> disconnected the disks from the system (pulled power) and consulted the
"NT
> System Resource Bible".
>
> Re-installed the stripe set back into the original server - NT Server
> recognizes it as a STRIPE SET but cannot access it. Chkdsk for NT 4 says
it
> was modified with a later version of NTFS, probably W2K. Installed
> auxillary W2K onto server to access stripe set. W2K initially reported
the
> disks as seperate. Used WINDISK and FTEDIT from NT 4 resource kit to
> re-establish the stripe link. Successful link.
>
> CHECK DISK for W2K has found all the information and the entire stripe set
> is INTACT. It reports an NTFS format and the correct VOLUME LABEL, amount
> used and amount free. The data is there and properly formatted. Ran
chkdsk
> with the "/F" option - ran it several times successfully and each time
> chkdsk reported all is okay. Windows NT 4 or W2K cannot access the disk
as
> it says the filesystem is corrupt.
>
> Is there something I can do to repair this problem without compromising
the
> data on the disk? It appears normal disk accesses are not able to read
the
> disks and reports the stripe set is not formatted. My thought would be to
> re establish the necessary informaiton WITHOUT having to reformat the
stripe
> set. Is there a program that can dig in, get the necessary disk geometry
> and re establish the set?
>
> Norton Disk Doctor is a bloody joke as it can't begin to fix this. I have
> no idea why Symantec continues to market this sort of crap. Norton was a
> great name for fixing problems. Peter Norton sold us out to big business
> and now we get GARBAGE. It won't fix simple disk access errors anymore!
>
> Thanks
>
> Ed
>
>
>
- Next message: Harry L.: "dfs, frs read only for access databases"
- Previous message: Thomas Åhlstedt: "NT4 Print diver on Windows 2003 server"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
|
