Coincidence or is it possible that the I/O errors are a direct correlation to the maintenance script?
Note that there were not I/O errors again until morning of Wednesday 13th when a new automated script was reintroduced. Doing this we had no performance hit on the application at all. While trying to rule out the maintenance script as potential cause we moved to manually stopping services, copying DB via commandline and starting services again. We terminated the automatic script as it was taking too long to complete and therefore overrunning the startup time of the application. The times seem to mostly coincide with periods when a maintenance run is copying database files to backup overnight (on same machine). The following sequence of I/O errors shows - I think the dates/times are relevant. First "error" I'd spotted in the log was BSD root: disk0s2, major 14, minor 2 which I've since learned is harmless.
Timing seems to coincide with a database copy during evening maintenance window rather than while "live".ĭoes the error signify imminent disk failure or potentially it could be down to software? I'm fairly new to Mac admin so any pointers on the above would be welcome.Ĭorrection to above - we started having performance issues morning of Monday 28Jul and the first I/O error showed up early hours of the 29th. The error crops up about 15 times in all over a 2 week period between 1 and 3 instances a day but not every day. I have run disk utility first aid and came up clean. The diskos2 error has me worried this is potential disk failure imminent based on some googling of the error. Problem has been happening for around 2 weeks now but the audit log error only started a few days ago so could be unrelated. Warning: audit space low (< 5% free)on audit log file-system I've spotted a couple of entries in the kernel.log which look somewhat alarming to whit: We have supplier looking into the app side of things but wanted to rule out hardware issues. Been chugging along just fine but recently (last 2 weeks) we've had issues with the apps needing to be restarted each day to avoid performance issues. Hardware specs Intel Core 2 Duo and 8GB RAM.
In addition, if needed, it includes a 1.66 GHz Intel Core Duo, an upgraded 2 GB of ram, and 120 GB of storage.įeel free to ask any other questions that may help to the solving of this problem.Been having some performance issues with a Mac Mini running a web application (Jboss/Tomcat). I attempted this Terminal method twice.Īs noted in the title, this Mac mini (Model A1176) is primarily running OS X 10.6.8, with a separate partition for 10.5.0. The pane where it is located is grayed out, and I attempted to use a Terminal command to change the name, which did work for a time, only to find it changed back the next time I booted it up.
The name is stuck as, exactly, STE3M19-02$. I am going to ask, firstly, the thing that personally bothers me most. For whatever reason, probably because of the background of the Macbook (Looked like a school computer), several things are now locked on the computer. From what I know, my friend attempted to use Migration Assistant from a Macbook onto the Mac mini I am writing about. Thank you for checking out my question.Ī bit of background information. Hello there! I am currently new to this site.