RAID ARRAY disk Failure - Error code 2000-142 - Dell diagnostics Status 79

bigint

Commendable
Feb 25, 2016
7
0
1,520
Hi,

I removed some old MS Office products from my PC yesterday and added MS Office 2016. Today, when I switched on my PC and started browsing in Firefox, the PC froze and I got a blue screen error message: STOP CODE - Memory Management.

The PC went into recovery mode and rebooted, as the PC was starting again I noticed a disk 'error occurred' message in red where there are usually two disks listed in green.

The PC is a Dell Studio XPS 435MT, with an i7 processor and 6gb RAM and 2 x Seagate 465.7 GB SATA hard drives using RAID ARRAY 0, level RAID 0 (STRIPE).

The operating system is a Windows 10 Home premium upgrade.

The boot-up screen that flashes when Windows is starting shows the system status as normal and bootable ‘yes’. But, Windows goes into a cycle of ‘repairing disk errors this may take over an hour to complete’.

When my PC RAID ARRAY 0 failed last year, system diagnostics said the disks were OK and I could still access and use windows. So, I rebuilt the RAID ARRAY and all was fine.

This time though system diagnostics, give error message, 2000-142, hard drive self-test unsuccessful status 79.

Before, I replace the hard drive I am going to try to repair the PC with a Windows installation disk, like others suggest online.

What I want to know is, why isn’t Windows booting from the good drive (half of the ARRAY), like it did when I had a RAID issue last year?

Is there any way by pressing F12 at start-up that I can change a setting to get Windows to try and boot from the good disk in the ARRAY? Isn’t that what a RAID setup is for or am I missing something?

All I am getting when I restart is the repairing disk message ‘repairing disk errors this may take over an hour to complete’ which ends up with:

Windows has encountered a problem communicating with a device connected to your computer

File: \Boot\BCD

Status: 0x00000e9

Info: An unexpected I/0 error has occurred

Thanks for any pointers.
 

S Haran

Distinguished
Jul 12, 2013
219
0
18,910
I think you are confusing RAID0 (striped volume, no redundancy) with RAID1 (mirroring)

With RAID0 you need both drives functioning. Lose one drive and your data is gone.

You state a drive is failing diagnostics so something is wrong. You might check the SMART health of the drives with a tool like CrystalDiskInfo.

The way to proceed depends on whether you care about the data. Perhaps you have backups.
 

bigint

Commendable
Feb 25, 2016
7
0
1,520
Thanks for posting back. Data and my programs are important to me.

I looked into CrystalDiskInfo, but I can’t see it listed as Windows 10 compatible or how to use it from a USB, so I’m not sure what to do with it.

I placed some images online; here is the sharable link: https://drive.google.com/drive/folders/0B0CWqkH8saKedUlkc0pZdTJBYmM?usp=sharing

I found a post by ‘dad rules ok’ (here - http://www.pcguide.com/vb/showthread.php?69036-Dell-Error-Code-2000-0142) stating how he resolved the same issue by running ‘CHKDSK/ R’ from command prompt after booting the PC from a disc with a repair copy of Windows 10 on.

So, I downloaded a copy of Windows 10 onto a USB and booted from it. Although, I initially had difficulty navigating away from X:\Sources>, I eventually managed to run CHKDSK / R on the C drive, but it keeps failing at around “Scanning and repairing drive (C) 42% complete”.

I tried to run DISM too, that wouldn’t run. I get “DISM does not support servicing Windows PE with the /Online option” – How can I overcome this please? Please be specific, this is new to me.

What’s killing me is that when I look at the drives from Command Prompt using the copy of Windows on the USB, both disks in the ARRAY are listed as one 916GB ‘healthy’ drive.

And, I can navigate to the C drive directories and list them using the USB Windows command prompt – please see images at link above.

Also, when I start the PC normally, Windows goes into a repairing disk errors cycle, doesn’t that show that Windows is working is some capacity and the data is actually OK – right?

If so, should I be able, or is there another way I might be able to get into Windows from where I am? I have tried to get in using every device in the boot list and they all produce errors or go into the recovery cycle.

From research, the initial STOP CODE: MEMEORY MANAGEMENT error and disk reads errors, in hand with healthy disk messages suggest the drive is OK, but cannot be read.

I’m thinking that if Windows cannot repair from the copy of Windows 10 on the USB, it won’t clean install either – although, I really don’t want to do that anyway.

I just think there will be a solution to this. It seems like the data is accessible, if I can just get in.

I hear what you say about Raid setups and thanks for the information, but I still I cannot understand why when my PC RAID ARRAY failed last year and the failed drive was disabled by the system, I could still access and use windows on the good disk, but I can’t now.

Finally, If I replace the drive, will it be as easy as plugging in a new drive and rebuilding the Raid setup which some suggest online? Will my programs and data be copied over from the good disc to the new one or will I need to clone it using another PC please? If so, I’ll probably need to pay somebody to do that.

I've spent 2 days researching online and trying things, but I'm really unsure where to go from here? Any help is appreciated.

Thanks again.
 

bigint

Commendable
Feb 25, 2016
7
0
1,520
Hi All,

I though I'd update the thread:

My drives are Seagate, so today I downloaded Segate tools and burned the program onto a CD disc. After changing the boot device to the CD-Rom, I booted from Seagate Tools and ran some tests.

One drive was fine. The drive with issues failed the short test, so I ran the long test, which repairs faults, it failed that too. I checked 'repair this one and all others' when a dialogue box opened up after the long test, repairs were then successfully carried out on all the faults. The short test ran again automatically and the drive passed.

I got really excited as my PC re-booted only to be deflated as I saw 'Error Occurred' again at start-up. I ran Seagate tools again, errors were found again, but this time Seagate Tools offered no repair options.

So, I presume that's it, new drives are required.
 

S Haran

Distinguished
Jul 12, 2013
219
0
18,910
Okay you've established that you have a failing drive. The key to recovery depends on the possibility of taking a sector by sector clone image copy of the failing drive. If you can take a high quality image then you can use it with the good drive to reassemble the RAID0 and recover your data.

There are tools like Linux ddrescue and hddsuperclone that are designed to image failing drives. But there is a risk the imaging process may cause further damage. So if this is high value data seek the help of a data recovery lab.

If you still want to pursue a DIY solution and need help I do a lot of work in this area and am happy to assist remotely if you like.



 

bigint

Commendable
Feb 25, 2016
7
0
1,520
Hi,

Thank you, S Haran. I really appreciate the offer; I might take you up on it.

The situation is: I build websites for a living, so I contacted a local PC repair guy and asked him if he wanted to swap a PC repair for some web development work. He sounded keen; I'm just waiting to hear back.

If we can't do a deal, it's down to me and I will definitely need guidance.

Thanks again.