An error was detected on device \device\harddisk0\dr0 during a paging operation
Hello,
I have a windows server 2008 machine, that only has one logical hard drive(2 physical in RAID1) with the following error.
An error was detected on device \Device\Harddisk0\DR0 during a paging operation.
I have run the builtin HP RAID manager, and it says that both disks are healthy and the RAID array is normal, I have also reboot, and there are no errors in the post, and it boots up fine.
To attempt to fix I have changed the size of the page file, rebooted, but that didn't fix it. Normally I would move the file to another HD but this is the only one present.
Also AD users and computers locks up after about 36 hours, on this domain controller only, this error is what made me start to look at the event viewer.
Any Ideas? Do I have a bad HD, if so how do I know which one it is so that I can swap it out. This server is no longer critical can be reformatted, but I don't know if this is a hardware or software problem
I have a windows server 2008 machine, that only has one logical hard drive(2 physical in RAID1) with the following error.
An error was detected on device \Device\Harddisk0\DR0 during a paging operation.
I have run the builtin HP RAID manager, and it says that both disks are healthy and the RAID array is normal, I have also reboot, and there are no errors in the post, and it boots up fine.
To attempt to fix I have changed the size of the page file, rebooted, but that didn't fix it. Normally I would move the file to another HD but this is the only one present.
Also AD users and computers locks up after about 36 hours, on this domain controller only, this error is what made me start to look at the event viewer.
Any Ideas? Do I have a bad HD, if so how do I know which one it is so that I can swap it out. This server is no longer critical can be reformatted, but I don't know if this is a hardware or software problem
http://support.microsoft.com/kb/244780 has some good information on troubleshooting that error. There's a lot of information in the event that is recorded that you haven't posted, so it's hard to tell you exactly what is going on. You should also run chkdsk on the drive to make sure there isn't a file system error causing your problems. You can only run that in Read Only mode while the OS is running, but if it finds errors you can then set it to run again after reboot to fix any errors it finds.
ASKER
acbrown2010:
I completely forgot, I tried to run chkdsk a week ago and I get an error that the disk is in RAW format and now NTFS. Disk management shows the same thing. I don't know how long it has been this way.
I completely forgot, I tried to run chkdsk a week ago and I get an error that the disk is in RAW format and now NTFS. Disk management shows the same thing. I don't know how long it has been this way.
ASKER
Sorry I just doublechecked the command prompt says that the disk is raw when I run chkdsk, but disk management shows NTFS as the file system
That is probably the root of your problem. I haven't run into that issue before, but it seems like the file system has lost its mind. Not necessarily a problem with the drives themselves. The only solutions I'm seeing to that is a backup/format/restore.
ASKER
acbrown2010:
I don't want to spend too much time on this because I can use other DCs, but I wonder if this will pop up if I reformat the server? I kind ofneed a new WSUS server. So I plan on shutting this down, waiting a week to see if anything else breaks or if there are any dependencies, and then reformatting. I'm not sure if I want to use new hard drives or not.
I don't want to spend too much time on this because I can use other DCs, but I wonder if this will pop up if I reformat the server? I kind ofneed a new WSUS server. So I plan on shutting this down, waiting a week to see if anything else breaks or if there are any dependencies, and then reformatting. I'm not sure if I want to use new hard drives or not.
Well, if you can pull this particular DC out of operation and re-purpose it, that would probably be a good idea. The errors you're getting doesn't really seem to suggest hardware failure, but that may not be too far down the road. If you reformat, it should resolve the file system errors, but I can't guarantee that they won't pop up in the future because the general cause is likely file system corruption, which can have any number of root causes. Just make sure to properly demote the DC before you take it offline for good, otherwise you will run into some problems down the road.
looks like you have a munged filesystem. rebuild the raid and the os from scratch, as if this was a full install.
you can't trust any file without looking at lots of log files and comparing . not worth the effort since you have other DCs.
the hardware could be perfectly fine. the read error could be file system related ... like trying to read block number -1
you can't trust any file without looking at lots of log files and comparing . not worth the effort since you have other DCs.
the hardware could be perfectly fine. the read error could be file system related ... like trying to read block number -1
looks like you have a munged filesystem. rebuild the raid and the os from scratch, as if this was a full install.
you can't trust any file without looking at lots of log files and comparing . not worth the effort since you have other DCs.
the hardware could be perfectly fine. the read error could be file system related ... like trying to read block number -1
you can't trust any file without looking at lots of log files and comparing . not worth the effort since you have other DCs.
the hardware could be perfectly fine. the read error could be file system related ... like trying to read block number -1
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Great advice, Thanks
Specifically what disks do you have?
If you do have the proper enterprise drives, then check your controller (HP has many) to see if there is an option for automatic patrol operations, and enable it. This will automatically fix bad blocks 24x7 in the background by reading all blocks on all disks and keeping them in sync. This way it will repair bad blocks by getting what it needs from the other drive, during idle time. It will eliminate those long waits for I/O.
The HP RAID Manager has some sort of event log... post it (as ascii text in body of message, as that is easiest to read). The \device\harddisk\dr0 is from windows O/S, and if it is a read I/O error, and the block number is not some invalid block number that doesn't exist .. due to a file system corruption issue, then the error means BOTH disks have a bad block at the same place.
NO cure for that other than to restore the damaged file, as part of that file is on an unreadable block.