Mini trying to eject non existent disk, every 12 seconds

Long story cut short, I had a DVD get stuck in my mini, but persuaded it out by holding it slot down (eventually). Trouble is it is still trying to eject the disk, about every 12 seconds.
Any suggestions on how I can get it to stop!
Cheers

The drive is clearly not functioning correctly or it would not have released the disk in the first place. The fact it seemed quite hard to get it into the drive is a further possible indicator, though slot loading drives do offer quite high levels of resistance when a disk is inserted, just to make sure that the drive isn't likely to try and swallow objects that are perhaps not intended!
The more you describe this though, the more it sounds to me as if it's going to be inevitable to open the system up and examine the drive, or simply add an external optical drive and ignore the internal one - at least for the time being. It certainly doesn't sound to me like a simple issue of the drive being misaligned, and while transporting the system in a bag rather than packed up neatly might have shaken it about a bit, the internal frame on which the drive is mounted is not prone to movement, and nor is the outer casing.

Similar Messages

I've just updated OS to 10.10.1 and Finder keeps trying to open and then closes every 2 seconds with the message Finder is not Available. If Safari is opened full window it immediately closes and will only work with window smaller than maximum.

I've just updated OS to 10.10.1 and Finder keeps trying to open and then closes every 2 seconds with the message Finder is not Available. If Safari is opened with the window full screen it immediately closes and will only work with window smaller than maximum. Driving me mad! Any help please!!

Hi Linc
Thank you for your response.
I'm a bit of an amateur so I hope below is the information you've asked for:
Step 1
23/11/2014 09:19:14.007 ReportCrash[294]: Saved crash report for Finder[4349] version 10.10.1 (10.10.1) to /Users/AAAA/Library/Logs/DiagnosticReports/Finder_2014-11-23-091914_BBBB-MacBoo k-Pro-2.crash
23/11/2014 09:19:14.008 ReportCrash[294]: Removing excessive log: file:///Users/AAAA/Library/Logs/DiagnosticReports/Finder_2014-11-23-091840_BBBB -MacBook-Pro-2.crash
23/11/2014 09:19:14.000 kernel[0]: CODE SIGNING: cs_invalid_page(0x103809000): p=4357[Finder] final status 0x3000a00, denying page sending SIGKILL
23/11/2014 09:19:14.000 kernel[0]: CODE SIGNING: process 4357[Finder]: rejecting invalid page at address 0x103809000 from offset 0x3f000 in file "" (cs_mtime:0.0 == mtime:0.0) (signed:0 validated:1 tainted:1 wpmapped:0 slid:0)
23/11/2014 09:19:14.454 com.apple.xpc.launchd[1]: (com.apple.Finder[4357]) Binary is improperly signed.
23/11/2014 09:19:14.454 com.apple.xpc.launchd[1]: (com.apple.Finder) Service only ran for 0 seconds. Pushing respawn out by 1 seconds.
23/11/2014 09:19:15.584 Finder[4359]: assertion failed: 14B25: libxpc.dylib + 97940 [9437C02E-A07B-38C8-91CB-299FAA63083D]: 0x89
23/11/2014 09:19:15.000 kernel[0]: CODE SIGNING: cs_invalid_page(0x10bfbf000): p=4359[Finder] final status 0x3000a00, denying page sending SIGKILL
23/11/2014 09:19:15.000 kernel[0]: CODE SIGNING: process 4359[Finder]: rejecting invalid page at address 0x10bfbf000 from offset 0x3f000 in file "" (cs_mtime:0.0 == mtime:0.0) (signed:0 validated:1 tainted:1 wpmapped:0 slid:0)
Step 2
Process:               Finder [4626]
Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Identifier:            com.apple.finder
Build Info: Finder_FE-932001003000000~1
Responsible:           Finder [4626]
PlugIn Path: /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
PlugIn Identifier:       com.apple.finder
-0 sec                         CODE SIGNING: cs_invalid_page(0x10c9a5000): p=4626[Finder] final status 0x3000a00, denying page sending SIGKILL
-0 sec                         CODE SIGNING: process 4626[Finder]: rejecting invalid page at address 0x10c9a5000 from offset 0x3f000 in file "" (cs_mtime:0.0 == mtime:0.0) (signed:0 validated:1 tainted:1 wpmapped:0 slid:0)
-2 sec                         CODE SIGNING: cs_invalid_page(0x10c5b3000): p=4624[Finder] final status 0x3000a00, denying page sending SIGKILL
-2 sec                         CODE SIGNING: process 4624[Finder]: rejecting invalid page at address 0x10c5b3000 from offset 0x3f000 in file "" (cs_mtime:0.0 == mtime:0.0) (signed:0 validated:1 tainted:1 wpmapped:0 slid:0)
-3 sec                         CODE SIGNING: cs_invalid_page(0x10f4bd000): p=4622[Finder] final status 0x3000a00, denying page sending SIGKILL
-3 sec                         CODE SIGNING: process 4622[Finder]: rejecting invalid page at address 0x10f4bd000 from offset 0x3f000 in file "" (cs_mtime:0.0 == mtime:0.0) (signed:0 validated:1 tainted:1 wpmapped:0 slid:0)
-5 sec                         CODE SIGNING: cs_invalid_page(0x105ecf000): p=4620[Finder] final status 0x3000a00, denying page sending SIGKILL
-5 sec                         CODE SIGNING: process 4620[Finder]: rejecting invalid page at address 0x105ecf000 from offset 0x3f000 in file "" (cs_mtime:0.0 == mtime:0.0) (signed:0 validated:1 tainted:1 wpmapped:0 slid:0)
-7 sec                         CODE SIGNING: cs_invalid_page(0x1012cd000): p=4617[Finder] final status 0x3000a00, denying page sending SIGKILL
-7 sec                         CODE SIGNING: process 4617[Finder]: rejecting invalid page at address 0x1012cd000 from offset 0x3f000 in file "" (cs_mtime:0.0 == mtime:0.0) (signed:0 validated:1 tainted:1 wpmapped:0 slid:0)
--> __TEXT 000000010c966000-000000010ce55000 [ 5052K] r-x/rwx SM=COW /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
    __DATA 000000010ce55000-000000010cf53000 [ 1016K] rw-/rwx SM=COW /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
