\device\harddisk0 has a bad block

Hi I'm receving since last two days the same message.
\device\harddisk0 has a bad block
when i click the details it is showing the following file name.
IoLogMsg.dll
My operating system is : Windows Server 2003
Can you help me?

On Tue, 31 Dec 2013 06:21:42 +0000, Mohamed Faisel wrote:
Hi I'm receving since last two days the same message.
\device\harddisk0 has a bad block
when i click the details it is showing the following file name.
IoLogMsg.dll
My operating system is : Windows Server 2003
Can you help me?
This forum is for security related questions, and this is not a security
related question.
Having said that, you need to run chkdsk on that disk.
Paul Adare - FIM CM MVP
Surely the 4 sysadmins of the apocalypse should be:
edquota, rm -rf, kill -9, and shutdown. -- Rob Blake

Similar Messages

Powerbook hard drive has 384 bad blocks -- replace?

I just ran techtool pro on my powerbook and it found a bunch of bad blocks. I read that if you have more than 5 bad blocks you should repair or replace the drive. But when I ran disk utility to repair it I got a message that the drive appears to be fine. The question is this; do I really need to buy a new drive?

When you go into disk utility, does the SMART status say failing? If so, replace the drive now. If you don't have it, you might want to install SMARTReporter which puts in icon on the menu bar which indicates the SMART status. It's available at http://www.corecode.at/smartreporter/
You should be making frequent backups and use TechTool to examine the drive on a regular basis. If the count increases, get a new drive.
One thing you can do is to erase your hard drive, using the security erase feature which writes zero's on the hard drive. This also maps out the bad sectors so the system won't try and use them.

Event ID 7- The device has a bad block

HDD is cannot initialize (\Device\HardDisk1\DR0), does not have any drive letter so I cannot perform chkdsk. I have tried putting on a freezer for 15-30 minutes and see if I will able to have a chance to retrieve files/folders. Please advise.

I've been a fan of Hiren's Boot CD. Has a ton of great, free tools. One of the tools is call DRevitalize, which is good for repairing sectors if there is an unexpected power-loss, brownout, OS crash, or improper disconnects. I can't say it will fix every
HDD issue but it's worth a shot. The DOS prompt may look overwhelming to some at first, but follow the instructions and you'll be fine.
When scanning a suspect disk, you should only see a small amount of errors, maybe 3 or 4; small amount. It's good if you see none. When they programs encounter an error, they will fix it in one or two tries. Anything more, you have a whole different problem.
Hirens CD Download: http://www.hirensbootcd.org/download/ - can be installed on cd or usb
How to Guide: http://www.piotrkn22.republika.pl/drev/next.html
Keep us updated!
-Jake

\Device\Harddisk0\DR0, has a bad block.

as the title says, my laptop keeps crashing randomly for various amounts of time

I recommend that you run the PC UEFI Diagnostics hard disk test on the notebook. If the Diagnostics test tells you that the hard disk has failed, then it will require replacement with a new hard disk.
Is your notebook still in warranty?
Check your warranty status Here.
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Ideapad Flex 15 - HDD has bad block

Hi All,
Thanks for Any help to address the problem.
I have already tried running the chkdsk /f /r which just got stuck at 10% and didn't move from there for about 40 minutes.
I started getting below message in Event viewer :
Log Name:      System
Source:        disk
Date:          1/19/2014 5:25:48 PM
Event ID:      7
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      PC
Description:
The device, \Device\Harddisk0\DR0, has a bad block.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="disk" />
    <EventID Qualifiers="49156">7</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-19T23:25:48.278119900Z" />
    <EventRecordID>5403</EventRecordID>
    <Channel>System</Channel>
    <Computer>PC</Computer>
    <Security />
</System>
<EventData>
    <Data>\Device\Harddisk0\DR0</Data>
    <Binary>030080000100000000000000070004C0000100009C0000C00000000000000000007007C5090000000C10010000000000FFFFFFFF000000005800008402010000E8200AFF42072000000200003C000000C09AAB030000000080957F0100E0FFFF0000000000000000C0C8250100E0FFFF0000000000000000B883E20400000000280004E283B800000100000000000000700003000000000000000000110000000000000000000000</Binary>
</EventData>
</Event>
Also similar message from Lenovo Solution Center:

Are you encountering the same startup errors when booting straight from the One Key Recovery button? I assume the startup error is occuring while trying to boot the OS, and not booting the recovery.
As far as I know, Lenovo utilizes a corporate activation (no printed key) on the Flex 15. You may be able to get Lenovo to send you recovery media, or even have them just re-image if covered by your warranty.
←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗
Tap that kudos button if I helped ^^
←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗

