Disk I/O problem

Hi!
I have a problem when i migrating from my old server to new one..
Old server:
Windows 2003 SP2 + Oracle 10gR2
CPU Pentium 4 2.4
RAM 2 GB
DISK 2 x RAID 1 (one for systen and instance another for data files)
On this system i have disk I/O about 35 - 45 mb per sec.
New server:
Windows 2003 SP2 x86 + Oracle 10gR2 x86
CPU 2 x Xeon Dual Core 1.6
RAM 4 GB
DISK 1 x RAID 1(system and instance) 1 x RAID 10 (4 disks SATA) (data files).
When i create tablespace i have disk I/O (EM) about 35 mb/sec and when i try to load data in my new databae (i am using Data Pump import) i have I/O 1 mb/sec. How can i solve this problem?
When i runing Sisoft Sandra i get a result ~100mb/sec. But the ORION get me a very small result aproximetly the same as in old server.

I have a mistake...
Windows pefom. monitor say:
Disk E: (data files)
Idle time 65% (!!!!!!!)
Read ~2mb per sec.
Write ~3 per sec.

Similar Messages

Failed restore from TM, disk now reporting problems.

Hello,
I have, unfortunately, landed in a bad position... My Macbook was last backed up last May with Time Machine. A few days ago, the internal hard drive in the Macbook went bad and was replaced with a new one by Apple. They installed 10.5.5 on the machine, so the welcome video starts up when I turn it on. At the genius bar, they told me to use the time machine backup option after the welcome video to restore my files. However, when I select that option, the window does not show the external hard drive I use to store the time machine backup.
Since no drive or backup was listed in that window, I assumed that this problem was caused by an incompatibility between 10.5.5 (which Apple installed on the new hard drive) and the older version of the system stored in my TM backups from last May (maybe 10.5.3?). Plus, I can see all the TM backups when I plug the drive into my other computers.
I booted the Macbook off the OS 10.5 DVD, and I selected the Restore from TM Backup option. This quickly pulled up the backup info from the external hard drive, and it began the restore process. Toward the end of the restore, the process failed, and it suggested I restart and try again. I restarted (booting off DVD again) and tried to restore again. This time, it told me that it can't access the files and the disk may have problems. I plugged the disk into another computer and ran "verify" in disk utility. It said "invalid index key," the volume needs to be repaired- Error: Filesystem verify or repair failed."
Here's my problem- I'm not sure that I want to mess with repairing the drive, as I don't want to potentially screw up the TM backup file structure. I don't have another copy of the info in these TM backups, since the original internal hard drive crashed and this is my restore option. Should I use a program like Superduper to make a copy before attempting a repair on the external drive? Is it likely a repair on the drive will screw up the TM backup data? I'm not really sure how to proceed safely.
Any help is greatly appreciated!
Thanks for your time.
~ Dan

Hi, Glenn,
Thanks for the suggestions. As an update, I did two clones of the drive using SuperDuper onto two other external drives. Both of those clones were successful, but none of the time machine backup data pulls up through the Leopard DVD, Time Machine itself, or through Migration Assistant. Disk utility finds errors in the data on both of the clones, but fixing the errors doesn't help the situation in any way.
In efforts to clean up the disk errors or pull the data off the drives manually, I have used Disk Warrior, Data Rescue II, File Salvage, and Disk Utility. Unfortunately, none of these apps have worked as a fix. I can't even seem to salvage the individual files to transfer them manually, leading me to believe that Time Machine is a deck of cards when part of the files become corrupted... What is frustrating is that I was able to see all of the backup files when I began the first restore process. Now I can't see them at all. I've never had a problem with the external disk drive, and all the utility programs seem to indicate that the problems are with the files versus the drive.
Any other ideas on how to get these files extracted? Given the 60GB or so of data recorded on the disk, I know the info is sitting there somewhere... I just can't get to it.
Thanks for the help!

Low Disk Space & Online Problem

Hi... need some help
first problem "Low Disk Space"
second problem after i free up some space, then i get Online all my free space is gone?
are they any virus or some thing that eat up my space...
Please help.
Thanks.

This is not due to a virus, or any other kind of malware.
For help solving the problem, see:
Where did my Disk Space go?

"Windows could not start because of a computer disk hardware configuration problem. "

