O Error Bummers
Please enter a title. You can not post a blank message. Please type your message and try again. poldo Level 1 (0 points) Q: Error -36ioErr I/O error (bummers) well I have been getting this error whenever I try to copy a file or back up with time machine and also when trying to play certain songs in itunes..pretty much itunes tries to play the song but it hangs until I restart if I am copying a file then the finder does the same exact thing but I get the error message -36 ..any idea how to fix this ? hardware tests show no troubles and all the utilities I tried show nothing out of the ordinary... At first I thought the HD was failing and had bad sectors but that would show in first aid and Disk warrior.. Help macbook 2ghz, Mac OS X (10.6.7) Posted on Apr 13, 2011 2:57 PM I have this question too Close Q: Error -36ioErr I/O error (bummers) All replies Helpful answers by Király, Király Apr 13, 2011 3:55 PM in response to poldo Level 6 (9,855 points) Mac OS X Apr 13, 2011 3:55 PM in response to poldo The -36 input/output error could be a variety of things:-bad cable-bad controller-failing hard drive (Disk Utility and Disk Warrior are not guaranteed to report accurately that a drive is about to failIs this error occurring only with a secondary drive? Helpful (0) Reply options Link to this post by poldo, poldo Apr 13, 2011 4:01 PM in response to Király Level 1 (0 points) Apr 13, 2011 4:01 PM in response to Király No unfortunately It's my main drive.. I can't even back it up because it stops as soon as it finds a file in a bad sector.. so far it's only having troubles with files in the itunes folder.. Helpful (0) Reply options Link to this post by Linc Davis, Linc Davis Apr 13, 2011 4:38 PM in response to poldo Level 10 (208,037 points) Applications Apr 13, 2011 4:38 PM in response t
Popular Forums Computer Help Computer Newbies Laptops Phones TVs & Home Theaters Networking & Wireless Windows 7 Windows 10 Cameras All Forums News Top Categories Apple Computers Crave Deals Google Internet Microsoft Mobile Photography Security Sci-Tech Tech Culture Tech Industry Photo Galleries Video Forums Video Top Categories Apple Byte Carfection CNET Top 5 CNET Update Googlicious How To Netpicks Next Big Thing News On Cars Phones Prizefight Tablets Tomorrow Daily CNET Podcasts How To Top Categories https://discussions.apple.com/thread/2814769?start=0&tstart=0 Appliances Computers Gaming Home Entertainment Internet Mobile Apps Phones Photography Security Smart Home Tablets Wearable Tech Forums Speed Test Smart Home Top Categories Tour CNET Smart Home Smart Home News Smart Home How To Best Smart Home Devices Cars Top Categories Car Reviews Best Cars New Cars Used Cars Deals Top Categories Cheapskate Best https://www.cnet.com/news/possibilities-for-overcoming-finder-error-36-in-os-x/ Tech Under $50 All Deals Tech Deals Non-Tech Deals Audio Deals Cell Phone Deals Desktop Deals Laptop Deals Hard Drive & Storage Deals Printer Deals Tablet Deals Camera Deals Monitor Deals Software Deals TV Deals Web Hosting VPN Services WordPress Hosting Domain Names Download Sign In / Join Sign In to CNET Join CNET Member Benefits My Profile Forums Sign Out US Other editions United Kingdom Australia China France Germany Japan Korea CNET en Español CNET Possibilities for overcoming Finder Error -36 in OS X Top Stories Internet outage swoops across the US AI expert: Super-smart cars are just a glorious beginning How Google's Pixel phone builds a better photo Nintendo Switch: Our 21 top unanswered questions YouTube is breaking into pay TV, starting with Dish Brilliant Jupiter image shows off planet's sunny swirls How the PS4 Pro made me a believer Bring back the badass black MacBook Which music streaming app is right for you? Felicity Jones talks 'Inferno,' 'Rogue On
we couldn't figure out why.We eventually turned to DTS, Apple's third party developer support team - you can buy a tech support "incident" from them - that http://hacksoflife.blogspot.com/2006/08/io-error-36-when-writing-on-mac.html is, assistance with one bug. It was from them that I got the missing tidbit of information:Usually ioErr (-36) means something has gone deeply wrong at the lowest levels. Here's what the actual header file says if you have Apple's Carbon SDK: ioErr = -36, /*I/O error (bummers)*/That is, generally speaking, application programs can't recover from this - it would usually mean the hard drive o error is going bad. By comparison paramErr (-50) means you passed something illegal to the function.Well it turns out that if you pass a block of memory to FSWriteFork and part of that memory is not mapped (that is, trying to access that memory to do the disk write generates a segfault) then you get ioErr back, not paramErr. That tip led us to realize that what o error bummers we really had was (blushes) bad endian-swapping code that (on little-endian Macs only) generated bogus pointers. Depending on luck and the stars, that bogus memory might be mapped (thus writing junk into the file) or unmapped (generating the -36 error), hence the unreliable behavior.In hindsight this isn't surprising, once you realize that Mac Carbon file calls are written on top of BSD file manager calls. I don't know the actual implementation of FSWriteFork, but what if it uses BSD's "write"? Well, that can return EFAULT if you pass in unmapped memory. Posted by Benjamin Supnik at 5:31 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Macintosh No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Contributors Benjamin Supnik Chris Blog Archive ► 2016 (7) ► September (2) ► July (3) ► May (1) ► January (1) ► 2015 (15) ► December (3) ► November (2) ► June (2) ► May (1) ► April (2) ► March (2) ► February (1) ► January (2) ► 2014 (1) ► December (1) ► 2013 (11) ► October (2) ► August (2) ► July (1) ► May (1) ► Apr