Hardware Error 0x03 0x01
Sense Code = 0x03, 0x01 error If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. Welcome to Mac-Forums! Join us to comment and to customize your site experience! Members have access to different forum appearance options, and many more functions. Results 1 to 2 of 2 Thread: Burning DVD's getting Sense Code = 0x03, 0x01 error Tweet Thread Tools Show Printable Version Subscribe to this Thread… 02-11-2007,12:11 AM #1 DjViral View Profile View Forum Posts Member Since Feb 10, 2007 Posts 5 Burning DVD's getting Sense Code = 0x03, 0x01 error Hey there Im trying to burn a Video_TS folder in Toast Titanium 8 and i keep getting this message at different times in the burning process "HARDWARE ERROR Sense Code = 0x03, 0x01" and then some other jumble. and then it says the disc was failed to be written and it ejects and i gotta throw it away cus its useless and not blank anymore. Ive lost about 6 dvd's so far trying different things, I have dent marks in my walls, from getting mad and throwing failed DVDs accross the room into the wall. I also tried Popcorn and it gave me the same things. Ive even put my tried all the different speeds of burning. I'm just lost now and dont know what to do, pLease if anyone has ny idea o what to do, it would be soooo much appreciatted . Thank you in advance. Guess well i'm waiting i'll re-plaster the wall lol. Oh yeh im using Memorex DVD-R 16x 4.7gb 120 min. but as i said i've tried burning at different speeds. Reply With Quote 02-11-2007,12:18 AM #2 NanoBite View Profile View Forum Posts Member Since Oct 27, 2005 Posts 4,702 G'day DjViral & welcome to Mac-Forums. The solution to your problem starts with you cooling down. Restart your computer, when computer chimes during restart, press and HOLD these keys: "Apple+Option+P+R". Continue to hold all four keys and wait for the computer to chime three more times, there is a small interval between each chime as it is resetting the video memory and something else. After the 3rd chime, you can release the keys and start up as normal, test your DVD burner again and see if it's working. If y
have moved this Blog to new Address:http://macandmobile.blogspot.com/ Please post comments on new Blog. I will disable further comments on this blog. Thank you Asim After 9 months of purchasing my MacBook Pro I was faced with Error while burning my CDs. Toast reported sense key = MEDIUM ERROR and eject CD. I google the error and was surprised to see so many users are having this error. Some were blaming to cheap CDs while others recommended to repair permissions or re-install OS. I continue to face error on some cds while some burn fine. I concluded that it may be defective cds but when I used same cd http://www.mac-forums.com/showthread.php?t=53392 on my external writer they burn fine. On 12 months my burner finally gave up and now it was not burning any type of CD/DVD. I went to shop purchased Philips CD Cleaner which had two brushed on it. Inserted it into my dvd drive. Instructions played to choose track no. 14 for cleaning. I did as instructed and WOW my dvd burner was functional. I have burnt quite a few CD https://asimag.wordpress.com/2008/04/08/how-to-resolve-sense-key-medium-error-on-macbook-pro/ with no problem at all. Like this:Like Loading... Related Comments» 1. tbone - May 31, 2008 I'm having the same issue with my macbook pro that I purchase about 10 months ago. It's an Intel Dual core 10.4.11 build. I've heard a lot of bs about this being an issue with the type of discs, or the processing speed being too slow. I have Verbatim top quality medium, along with the 2.4 Ghz processors, so it's def. not that. I'm going to try using a disc cleaner, your post was really helpful, thanks. Reply 2. Lincoln K. - June 3, 2008 Yes I agree , Many thanks for this obvious tip! Ive had my Mpro for 8 months and its obvious to me now that Your right the Laser just needs a Clean, and then will work fine🙂 I will Post this around the net cheers, Many people are stumped by this error! Why Da hell dont software just say, "CLEAN HEADS PLZ" Reply 3. Gijs van de Nieuwegiessen - July 1, 2008 Experiencing the exact same problem when burning DL DVD's. I wasn't able to burn Memorex, or whatever the brand is called. I've read lots of posts advising to use Verbatim instead. It solved my problem back then, Right now (2 months afte
Possible values are:
Function | Error | Description =========|==============|============================================= open | ENXIO | not a valid device | EACCES | access mode is not read/write (O_RDWR) | EBUSY http://www.tldp.org/HOWTO/archived/SCSI-Programming-HOWTO/SCSI-Programming-HOWTO-21.html | device was requested for nonblocking access, | | but is busy now. | ERESTARTSYS | this indicates an internal error. Try to | | make it reproducible and inform the SCSI | | channel (for details on bug reporting | | see Drew Eckhardts SCSI-HOWTO). ioctl | ENXIO | not a valid device read | EAGAIN | the device would block. Try again later. | ERESTARTSYS | this indicates hardware error an internal error. Try to | | make it reproducible and inform the SCSI | | channel (for details on bug reporting | | see Drew Eckhardts SCSI-HOWTO). write | EIO | the length is too small (smaller than the | | generic header struct). Caution: Currently | | there is no overlength checking. | EAGAIN | the device would block. Try again later. | ENOMEM | memory required for hardware error 0x03 this request could not be | | allocated. Try later again unless you | | exceeded the maximum transfer size (see above) select | | none close | | noneFor read/write positive return values indicate as usual the amount of bytes that have been successfully transferred. This should equal the amount you requested. 21.1 Error status decoding Furthermore a detailed reporting is done via the kernels hd_status and the devices sense_buffer (see section sec-sensebuff ) both from the generic header structure. The meaning of hd_status can be found in drivers/scsi/scsi.h: This unsigned int is composed out of different parts:
lsb | ... | ... | msb =======|===========|===========|============ status | sense key | host code | driver byteThese macros from drivers/scsi/scsi.h are available, but unfortunately cannot be easily used due to weird header file interdependencies. This has to be cleaned.
Macro | Description =======================|================================================= status_byte(hd_status) | The SCSI device status. See section Status codes msg_byte(hd_status) | From the device. See section SCSI sense keys host_byte(hd_status) | From the kernel. See section Hostcodes driver_byte(hd_status) | From the kernel. See section midlevel codes21.2 Status codes The following status codes from the SCSI device (defined in scsi/scsi.h) are available.
Value | Symbol ======|===================