Logfile too large to paste into your forum message? SUBMIT LOGFILE HERE |
|
Welcome to the DIY DataRecovery Support Forum!
The Forum is monitored working days from 9.00 AM - 5.00 PM (Central European Time). IMPORTANT! This forum is no longer monitored and is read-only. Visit our new forum! |
|
General Forum
Author
Comment
A Windows 2000 Server had a hard/ dirty shutdown due to a power outage. The partition on which the OS resides is acessible by Windows and the Server will boot up. However, the additional drives show as unallocated. I have run diskpatch and here is the log file: Product you are using: diskpatch 2.0 Standard Operating system / Service Pack: Windows Server 2000 Size of subject harddisk: Raid 5 135 Gb Feb 9th, 2005 - 12:53 AM
Hello, Feb 9th, 2005 - 10:17 AM
The 135 Gb disk is dynamic and has ben from the start. It is actually 3 72 Gb disks running in Raid 5, so I think the 48 bit addressing is not an issue. Product you are using: diskpatch 2.0 Standard Operating system / Service Pack: Windows Server 2000 Size of subject harddisk: Raid 5 135 Gb Feb 9th, 2005 - 3:56 PM
Here is the newest log file, however it is not dp.log, I am unable to find a dp.log, this file is dp.txt. I will also submit the dp.lo5 file via your log file submission link. Product you are using: diskpatch 2.0 Standard Operating system / Service Pack: Windows Server 2000 Size of subject harddisk: Raid 5 135 Gb Feb 9th, 2005 - 8:12 PM
Hello, Feb 10th, 2005 - 1:08 PM
I updated Windows Server 2000 to Service Pack 4 and changed the EnableBigLBA registry to perform 48 bit addressing, actualy I used the EnableBigLBA tool on www.48bitlba.com. Product you are using: diskpatch 2.0 Standard Operating system / Service Pack: Windows Server 2000 Size of subject harddisk: Raid 5 135 Gb Feb 11th, 2005 - 1:22 AM
Here is the latest log file. Product you are using: diskpatch 2.0 Standard Operating system / Service Pack: Windows Server 2000 Size of subject harddisk: Raid 5 135 Gb Feb 11th, 2005 - 5:38 PM
Hello, Feb 14th, 2005 - 9:53 AM
Here is the log file from iRecover. It did error out, but here is what I got in the log. If there is a particular iRecover configuration that I need to run, please let me know. Product you are using: iRecover Demo Operating system / Service Pack: Windows 2000 Server SP4 Size of subject harddisk: 135 Gb Raid 5 (3 72Gb physical drives) Feb 14th, 2005 - 10:01 PM
So I am running iRecover again, and I am asked to Select a File Record Segment (FRS) size from a list, but the list is completely blank and unpopulated. I am unable to select a FRS size and unable to proceed to the next step in the iRecover scan. This scan, like my first, is an Advanced scan. My second scan was a simple scan, that is when I recieved the 'No Value Selected' after a portion of the scan, I believe Part 1, had completed. Product you are using: DiskPatch Operating system / Service Pack: Windows Server 2000 Feb 15th, 2005 - 12:29 AM
From all the information you have supplied it seems that only 1 conclusion can be drawn: the disk is completely empty. No data of any kind has been found sofar, no disk structures, nothing. So obviously there's nothing to recover. I can't think of a scenario that wipes a disk this thorough that has anything to do with power outage, but it would almost make you think something's fishy on a hardware level. Or something else has happened. Anyway, we can't get anything from this disk 'cause there doesn't seem to be anything on it. Sorry. |