Updated to Windows 8.1 after group policy errors. Disk Management now shows RAID 0 disk with only one drive.

Robert Spina

Honorable
Jan 24, 2014
4
0
10,510
My 2x 1TB WD SATA NTFS RAID 0 HDD setup is having a major problem. Only one drives is being recognized in Disk Management after I had to reformatted (because of a major group policy error the locked my out of my most important service) my OS and updated to windows 8.1. Now all of my files have been removed and only half can be retrieved from a partition recovery. Chkdsk will not fix it and diskpart isn't working correctly. Refreshing windows doesn't work and made things worse. Partition recovery is recognizing the RAID 0 array and with both drives as healthy in BIOS. In the partition recovery I am being shown with a lot of the files as a RAW file system.

So here's how it all started out. I created a VPN with my ASUS NT56u router awhile back and ended up deleting it. I ended up ruining my group permissions and couldn't get access to services and when I tried to start them I would get error messages. What I think is happening here is I got locked out of the one of the drives because chkdsk wouldn't and still wont repair the disks and says I am locked out of them.

I did a computer refresh and I was able to reformat windows. (Note my BIOS says my RAID 0 array has both drives but windows only recognizes one of the drives. Disk management says its 988GB when it should be 1.8TB.) From there every time I tried to update drives and devices the computer would either freeze or I'd get BSOD storahci.sys errors, so I upgraded to windows 8.1. THAT F'd everything up. All of my files were removed from the system and I had to reformat windows again.

Every time I restarted my computer I would have to reformat. Now I got my computer to where I don't have to reformat but Disk Mananger is still recognizing only one of the two RAID drive. Partition recovery is recognizing the 150 different partitions but a lot of the files have turned RAW or are lost.

Even with a RAID 0 I know you can get your files back with high quality partition recoveries. I know something is wrong with that drive and I don't know how to fix it because I HAVE TRIED EVERYTHING. I can recover some of the files but not all. Is there any way where I can find a .sys file or a system partition image file or some kind of data I can load from a partition recovery to my OS that can fix this.

Some of the RAW files when recovered work but have a video thumbnail but play music. None of the files should be RAW so I don't know how this inaccessible drive has turned RAW when it should be NTFS.

I greatly thank whoever fixes this problem because I have about 1.4TB of data I need to recover.

***ADDED***:

-I am also willing to find thedata in HEX Key and using a HEX editor to get all the files back.

-Recovering the non RAW drive files have the same file size as the original files when I download them but they just wont open

◄◄◄ = Some problems I have noticed

OS Name Microsoft Windows 8 Pro
Version 6.2.9200 Build 9200
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name PC-Rom
System Manufacturer ASUS
System Model All Series
System Type x64-based PC
System SKU All
Processor Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz, 3501 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1205, 06/26/13
SMBIOS Version 2.7
Embedded Controller Version 255.255
BIOS Mode Legacy
BaseBoard Manufacturer ASUSTeK COMPUTER INC.
BaseBoard Model Not Available
BaseBoard Name Base Board
Platform Role Desktop
Secure Boot State Unsupported
PCR7 Configuration Binding Not Possible
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume1 ◄◄◄ (No Drive Letter & the volume was called Volume0)
Hardware Abstraction Layer Version = "6.2.9200.16384"
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.94 GB
Available Physical Memory 5.01 GB
Total Virtual Memory 23.5 GB ◄◄◄
Available Virtual Memory 19.7 GB

Hardware Storage

Drives:

Drive C:
Description Local Fixed Disk
Compressed No
File System NTFS
Size 922.83 GB (990,878,101,504 bytes) ◄◄◄ (Should be 2000.1GB)
Free Space 883.09 GB (948,210,614,272 bytes)
Volume Name
Volume Serial Number C64B2311

Drive D:
Description CD-ROM Disc

Drive E: ◄◄◄ (These are SSD)
Description Local Fixed Disk
Compressed No
File System NTFS
Size 1.82 TB (2,000,395,694,080 bytes)
Free Space 1.82 TB (1,999,187,578,880 bytes)
Volume Name Seagate Backup Plus Drive
Volume Serial Number 924A0220

Drive F: ◄◄◄ (These are SSD)
Description Local Fixed Disk
Compressed No
File System NTFS
Size 232.88 GB (250,057,060,352 bytes)
Free Space 114.51 GB (122,952,523,776 bytes)
Volume Name New Volume
Volume Serial Number 5E27B8B2

Disks:

Description Disk drive
Manufacturer (Standard disk drives)
Model Volume1 ◄◄◄ (It used to be called Volume0)
Bytes/Sector 512
Media Loaded Yes
Media Type Fixed hard disk
Partitions 2
SCSI Bus 0
SCSI Logical Unit 0
SCSI Port 0
SCSI Target ID 0
Sectors/Track 63
Size 1.82 TB (2,000,379,870,720 bytes)
Total Cylinders 243,199
Total Sectors 3,906,991,935
Total Tracks 62,015,745
Tracks/Cylinder 255
Partition Disk #0, Partition #0
Partition Size 350.00 MB (367,001,600 bytes)
Partition Starting Offset 1,048,576 bytes
Partition Disk #0, Partition #1
Partition Size 922.83 GB (990,878,105,600 bytes)
Partition Starting Offset 368,050,176 bytes

