Link to home
Create AccountLog in
Avatar of lloving
lloving

asked on

Event ID 7 \Device\Harddisk1\DR1 has bad block that cannot be cleared

Trying to fix "Event ID 7 \Device\Harddisk1\DR1 has bad block". 

Assuming \Device\Harddisk1\DR1\ is referring to the C: drive on this device (Windows Server 2019 Standard) I have run Chkdsk /f /r but the error(Event 7) persists. 

ChkDsk with no switches returns no errors. 


Backup app will not complete due to CRC errors that I am assuming are related to the Event ID7 "\Device\Harddisk1\DR1 has bad block"



Avatar of CompProbSolv
CompProbSolv
Flag of United States of America image

What options did you run with chkdsk?

If this is a single physical drive (not a RAID array or VM), consider running the most extensive test that the drive manufacturer provides.

Keep in mind that passing any disk test is not complete assurance that there are no problems.  Failing one is usually a very strong indication that there IS a problem.

I would have concerns about the integrity of the drive and would strongly consider replacing it.  What make and model is it?  A sector-by-sector copy to a different drive is a good way both to image the drive for replacement as well as to test the drive for read errors.
Avatar of lloving
lloving

ASKER

This is a Dell PowerEdge T440. Hard drive is a 1TB 7.2K RPM SATA 6Gbps 512n 2 .5in Hot-plug Hard Drive. Looks like a sector by sector clone is in order.
I would look at a 1T (if that's the capacity you need) SSD to replace the HD.
Avatar of lloving

ASKER

Good point on the SSD
are you  SURE disk1 refers to the C: drive?
what other drives are connected?
i have HDDRegenerator to run on such drives - it fixes many bad sector problems - but it is not free    http://www.dposoft.net/hdd.html      

The error you reported related to a Physical disk drive. Windows numbers physical disks starting with 0.  The disk numbers have no particular relationship with the partitions on the disks or the partition you boot from (C drive).  

Chkdsk only checks within a partition, not an entire physical disk.

You can use disk manager to see what partitions reside on disk 1.  Then try chkdisk on each partition located on drive 1.
Avatar of lloving

ASKER

HardDisk1 has only one partition. ChkDsk /f yeilds no errors.
That said the repetitive nature of these Events gives me concern about that drive. I may replace it while it thinks its healthy.
Keep in mind that chkdsk /f only looks for logical errors.  If you want to test the readability of the whole drive (whether or not there is data there), use chkdsk /r .  Be aware that it will take much longer.
check the drive model, and use the manufacturers diagnostic tool to test it ( complete scan)
I think its a good idea to replace the disk, why take a chance.  

However, compPorbSolv and Nobus have good suggestions, and I would add HDTune.  The free version includes some tests including a sector scanner.  
See: http://www.hdtune.com/download.html

Keep in mind, any disk problems have the remote possibility of being aggravated by intense testing, depending on the underlying issue causing the problem.  
Fred makes an excellent point about how testing can stress the drive further and may cause it to degrade.  That makes a good argument for copying the drive first.  That's one of the first steps I'll make when I have any reason to believe there are issues with a drive.
Avatar of lloving

ASKER

Replacement drive on the way from Dell. Expect to clone to new drive using sector by sector
keep in mind that cloning will also copy all errors over too !
I would not do sector by sector first.  You ran chkdisk, seems like your file structures are fine. Just do a standard clone.  If that fails you might need sector by sector, but most clone apps will fail when they hit a bad sector.
fred:

Part of my reason to suggest sector-by-sector copying was to test the readability of the original drive.  Now I think that it makes more sense to follow your suggestion about standard cloning, then run chkdsk /r to test the drive thoroughly.  Unless the drive is going to be scrapped, I think it is important to confirm whether or not it has a problem.
Avatar of lloving

ASKER

FWIW this is not the boot drive. Chkdsk /r has been run on this drive and errors persist.
Event viewer indicates continuing issue with bad blocks. Drive is being replaced tomorrow. Expect to run straight clone and trash defective drive.
that was exactly what i asked in my first post on 8/4  : is this the correct disk ?
i knew there is confusion due to enumeration  starting from 0 or 1

i advise to disconnect all other drives  than the boot drive to be sure ( label them  + the cable  -if needed)  so you identify the correct one
Avatar of lloving

ASKER

The offending disk is labeled HardDisk1 in the Event viewer and is listed as HardDisk1 in Disk Manager.
would you mind telling us how the disks show in the bios, or in DEVICE manager? screenshot?
ha - i see the difficulty ( i think) they have the same size, even being  another brand
try running chkdsk on the other one
Avatar of lloving

ASKER

Two things indicate the drive letter is E:.
The backup client errors out on the E: drive, proven by removing that drive from the backup sweep.
RMM reports the error on HardDisk1 which when checked using disk manager is the E: drive.

The E: drive will be replaced shortly which I think will confirm the offending drive letter.
yes, but chkdsk was not running on the E: Drive, but on the C: drive
try it from explorer : select the disk you want to run chkdsk E:- right click it and select properties> run a disk check
Avatar of lloving

ASKER

ChkDsk was run on E:. Volume was dismounted and ChkDsk /r was run.
Also ran Check from explorer. No errors reported but Event ID 7 (Bad block) occurs almost daily.
Drive replacement appears to be the right solution.
ok - try another approach
what disk model is it?  look it up in device manager> disks
then you can use the manufacturers diag tool
I'm not sure why we are talking about which disk.  Disk 1 is Windows drive E:  and that the only partition on the drive.
I didn't see any pic or comment above to indicate you did not run chkdisk on the correct drive.

I assumed you ran chkdisk e:   or you ran it from a right click in explorer.

Did I miss something?

In any case I would not be messing around on a drive getting errors.  Make a copy of it first!   Either make a drive image or clone it to another drive.

If you don't have a tool for that, I like LazesoftSuite
https://lazesoft.com/lazesoft-recovery-suite.html
Avatar of lloving

ASKER

OK.  The plot thickens.
Installed a new hot plug drive in the offending server.
The drive lights up but the server, a Dell PowerEdge T440, does not recognize the drive is there. Nothing in disk manager.
Contacted Dell support, but since this server has recently outlived its supported life Dell is not willing to answer any questions without being paid. So I'm hoping to get some guidance here.
Is it any sort of RAID controller?  If so, you'll have to configure it in the RAID utility first.

It would be wise to install the OpenManage Administrator.  I think this is the correct one: https://www.dell.com/support/home/en-us/drivers/driversdetails?driverid=d9nc5&oscode=ws19l&productcode=poweredge-t440

From there you should be able to inspect what the system has found in the way of drives.

If you are trying to configure it as a single drive, you usually set it up as RAID 0.
ASKER CERTIFIED SOLUTION
Avatar of lloving
lloving

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
What did you change to get the drive to be recognized in Disk Manager?
Avatar of lloving

ASKER

OpenManage Administrator as you suggested. Thanks

Good to know what resolved that part of the process.  That may be very helpful to someone in the future who runs into this thread.