Drobo

Event 51 errors

I have a Drobo connected via USB to a Windows XP SP3 pc with drobo dashboard 1.5.1 and drobo firmware 1.3.5.

I have three of the four drive bays in use.

My windows registiry shows many errors like this:
( by many I mean several hundred in a few months sometimes 6 a day)

Event Type: Warning
Event Source: Disk
Event Category: None
Event ID: 51
Date: 10/19/2009
Time: 6:06:16 AM
User: N/A
Computer: BART
Description:
An error was detected on device \Device\Harddisk2\D during a paging operation.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 03 00 68 00 01 00 b6 00 …h…¶.
0008: 00 00 00 00 33 00 04 80 …3…€
0010: 2d 01 00 00 00 00 00 00 -…
0018: 00 00 00 00 00 00 00 00 …
0020: 00 00 00 00 00 00 00 00 …
0028: 14 dc 3a 04 00 00 00 00 .Ü:…
0030: ff ff ff ff 03 00 00 00 ÿÿÿÿ…
0038: 40 00 00 49 00 00 00 00 @…I…
0040: 00 20 0a 12 48 02 20 40 . …H. @
0048: 00 10 00 00 0a 00 00 00 …
0050: 00 00 00 00 b0 b5 3c 8a …°µ<Š
0058: 00 00 00 00 50 7c fe 88 …P|þˆ
0060: 00 00 00 00 af 00 00 00 …¯…
0068: 28 00 00 00 00 af 00 00 (…¯…
0070: 08 00 00 00 00 00 00 00 …
0078: 00 00 00 00 00 00 00 00 …
0080: 00 00 00 00 00 00 00 00 …
0088: 00 00 00 00 00 00 00 00 …

The knowledge base refers to a possible failure of TWO disks.

How can I check if one of my disks has a failure.

I would first recommend running CHKDSK from the command prompt.

Thanks Jennifer, I run the chkdsk on Friday.

On Sunday I got over 1700 errors of the same type during my backup process. As well as those error, there are new disk errors, Error: 57 , Error: 50 as well as pop-ups regarding the “Delayed Write” situation.

My drobo actually stopped working until I unplugged it and plugged it back in again.

My backup implements “Volume Shadow Copy”. Is this somehow related to the problem?

Again, I’d like a way to test the actual drives to see if any are failing. How can I do this?

Sincerely,

Peter

Event Type: Warning
Event Source: Ftdisk
Event Category: Disk
Event ID: 57
Date: 10/25/2009
Time: 8:45:01 AM
User: N/A
Computer: BART
Description:
The system failed to flush data to the transaction log. Corruption may occur.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 01 00 be 00 …¾.
0008: 02 00 00 00 39 00 04 80 …9…€
0010: 00 00 00 00 0e 00 00 c0 …À
0018: 00 00 00 00 00 00 00 00 …
0020: 00 00 00 00 00 00 00 00 …

Event Type: Warning
Event Source: Ntfs
Event Category: None
Event ID: 50
Date: 10/25/2009
Time: 8:45:01 AM
User: N/A
Computer: BART
Description:
{Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 04 00 02 00 52 00 …R.
0008: 00 00 00 00 32 00 04 80 …2…€
0010: 00 00 00 00 0e 00 00 c0 …À
0018: 00 00 00 00 00 00 00 00 …
0020: 00 00 00 00 00 00 00 00 …
0028: 0e 00 00 c0 …À

Event Type: Warning
Event Source: Ntfs
Event Category: None
Event ID: 50
Date: 10/25/2009
Time: 8:45:01 AM
User: N/A
Computer: BART
Description:
{Delayed Write Failed} Windows was unable to save all the data for the file . The data has been lost. This error may be caused by a failure of your computer hardware or network connection. Please try to save this file elsewhere.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 04 00 04 00 02 00 52 00 …R.
0008: 00 00 00 00 32 00 04 80 …2…€
0010: 00 00 00 00 0e 00 00 c0 …À
0018: 00 00 00 00 00 00 00 00 …
0020: 00 00 00 00 00 00 00 00 …
0028: 0e 00 00 c0 …À

Open a support case and attach a diagnostic file so we can review it and look at the drives.

I have had a similar problem on my 2nd Gen Drobo. I submitted the drobo log to DRI for analasys. In my case, I pulled each drive out one by one and ran Hitachi’s DFT scan on each and they all passed. I guess that doesn’t mean that one of them couldn’t still have an intermitant problem but I was under the asumption that if it were failing, the Drobo would let me know…

I’ll post back if there is a solution from my submission

I had severe problems with my USB connection to the Drobo. I finally find out that it was the motherboard that had some kind of problem. After replacing it I had no more problems and the Dobo was stable as a rock.

http://www.drobospace.com/forums/showthread.php?tid=883

I have an ugly suspicion growing in the back of my mind regarding the motherboard as the culpret. DRI didn’t find any faults in the Drobo log…

Well, no resolution to my problem was ultimately reached in dealing with Drobo support but they were very helpfull and I don’t believe the problem was with the DROBO itself.

Interestingly, I had a PCI slot go bad on the main board…

My final resolution was to install linux on an older PC that wasn’t being used and hook the DROBO up to it via Firewire 800 shared on the network via Samba. I couldn’t be happier. It’s much faster and stable as a rock now. I am getting read speeds averageing 38MBps over gigabit.

PCI slots going bad on the motherboard is definitely not a good sign. Your problem PC might have a short (can happen if you have an extra standoff installed), a power supply problem, or a problem with the motherboard itself. Either way, I’d retire that PC before it kills anything else.