Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Jolly Roger Newsgroups: comp.sys.mac.system,comp.sys.mac.hardware.misc,comp.sys.mac.portables Subject: Re: A 13.3" MacBook Pro (MBP) gets stuck during its boot ups and tests... disk's I/O error in verbose bootup! Followup-To: comp.sys.mac.system Date: 25 Sep 2015 05:23:13 GMT Organization: People for the Ethical Treatment of Pirates Lines: 45 Message-ID: References: <2LadnXzoYex-gZnLnZ2dnUU7-Y_46u6z@earthlink.com> <5604d3f0$0$4059$c3e8da3$12bcf670@news.astraweb.com> X-Trace: individual.net ruEDl1Xt97lhzc7qx31gDAiet9ZHd/Zg5/Ker1HQPyysuopQPQ Cancel-Lock: sha1:PVH9HSznTYpRYeJGkp+qPzw5yCQ= X-Face: _.g>n!a$f3/H3jA]>9pN55*5<`}Tud57>1Y%b|b-Y~()~\t,LZ3e up1/bO{=-) User-Agent: slrn/1.0.1 (Darwin) Xref: csiph.com comp.sys.mac.system:80571 comp.sys.mac.hardware.misc:1798 comp.sys.mac.portables:782 On 2015-09-25, JF Mezei wrote: > On 15-09-24 11:58, Jolly Roger wrote: > >> Repair will cause Disk Utility to attempt to *modify* the disk before >> you have had a chance to read the output to determine what is wrong. > > If Disk Utility is unable to read a disk block, it won't attempt to fix > it since it can't write to it. Irrelevant to my point above. > The "repair" only applies to the file system (some lost files not in any > directories, some catalog bits not set properly etc). I suspect that > Disk Utility will not detect a few corrupt blocks inside a file. Again, irrelevant. Your assumption that this volume must have bad blocks is premature and based on ignorance. We do not know what is wrong with the volume, which is why it is best not to attempt modification which may result in data loss. > Yes, you can run "Verify" first. However, it will take twice as long. Wrong. Verify operations actually take less time than Repair operations because repairs naturally take time to make. Without the repairs, there is less to do, which means the operation finishes faster. > The problem is that if you run Verify and then Repair, you double the > number of disk operations that get done and if the disk is on its last > legs, you may not want to do this. If you want to determine what is wrong with the volume you have to verify it, silly. Otherwise you might as well just throw the drive away, which is just plain silly. > In fact, if you have a spare disk, I would do a disk backup on the > device (dismount the disk and do the disk image on the drive, using Disk > Utility). He already has a backup. Please pay better attention. -- E-mail sent to this address may be devoured by my ravenous SPAM filter. I often ignore posts from Google. Use a real news client instead. JR