Cd rom has bad block event 7

I keep gettinbg an event log error CDROM has a bad block, Error 7 and error 51 paging error. Windows 7 freezes up. Is my cd bad? Is there anyway to restore the data on it.?

Hi,
I would like to know if other CD occurs the same issue.
Usually this error is the result of a failing CD-ROM drive, or faulty media. You can try the following methods to troubleshoot the issue.
Reinstall the device driver
1. Restart your computer.
2. Keep pressing F8 and then select Safe Mode.
3. When booting in Safe Mode, go to Device Manage.
4. Expand the "DVD/CD-ROM drives" item.
5. Right click your CD-ROM device and choose Uninstall.
6. Click OK to proceed.
7. Restart your computer. The computer will automatically detect the
device and install the driver.
Remove the upper filter and lower filter values from the Registry
1. Click the Start Button, type "regedit" (without quotation marks) in the Start Search box and then press ENTER.
2. Navigate to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E965-E325-11CE-BFC1-08002BE10318}
Note: This is the CD-ROM/DVD global class key.
3. Right click the {36FC9E60-C465-11CF-8056-444553540000} entry, choose "Export", select Desktop in the Save in box and type backup in File Name. Click Save.
Note: The backup file is on the Desktop and named backup.reg. We can simply restore the registry by double-clicking the backup.reg file.
4. Highlight this key {4D36E965-E325-11CE-BFC1-08002BE10318}, on the right pane, delete the upperfilter and lowerfilter entries if these strings are present.
5. Restart your computer and check if the problem disappears.
If the problem persists after trying all of the above methods but the CD can be read on other computer, it could be CD-ROM physically damaged. You need to contact
the manufacture to fix the hardware issue.
Best Regards,
Niki
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

IMac 27" late 2012 3TB hard drive bad blocks

Hi Guys,
I just received the new iMac 27" late 2012 with 3TB hard drive and as soon as I run Drive Genius version 3.2.2 I saw that the drive has 8 bad blocks.
I tried to deleted the logical volume and reinstall the OS X 10.8.2 and after a scan I got the same 8 bad blocks. I give it another try and erase the entire 3 TB volu except the recovery partition and installed Mountain Lion and after running another Drive Genius SCAN for almost 12 hours I got 8 bad blocks again.
Called Apple Support and they are clueless about what is going on as they are not even aware that the late 2012 iMac 27" is not even in stores yet.
I was told that as long as I do not have errors within the OS X I should not worry about as he HDD is fine. I do not believe it since from my experience when you have a bad block you also have a physical damage on you disk surface.
I called Apple Support again and I was told to go to Genius Bar and have them to replace the HDD to a unit not even a week old. I think that I am going to return the unit, maybe I got a lemon and the unit got dropped during the shipping process or who knows.
I hope that this thread will help other owners to have them to run a check disk or scan disk just to make sure that they do not have a bad hard drive on their new iMac late 2012.
Again I have nothing against to anyone as I just hope that someone from Apple will find this thread and try to prevent this from happening to a large scale.
Thank you.

Colos2012 wrote:
... soon as I run Drive Genius version 3.2.2 I saw that the drive has 8 bad blocks.
Drive Genius will report bad blocks when none are present. It may even be responsible for disk corruption.
See: DriveGenius = Problem
Get rid of Drive Genius. Do not install such junk on a Mac.

My Arch won't boot anymore something about bad blocks

It was working fine. I booted it up this morning said it found some bad blocks on some of my Linux partitions. How do I scan the surface of my drives with Archlinux.?. Is that even possible with Linux?. This is my USB drive that has the bad blocks.

Quicken2k wrote:Boot with ro 1?. I'm new to Arch and need a bit more info. Are you telling me to boot up in read only mode?. How?.
No worries! Simply, boot your computer and when you get to GRUB, select your Arch install and hit 'e'. Now you can edit the 'kernel' line. Append 1 (one) to the end of the line. Hit enter again, and hit 'b' to boot into single user mode. Now you can login as root, and perform whatever fsck's and debugging. Be sure to report back.

Does RAID Rebuild Fix Bad Blocks on RAID Slice?

I have RAID 1 enabled (the mirroring option) between two drives on my XServe G4. Yesterday, Server Monitor reported that the RAID was degraded. I booted off the install CD. I launched Disk Utility. Disk Utility immediately rebuilt the RAID. By immediately I mean that it didn't ask if I wanted to, but it took over two hours.
Today, I ran TechTool Pro. It says that one of the disks in the RAID has 3 bad blocks. It says that the only way to fix that is to erase the disk and zero all data.
When TechTool scanned the RAID itself as a disk, however, it did not report any bad blocks. This makes me wonder if rebuilding the RAID somehow took care of the bad blocks already.
Please let me know if my theory is correct!