My hp mini notebook 100-300 is continues reboot, i have done format os and try to install window xp thorough bootable pendrive, after finished installation, system is restart as show message as " "Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk. Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information."
so please help me what i do next...........

AmitNandha wrote:
My hp mini notebook 100-300 is continues reboot, i have done format os and try to install window xp thorough bootable pendrive, after finished installation, system is restart as show message as " "Windows could not start because of a computer disk hardware configuration problem. Could not read from the selected boot disk. Check boot path and disk hardware. Please check the Windows documentation about hardware disk configuration and your hardware reference manuals for additional information."
so please help me what i do next...........
Here's the problem XP will not install and work correctly that is why your getting that message.....Stay with the O/S that came with the laptop if you want to have stability in software and hardware operations.
I am a Volunteer to help others on here-not a HP employee.
Replies aren't online 24/7 because of Time Zone differences.
Remember in this Day and Age of Computing the Internet is Knowledge at your fingertips if you choose understand it. -2015-

Hi I just updated from Snow Leopard to Mountain Lion. I write DVD's using Final Cut Pro, creating a DVD that plays HD and Standard Definition on one disk. My problem is when I used load the disk on my G5 it would ask if you want High Definition or Standar

Hi I just updated from Snow Leopard to Mountain Lion.
I write DVD's using Final Cut Pro, creating a DVD that plays HD and Standard Definition on one disk.
My problem is when I used load the disk on my G5 it would ask if you want High Definition or Standard Definition, now it just defaults to Standard Definition.(I'm using Apple's DVD Player)
Can I fix this problem?