Description Disk drive (External to recover to) ***NOT IMPORTANT***
Manufacturer (Standard disk drives)
Model Seagate Backup+ Desk SCSI Disk Device
Bytes/Sector 512
Media Loaded Yes
Media Type Removable media
Partitions 1
SCSI Bus 0
SCSI Logical Unit 0
SCSI Port 3
SCSI Target ID 0
Sectors/Track 63
Size 1.82 TB (2,000,396,321,280 bytes)
Total Cylinders 243,201
Total Sectors 3,907,024,065
Total Tracks 62,016,255
Tracks/Cylinder 255
Partition Disk #1, Partition #0
Partition Size 1.82 TB (2,000,395,698,176 bytes)
Partition Starting Offset 1,048,576 bytes

Description Disk drive (External to recover to) ***NOT IMPORTANT***
Manufacturer (Standard disk drives)
Model Seagate FreeAgent Go USB Device
Bytes/Sector 512
Media Loaded Yes
Media Type Removable media
Partitions 1
SCSI Bus 0
SCSI Logical Unit 0
SCSI Port 0
SCSI Target ID 0
Sectors/Track 63
Size 232.88 GB (250,056,737,280 bytes)
Total Cylinders 30,401
Total Sectors 488,392,065
Total Tracks 7,752,255
Tracks/Cylinder 255
Partition Disk #2, Partition #0
Partition Size 232.88 GB (250,057,064,448 bytes)
Partition Starting Offset 1,048,576 bytes

SCSI:

Name Intel(R) ICH8R/ICH9R/ICH10R/DO SATA RAID Controller
Manufacturer Intel
Status OK
PNP Device ID PCI\VEN_8086&DEV_2822&SUBSYS_85341043&REV_04\3&11583659&0&FA
I/O Port 0x0000F090-0x0000F097
I/O Port 0x0000F080-0x0000F083
I/O Port 0x0000F070-0x0000F077
I/O Port 0x0000F060-0x0000F063
I/O Port 0x0000F020-0x0000F03F
Memory Address 0xF5136000-0xF51367FF
IRQ Channel IRQ 19
Driver c:\windows\system32\drivers\iastorv.sys (8.6.2.1019, 402.23 KB (411,888 bytes), 06/02/12 7:32 AM)

Name Microsoft Storage Spaces Controller
Manufacturer Microsoft
Status OK
PNP Device ID ROOT\SPACEPORT\0000
Driver c:\windows\system32\drivers\spaceport.sys (6.2.9200.16384, 277.23 KB (283,888 bytes), 07/25/12 7:28 PM)

Name USB Attached SCSI (UAS) Mass Storage Device
Manufacturer USB Attached SCSI (UAS) Compatible Device
Status OK
PNP Device ID USB\VID_0BC2&PID_A0A4\MSFT30NA5KWSNF
Driver c:\windows\system32\drivers\uaspstor.sys (6.2.9200.16384, 94.73 KB (97,008 bytes), 07/25/12 7:27 PM)

IDE:

Name Standard SATA AHCI Controller
Manufacturer Standard SATA AHCI Controller
Status OK
PNP Device ID PCI\VEN_1B21&DEV_0612&SUBSYS_858D1043&REV_01\4&1933C71D&0&00E1
I/O Port 0x0000C050-0x0000C057
I/O Port 0x0000C040-0x0000C043
I/O Port 0x0000C030-0x0000C037
I/O Port 0x0000C020-0x0000C023
I/O Port 0x0000C000-0x0000C01F
Memory Address 0xF7B00000-0xF7B001FF
IRQ Channel IRQ 17
Driver c:\windows\system32\drivers\storahci.sys (6.2.9200.16384, 75.73 KB (77,552 bytes), 07/25/12 7:30 PM)

Name Standard SATA AHCI Controller
Manufacturer Standard SATA AHCI Controller
Status OK
PNP Device ID PCI\VEN_1B21&DEV_0612&SUBSYS_858D1043&REV_01\6&366007D&0&004800E3
I/O Port 0x00009050-0x00009057
I/O Port 0x00009040-0x00009043
I/O Port 0x00009030-0x00009037
I/O Port 0x00009020-0x00009023
I/O Port 0x00009000-0x0000BFFF
Memory Address 0xF7600000-0xF76001FF
IRQ Channel IRQ 16
Driver c:\windows\system32\drivers\storahci.sys (6.2.9200.16384, 75.73 KB (77,552 bytes), 07/25/12 7:30 PM)
 
