Go Back   TechArena Community > Software > Operating Systems
Become a Member!
Forgot your username/password?
Register Tags Active Topics RSS Search Mark Forums Read

Sponsored Links



Recovering orphaned file into directory file

Operating Systems


Reply
 
Thread Tools Search this Thread
  #1  
Old 26-05-2009
Member
 
Join Date: May 2008
Posts: 372
Recovering orphaned file into directory file
  

hi,

Description of error:
HP DL380 server
disk array MSA1000, connected optics, RAID5, the volume of the logical disk 1.65 TB
Windows Server 2003 R2

There was a problem: After the couple of emergency shutdown (UPS died) there were logical errors on the disc.
chkdsk finds them, and proposes to correct all at the next reboot.
However, when I restart the chkdsk simply hang up on 0%.
Tried chkdsk with the key / I: validation runs for 1.5 hours, the error is 3, writes that the fixed - but if you start again, the errors are back.

Here's a situation here:
Key C / I chkdsk runs, it errors remain
Without the key / I chkdsk hang up on startup

Who can something efficient advice?
Maybe there is in the nature of any utility checks the disc, which does not require rebooting the server?

Here is a piece of log chkdsk with the key / I:
Every time you start - the log is the same, the same mistakes, same files, same indexes, all 1:1

Code:
You may cancel the disk check, but it is strongly recommended that you continue. Windows will now check the disk. The USA check value, 0x6c12, at block 0x3 is incorrect. The expected value is 0x15b. The USA check value, 0x3835, at block 0x3 is incorrect. The expected value is 0x8d. The USA check value, 0x0, at block 0x3 is incorrect. The expected value is 0x[b]2f2. The USA check value, 0x6c12, at block 0x3 is incorrect. The expected value is 0x15b. The USA check value, 0x3835, at block 0x3 is incorrect. The expected value is 0x8d. The USA check value, 0x0, at block 0x3 is incorrect. The expected value is 0x2f2. Unable to locate the file name attribute of index entry 204814~1.LNK of index $I30 with parent 0x38f32 in file 0x33efb. Deleting index entry 204814~1.LNK in index $I30 of file 233266. The USA check value, 0x3835, at block 0x3 is incorrect. The expected value is 0x8d. Index entry RUB18E~1.TXT of index $I30 in file 0x71c86 points to unused file 0x22193c. Deleting index entry RUB18E~1.TXT in index $I30 of file 466054. The USA check value, 0x3835, at block 0x3 is incorrect. The expected value is 0x8d. Index entry rubt0110@customcoupon[1].txt of index $I30 in file 0x71c86 points to unused file 0x22193c. Deleting index entry rubt0110@customcoupon[1].txt in index $I30 of file 466054. The USA check value, 0x0, at block 0x3 is incorrect. The expected value is 0x2f2. Index entry D6EF~1.DOC of index $I30 in file 0x1cc634 points to unused file 0x221944. Deleting index entry D6EF~1.DOC in index $I30 of file 1885748. The USA check value, 0x0, at block 0x3 is incorrect. The expected value is 0x2f2. The USA check value, 0x6c12, at block 0x3 is incorrect. The expected value is 0x15b. Index entry 7C81~1.TIF of index $I30 in file 0x220428 points to unused file 0x221802. Deleting index entry 7C81~1.TIF in index $I30 of file 2229288. The USA check value, 0x6c12, at block 0x3 is incorrect. The expected value is 0x15b. The USA check value, 0x6c12, at block 0x3 is incorrect. The expected value is 0x15b. The USA check value, 0x3835, at block 0x3 is incorrect. The expected value is 0x8d. The USA check value, 0x0, at block 0x3 is incorrect. The expected value is 0x2f2. Cleaning up minor inconsistencies on the drive. CHKDSK is recovering lost files. Recovering orphaned file 7C81~1.TIF (2234370) into directory file 2229288. Recovering orphaned file RUB18E~1.TXT (2234684) into directory file 466054. Recovering orphaned file rubt0110@customcoupon[1].txt (2234684) into directory file 466054. Recovering orphaned file D6EF~1.DOC (2234692) into directory file 1885748. Cleaning up 1389 unused index entries from index $SII of file 0x9. Cleaning up 1389 unused index entries from index $SDH of file 0x9. Cleaning up 1389 unused security descriptors. CHKDSK is verifying Usn general... General verification completed. CHKDSK discovered free space marked as allocated in the master file table (MFT) bitmap. Windows has made corrections to the file system. 1422627839 KB total disk space. 1130215760 KB in 2165081 files. 981996 KB in 151133 indexes. 0 KB in bad sectors. 2788807 KB in use by the system. 65536 KB occupied by the log file. 288641276 KB available on disk. 4096 bytes in each allocation unit. 355656959 total allocation units on disk. 72160319 allocation units available on disk