Addendum: I read on a post here (http://forums.macrumors.com/showthread.php?t=420169) about removing some kext files in order to trick OSX into thinking that there were no FireWire ports.
I followed the instructions and removed from /System/Library/Extensions/ the following files:
IOFireWireSerialBusProtocolTransport.kext
IOFireWireAVC.kext
IOFireWireFamily.kext
IOFireWireIP.kext
IOFireWireSBP2.kext
I restarted and BAM...Snow Leopard booted crazy fast and the mouse and keyboard worked instantly.
The System Profiler says "No FireWire ports were found."
So this tells me that the FW port is probably the culprit and is messing up the installation.
So how do I hack the Mountain Lion installer and tell it to ignore the FW port, which is obviously quite dead? Or is there something I can do to the Base system that is similar?

Burned disk has permissions problem

I have burned 4 or 5 bad DVDs trying to figure this out and getting nowhere. I have a folder of photos on my desktop. When I tell the Mac to burn them to disk, the resulting disk had permission problems. The folders have minus signs in little red circles, and the only pemission is "everyone" has NO read or write permission.
The original permissions for the folder I burned were read and write for me, and read for everyone. I tried changing to read and write for everyone. I tried burning it directly from the finder, and I tried using disk utility. I would be grateful if anyone can give me a clue.
Jim

I repaired permissions; still burning coasters. Any ideas out there?

When updating to Mountain Lion I get this measageThis disk has S.M.A.R.T. errors. This disk has hardware problem that can't be repaired. Back up as much data as possible and replace the disk.

When updating to Mountain Lion I get this measage
This disk has S.M.A.R.T. errors. This disk has hardware problem that can’t be repaired. Back up as much data as possible and replace the disk.
never had this before download of Mountain Lion.

As others have stated, this is a potentially catastrophic event. Consider yourself lucky, as hard drives usually just fail wihtout warning. Your disk could die at any time. This is a mechanical / physical failure, not software related.
Going forward, I would suggest utilizing a utility that monitors SMART status, which you obviously don't have, such as SpeedTools.

External Hard disk has space problem for Time Machine

Im not sure this is the right place to post this, but I've just got OSX.5 so Time Machine is new to me. I've got a 500Gb Firewire Lacie Drive which I now have, as far as I can see, about 110GB of stuff in. I have a bout 300Gb to back up. Currently my mac can only see 260GB free, which means theres about 150GB that isnt explained. I have run Disk Inventory, which shows the dot files on the drive. There seem to be hardly any. Is there anything else that could be taking up such a large amount of disk space? Theres one movie file of 28GB that I cannot move off the drive.

Tim Whelan2 wrote:
Im not sure this is the right place to post this, but I've just got OSX.5 so Time Machine is new to me. I've got a 500Gb Firewire Lacie Drive which I now have, as far as I can see, about 110GB of stuff in.
Let's see what Disk Utility (in your Applications/Utilities folder) says. When it starts, click the top line for your drive in the sidebar (should have size and make), then the Partition tab. Towards the bottom is a *Total Capacity* line, followed by two different numbers: one in GB, the other in bytes. The first will be about 465 GB, the second roughly 500 billion. This is the different way of counting: decimal vs. binary.
There's also a *Partition Map Scheme* line. This should be followed by GUID or +Apple Partition Map.+ If your drive isn't one of those, you're going to have a problem using it with Time Machine. Report back what this says.
In the center part of the display is a diagram showing all the partitions currently on the disk. Each is represented by a box, with a name in the center, and the amount used represented by light blue shading.
If there's only one partition, it's total size and amount available will be in the center, shown in GB.
If there are 2 or more, click each one in turn to see it's sizes. The Total of the sizes should be almost the same as the total at the bottom (the Partition Map takes a bit of space).
It sounds like you may have 2 partitions, one for TM backups, one for your "other stuff". If so, each partition is treated separately for most purposes: there should be two icons on your desktop and/or Finder sidebar, for example.
Report back what you find, and whether it makes sense to you or not. Then we can figure out what's going on and what you need to do.
But note this: This drive is a bit small to use with Time Machine. TM works best if it has 2-3 times the space of what it's backing-up, so it can keep a few months of your backups. See item #1 of the Frequently Asked Questions post at the top of this forum.
Even if you could use the entire 465 GB or so, that's less than twice the 300 gb you want to back up. That would work, for a while, but depending on how you use your Mac, TM may not be able to keep your backups for very long.

OCR and voting disks on ASM, problems in case of fail-over instances

Hi everybody
in case at your site you :
- have an 11.2 fail-over cluster using Grid Infrastructure (CRS, OCR, voting disks),
where you have yourself created additional CRS resources to handle single-node db instances,
their listener, their disks and so on (which are started only on one node at a time,
can fail from that node and restart to another);
- have put OCR and voting disks into an ASM diskgroup (as strongly suggested by Oracle);
then you might have problems (as we had) because you might:
- reach max number of diskgroups handled by an ASM instance (63 only, above which you get ORA-15068);
- experiment delays (especially in case of multipath), find fake CRS resources, etc.
whenever you dismount disks from one node and mount to another;
So (if both conditions are true) you might be interested in this story,
then please keep reading on for the boring details.
One step backward (I'll try to keep it simple).
Oracle Grid Infrastructure is mainly used by RAC db instances,
which means that any db you create usually has one instance started on each node,
and all instances access read / write the same disks from each node.
So, ASM instance on each node will mount diskgroups in Shared Mode,
because the same diskgroups are mounted also by other ASM instances on the other nodes.
ASM instances have a spfile parameter CLUSTER_DATABASE=true (and this parameter implies
that every diskgroup is mounted in Shared Mode, among other things).
In this context, it is quite obvious that Oracle strongly recommends to put OCR and voting disks
inside ASM: this (usually called CRS_DATA) will become diskgroup number 1
and ASM instances will mount it before CRS starts.
Then, additional diskgroup will be added by users, for DATA, REDO, FRA etc of each RAC db,
and will be mounted later when a RAC db instance starts on the specific node.
In case of fail-over cluster, where instances are not RAC type and there is
only one instance running (on one of the nodes) at any time for each db, it is different.
All diskgroups of db instances don't need to be mounted in Shared Mode,
because they are used by one instance only at a time
(on the contrary, they should be mounted in Exclusive Mode).
Yet, if you follow Oracle advice and put OCR and voting inside ASM, then:
- at installation OUI will start ASM instance on each node with CLUSTER_DATABASE=true;
- the first diskgroup, which contains OCR and votings, will be mounted Shared Mode;
- all other diskgroups, used by each db instance, will be mounted Shared Mode, too,
even if you'll take care that they'll be mounted by one ASM instance at a time.
At our site, for our three-nodes cluster, this fact has two consequences.
One conseguence is that we hit ORA-15068 limit (max 63 diskgroups) earlier than expected:
- none ot the instances on this cluster are Production (only Test, Dev, etc);
- we planned to have usually 10 instances on each node, each of them with 3 diskgroups (DATA, REDO, FRA),
so 30 diskgroups each node, for a total of 90 diskgroups (30 instances) on the cluster;
- in case one node failed, surviving two should get resources of the failing node,
in the worst case: one node with 60 diskgroups (20 instances), the other one with 30 diskgroups (10 instances)
- in case two nodes failed, the only node survived should not be able to mount additional diskgroups
(because of limit of max 63 diskgroup mounted by an ASM instance), so all other would remain unmounted
and their db instances stopped (they are not Production instances);
But it didn't worked, since ASM has parameter CLUSTER_DATABASE=true, so you cannot mount 90 diskgroups,
you can mount 62 globally (once a diskgroup is mounted on one node, it is given a number between 2 and 63,
and other diskgroups mounted on other nodes cannot reuse that number).
So as a matter of fact we can mount only 21 diskgroups (about 7 instances) on each node.
The second conseguence is that, every time our CRS handmade scripts dismount diskgroups
from one node and mount it to another, there are delays in the range of seconds (especially with multipath).
Also we found inside CRS log that, whenever we mounted diskgroups (on one node only), then
behind the scenes were created on the fly additional fake resources
of type ora*.dg, maybe to accomodate the fact that on other nodes those diskgroups were left unmounted
(once again, instances are single-node here, and not RAC type).
That's all.
Did anyone go into similar problems?
We opened a SR to Oracle asking about what options do we have here, and we are disappointed by their answer.
Regards
Oscar

Hi Klaas-Jan
- best practises require that also online redolog files are in a separate diskgroup, in case of ASM logical corruption (we are a little bit paranoid): in case DATA dg gets corrupted, you can restore Full backup plus Archived RedoLog plus Online Redolog (otherwise you will stop at the latest Archived).
So we have 3 diskgroups for each db instance: DATA, REDO, FRA.
- in case of fail-over cluster (active-passive), Oracle provide some templates of CRS scripts (in $CRS_HOME/crs/crs/public) that you edit and change at your will, also you might create additionale scripts in case of additional resources you might need (Oracle Agents, backups agent, file systems, monitoring tools, etc)
About our problem, the only solution is to move OCR and voting disks from ASM and change pfile af all ASM instance (parameter CLUSTER_DATABASE from true to false ).
Oracle aswers were a litlle bit odd:
- first they told us to use Grid Standalone (without CRS, OCR, voting at all), but we told them that we needed a Fail-over solution
- then they told us to use RAC Single Node, which actually has some better features, in csae of planned fail-over it might be able to migreate
client sessions without causing a reconnect (for SELECTs only, not in case of a running transaction), but we already have a few fail-over cluster, we cannot change them all
So we plan to move OCR and voting disks into block devices (we think that the other solution, which needs a Shared File System, will take longer).
Thanks Marko for pointing us to OCFS2 pros / cons.
We asked Oracle a confirmation that it supported, they said yes but it is discouraged (and also, doesn't work with OUI nor ASMCA).
Anyway that's the simplest approach, this is a non-Prod cluster, we'll start here and if everthing is fine, after a while we'll do it also on Prod ones.
- Note 605828.1, paragraph 5, Configuring non-raw multipath devices for Oracle Clusterware 11g (11.1.0, 11.2.0) on RHEL5/OL5
- Note 428681.1: OCR / Vote disk Maintenance Operations: (ADD/REMOVE/REPLACE/MOVE)
-"Grid Infrastructure Install on Linux", paragraph 3.1.6, Table 3-2
Oscar

Disk Utility 13 problem with USB drives

There appears to be a problem with Disk Utility 13 (part of OS X 10.9). At least, so far as I can tell, everything traces back to this app, or possibly OS X 10.9 itself.
I recently upgraded my MacBook Air to OS X 10.9 (reformatted hard drive, installed system from scratch, updated with all the latest Apple updates). I pre-checked all my third party software to make sure it was 10.9 compatible before installing it after the system cleanup, so everything I’m running supposedly has been approved as safe for 10.9. But I’m seeing a problem formatting USB drives that I do not encounter when running under 10.8.
I have a Seagate STAA500101 (“FreeAgent GoFlex”) drive connected via Seagate’s USB3 adapter that I’ve used for some time as a Time Machine backup. Post-overhaul, I decided to erase the backup and start fresh. When I attempt to format it (single GUID partition) with Disk Utility, I see the following messages go by:
Formatting disk1s2 as Mac OS Extended (Journaled) with name Untitled 1
Could not mount disk1s2 with name (null) after erase
Then there’s a pause, and the format appears to conclude fine. But if I run a “Verify Disk” immediately, I get this:
Verifying partition map for “Seagate FreeAgent GoFlex Media”
Checking prerequisites
Checking the partition list
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Volume on disk1s2 has 0 bytes of trailing loader space and it needs 134217728 bytes
Problems were found with the partition map which might prevent booting
Error: Partition map needs repair because a data partition needs loader space.
As the drive has just been formatted, that seemed odd. I took it over to another Mac still running 10.8.5 and formatted it there — it worked just fine. Verified just fine. Took the drive back to my MacBook Air and tried to verify the disk — same failure.
I wanted to rule out bad media, so I took a Lexar 16GB USB flash drive and tried to format it with Disk Utility 13 — got the same problem.
The only success I’ve had formatting USB drives under 10.9 is to boot up into OS X Recovery. Disk Utility there formatted my Seagate drive without an error. But once I booted back into normal 10.9 operating mode, the drive once again fails to verify; it makes me leery about using it as a Time Machine backup.
I suppose it’s possible there could be some background component like Sophos causing problems when formatting drives, but if I format a drive via OS X Recovery or another Mac under 10.8, that wouldn’t explain why the drives fail to verify.
Anyone got any other observations on this issue?

Problem resolved. I'm posting this note for anyone else who might run into this situation and come across this discussion.
It actually did turn out to be Sophos -- Cloud, that is. I'd been using Sophos' free Mac antivirus software on a variety of systems but forgot that I was now testing out Sophos Cloud on my own MacBook, which is their new endpoint solution, and supposed to be compatible with OS X 10.9 (although the Mac version is listed as "beta") Sophos Cloud includes a new feature called Device Control which allows you to create a company-wide policy to control access to hardware such as USB drives, optical drives, etc. But apparently it's still pretty buggy. I had my Device Control configured with the default setting of "monitor but do not block" but it was most definitely gumming up the system. With Sophos Cloud installed, here's what happens if I try to run "Verify Disk" on any attached drive. Note on the left side how "disk2s2" shows as a sub-volume for each hard drive.
So if I uninstall Sophos Cloud, reboot and rescan, here's what I get:
Works fine. Note that the "disk2s2" subvolumes are also gone. This is the way Disk Utility also appears on a 10.8 or 10.9 system, even if you have the standard free Sophos for Mac software installed. It's only Sophos Cloud that's not playing nice. It also appears to have stopped me from being able to play DVDs from an attached Apple USB SuperDrive -- that problem was likewise solved by removing Sophos Cloud.

The dreaded 3F0, "hard disk not exist" problem

Okay, I have a degree in EE with a minor in comp sci. I understand how bios' work, etc. This is why the "answers" HP "tech support" gave me make absolutely no sense. Could someone please shed some light on this bizarre problem? I am trying to install a BRAND NEW, WORKING hard drive in a DV7-6163 and the laptop refuses to recognize the existence of the SATA drive. I have tried this drive in another laptop and IT WORKS, I have tried other working hard drives in this machine and they DO NOT work. I have checked to make sure the SATA cable was good....yes! I went as far as to switch the connector from the DVD drive to the SATA port that was meant for the hard drive. Guess what, IT WORKS and the laptop thinks there is a hard drive installed (it even runs the hd diag.. no more "hard disk not exist" error!!) SO I now know that that actual hardware port is able to communicate with a SATA device. HP has been LESS THAN HELPFUL as they insist it must be a bad drive or bad main board (even after I explained my various tests demonstrate that it cannot be (why does the port that refuses to recognize the hard drive talk fine to the DVD drive??). So the only thing left is either a corrupted bios, or a major firmware issue with the code. Could someone please point me in the right direction? This was a very expensive laptop and I am ready to throw it through a window!!

Could you provide a link to the UEFI diagnostics utility? I tried to google it, but there are so many hits, it makes it confusing to know which one! Are you saying that the UEFI diag dos utility can bypass the bios functions? HP blatently LIES about the ability to access the advanced bios settings! How do I know? I have the Insyde H20 EzH20 tool. For some reason i cannot get it to work with my dv7 bios (it is RSA signed), but it works fine on my DV6 bios and allows you to access a plethora of advanced settings! Namely the SATA mode which I sorely need access to. How HP justifies not allowing a customer access to settings on property we own is beyond me. Of course the impetus must be they want to be able to charge us to change a simple setting. I will NEVER buy HP again! Twenty years ago they were a respectable brand. Today, they are all about squeezing every drop of blood from the customer!

Could Very Low Disk Space Cause problems?

Hi, my 600 GB Hard Drive only had around 5 GB of space left . I purchased a new 1 TB Hard Drive in order to delete media so that I could gain the space back. I've since gained back 200 GB of Space but Could very low disk space cause issues? What kind of issues could occur? Thanks
Message was edited by: Stuart Lawrence

There are any number of reasons for occasional beachballs to appear. They will appear when some programs are involved in heavy disk I/O which tends to be processor dependent and causes the program to suspend all other activity until the disk activity has completed. This is more often the case when writing to the disk. Beachballs may also appear if the OS has to use disk I/O and is slowed down by an over-filled and/or fragmented hard drive. The fuller a drive gets the greater the likelihood that fragmentation will become a more noticeable problem. Beachballs can appear if you are low on physical memory so applications must resort to disk-based virtual memory which is considerably slower and tends to cause the computer to become slow or unresponsive for a period of time. It can also cause disk-thrashing. Beachballs can occur if the disk has become corrupted causing applications to have difficulty reading from or writing to the disk.
It is possible to repair a drive's directory, and it's even possible to identify corrupted files, but it's not possible to repair corrupted files nor repair a corrupted drive. If a drive develops corrupted files either the files will need to be replaced or deleted. If a drive develops soft sector errors these can be repaired by erasing the drive (reformatting.) If a drive develops hard sector errors these may or may not be repairable, but if they are repairable it requires zeroing the data during a disk formatting operation. If the disk directory becomes corrupted that can be repaired using Disk Utility or one of the various third-party utilities such as Disk Warrior. Disk Utility can repair many but not all directory corruption problems. What DU cannot fix Disk Warrior usually can.
You can start repairing a drive as follows;
Repairing the Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger and Leopard.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
This applies to your startup volume. No need to repair permissions on any but a startup volume.

Disk Utility sees problem invisible to Disk Warrior?

Hi all,
In brief: Disk Utility seems to think I've got a big problem, Disk Warrior seems to be unable to fix it.
More detail: I ran verify disk from Disk Utility and was told I needed to repair my startup volume. So I ran Disk Utility's repair disk function from the install CD and it was unable to repair the disk. It was also unable to repair permissions.
So I reached for trusty Disk Warrior and ran that. It rebuilt the directory, reporting various changes, eventually ending with zero errors. That should have fixed it, right?
But then I re-ran Disk Utilty and was told, again, that the disk needed to be repaired.
Here's what happened when I ran DU's repair function from the install CD:
- I selected only the volume containing Mac OS X for repair and Disk Utility reported there's an "invalid leaf record count (it should be 3 instead of 525) and also that '1 HFS volume repaired' but '1 HFS volume could not be repaired'. (I'd selected only my startup volume).
- The verify disk function reports the same
- The repair disk permissions function cannot complete its task. Its error message reads: "Disk Utility internal error: disk utility has lost its connection with the disk management tool and cannot continue. Please quit and relaunch disk utility."
So, I ran Disk Warrior AGAIN (2nd time) and sure enough, it reports that it successfully rebuilt the directory but that the rebuilt version has no changes from the original version (meaning it's ok, right?).
Needless to say, if my startup disk DOES need repair, I want to do something about it. But does it need repair? And if Disk Warrior can't fix it, what can? Could it be that Disk Utility is seeing a problem that's invisible to Disk Warrior?
By the way, I ran DW's manual diagnostic and it said the drive itself was operating normally.
Very grateful if any of you can give me some insight into this.
Jason
Dual G5 2.5Ghz 2GB RAM, Powerbook G4 1.33Ghz, iPod 60GB Mac OS X (10.4.8) 500GB internal HDD

Hi Allan,
Sure thing. Here's the business.
Disk Warrior (v3.0.3)
DW reports that it's successfully rebuilt a new directory each time I run it. I've run it three times now. The first time, there were differences between the original directory and the rebuilt version and it displayed a message coloured red describing this. On the subsequent two occasions, it has displayed a message coloured green and said there are "no changes to the number or contents of the files and folders" in the rebuilt directory.
DW's manual diagnostic reports that the drive itself is "operating normally."
DU
Running DU internally (from the volume that also contains 10.4.9), it can only 'verify', of course. The volume's name is 'G5 hard drive'. The full message is:
Verifying volume “G5 hard drive”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Incorrect number of Extended Attributes
Checking volume bitmap.
Checking volume information.
d.",1)
G5 hard drive
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
Running DU (repair disk) from the install CD (for Powermac G5, OS X 10.3.5) produces the following report:
Repairing disk for "G5 hard drive"
Checking HFS plus volume
Checking extents overflow file
Checking catalog file
Checking multi-linked files
Checking catalog hierachy
Checking extent attributes file
Invalid leaf record count
(It should be 3 instead of 422)
Repairing volume
The volume G5 hard drive was repaired successfully
Repair attempted on 2 volumes
1 HFS volume repaired
1 HFS volume could not be repaired
So let's say that DW is doing it all right, and the copy of DU on the install CD (10.3.5) is producing an inaccurate result because it doesn't match up with Tiger, I can understand that. But why would the same problem come up with DU run internally from (in the course of the last 24 hours) both 10.4.8 and 10.4.9 (because the problem survived my upgrade)?
On the other hand, Allan, possibly DW isn't the right tool for the job. In that case, do you know what is?
Thanks,
Jason
Dual G5 2.5Ghz 2GB RAM, Powerbook G4 1.33Ghz, iPod 60GB Mac OS X (10.4.9) 500GB internal HDD

New MBP 15" Weird Freezing & Disk (Volume Header) Problems, related?

Hi all
I hope someone can help me, and I hope I don't have a faulty Mac!
I bought a 15" MBP a week ago and while it's awesome, I have a problem where the system will completely freeze, except for the mouse cursor.
Nothing on the keyboard works, force quit doesn't come up, plugging in / removing the power supply doesn't change the battery icon, there's no spinning beach ball. Literally the whole system is unresponsive except for the mouse cursor which seems to be moving fine. None of the hardware controls work either, i.e. eject button
The only consistency that I can think of is that of all the times that it has happened, Firefox was open (ver. 2.0.0.2), except once where Firefox had just started (it froze with Firefox darkened in the dock)
Since then I've reinstalled Firefox but I have another problem and wonder if they're related.
Fresh out of the box I tried to install Windows through Boot Camp but when Boot Camp tried to partition my disk it gave me an error and referred me to Disk Utilities. Disk Utilities gave me a "Volume Header needs minor repair" error, so I fixed it from an older Mac that I have with the MBP mounted in disk mode.
This fixed it, Boot Camp then installed fine, I managed to get myself a virus so I deleted the Windows partition through Boot Camp and tried to partition the disk again with the intent of installing Windows and not get a virus this time
However, Boot Camp gave me the same "Volume Header needs minor repair" error!
The consistency of these errors is making me concerned about the quality of the hdd that's in my MBP!
Some info you might need to know about my MBP
15" MBP Core2Duo
2.33 ghz
Boot ROM ver: MBP22.00A5.B01
SMC Version: 1.12f5
HDD: Toshiba MK2035GSS
Revision: DK021B
The Disk Utility error:
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
Volume Header needs minor repair
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
Also, I'm not sure if this has any bearing but I migrated all the info from my old 12" PB onto this.
I hope someone can tell me that everything's ok!!
15" MBP, Core2Duo, 2.33; G5 iMac, no iSight; 12" Powerbook 867 Mac OS X (10.4.8)

Hi all
I hope someone can help me, and I hope I don't have a faulty Mac!
I bought a 15" MBP a week ago and while it's awesome, I have a problem where the system will completely freeze, except for the mouse cursor.
Nothing on the keyboard works, force quit doesn't come up, plugging in / removing the power supply doesn't change the battery icon, there's no spinning beach ball. Literally the whole system is unresponsive except for the mouse cursor which seems to be moving fine. None of the hardware controls work either, i.e. eject button
The only consistency that I can think of is that of all the times that it has happened, Firefox was open (ver. 2.0.0.2), except once where Firefox had just started (it froze with Firefox darkened in the dock)
Since then I've reinstalled Firefox but I have another problem and wonder if they're related.
Fresh out of the box I tried to install Windows through Boot Camp but when Boot Camp tried to partition my disk it gave me an error and referred me to Disk Utilities. Disk Utilities gave me a "Volume Header needs minor repair" error, so I fixed it from an older Mac that I have with the MBP mounted in disk mode.
This fixed it, Boot Camp then installed fine, I managed to get myself a virus so I deleted the Windows partition through Boot Camp and tried to partition the disk again with the intent of installing Windows and not get a virus this time
However, Boot Camp gave me the same "Volume Header needs minor repair" error!
The consistency of these errors is making me concerned about the quality of the hdd that's in my MBP!
Some info you might need to know about my MBP
15" MBP Core2Duo
2.33 ghz
Boot ROM ver: MBP22.00A5.B01
SMC Version: 1.12f5
HDD: Toshiba MK2035GSS
Revision: DK021B
The Disk Utility error:
Verifying volume “Macintosh HD”
Checking HFS Plus volume.
Checking Extents Overflow file.
Checking Catalog file.
Checking multi-linked files.
Checking Catalog hierarchy.
Checking Extended Attributes file.
Checking volume bitmap.
Checking volume information.
Volume Header needs minor repair
The volume Macintosh HD needs to be repaired.
Error: The underlying task reported failure on exit
1 HFS volume checked
Volume needs repair
Also, I'm not sure if this has any bearing but I migrated all the info from my old 12" PB onto this.
I hope someone can tell me that everything's ok!!
15" MBP, Core2Duo, 2.33; G5 iMac, no iSight; 12" Powerbook 867 Mac OS X (10.4.8)

Repair Disk Permissions - Safari problem not going away

Please help i seem to have come across a problem where when i repair disk permission i keep getting this message
Permissions differ on “Applications/Safari.app/Contents/Resources/Safari.help/Contents/Resources/inde x.html”; should be lrwxr-xr-x ; they are -rwxr-xr-x .
After I repair the problem just comes back. Im sure something isnt right please help

I also see this issue.
But in my case, repairing permissions on getting a nasty glitch [lots of character "u" appearing, on a Macbook]u
Should indeed be unrelated, but have been finding that permissions repair temporarily fixes issue - and this is only consistent permission error reported
Yes, I should take this machine in for checking/repair, but I mention here in case the problem is somehow linked to an issue that can occur on a few Macs...

Disk utility restore problem: cannot drag internal hdd to destination field

I'm currently trying to restore a time machine backup after my boot ssd recently failed, but am having trouble restoring the backup to my secondary internal drive in the optical bay. My set up isthe following:
Failed ssd in primary hdd bay of MacBook Pro (mid 2010)
1tb secondary hdd in optical drive bay with time machine backup of failed ssd.
2tb external drive
The following is what I have done so far...
1. Booted into the secondary internal drive and restored the time machine backup onto the external USB drive.
2. Booted from the restored backup on the USB drive (this now looks like my old computer again but is very slow as its USB 2.0)
3. Partitioned the secondary internal drive in the optical bay.
4. Now I want to copy the restored volume on my USB drive to the secondary internal drive in the optical bay.
When I open disk utility's restore function I can put my original volum in the source field, however, it will not let me put either partition of my internal drive in the destination field. It has no problem putting other partitions from the USB drive in the destination field - just will not allow anything from the internal drive. Why is this?
I'm thinking it could possibly be because it is in the optical drive bay and apple has prevented copying full volumes into this bay, but then again surely this would be needed when burning DVDs at some stage. Any ideas? Many thanks in advance for any help.

I managed to complete the restore and you may have been right - I booted from the internal hdd then restored the time machine backup stored on the usb drive to a different partition on the internal hd. Seemed to work fine now running of the hd in the optical drive bay but has still crashed a couple of times which is pretty odd. Perhaps the failed ssd in the main drive bay is still causing a bit of a nuisance (it registers for the first 3 minutes after booting up then disappears). Also didnt notice the responsiveness too much when upgrading from hd to ssd, but going the other way back to hd - can definitely now tell the difference. Painfully slow at times! I need to get that ssd replaced I think. Anyway thanks for your advice!

Disk I/O problem

Similar Messages

Maybe you are looking for