Oh...if you have data you are trying to save then its best to try cloning the drive to another one, which should save its data as-is to another drive. Hopefully you can do so without there being hangups around the bad blocks and keep at least most of your data intact. I'd recommend you try using Carbon Copy Cloner to do this, but you will need a secondary drive that is at least the size of the data on the problematic drive.

[Repaired] Bad blocks cause kernel blocking to the device

I got
May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] Unhandled sense code
May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] Sense Key : 0x3 [current]
May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] ASC=0x14 ASCQ=0x0
May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 25 42 ea af 00 00 01 00
May 10 10:08:13 qslap kernel: end_request: I/O error, dev sdb, sector 625142447
May 10 10:08:13 qslap kernel: Buffer I/O error on device sdb, logical block 78142805
in system log when I try to access /dev/sdb in some way (for example, plug in, fdisk, gparted, but not palimpsest).
This kind of log repeats several times and blocks any access to that device for tens of seconds (Seems kernel keep retrying, not give up the first time), which is annoying.
From palimpsest, I can see:
Current Pending Sector Count: Value: 1 sector
Uncorrectable Sector Count: Value: 1 sector
It says when write fails, "Current Pending Sector" will be remapped automatically by hardware.
I got the sector size = 512 bytes:
# fdisk -lu /dev/sdb
Disk /dev/sdb: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xaaaaaaaa
Disk /dev/sdb doesn't contain a valid partition table
badblocks detects the bad sector well:
# badblocks -svw -b 512 /dev/sdb 625142447 625142447
Checking for bad blocks in read-write mode
From block 625142447 to 625142447
Testing with pattern 0xaa: 625142447one, 0:20 elapsed
done
Reading and comparing: done
Testing with pattern 0x55: done
Reading and comparing: done
Testing with pattern 0xff: done
Reading and comparing: done
Testing with pattern 0x00: done
Reading and comparing: done
Pass completed, 1 bad blocks found.
From above, you can see that write a block one time takes 20 seconds due to kernel blocking.
badblocks writes 4 times, ~80 seconds.
Note: badblocks doesn't find any bad blocks when performing a full disk read-only test.
However, the sector wasn't automatically remapped (badblocks has already written that sector)
the kernel is still generating logs and blocking, which is very annoying.
I also tried to write at that sector directly, no luck:
# dd if=/dev/zero of=/dev/sdb bs=512 count=1 seek=625142447
dd: writing `/dev/sdb': Input/output error
1+0 records in
0+0 records out
0 bytes (0 B) copied, 7.26951 s, 0.0 kB/s
What should I do to let the hardware remap that sector?
If no way due to hardware limitation, then how can I mute the annoying log and let the kernel not blocking ?
Additional: I am looking for a way to let kernel not blocking, give up at the begining asap, or let the hardware SMART mark that sector not to be 'Pending', not for a way to create fs with bad blocks marked.
I know if I provide a list of badblocks to mkfs.*** to create a fs, these blocks will not be used.
However, when I plug in the removable harddisk, BEFORE performing ANY r/w instructions, the kernel starts to generate logs and /dev/sdb is not visible in tens of seconds. Same situation occurs when I run / fdisk / gparted (these programs are not responsible for tens of seconds due to kernel blocking) ...
I guess that SMART does these checks automatically and cause kernel blocking, while SMART can't handle these things well.
This is the output of smartctl -a /dev/sdb -d sat, which may be helpful:
smartctl 5.39.1 2010-01-28 r3054 [i686-pc-linux-gnu] (local build)
Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Seagate Momentus 5400.5 series
Device Model: ST9320320AS
Serial Number: 5SX3YFQ8
Firmware Version: SD03
User Capacity: 320,072,933,376 bytes
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Mon May 10 11:25:42 2010 CST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
See vendor-specific Attribute list for marginal Attributes.
General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: ( 700) seconds.
Offline data collection
capabilities: (0x73) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
No Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 114) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 094 088 006 Pre-fail Always - 182650280
3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 595
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 30942693
9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 4482
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 1
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 579
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 1812
188 Command_Timeout 0x0032 100 099 000 Old_age Always - 2
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 067 039 045 Old_age Always In_the_past 33 (0 166 39 23)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 98
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 48
193 Load_Cycle_Count 0x0032 011 011 000 Old_age Always - 178621
194 Temperature_Celsius 0x0022 033 061 000 Old_age Always - 33 (0 12 0 0)
195 Hardware_ECC_Recovered 0x001a 060 039 000 Old_age Always - 182650280
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
SMART Error Log Version: 1
ATA Error Count: 1979 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 1979 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 da 01 ff ff ff 4f 00 13:43:15.498 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:13.155 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
Error 1978 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 da 01 ff ff ff 4f 00 13:43:13.155 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
Error 1977 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:10.885 READ DMA EXT
Error 1976 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 da 01 ff ff ff 4f 00 13:43:08.457 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:06.082 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:03.814 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
Error 1975 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 da 01 ff ff ff 4f 00 13:43:06.082 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:03.814 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Extended offline Completed: read failure 90% 4480 625142447
# 2 Short offline Completed: read failure 90% 4474 625142447
# 3 Extended offline Completed: read failure 90% 4474 625142447
# 4 Short offline Completed: read failure 90% 4474 625142447
# 5 Conveyance offline Completed: read failure 90% 4473 625142447
# 6 Short offline Completed: read failure 90% 4473 625142447
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
Last edited by b6fan (2010-05-10 07:18:46)

Bad block repaired by SeaTools for DOS.
Seems only SeaTools for DOS can repair this issue.

EventId: 32, disk - The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled

Virtualized 2012 R2 Domain Controller running on hyper-V. Every boot lists the following error three times:
EventId: 32, disk - The driver detected that the device \Device\Harddisk0\DR0 has its write cache enabled.
Data corruption may occur.
Having checked the virtual SCSI disks all have their write cache enabled, is this correct or do I need to take some action to prevent these events?

Hi,
This is normal and you can't change it. This tells AD that write caching is enabled so it uses a different method to store information.
http://www.hyper-v.nu/archives/hvredevoort/2013/07/keeping-your-virtual-active-directory-domain-controllers-safe/
More information there.
Thanks
Denis
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
Blog: http://www.windows-support.co.uk
Twitter: LinkedIn:

Hard Disk has bad block.

Hi Experts,
I have seen the bad block error entry in event viewer on Server.
Server configuration as follows...
Windows server 2008 R2.
ECC 6.0
IBM DB2 9.7
Its a development system.
We have faced same issue on same server 4 months ago, that time I have recovered that bad sector via CHKDSK /f /r command and then after that recover the database, so after that there is no any error entry in event viewer about bad block and etc.
But today again same error occurs, please suggest me how should I proceed now?
Regards,
Sahani.

Dear Deepanshu,
Thanks for your suggestions.
1. Sure.
2. Can we restore the database on another server which have different SAP SID and DB SID ?
3. Suppose I have to replace the old hard disk with new one, so what steps i have to do?
I mean firstly I have to install the EHP5 ECC 6.0 same as my previous server versions i.e. patch level, sap SID, Database version and patches, DB SID, and after that restore the database with the help of backup file of previous server. is it so?
Yes we are taking backup on weekly basis for Development server.
Regards.
Sahani.

Disk Utility: for bad blocks on hard disks, are seven overwrites any more effective than a single pass of zeros?

In this topic I'm not interested in security or data remanence (for such things we can turn to e.g. Wilders Security Forums).
I'm interested solely in best practice approaches to dealing with bad blocks on hard disks.
I read potentially conflicting information. Examples:
… 7-way write (not just zero all, it does NOT do a reliable safe job mapping out bad blocks) …
— https://discussions.apple.com/message/8191915#8191915 (2008-09-29)
… In theory zero all might find weak or bad blocks but there are better tools …
— https://discussions.apple.com/message/11199777#11199777 (2010-03-09)
… substitution will happen on the first re-write with Zeroes. More passes just takes longer.
— https://discussions.apple.com/message/12414270#12414270 (2010-10-12)
For bad block purposes alone I can't imagine seven overwrites being any more effective than a single pass of zeros.
Please, can anyone elaborate?
Anecdotally, I did find that a Disk Utility single pass of zeros seemed to make good (good enough for a particular purpose) a disk that was previously unreliable (a disk drive that had been dropped).

@MrHoffman
As well pointed your answers are, you are not answering the original question, and regarding consumer device hard drives your answers are missleading.
Consumer device hard drives ONLY remap a bad sector on write. That means regardless how many spare capacity the drive has, it will NEVER remap the sector. That means you ALWAYS have a bad file containing a bad sector.
In other words YOU would throw away an otherwise fully functional drive. That might be reasonable in a big enterprise where it is cheaper to replace the drive and let the RAID system take care of it.
However on an iMac or MacBook (Pro) an ordinary user can not replace the drive himself, so on top of the drive costs he has to pay the repair bill (for a drive that likely STILL is in perfect shape, except for the one 'not yet' remaped bad block)
You simply miss the point that the drive can have still one million good reserve blocks, but will never remap the affected block in a particular email or particular song or particular calendar. So as soon as the file affected is READ the machine hangs, all other processes more or less hang at the same moment they try to perform I/O because the process trying to read the bad block is blocking in the kernal. This happens regardless how many free reserve blocks you have, as the bad block never gets reallocated, unless it is written to it. And your email program wont rewrite an email that is 4 years old for you ... because it is not programmed to realize a certain file needs to be rewritten to get rid of a bad block.
@Graham Perrin
You are similar stubborn in not realizing that your original question is awnsered.
A bad block gets remapped on write.
So obviously it happens at the first write.
How do you come to the strange idea that writing several times makes a difference? How do you come to the strange idea that the bytes you write make a difference? Suppose block 1234 is bad. And the blocks 100,000,000 to 100,000,999 are reserve blocks. When you write '********' to block 1234 the hard drive (firmware) will remap it to e.g. 100,000,101. All subsequent writes will go to the same NEW block. So why do you ask if doing it several times will 'improve' this? After all the awnsers here you should have realized: your question makes no sense as soon as you have understood how remapping works (is supposed to work). And no: it does not matter if you write a sequence od zeros, of '0's or of '1's or of 1s or of your social security number or just 'help me I'm hold prisoner in a software forum'.
I would try to find a software that finds which file is affected, then try to read the bad block until you in fact have read it (that works surprisngly often but may take any time from a few mins to hours) ... in other words you need a software that tries to read the file and copies it completely, so even the bad block is read (hopefully) successful. Then write the whole data to a new file and delete the old one (deleting will free the bad block and ar some later time something will be written there and cause a remap).
Writing zeros into the bad block basically only helps if you don't care that the affected file is corrupted afterwards. E.g. in case of a movie the player might crash after trying to display the affected area. E.g. if you know the affected file is a text file, it would make more sense to write a bunch of '-' signs, as they are readable while zero bytes are not (a text file is not supposed to contain zero bytes)
Hope that helped ;)

How to keeps track of new coming bad blocks on a hdd

I have some 2,5 hdd lying around and wanted to test them for bad blocks and found that I can use Badblocks for this.
But how do I keep the "list" of bad blocks up-to-date if new bad blocks are detected, or is this not posseble?
Solixxx
Last edited by solixxx (2013-09-30 23:48:21)

graysky wrote:You can detect and lock out bad ones... but the danger is not knowing which good blocks will go bad in the future. I have a hdd in an old machine that has bad blocks on it... been running fine for 9+ months now after isolating them.
Exactly :-)
I've been using a drive with isolated bad blocks for over a year now, but I store only data I don't care that much about - I can re-download or recreate it.
I thought you just wanted to list the bad blocks. If you're going to reformat the device, it is the mechanism of isolating the bad blocks I wrote about, so you should be OK.
I think badblocks prevents the bad block from being used by the filesystem, but they still reside on the device, so if you run badblocks again, it should list both the old bad blocks and any new ones too.

Just receive this email. There is no evidence that i have purchased anything. Dear client(e), Your ID, was just used to purchase "Wrecking ball.Mp3" by 'Miley Cyrus' from iTunes Store on a computer or device that has never been used by you before.

Just received this email. Havn't purchased anything any idea????
Dear client(e),
Your ID, was just used to purchase "Wrecking ball.Mp3" by 'Miley Cyrus' from iTunes Store on a computer or device that has never been used by you before.
This purchase was initiated from 'BRAZIL'
If you made this purchase you can ignore this email, but if it was made in error, or if you believe an unauthorized person accessed your account, please reset your account informations immediately by going to
ireset.appleaccount.com => Confirm that you're the account holder and then
change your password.
N.B: If you don't update your account, Please note that it can be
used to make more orders in our stores, and then we'll be obliged to block it.
Thanks,,
Regards,
Customer Support

It's a phishing attempt to get your account and payment details, it's not from Apple - if you clicked on the links in it and entered your details then you should change your password immediately e.g. by tapping on your id in Settings > iTunes & App Store on your iPad and selecting 'view apple id' on the popup and signing into it, via the Store > View Account menu option on your computer's iTunes or via http://appleid.apple.com
If you still have the email then you could forward it to Apple : [email protected]

\device\harddisk0 has a bad block

Similar Messages

Maybe you are looking for