Previous 1 2 Next 18 Replies Latest reply: Jun 18, 2010 1:44 PM by David Crigger
RockSmurf Level 1 Level 1 (0 points)
Hello all,

Recently, I have been suddenly getting this error message:

"Logical end-of-file reached during read operation. Result Code = -39."

In my case, when it does come up, it always pops up during the recording of an audio take. Almost immediately after hitting the stop button, this error message would pop up. And then when I go to check the take that was just recorded, there is nothing but shrieking noise. As a result, this pop up error trashes any good take I may have had. It's unpredictable as to when this error decides to pop up as well. So now, when I record, I tend to just have my fingers crossed and hope that this error doesn't pop up especially right after recording a good take!

To no avail, I have tried different I/O buffer settings, repaired permissions, rebooted, and even re-formatted my recording hard disk.

Could this be a possible hint that my hard disk is about to physically collapse? I have had it for about 2 years. Could it be some sort of bug in Logic? Or something else perhaps?

Appreciate any feedback! Thanks a lot!

Mac Pro Intel 2.8 GHz Quad 8GB Ram, Mac OS X (10.6.3), LP 9.1.1, ULN-2
  • Marty Frasu Level 3 Level 3 (935 points)
    I am going to assume you have an intel Mac, make sure the disk you are recording to is partitioned GUID and not Apple Partition Map.
  • DamonGrant Level 1 Level 1 (0 points)
    Marty Frasu wrote:
    I am going to assume you have an intel Mac, make sure the disk you are recording to is partitioned GUID and not Apple Partition Map.



    I have also been having this problem with exactly the same result: an unusable file full of white noise. Very frustrating while tracking! Mine system is an intel mac (MBPro 17") about 3 years old and am recording to an external firewire disc. I'm not sure about the type of partitioning you are talking about. I assume you check this in Disc Utility, but I can't see anything about Apple Partition Map or GUID. It says "Partition Map Scheme: Master Boot Record." It is formatted as Mac OS Extended (journaled).

    Can you help me to find this partitioning info and is this a likely source of the problem?

    Thanks!
  • Eriksimon Level 6 Level 6 (11,780 points)
    Yes. Master Boot Record is for Windows disks. You need GUID. For that you'll have to repartition your disk; select it in Disk Utility, go to the Partition page, click on the options button and select GUID from the (three) options there.
    Repartitioning means your disk will be completely erased though, so back up any files from it first.
  • Pancenter Level 6 Level 6 (8,915 points)
    Eriksimon wrote:
    Yes. Master Boot Record is for Windows disks. You need GUID. For that you'll have to repartition your disk; select it in Disk Utility, go to the Partition page, click on the options button and select GUID from the (three) options there.
    Repartitioning means your disk will be completely erased though, so back up any files from it first.


    Erik,

    I thought GUID was only for the boot disk, there shouldn't be any problem with Mac OS Extended on an audio disk.

    pancenter-
  • Eriksimon Level 6 Level 6 (11,780 points)
    Pancenter wrote:
    I thought GUID was only for the boot disk, there shouldn't be any problem with Mac OS Extended on an audio disk.

    pancenter-



    I thought MBR doesn't work, mainly because of what Disk Utility itself says about it here:
    !http://farm4.static.flickr.com/3229/4559663725_4215cb9f79.jpg!

    Are you sure MBR is okay for a Mac file disk? At the very least, there is no need to use this partition scheme over GUID... right?
  • Pancenter Level 6 Level 6 (8,915 points)
    Eriksimon wrote:


    Are you sure MBR is okay for a Mac file disk? At the very least, there is no need to use this partition scheme over GUID... right?


    Oops... no you are correct!

    The disk should not be MBR partitioned unless it's used to run Windows,or a Windows compatible partition is needed that the Mac can write to as can be formatted FAT32. (Macs can read but not write NTFS file systems out of the box)

    What I meant was... MAc OS Extended/Apple Partition Map can be used with an Intel machine, just not to boot the computer... works fines as an audio/data disk.

    pancenter-
  • DamonGrant Level 1 Level 1 (0 points)
    Ok , Thanks guys. But it looks like re-partitoning may not be the answer to my problems. What do you think? I'll give it a go anyway, but just wondering if there may be other causes?
  • Eriksimon Level 6 Level 6 (11,780 points)
    DamonGrant wrote:
    Ok , Thanks guys. But it looks like re-partitoning may not be the answer to my problems.


    Why on earth not? Seems pretty likely to me. I have a spare disk right now, I'll try it out myself. Back in a jiffy!
  • Eriksimon Level 6 Level 6 (11,780 points)
    Hmm, OK, it is bad news for this issue - I can record to an MBR formatted disk no problem. The only factor that is different, is that mine is a SATA disk, not FireWire. Alas I have no FW disk I can format to test. But it seems like the MBR partitioning should not be a problem.
  • DamonGrant Level 1 Level 1 (0 points)
    Ok I did this and still have the problem...anyone else got any ideas?....It's a drag when you lose a good take!
  • Eriksimon Level 6 Level 6 (11,780 points)
    And what happens when you (for testings' sake) record to your startup disk? Does that work?

    Have you tried recording to a different or new folder on the same disk?

    It could be a FireWire chipset issue (I hope not, but it could) or it could be a FireWire chipset driver (system-) issue. It would help if you somehow got a hold of a different FW disk that has proven to work. If that also fails, we know it is your system at fault, if it works, we know it must be your disk that is at fault.

    EWhen did this behaviour start? Installed anything new just before this started happening?

    What you could also try is to create a new User account, boot into it and see if the problem persists or not.
  • DamonGrant Level 1 Level 1 (0 points)
    Thanks for those suggestions Erik...

    It's been happening for a month I guess and I don't think that anything new's been installed. I will try recording to the start up disc and to maybe to some USB discs I have.

    It seems to happen after working on a project for some time. After say tracking takes for 45 mins or so. Maybe it's just coincidence, but do you think that might indicate a hardware issue?

    Thanks

    Damon
  • Eriksimon Level 6 Level 6 (11,780 points)
    DamonGrant wrote:
    Thanks for those suggestions Erik...

    It's been happening for a month I guess and I don't think that anything new's been installed. I will try recording to the start up disc and to maybe to some USB discs I have.

    It seems to happen after working on a project for some time.
    After say tracking takes for 45 mins or so. Maybe it's just coincidence, but do you think that might indicate a hardware issue?


    Now there might be a clue. What happens when you then quit Logic, reboot your Mac, and reopen the active session? It might be that your disk has become a bit messy from all the traffic, and it just needs to 'settle' in OS X again. Click on the *Spotlight icon* top right of your screen and see if any indexing is taking place. Wait for it to finish before launching Logic.
    Alternatively, you could exclude your recording disk from Spotlight indexing alltogether, by dragging the disk to the Privacy field in the Spotlight Sysprefpane.

    One other thing to do: turn off Journaling , using *Disk Utility.* Select your recording volume in Disk Utility, hold the alt key while dropping down the File menu. Choose *Disable Journaling.*

    On the other hand, it might also point to a RAM issue. Do you ever suffer Kernel panics (=the darkening 'curtain' and the message "You need to restart your Mac... etc")? or 'unexplained' crashes? If not or very rarely, I'ld rule out a RAM issue. If daily, it could be. What you can try in this case is to turn of your Mac and physically take out and reinsert your RAM.
    And when you trash (=eject/unmount), physically disconnect and reconnect your recording disk? Does that help? (Logic should not be running when you do this)
  • DamonGrant Level 1 Level 1 (0 points)
    Thanks again for those extra suggestions. I'll try some of them over the next day or two and let you know how I go.

    I don't think it's the RAM issue as I don't experience kernel panics or crashes.

    I appreciate the suggestions!
Previous 1 2 Next