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.

Similar Messages

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 ^^
←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗←↑→↓↘↙↖↗

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.

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.

Does DU (11.0) update a drive's bad block map?

I have an external drive (an old WD 256Gb I pulled form a Tivo) that I suspect has bad blocks. Does Disk Utility (11.0 as provided with 10.5.2) update the bad block map so that this drive may become reliable?

Only if you format the drive using the Zero Data option. You will also need to repartition the drive:
Extended Hard Drive Preparation
1. Open Disk Utility in your Utilities folder. If you need to reformat your startup volume, then you must boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger or Leopard.)
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Click on the Options button, set the partition scheme to GUID (only required for Intel Macs) then click on the OK button. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the volume(s) mount on the Desktop.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process will take 30 minutes to an hour or more depending upon the drive size.
Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive.

Tech Tool Deluxe identifies "Bad Blocks"

I have two G4's that have been misbehaving. I ultimately erased both hard drives, zeroed out the data, re-installed 10.4, and then ran Tech Tool Deluxe. On my newer G4, the analysis revealed 6 bad blocks. On the older G4, I am only half done and I have 300 bad blocks. One discussion mentioned that "zeroing" the data on the drive would solve the problem - I did that and still have the bad blocks. Should I have ZERO bad blocks - are a few OK?
Thank you

So, when I erased my disk, "zeroed" out the data (using Disk Utility), should I have zeroed-out the bad blocks as well (identified them, re-addressed them, etc)?
Zeroing the data re-writes every block. As you know, it takes hours to complete. This forces IDE/ATA drives to substitute spares for up to 10 blocks known to have problems, IF
• enough spare blocks are available AND
• spares are not also bad AND
• not more than 10 substitutions are required.
afterward, I did an AHT - no negative result
AHT checks the Directory data structures for damage. It does not read every block, and cannot detect all Bad Blocks on the drive. Doing that takes almost as long as Zero all Data, and AHT is done in only a few minutes.
Disk Utility also did not identify any problems (a few Disk Permissions).
Disk Utility's Repair and Repair Permissions features check the Directory Data Structures and File Permissions for damage and inconsitency. They cannot detect all bad Blocks on the drive. Doing that takes almost as much time as Zero all Data, and AHT is done in only a few minutes.
It was Tech Tool Deluxe that discovered the bad blocks
The "Surface Scan" function reads every block. It is the only test you listed that reads every block, but takes a really long time to do so. It can detect Bad Blocks, but does not fix them. Also, when an IDE/ATA drive has Bad Blocks, its "Smartdrive" status is usually something horrible-sounding like "Failed".
For the drive with 6 bad blocks - what should I do (and in what order) to see if they can be eliminated?
That requires another initialize with "Zero all Data". If there are enough spares in the right neighborhoods, it may be able to substitute spares to make it 100 percent good blocks. There is a possibility that some of the remaining Bad Blocks cannot be repaired, and that may mean the drive is not in good enough shape to continue using it.

\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

On v880 : "metadb: has bad master block on device"

Hi,
In my production environment I have a v880 server. While I was trying to replace a bad disk I had the
message: metadb: oradb1: has bad master block on device, when I ran the metadb -a -f -c3 /dev/dsk/c1t1d0s5
I can not find any information on the internet. Also, I have seen the thread https://community.oracle.com/thread/1918834, which is very old.
According to the thread I have to split all the submirrors and create the mirrors again. That is very difficult for me to do it, because I have mounted volumes.
Any ideas?
Regards,
Panos

OK - after talking with a very knowledgable/helpful guy in Sun's storage group, the problem is solved. It turned out that since the new disk had a different DevID, the mirror did not get correctly restored. The solution was to do the following (note: d23 is the slice where I was trying to create the state db):
# metaclear d23
# metadb -a -c 2 c1t11d0s7
# metattach d3 d23
He also referred me to doc 73132
Thanks Dan!

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.

ORA-01578 - bad blocks.

Hello,
We had a SAN crash last month and with all the confusion I missed that we had some bad blocks after the crash. Our RMAN backups have now aged out so we don't have a RMAN backup. What I do have is a datapump backup from before the event. This is table corruption. Is there a way to either restore the table to a stage location, catalog the table or datafile somehow, then restore the bad block? Otherwise, somehow determine the bad data and get the data from the backed up table and insert it back into the bad table after I re-recreate it without the bad blocks?
Oracle support is just saying recreate the table skipping the bad blocks but there has to be some way here if the data is on that datapump backup that I can determin what it is then restore it.
Thanks