0   com.apple.finder                                 0x000000010c9a521f 0x10c966000 + 258591
10 com.apple.finder                               0x000000010c9977b5 0x10c966000 + 202677
11 com.apple.finder                               0x000000010c988154 0x10c966000 + 139604
12 com.apple.finder                               0x000000010c987e15 0x10c966000 + 138773
13 com.apple.finder                               0x000000010c987d35 0x10c966000 + 138549
14 com.apple.finder                               0x000000010c987cfd 0x10c966000 + 138493
28 com.apple.finder                               0x000000010c96b960 0x10c966000 + 22880
1   com.apple.finder                                 0x000000010c98a69d 0x10c966000 + 149149
2   com.apple.finder                                 0x000000010c98aba7 0x10c966000 + 150439
3   com.apple.finder                                 0x000000010c9795d2 0x10c966000 + 79314
4   com.apple.finder                                 0x000000010c98aa0b 0x10c966000 + 150027
5   com.apple.finder                                 0x000000010c98a952 0x10c966000 + 149842
6   com.apple.finder                                 0x000000010c98a78a 0x10c966000 + 149386
7   com.apple.finder                                 0x000000010c979496 0x10c966000 + 78998
8   com.apple.finder                                 0x000000010c98a548 0x10c966000 + 148808
9   com.apple.finder                                 0x000000010c98a410 0x10c966000 + 148496
10 com.apple.finder                               0x000000010c983df6 0x10c966000 + 122358
       0x10c966000 -        0x10ce54ffb com.apple.finder (10.10.1 - 10.10.1) <33C3024A-4A16-3485-B2B1-89FA33B9558A> /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder
