The device, \Device\Harddisk2\DR2, has a bad block.

Raid - Physical ViewRaid - Logical ViewHi,
  I have SBS2011 with 6 HDs on RAID 10. Yesterday it lost network connection (I could not access it from workstation PCs for files and email). So I tried to restart it, but it got stock in "Please wait for the Group Policy Client...". After waiting 30 minutes, I manually powered it down and turned it back on. Luckily the server came up without any issues.
  When I check "System" log in Event Viewer, I see the following error literally every single second. "The device, \Device\Harddisk2\DR2, has a bad block" Event ID: 7, Source: Disk
Also I see this message constantly "The system failed to flush data to the transaction log. Corruption may occur." Event ID: 57  Source: Ntfs

So I open LSI MegaRaid Storage Manger and everything looks normal and all the lights on hot-swap Hard drives are green with no alarm sound

How do I address this issue?

Thanks.
LVL 1
sgleeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gary ColtharpSr. Systems EngineerCommented:
The Physical Device Object Name property in the properties of the drive in windows should help you identify to which disk the error is referring specifically. Are there any other drives attached? ie; USB etc?

Once the drive is identified, an offline chkdsk with repair. You may also check to see if there is a paging file on the drive once it has been identified and reinitialize it by unsetting it, rebooting and resetting it.

HTH
Gary
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Chris MillardCommented:
I don't think the alarms will sound for bad blocks - only with disk failures. The best option is to replace the failed disk as soon as possible and let the raid rebuild. If you end up with another drive going down whilst this one is faulty, you could end up with some major data loss.
0
Ricardo MartínezInformation SecurityCommented:
Replace is the best idea if you have bad sectors and have identified the disk with them, but you can also remove the disk, do a chkdisk to attempt the recovery of those sectors, if it works, re attach the disk to fix the arrange, or you also can do a low level format and rebuild the RAID with the same disk after formatting it.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

sgleeAuthor Commented:
Disk ManagementEvent ViewerUpdate:
I made an error in my original posting.
Those two errors stopped as of 6AM yesterday and I had to hard-reset the server about 5PM yesterday. There is nothing recorded between 6AM and 5:11PM.

I traced "Harddisk2" to the External USB Hard Drive for Windows Server Backup.
I will move it to my computer and run Seatools against it.

I still need to find out what caused the server crash.
0
Gary ColtharpSr. Systems EngineerCommented:
What was this volume used for? SBS Backup or just archive storage?

I realize the server was unreachable via network but was it blue screened or unresponsive at the console?

HTH
Gary
0
Chris MillardCommented:
It's possible that some activity to / from that external hard drive was causing the issue. I take it that the USB drive was connected to the server at the time you lost connectivity?
0
sgleeAuthor Commented:
What was this volume used for? SBS Backup or just archive storage? --> SBS Backup. I have two 2TB External USB HDs  that I rotate once a week.

I realize the server was unreachable via network but was it blue screened or unresponsive at the console? --> There was no BSOD (thank god!). Also I was able to do Ctrl-Alt-Del to log in and try to restart the server. But unfortunately it got stock at "Please wait for the Group Policy Client..." screen during shutdown and that's when I did "hard reset".
0
sgleeAuthor Commented:
I take it that the USB drive was connected to the server at the time you lost connectivity?  --> Yes
0
Don ThomsonCommented:
Even though the backup drive shows in the Storage devices - There is normally no drive letter assigned to it. Kind of hard to fix it if you can't see it.

Assign a drive letter to it and then do a chkdsk  on it - It should fix the bad block problem - After you are done, Take off the drive letter and reapply the Backup settings
0
Gary ColtharpSr. Systems EngineerCommented:
I would doubt that the backup drive had anything to do with the unresponsive issue. Getting to the bottom of the event without any hints in the event log may be difficult. Maybe chalk it up to a glitch and move on, keeping a close eye on it.

HTH

Gary
0
sgleeAuthor Commented:
I am running chkdsk on the external USB HD. It is taking a long time. I will keep you posted.
0
sgleeAuthor Commented:
Here is the result of the chkdsk repair in Event Viewer. I see some "error corrections", but I dont' even see any bad sections reported.
Do you think these errors could have caused for SBS2011 to loose the network connection and fail to restart (stuck at "Please wait for the Group Policy Client...")?
-----------------------------------------------------------------------------------------------
Cleaning up 1 unused index entries from index $SII of file 0x9.
Cleaning up 1 unused index entries from index $SDH of file 0x9.
Cleaning up 1 unused security descriptors.
CHKDSK is verifying file data (stage 4 of 5)...
File data verification completed.
CHKDSK is verifying free space (stage 5 of 5)...
Free space verification is complete.
The upcase file content is incorrect.
Correcting errors in the uppercase file.
Windows has made corrections to the file system.

1953491967 KB total disk space.
1576055852 KB in 42 files.
        52 KB in 17 indexes.
         0 KB in bad sectors.
    125819 KB in use by the system.
     65536 KB occupied by the log file.
377310244 KB available on disk.

      4096 bytes in each allocation unit.
488372991 total allocation units on disk.
  94327561 allocation units available on disk.
-----------------------------------------------------------------------------------------------
0
Gary ColtharpSr. Systems EngineerCommented:
I would stand by my comment that they were unrelated. Have you examined the event periods in the event logs for errors? If you can't find any evidence, it goes in the glitch bin.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Storage Hardware

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.