The fix blocks procedure did not work and I have not attempted the skip blocks. If I run the skip corrupt blocks will my query work? Is that worth a shot next?
select count(*) TRACKING_ID from JEBCS3NM.TRACKABLE_OBJECT t, JEBCS3NM.CONVEYANCE c where c.TRACKABLE_OBJECT_GUID = t.TRACKABLE_OBJECT_GUID and PRIMARY_MOVER_ID is null
ERROR at line 1:
ORA-01578: ORACLE data block corrupted (file # 75, block # 1024073)
ORA-01110: data file 75: '/u02/oradata/bcso/jebcs3nm_d.dbf'
SELECT OBJECT_NAME, BLOCK_ID, MARKED_CORRUPT
2       FROM REPAIR_TABLE;
OBJECT_NAME                      BLOCK_ID MARKED_COR
CONVEYANCE                        1024073 TRUE
CONVEYANCE                        1024105 TRUE
CONVEYANCE                        1024113 TRUE
SQL> SET SERVEROUTPUT ON
SQL> DECLARE num_fix INT;
2 BEGIN
num_fix := 0;
DBMS_REPAIR.FIX_CORRUPT_BLOCKS (
     SCHEMA_NAME => 'JEBCS3NM',
6       OBJECT_NAME=> 'CONVEYANCE',
7       OBJECT_TYPE => dbms_repair.table_object,
     REPAIR_TABLE_NAME => 'REPAIR_TABLE',
     FIX_COUNT=> num_fix);
DBMS_OUTPUT.PUT_LINE('num fix: ' || TO_CHAR(num_fix));
END;
12 /
num fix: 0
PL/SQL procedure successfully completed.

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.

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 ;)

Do the bad blocks preventing me mount my system HD mean I need to replace it?

I have asked this question elsewhere in a different way but didn't get much help - since then I've ran a few more tests and can hopefully zero in on the issue.
I have a 3TB fusion drive late 2012 model 27" iMac that started behaving sluggishly - transferring things from folder to folder in Finder would bring up the spinning beachball (luckily I managed to transfer my important files). When I ran Disk Utility it said that 't stopped verifying "MacintoshHD" and this disk needs to be repaired using the Recovery HD'. I did the restart and attempted the repair and got the message that DU couldn't repair the HD, backup files and reformat the disk. When I attempted to do this I then got the window "Disk Erase failed with the error: The given file system is not supported on Core Storage". The image of the HD also disappeared from view so I can't do anything... not reformat, reinstall Yosemite etc
I ran Tech Tools ProToGo from a USB drive and it showed I had 90 bad blocks on my HD (not the SSD part) but the repair button was greyed out.
I like to think I'm relatively competant with self repair/diagnosis but I've hit a brick wall here. The jury seems to be out whether bad blocks are an indication that the HDD has to be replaced - I've read conflicting reports in these very forums.
FTR I installed Yosemite on an external HD and am using my iMac that way so I guess a lot of stuff under the hood continues to work perfectly.
I would really appreciate any advice.
I've included a couple of relevant pics below; here's the link from my previous question that has a lot more pics and info if anyone wants to have a look Total HD crash - how to get the files

I've tried reading through both threads but am not quite able to follow along....one thought though, have you tried using OS X Internet Recovery?
OS X: About OS X Recovery - Apple Support maybe the Utilities there will allow you to repair the hard drive.

How to repair a bad block on internal hard drive?

I've just performed a surface test on my internal HD
It reports back one bad block, at # 1, 118, 671, 700.Filename = N/A.
1. Should I be concerned about this? I have not noticed any performance issues.
2. If I wanted to get rid of it anyway, how do I repair that bad block?
Please advise.
Many thanks.
/gh

Good to know this happens automatically.
Is that something OS X automatically does on startup, or on shut down, or in background?
But in this case, that automatic feature seems to have missed this block. Else the bad block would not show up in the utility, with a file in it.
Or ,,,,perhaps it still shows up as a bad block in the utility, even though it's been mapped out.
If that's the case, then I guess I need another kind of utility that would report the block has been mapped out....
Any suggestions?

More than 1200 bad blocks do I need to change my Hard Disk

Hi
my hard disk on a Macbook pro has more than 1200 bad blocks do I need to change my Hard Disk
Thanks for your help

yousseffromlimoges wrote:
my hard disk on a Macbook pro has more than 1200 bad blocks do I need to change my Hard Disk
What software and version did you use to determine you had 1200+ bad blocks?
Was it compatible with Lion?
Run the scan again and take a screen shot of the results and make sure to save it to a external media and disconnect it, you will need this to perform a warranty call and have the drive replaced.
After you have backed up your files to a external storage drive and disconnected it.
Hold Command r upon rebooting and enter the Lion Recovery Partition and run Disk Utility, see if the drive needs repair. I suspect it does. Check the smart status too.
Follow the
Restoring OS X 10.7 (new drive, total reformat method)
https://discussions.apple.com/message/16276201#16276201
Also make a clone of your OS X Lion Partition on a external drive, this way your prepared if the drive dies, you can option boot off the clone. If you get a new drive you have a copy of Lion Recovery on the USB.
It's highly unusual for a drive to have 1200+ bad blocks, the Zero Erase Free Space will confirm it as it's going to use up all your spare blocks.
The drive will likely brick, which you then can option boot off the clone.
Schedule a Apple warranty/AppleCare call if your under it, or order a new drive online from OtherWorld Computing "kits", iFixit for videos or other Mac places online.
http://eshop.macsales.com/installvideos/
You can read my link provided how to format the drive.
However if your Zero Erase Free Space turns out fine, then I suspect the software you used or perhaps something else is wrong with your OS X not correctly reporting your drives data characteristics correctly.
You could be spared a costly repair if that's the case.
Good Luck.

Cd rom has bad block event 7

Similar Messages

Maybe you are looking for