NTFS corrupted file system

[wizzleme]

Chkdsk will not run on my data partition giving "unspecified error" messages. Googling this gives a multitude of reasons and solutions, non of which work (such as running from dos/safe mode).

I think it's a corrupted NTFS file system but I could be wrong, cuz it happened when I was organizing files on the drive with two different apps and the file names show up but are "not found" when trying to open them.

I ran sfc /scannow which found errors, but like most windows crap was no use "unable to fix them".

bootitbm cannot image the drive successfully giving these errors when trying to open:

"insert media 1 containing file C:\lenovo_DDATBAK_2-2-17.tbi

unable to open file

error 6 opening file c:\lenovo_ddatbak_2-2-17.tbi

This usually means the file is not accessible or the file is invalid
Ensure the file exists and the user has read permissions; update to latest
version of tbiview; consider checking or replacing system ram"

I am experiencing no other noticeable problems with ram (except occasional lags of failure to load bootitbm opening screen). Permissions are ok for the file. FIle exists cannot open it. Imaged it twice with verify byte by byte.

I have downloaded western digitals DLG check(an supposedly repair), but I have my doubts it will work).

I spent hours transferring data files to this drive and erasing same files from USB. I'd HATE to have to reformat the drive so I can run chkdsk. THe drive is functioning normally and I can access 99.9 percent of what's on it, but I can no longer image the drive with bootitbm, cuz the image fails.

Any ideas? Thanks for all your helpful replies.

[Brian K]

wizzleme wrote:
> giving these errors when
> trying to open:
>
> "insert media 1 containing file C:\lenovo_DDATBAK_2-2-17.tbi
>
> unable to open file
>
> error 6 opening file c:\lenovo_ddatbak_2-2-17.tbi
>
> This usually means the file is not accessible or the file is invalid
> Ensure the file exists and the user has read permissions; update to latest
> version of tbiview; consider checking or replacing system ram"
>



That is normal for an offline backup. The image is OK. Fix it with...

http://www.terabyteunlimited.com/kb/article.php?id=581

[wizzleme]

If the link is correct, then why am I able to access earlier img files from the same partition made a week or two ago?

The link you supplied makes no sense because the D data partition ntfs was created under win7 , same laptop and that partition has been successfully imaged several times before and they all open fine.

Unless the link means (which it does not say) that any FILE transferred from some other originating computer (earlier versions of window) prevents the image from being accessed.

Also, there is not admin password, Iam the only user and I am admin.

So the link makes no sense. Fact is bootitbm was imaging the same partition ok a week and two weeks ago and now suddenly cannot open an image it created. I have never imaged under DOS as the link implies, nor have I used any other imaging program other than bootitbm on this same machine?

SO what am I missing here?

I looked under properties for the D: partition and as far as I know nothing has changed on the ownership status of the drive or files. IT is possible some of the FILES and DIRECTORIES I transferred from usb sticks have read only attributes. THey came from previous Win os's such as xp and win98se.

Nonetheless, I will try to follow the links instructions on ownership changes. Weird. Never had such a problem with bootitng.

[wizzleme]

Additionally I ran Western Digital's Data Life Guard hard drive fault detector program and it reports the drive is A-ok (passed). So it's not a hardware problem.

Also the link says that I should try running tbiview as admin. Already tried that as I recall and image is still inacessable.

Also ran a complete system scan using F-secure, highest rated AV program and system is clean.

Chkdsk on the partition in question will not run and gives an unspecified error message which persists under all conditions (safe mode, admin, etc). I have found so far no good alternative to chkdsk which has MANY user complaints about it not running correctly.

[wizzleme]

ok, I ran tbiview as administrator and was able to access the backup image of the D: data partition.

Only thing I can think of as the cause is that the image was targeted to c: drive whereas previously it was sent to E: drive.

I think terabyte should edit it's eror messages for this error to let users know to try running tbiview as admin. The account I was using is same as admin though, there is only one user and that is admin. However I still had to run tbiview as admin to get into the image.

Since the image is created outside windows by bootitbm, why does the image take on admin ownership rights anyways? And why does it only happen when target is c: drive. I looked at the permission for c: drive and they appear to be very open with several users being able to access files full control.

I am rethinking the use of TB image programs. They are just too many caveats and problems that need to be dealt with and I don't have time or desire to become a hard drive geometry expert. I recently found a free backup program that imaged the drive in about 5 minutes whereas bootitbm takes about 30 minutes. There should be no reason why an image should be created that is not accessible by tbiview or preferably any image program that can read .img files. I have not tried restoring using this program but so far it looks really fast and easy to use. I do note that tbiview is alot faster than it was under bootitng though.

[TeraByte Support(PP)]

From what I've seen, saving from outside Windows (e.g. BIBM, IFD, etc.) to the root of C: seems more likely to cause that issue than other more non-system locations. You could try creating a folder in Windows (e.g. C:\IFD Backups) with full/normal permissions for users/everyone and use that as the destination for the images instead of the root folder.

For the speed issue, IFD depends heavily on the BIOS and the speed can vary greatly from system to system. IFW (Windows environment) and IFL (Linux environment) are usually many times faster than IFD.

[DrTeeth]

On Sun, 5 Feb 2017 09:19:25 PST, just as I was about to take a herb,
TeraByte Support(PP) disturbed my reverie and wrote:

>For the speed issue, IFD depends heavily on the BIOS and the speed can vary greatly from system to system. IFW (Windows environment) and IFL (Linux environment) are usually many times faster than IFD.

I can vouch for that. IfL is five times faster in my current system
than IfD. It's a shame that IfL cannot be included in BIBM.
--
Cheers,

DrT

"If you want to find out what is wrong
with democracy, spend five minutes with
the average voter." - Winston Churchill

[Brian K]

DrTeeth wrote:
It's a shame that IfL cannot be included in BIBM.
> --

DrT,

I run IFL from the BIBM Boot Menu. No IFL boot disk needed.

[db2man]

How did you set that up Brian? Is there a guide on the TB site?

On 2/5/2017 4:41 PM, Brian K wrote:
> DrTeeth wrote:
> It's a shame that IfL cannot be included in BIBM.
>> --
>
> DrT,
>
> I run IFL from the BIBM Boot Menu. No IFL boot disk needed.
>
>

[Brian K]

Tom,

This is the only one I can find...

viewtopic.php?f=4&t=291

There is an older method I used to use but I can't find it. But never mind as I use a simpler method now.

Create an IFL flash drive. Use IFW to Copy the flash drive partition to Free Space on the HD. Use 100 MiB for Resize After Copy on the IFW Options window. Setup a Boot Item in BIBM. All done in a few minutes.

The following doesn't apply to BIBM but in a UEFI system you can copy the IFL flash drive partition to a GPT disk and boot IFL from the "BIOS" boot menu.