Currently Being ModeratedMay 13, 2012 10:26 PM (in response to dalidrama)
It sounds as though you are getting a Kernel Panic, which is only partially related to you deleting the file.
Can you open Finder and click Go->Go To Folder and open ~/Library/Logs/DiagnosticReports/
If you can paste the contents of the last kernel panic, that'd be helpful.
Currently Being ModeratedMay 13, 2012 10:34 PM (in response to dalidrama)
Try deleting it from the terminal (in Utilities). Type rm -f followed by a space. Then drag the file icon into the terminal window. You should have a line that looks similar to this:
rm -f /path/to/file
Hit return and hope for the best. Given the file's size it still may take a little time before you see the terminal prompt again indicating completion.
Currently Being ModeratedMay 13, 2012 10:39 PM (in response to PaulKemp)
Sun May 13 21:33:15 2012
panic(cpu 0 caller 0xffffff80003224be): "jnl: transaction too big (1831424 >= 1834496 bytes, bufsize 4096, tr 0xffffff800b327f48 bp 0xffffff807a5b20e0)\n"@/SourceCache/xnu/xnu-1699.26.8/bsd/vfs/vfs_journal.c:262 3
Backtrace (CPU 0), Frame : Return Address
0xffffff807ee632b0 : 0xffffff8000220792
0xffffff807ee63330 : 0xffffff80003224be
0xffffff807ee63370 : 0xffffff80004d56a3
0xffffff807ee63390 : 0xffffff800050dc0d
0xffffff807ee63460 : 0xffffff800050926c
0xffffff807ee63540 : 0xffffff80005101da
0xffffff807ee637a0 : 0xffffff8000510294
0xffffff807ee63860 : 0xffffff8000510d6c
0xffffff807ee63930 : 0xffffff80004e9d74
0xffffff807ee639e0 : 0xffffff80004e9fe0
0xffffff807ee63a40 : 0xffffff80004de46c
0xffffff807ee63ad0 : 0xffffff80004dea22
0xffffff807ee63b10 : 0xffffff8000319b82
0xffffff807ee63b50 : 0xffffff80002ffb53
0xffffff807ee63b80 : 0xffffff80002ffc3c
0xffffff807ee63ba0 : 0xffffff800030bc67
0xffffff807ee63d90 : 0xffffff800030bd20
0xffffff807ee63f50 : 0xffffff80005cd61b
0xffffff807ee63fb0 : 0xffffff80002daa13
BSD process name corresponding to current thread: Finder
Mac OS version:
Darwin Kernel Version 11.4.0: Mon Apr 9 19:32:15 PDT 2012; root:xnu-1699.26.8~1/RELEASE_X86_64
Kernel UUID: A8ED611D-FB0F-3729-8392-E7A32C5E7D74
System model name: iMac8,1 (Mac-F227BEC8)
System uptime in nanoseconds: 2062336604249
last loaded kext at 46331332223: com.apple.filesystems.msdosfs 1.7.1 (addr 0xffffff7f8137a000, size 57344)
com.Logitech.Control Center.HID Driver 3.4.0
Currently Being ModeratedMay 13, 2012 10:47 PM (in response to X423424X)
Nope, crashed my computer. Something new, so appreciated.
Currently Being ModeratedMay 13, 2012 10:57 PM (in response to dalidrama)
Boot from your recovery partition and run Disk Utility to repair/verify your drives (not repair permissions). I think some disk repairs are needed. The rm should work no matter what the size.
Boot in safe mode and try the rm again while booted in this mode.
Currently Being ModeratedMay 13, 2012 11:23 PM (in response to dalidrama)
There is an old trick which may work.
Make a new folder and move the problem file into it.
Outside of that folder (like on the desktop) create a TextEdit file; it can be empty. Give it the exact same name as the problem file. Then drop it into the folder containing the problem file. A splash screen should appear; one of the choices offered should be "replace" - select that one.
If this works, the problem file should disappear immediately, replaced by the far smaller TextEdit file.
Currently Being ModeratedMay 14, 2012 6:02 AM (in response to Don Archibald)
Any reason it should be text edit? I already tried "replacing" the video with the same-named smaller file and it crashed the computer.
Currently Being ModeratedMay 14, 2012 6:27 AM (in response to dalidrama)
No, using a TextEdit file is just convenient; it can be any kind of file as long as the name is the same. Since you already tried it, doing it again probably won't work.
Currently Being ModeratedMay 14, 2012 9:02 AM (in response to dalidrama)
Looking at the last 4 loaded kexts:
com.Logitech.Control Center.HID Driver 3.4.0
Makes me wonder why the msdos file system kext is loaded.. a 15GB file cannot fit on a FAT partition if I remember correctly. Where is the file located and what file system is it on?
You may want to remove the Seagate and Logitech software temporarily and see if that helps (and make sure the kext is not loaded).
Lastly, if you really want to eliminate the possiblility of a HW issue, you can boot to another OS and try to delete the file. I'd say try the Lion Recovery Partition and Utilities->Terminal, but not sure if that mounts the HD with R/W access and don't currently have the ability to test that as an option.
Currently Being ModeratedMay 14, 2012 12:58 PM (in response to PaulKemp)
My last suggestion was to boot in safe mode and try the rm that way. A safe boot will suppress all those third party extensions (among other things) so that they don't have to be removed.
It is curious however why that msdosfs kext is running.
Currently Being ModeratedMay 14, 2012 8:06 PM (in response to X423424X)
I tried to trash it in safe mode: CRASHED. I tried to trash it in safe mode through Terminal: CRASHED.
No idea what this issue is. Looking at my other video projects, I have a 30GB video that I have rendered (and replaced) many times, but that is located on my external HD - this is probably the first time I placed something (large HD video) on my computer.
It's a real pain - if anyone thinks of anything else to try, I'd love to hear it. Otherwise, I've been eager to buy a new iMac since December and it looks like a new model is coming out in June so I can just deal with this large file on my desktop and wipe out the entire computer when I'm done with it.
Currently Being ModeratedMay 14, 2012 8:30 PM (in response to dalidrama)
Did you ever run Disk Utility from the recovery partition?
Currently Being ModeratedMay 18, 2012 8:09 AM (in response to X423424X)
What is the recovery partition? (how do i run "Disk Utility from the recovery partition?") thx
Currently Being ModeratedMay 18, 2012 8:14 AM (in response to dalidrama)
Restart holding down Command+R and it should be clear from there.