Many thanks
David

Init writes to disk every few seconds?

Just wondering if anyone knows why init is writing 16K to disk every few seconds. It kinda annoys me.
I'm using the standard 2.6.11 kernel -- nothing special about the daemons I'm running, either.

Try this, courtesy of Baltwo. It will delete the Spotlight V-100 index and then force Spotlight to re-index.
Be absolutely certain to only copy/paste these commands exactly. DO NOT try to type these in. One typo or wrong space in the first one could wipe your drive competely. Hit return after each.
Delete the entire Spotlight directory and reindex, running these commands in the Terminal app:
*sudo rm -R /.Spotlight-V100*
*sudo mdutil -i on /*
*sudo mduitl -E /*
https://discussions.apple.com/message/12988300#12988300

IPhoto repeatedly tries to import non-existing photos

I recently deleted 100 photos from iphoto. Now whenever I open iPhoto a box pops up that says "2 photos have been found in the iPhoto library that have not been imported. Would you like to import them?" Whether I click yes or no, a second box will pop up saying that the photos have been placed in a recovery file. This process happens 2 times every time I open iPhoto. The empty "recovery" files continue to build each time this happens. How do i make iPhoto stop asking me about these 2 non-existent photos, and how do I make it stop creating recovery files?

Go to your Pictures Folder and find the iPhoto Library there. Right (or Control-) Click on the icon and select 'Show Package Contents'. A finder window will open with the Library exposed.
Look there for a Folder called 'Import' or 'Importing'.
Drag it to the Desktop. *Make no other changes*.
Start iPhoto. Does that help?
If it does then look inside that folder on your desktop. Does it contain anything you want? If not you can trash the folder.
Regards
TD

Hard disk always working - sync_supers writting to disk every 5 second

As the topic says. My computer is on my desk while I work and I can't stand the noise of hard disk doing something every 5 seconds. I think I noticed this since 2.6.36 kernel.
When computer is completely idle it still writes to disk.
Tried Ubuntu 10.10 and got the same result. I have WD Caviar Blue 500gb. On ext4 filesystem there is jbd2/sda* doing write every 5 seconds or so and on reiserfs there is sync_supers doing the same. I guess those that is journaling acitivy, but its anoying to hear hard drive working when computer is completely idle.
Any tips?

linux wrote:Does anyone know the destination where sync_supers is writing to?
The Linux kernel mailing list has some information that may help on identifying what sync_supers is doing, http://lkml.org/lkml/2012/4/11/147.
While you wait for kernel patches, there are some mount options that other people have suggested may help:
Use noatime or at least relatime for ext* filesystems
Use the option commit=60 or commit=300 to lengthen the time between syncs of data and metadata from 5 seconds to 1 or 5 minutes. However, if the computer crashes between commits there may be some data loss.
Use hdparm to change the acoustic management settings – https://bbs.archlinux.org/viewtopic.php … 5#p1063185

Process "mdworker" Writes to Disk Every 10 Seconds

I noticed disk activity occurring every 10 seconds while my computer was idle. In Activity Monitor I could see this writing going on and at the same time the process "mdworker" would tick up just a little bit of processor activity. A Restart didn't help. The following is what I did to make it stop. I've seen many posts on here with a similar problem so maybe this info will be helpful to someone.
I brought up a Terminal window and entered the following command:
sudo fs_usage -w -f filesys
That will show youa continuous list of all processes that are reading/writing to disk (use Control-c to make it stop). I found mdworker doing a fair amount of disk activity every 10 seconds. But the important thing is that it was the identical activity every 10 seconds, and the common thing in almost every entry was "Default Folder X". So I concluded that it was having trouble indexing something about Default Folder's data. (mdworker is used to index your data via Spotlight.) After uninstalling and reinstalling Default Folder, the constant writing stopped and has yet to happen again.
If you're having a problem similar to this you may find this method of identifying the culprit and fixing it useful.

Try this, courtesy of Baltwo. It will delete the Spotlight V-100 index and then force Spotlight to re-index.
Be absolutely certain to only copy/paste these commands exactly. DO NOT try to type these in. One typo or wrong space in the first one could wipe your drive competely. Hit return after each.
Delete the entire Spotlight directory and reindex, running these commands in the Terminal app:
*sudo rm -R /.Spotlight-V100*
*sudo mdutil -i on /*
*sudo mduitl -E /*
https://discussions.apple.com/message/12988300#12988300

What program access hard disk every 30 second?

I have a very loud hard disk. The hard disk make a very short noice every 30 seconds, even for a new boot. Anyway to check which programming access the hard disk repeatly so I can figure out if it's possible to make the machine quiet?

somthing I read about disk flush/sync timings. There is some sort of 'laptop' mode in some kernels that if set will cause the disk to sync after a period of time in order to let APM/ACPI put the drive to sleep.
There may be settings for your filesystem to do the same(!?). I remember old Windoze NT4 had similar problem and was not remedied until Win2k for use on laptops .... yuck, ... I said the W word.
Here's something I just dug-up:
Laptop mode ===========
This small doc describes the 2.4 laptop mode patch.
Last updated 2003-05-25, Jens Axboe <[email protected]>
Introduction ------------
A few properties of the Linux vm makes it virtually impossible to attempt to spin down the hard drive in a laptop for a longer period of time (more than a handful of seconds). This means you are lucky if you can even reach the break even point with regards to power consumption, let alone expect any decrease.
One problem is the age time of dirty buffers. Linux uses 30 seconds per default, so if you dirty any data then flusing of that data will commence at most 30 seconds from then. Another is the journal commit interval of journalled file systems such as ext3, which is 5 seconds on a stock kernel. Both of these are tweakable either from proc/sysctl or as mount options though, and thus partly solvable from user space.
The kernel update daemon (kupdated) also runs at specific intervals, flushing old dirty data out. Default is every 5 seconds, this too can be tweaked from sysctl.
So what does the laptop mode patch do? It attempts to fully utilize the hard drive once it has been spun up, flushing the old dirty data out to disk. Instead of flushing just the expired data, it will clean everything. When a read causes the disk to spin up, we kick off this flushing after a few seconds. This means that once the disk spins down again, everything is up to date. That allows longer dirty data and journal expire times.
It follows that you have to set long expire times to get long spin downs. This means you could potentially loose 10 minutes worth of data, if you set a 10 minute expire count instead of just 30 seconds worth. The biggest risk here is undoubtedly running out of battery.
Settings --------
The main knob is /proc/sys/vm/laptop mode. Setting that to 1 switches the vm (and block layer) to laptop mode. Leaving it to 0 makes the kernel work like before. When in laptop mode, you also want to extend the intervals desribed above. See the laptop-mode.sh script for how to do that.
It can happen that the disk still keeps spinning up and you don't quite know why or what causes it. The laptop mode patch has a little helper for that as well, /proc/sys/vm/block-dump. When set to 1, it will dump info to the kernel message buffer about what process caused the io. Be very careful when playing with this setting, it is advisable to shut down syslog first!
Result ------
Using the laptop-mode.sh script with its default settings, I get the full 10 minutes worth of drive spin down. Provided your work load is cached, the disk will only spin up every 10 minutes (well actually, 9 minutes and 55 seconds due to the 5 second delay in flushing dirty data after the last read completes). I can't tell you exactly how much extra battery life you will gain in laptop mode, it will vary greatly on the laptop and workload in question. The only way to know for sure is to try it out. Getting 10% extra battery life is not unrealistic.
Notes -----
Patch only changes journal expire time for ext3. reiserfs uses a hardwire value, should be trivial to adapt though (basically just make it call get_buffer_flushtime() and uses that). I have not looked at other journalling file systems, I'll happily accept patches to rectify that!

OVM Servers trying to start non-existing VM??

Hi,
all of my OVM servers log(AdminServer.log) are continually reporting error message:
[2011-10-24 16:33:25 15835] ERROR (OVSCommons:142) catch_error: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg'] failed (1): Error: Unable to open config file: /OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg
Traceback (most recent call last):
File "/opt/ovs-agent-3.0/OVSCommons.py", line 140, in wrapper
return func(*args)
File "/opt/ovs-agent-3.0/vm.py", line 558, in start_vm
run_cmd(['xm', 'create', path])
File "/opt/ovs-agent-3.0/OVSCommons.py", line 31, in run_cmd
raise RuntimeError('Command: %s failed (%s): %s ' % (cmd,
RuntimeError: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg'] failed (1): Error: Unable to open config file: /OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg
In my repository there's no such location. Recently, I've reinstalled OVMM 3.0.2 and imported .dmp file, redisovered pool, servers and my VM's are running fine, but still there's this error in OVMM AdminServer.log.
I truly hope that I'll get an answer this time :(
Thanks.

My advice is not to reimport the .dmp file -- rather, re-install your manager using the same UUID as before and then just discover your servers/repositories. It will rebuilt the DB from the on-disk data and thus should not have any phantom VM data left.Avi,
I've done this, everything is working fine, AdminServer.log have no errors, but ovs-agent.log on every OVM server still have this message:
[2011-10-25 10:20:22 24604] ERROR (OVSCommons:142) catch_error: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg'] failed (1): Error: Unable to open config file: /OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg
Traceback (most recent call last):
File "/opt/ovs-agent-3.0/OVSCommons.py", line 140, in wrapper
return func(*args)
File "/opt/ovs-agent-3.0/vm.py", line 558, in start_vm
run_cmd(['xm', 'create', path])
File "/opt/ovs-agent-3.0/OVSCommons.py", line 31, in run_cmd
raise RuntimeError('Command: %s failed (%s): %s ' % (cmd,
RuntimeError: Command: ['xm', 'create', '/OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg'] failed (1): Error: Unable to open config file: /OVS/Repositories/0004fb0000030000944aa10331c83564/VirtualMachines/0004fb000006000080e85156ed2c669d/vm.cfg
Is it ok to ignore and wait for 3.0.3 patch release, or what?
Thanks.

Tiger upgrade of mail tries to import non existant messages

On my G5 17" iMac, I've upgraded from Panther to Tiger. I can't upgrade to 10.5 because I need some OS 9 aps. The first time I open Mail in Tiger, it wants to import my 2 imap accounts. It is trying to import messages I've deleted and cleared. I synced the mail accounts on another computer and the imap account shows there are less than 2000 messages. Mail is trying to import 12k and gets hung up around 2.6k. I wants 5 hours to do the import. I tried restarting the computer. I re-synced the mail accounts and mail rules. And the thing still wants to import messages that I've cleared from the imap server.
Ideas?
Thanks.

The conversion from Mail 1.x to Mail 2.x is broken, but it isn’t clear what the problem really is nor what it really is that Mail is trying to import in your case. I’d set up Mail again from scratch and manually import back afterwards any messages you may have stored in local mailboxes, as follows:
1. Quit Mail if it’s running.
2. In the Finder, go to ~/Library/. Move (not copy) the entire Mail folder out of there, to the Desktop.
3. In the Finder, go to ~/Library/Preferences/. Locate com.apple.mail.plist and move it to the Desktop.
4. Open Mail and set it up again from scratch. If given the option to import existing mailboxes or something like that, don’t. Just enter the account information and check that everything works fine.
5. You’ll have to re-configure your Mail > Preferences settings. For spam-related security reasons, the first thing you should do is go to Preferences > Viewing and disable Display remote images in HTML messages if it’s enabled.
6. If Mail works fine now and you had any messages stored in local mailboxes, do File > Import Mailboxes and follow the instructions to import your mail from the old Mail folder that’s now on the Desktop. Import the Mailboxes folder first, then each of the POP-username@mailserver account folders, if any.
There are two ways to import Mail 1.x mailboxes into Mail 2.x. The obvious one is importing them as Mail for Mac OS X. But Mail 1.x stored mail in standard mbox format plus some additional support files, and this allows Mail 1.x mailboxes to also be imported as Other, i.e. as generic mailboxes in standard mbox format.
Importing as Mail for Mac OS X produces the best results when it works, because it takes into consideration all the files in the mailboxes, not just the mbox files where the messages are stored, and hence, allows information such as status flags to be preserved. Importing as Other, on the other hand, may work in cases where importing as Mail for Mac OS X doesn’t, because it looks at the mbox files only, ignoring the support files which is what Mail 2.x usually chokes on, but precisely because of that, information such as status flags is lost and previously deleted messages may reappear.
Hence, you may try importing as much as you can as Mail for Mac OS X, then import the problematic mailboxes as Other.
Note that what Mail asks for when importing depends on the format chosen. Mail always asks for the folder that contains the “things” to be imported. If Mail for Mac OS X is chosen as the data format, the “things” to be imported are the .mbox folders, so you must choose the folder that contains them, not the .mbox folders themselves. On the other hand, if Other is chosen as the data format, the “things” to be imported are the mbox files, so choosing the .mbox folders would work in that case.
As a result of doing the above, some messages may be duplicated. Andreas Amann’s Mail Scripts has a Remove Duplicates script that you may find useful.
Do with the imported mail whatever you wish. You may move the messages to other mailboxes and get rid of the imported mailboxes afterwards if you want.
If all is well and you don’t miss anything, the files on the Desktop can be deleted, although you may want to keep them for a while, just in case.
Note: For those not familiarized with the ~/ notation, it refers to the user’s home folder. You can easily locate any of the folders referred to in this post by copying the folder path here, doing Go > Go to Folder in the Finder, and pasting the folder path there.

SCCM Trying to Transfer Non-Existent Package

Our SCCM site is trying to transfer a package that no longer exists to the remote distribution points it was initially distributed to. The SMS_PACKAGE_TRANSFER_MANAGER log shows "Package Transfer Manager is retrying to distribute package <package
ID> to distribution point <DP FQDN>. Wait to see if the package is successfully distributed on the retry." It has been trying this for two weeks now. How can I force SCCM to recognize that this package no longer exists? If
it matters, the package was Software Updates Deployment Package.

Since no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

Reader looks for non-existent Disk

When I run Reader (X), on occasion (but most times) it displays a dialog box telling me there is no disk in Drive E: (which is one of my CD drives). The files I'm reading are on a different drive. I have to click Cancel twice to continue work. How can I stop this?

There may be something in your registry that points to that E: drive.
Try if this can find and fix it: http://fixitcenter.support.microsoft.com/Portal/

AME looking for non-existent disk drives and now disappeared from hard drive.

AME stopped launching for some reason. now its completely left my system. Reinstall of Premiere Pro CS6 family in Creative Cloud App Manager does not help reinstall AME. How do I get AME back and working?
Windows 8, fast computer, all the other Creative Cloud apps working perfectly.
thanks

Have you verified, that it actualyl exists in your Program Files\Adobe Folder. Did you run the Creative Suite Cleaner Tool? Have you flushed the AME/ PPro prefs?
Mylenium

RMAN is trying to read non-existing files

We have an application that runs on two
Oracle databases - one serves as processing engine and another one as a data warehouse.
The enformation is exchanged using transportable tablespaces - they are plugged in into the warehouse, information is moved
using INSERT AS SELECT, and then
these tablespaces are dropped.
After the drop is completed, I attempt to
run database-level incremental backup of the
warehouse. After allocating channels and doing "implicit partial resync of the recovery catalog" RMAN displayes messages
RMAN-06052: no parent backup or copy of datafile 317 found.
The same message is displayed for files
313
314
316
317
319
320
321
But there is no file 317 in the database!
SELECT * from V$DATAFILE WHERE File#=317
returns no rows
These files do appear in SYS.FILE$
where they have STATUS$ column equal to 1,
while most other files have STATUS$ = 2.
However, there are quite a few other files
in SYS.FILE$ that also have STATUS$=1 (up to File#=333), but RMAN does not list them.
I know that RMAN-06052 is an "information" message indicating that RMAN could not find level-0 (or "parent") backup, but why is it listing files that have been dropped?
Environment:
Oracle 8.1.6.0.0 on Sun Solaris 2.7
Regards,
Sev
null

We need the following information:
Complete RMAN output from the incremental backup.
Output from the following query, run at the target database:
select * from v$datafile where file# in (313,314,316,317,319,320,321);
select * from file$ where file# in (313,314,316,317,319,320,321);
and the following query, run at the recovery catalog:
select * from rc_datafile where file# in (313,314,316,317,319,320,321);
These queries should be run immediately after the incremental backup that they
are concerned about.
You may want to open a TAR with support and upload trace files or see if you can post the information here.
Thanks.

Generic problem: superdrive malfunction - trying to eject disk?

I've previously posted this problem on the Powerbook thread, but following my initial problem of not getting a stuck disk out of the superdrive, this seems to have progressed into a more serious issue which may be solved using a generic OSX solution?
It started a stuck disk in the drive, so I used a credit card and a sharp, very thin letter opener (metal) and used them like tweezers to force the disk out.
However, now I'm left with a machine that continually tries to eject an imaginary disk, over and over again. But the disk has been forced out by myself.
Can I over-ride this command in Terminal or somewhere else?
Thank you in advance.
C Marks

Hi Carey,
Optical drives are all too short lived i my experiences, Slot loading ones the worst.
This may take a few back & forths, but...
In Finder, select Go menu>Go to Folder, and go to "/volumes".
Volumes is where an alias to your hard drive ("/" at boot) is placed at startup, and where all the "mount points" for auxiliary drives are created for you to access them. This folder is normally hidden from view.
Drives with an extra 1 on the end have a side-effect of mounting a drive with the same name as the system already think exists. Try trashing the duplicates with a 1 or 2 if there are no real files in them, and reboot.
Safe Boot , (holding Shift key down at bootup), use Disk Utility from there to Repair Permissions, test if things work OK in Safe Mode.
Then move these files to the Desktop...
/Users/YourUserName/Library/Preferences/com.apple.finder.plist
/Users/YourUserName/Library/Preferences/com.apple.systempreferences.plist
/Users/YourUserName/Library/Preferences/com.apple.desktop.plist
/Users/YourUserName/Library/Preferences/com.apple.recentitems.plist
Reboot & test.

IPhoto "importing" spurious non existing photos

iPhoto constantly tries to "import" 2 non existing photos every time it opens.
I tried import as an answer to the - do you wish to import? question as well as No in answer to the annoying start-up question, but all to no avail.
How do I stop this annoying start-up?
Please assist if you know the cause..

Quit iPhoto and to to the iPhoto library (by default in your pictures folder) - right click (control click) on it and select show package contents - find the folder named import (on importing) and drag it to the desktop - DO NOT MAKE ANY OTHER CHANGES - launch iPhoto and you will be fine.
Open the import(ing) folder and if there is nothing in it that you need move it to the trash and empty the trash
LN

Mini trying to eject non existent disk, every 12 seconds

Similar Messages

Maybe you are looking for