Reply With Quote
  #2  
Old 26-05-2009
Member
 
Join Date: Dec 2007
Posts: 493
Re: Recovering orphaned file into directory file

So waited possible to overload the server.

On the restart it started chkdsk, began to check, hanging on the second step (verifying indexes) at 0%

Reboot in recovery console, ran chkdsk - in reply received a message that the check disk can not be (exact description, unfortunately, do not remember)

Reboot in safe mode, run chkdsk - hanging on the second step to 0%

The problem was never solved.
So far, as an interim measure, disable the disk to restart (as it already once had to go to work at night, after the established update and reboot the server and hanging on chkdsk'e)

Who could even suggest that?

Quote:
Maybe there is in the nature of any utility checks the disc, which does not require rebooting the server? "
Incidentally. The disc is not local - disk shelf to MSA1000, attached optics.
Reply With Quote
  #3  
Old 26-05-2009
Member
 
Join Date: May 2008
Posts: 297
Re: Recovering orphaned file into directory file

File system is wrong, the data is corrupted file system, these errors
software error
physical disk hardware failure
Why is that. Fsck command, the logical configuration of the file system check (audit), or by removing the incorrect part is used to repair.

fsck command to check the following items.

superblock
inodes
indirect blocks
derectory data block

fsck command automatically on system boot, check the file system is mounted. Check one or more of the files manually to the system, which only the unmounted file system can only check and repair.
One or more of the raw logical device names (partitions) will be specified by the argument of the fsck, mkfs command, such as by using the-F option is used to specify a file system check.

10001-F option is not specified, the default file system / etc / default / fs default is specified in the file system.

Do not add to the partition (raw logical device name), all the file system is specified, / etc / vfstab file is checked by referring to the list.
Reply With Quote
  #4  
Old 26-05-2009
Member
 
Join Date: May 2008
Posts: 335
Re: Recovering orphaned file into directory file

It is a low-level error at NTFS map. First try to make a backup of the data partition (although perhaps some may not be copied). '

1. Running the Command Prompt chkdsk c: / f / r Let chksdk run more (2-3 hours), can still resolve the issue. While chkdsk is running an error in Event Viewer - Application and Event Viewer - System?

2. Try a program of site-HDD manufacturer's website. It is possible to have bad links and then you too can be great, except for a
format and hope that the bad-will be isolated. Data can be lost in large part to recover after a format.
Reply With Quote
Reply

  TechArena Community > Software > Operating Systems
Tags: , ,



Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "Recovering orphaned file into directory file"
Thread Thread Starter Forum Replies Last Post
Stellar Phoenix Windows Data Recovery 5.0 crash on recovering mp4 file Punati Windows Software 4 12-07-2013 03:07 PM
after recovering the deleted file getting error - files are corrupted Ann Mery Windows Software 1 04-12-2011 01:37 AM
Windows Batch file to output directory names and size to txt file m2thearkus Software Development 6 16-07-2010 12:04 AM
.wav USB connected sandisk sansa audio recorder - this file or directory is corrupted and unreadable - file recovery - Chkdsk utility mirrorrorrim Portable Devices 2 17-08-2009 08:21 AM


All times are GMT +5.5. The time now is 11:29 PM.