Solution
On a side note, why does a jukebox need such a horrendously huge swap file AND 8Gb ! Meybee Wyn 8 do gots a memory leak. Keep extracting the .RAW files and open them each with your hex editor and look at the first four characters . 4CCode - and that will tell you what three letter dot extension to rename video files so they will open with the right player instead of music. And if you don´t see video but hear audio then you need a codec.
http://www.shouldiremoveit.com/IntelliMemory-28211-program.aspx
http://www.tomshardware.com/forum/840-73-windows-extremely-high-memory-usage

Robert Spina

Honorable
Jan 24, 2014
4
0
10,510
Yes I am 110% positive. On start-up it shows my two hard drives setup as a RAID 0 strip. But my Disk management should only show the two drive as one big drive since the RAID is setup in the BIOS.

i2n2vn.jpg


2pyoqpt.jpg
 

Robert Spina

Honorable
Jan 24, 2014
4
0
10,510
I am able to find all my files in the partition recovery software but maybe since the RAID isn't written correctly the files are showing up as lost. When I try to recover them most of them wont open properly while others are not the full length files. I am also able to retrieve a folder called system volume information, I found some folders that have chkdsk information on them, and also some registry key formats if that helps. Maybe if somebody could show me how to retrieve the files properly and re-write the changed file system/RAID 0 setup maybe I could get these files back.

Here's chkdsk showing that the NTFS is only finding one drive.

2wbrcpv.jpg


Here's chkdsk showing that it cannot lock the drive. When I restart the computer and uses the BIOS to repair the disk it goes straight to 100% and doesn't repair anything.

2mdguvr.jpg


***ADD***
- windows 8 is installed but it should be windows 8 pro
- can I use a partition editor to drive and fix the permissions on the drive because I know that has something to do with it.
- some service aren't running when the computer starts and I have to start them on my own
- I can't update my devices and when I scan for new hardware the computer freezes

 

Robert Spina

Honorable
Jan 24, 2014
4
0
10,510
If I remove the UEFI RAID 0 partition in bios and reformat will a high quality software like iCare or R-Studios still find the partitions?

R-Drive shows that it is a RAID 0 but the disk only has one drive.

iy3hi1.jpg
 

RnTk

Honorable
Feb 8, 2014
14
0
10,520
Here is what RAID 0 does: Spans two drives to make them look like one single partitionable area. NTFS puts a directory somewhere within that structure physically in the middle, hopefully but not necesecarily spanning both drives since the hardware hides the fact of two seperate devices , but the FACT is that the refresh format repurposed the first gigabytes of one with new data during the Armageddon trip 8.1 back to Windows 8, definitely overwriting the first drive´s initial begining area but luckily not with enough bloat to mutilate the contents of both directories since the hence the recoverable names but unusable files. Since it was not a compressed nor encrypted volume the difference in directory locations of single vs. spanned layout spared the central directory area that served both drives, and the fact that the file name area is readable proves that the cluster sizes remained the same.
 

RnTk

Honorable
Feb 8, 2014
14
0
10,520
But rather than dwell on NTFS and RAID 0, I should explain how data recovery software like Spinrite works. It ignores dying HDD hardware´s attempts to rescue itself and takes guesses at what it sees on damaged areas of unusable drives. You don´t have a failing drive, you have the healthy equivalent of a 2TB area repartitioned to 1TB and thus partially reused single hard drive, and the longer you continue to fill it and actively use it in the system, the more data goes bye+bye. But your more pressing problem is that hardware scans malfunction and I believe you are in Safe Mode which is why some drivers must be started manually AND why the 2nd drive is not usable. I believe that the storahci error was your raid controller going bats over something, possibly an IRQ conflict or chip creep or bad data or power supply cable, which you tried to fix ethereally with faulty software. Yep, 8.1 preview is newly obsolete. There is probably a controller bootup menu to setup RAID controller but do NOT use it before you repair your HW bug first. And stop squeezing the Charmin; don´t boot from those two drives anymore just remove and send BOTH off to forensics because once you get out of Safe Mode, PNP will work again and drivers and updates will load and bloat until all the old data on BOTH drives is gone. The refresh already put 988Gb of data in peril - and you are lucky that that whole 2TB is not occupied or the directory area would become unrecoverable, too.
 

RnTk

Honorable
Feb 8, 2014
14
0
10,520
On a side note, why does a jukebox need such a horrendously huge swap file AND 8Gb ! Meybee Wyn 8 do gots a memory leak. Keep extracting the .RAW files and open them each with your hex editor and look at the first four characters . 4CCode - and that will tell you what three letter dot extension to rename video files so they will open with the right player instead of music. And if you don´t see video but hear audio then you need a codec.
http://www.shouldiremoveit.com/IntelliMemory-28211-program.aspx
http://www.tomshardware.com/forum/840-73-windows-extremely-high-memory-usage
 
Solution