OS X Hard Drive I/O Error, Unable to Boot

Question

Level 1

2 points

OS X Hard Drive I/O Error, Unable to Boot

I have never experienced any problems that could indicate a hard drive failure on my MacBook Pro (15-inch late-2011, OS X 10.10.3, 500GB SATA HDD), which I have been using for three years and a half. I have never seen I/O error message poped up in my terminal or heard problematic sounds from my hard drive.

It all started yesterday afternoon when I opened the lid and woke up the laptop. I noticed the system's response was extremely slow. It took about ten minutes to get the login screen unlocked. After logging in, some parts of the system seemed to be unresponsive. System clock was frozen for like ten minutes. I don't have many Apps running in the front, but Finder and MacVim (with the text I was editing), and Activity Monitor in the backend. These Apps were still interactive, but with great and almost intolerable latency. MacVim kept telling me that it had errors writing into the swap file. I tried to open TextEdit multiple times but it could not start. I managed to close all running Apps through normal means, and I shutdown the system.

When I restart, I find the OS automatically shuts down. I restarted in verbose mode and found these boot messages (see below). These messages indicate that a serious I/O error has prevented the OS to mount the file system partition.

CoreStorageGroup::completeIORequest - error 0x000002ca detected for LVG "Macintosh HD" ...... offset = 16904192

disk1: I/O error.

jnl: b(1, 4): update_fs_block: failed to update block 33016 (ret 5)

jnl: b(1, 4): journal_open: Error replaying the journal!

hfs: early jnl init: failed to open/create the journal (retval 0)

hfs: mounted Macintosh HD on device root_device

VM Swap Subsystem is ON

Darwin Bootstrapper Version 2.0.2: Mon Mar 23:27:57 PST 2015; root:llbxpc_executables-599.20.9-1/launchd/RELEASE_X86_64

boot-args = -v

** /dev/rdisk1 (NO WRITE)

** Root file system

Executing fsck_hfs (version hfs-285)

jnl: disk1: replay_journal: from 14018048 to 20084224 (offset 0xe38a000)

CoreStorageGroup::completeIORequest - error 0xe00082ca detected for LVG "Macintosh HD" ...... offset = 16822272

disk1: I/O error

jnl: disk1: update_fs_block: failed to update block 32856 (ret 5)

jnl: disk1: journal_open: Error replaying the journal!

hts_mxnt larnatjournal_open == NULL; couldn't be opened on Macintosh HD

mount_hts: Invalid argument

Sun Dec 31: 16:53:45 2000 localhost com.apple.xps.Iaunchd <Emergency>: Boot task failed: mount

Sun Dec 31: 16:53:45 2000 localhost com.apple.xpc.launchd[1] <Emergency>: Shutting down in 3 seconds.

What should be my next step?

Posted on Apr 11, 2015 5:01 AM

Reply

Answer 1

Best reply

jtm2n5

Level 1

10 points

Apr 11, 2015 6:24 AM in response to initium

Try booting into recovery mode (hold command + R during boot). After in recovery mode use disk utility to repair your disk. If this does not work I would try running a diagnostics test (hold D during boot) to see if there is a hardware failure in your system.

If you have more questions about recovery mode here is a link to an official article from Apple: OS X: About OS X Recovery - Apple Support

I hope this help!

Reply

Answer 2

initium Author

Level 1

2 points

Apr 11, 2015 12:46 PM in response to jtm2n5

Hello,

Thanks for your reply. As command + R couldn't take me into recovery mode (the progress bar stalls), I still managed to boot from a USB drive on which I have OS X 10.10.3 installed. I ran Disk Utility from there to try fixing the 500 GB "Macintosh HD".

Verify/Repair Disk Permissions is disabled.

Ran Verify Disk. It said the Drive needs to be repaired.

Ran Repair Disk as instructed. It ended up with

Disk Utility stopped repairing "Macintosh HD": Disk Utility can't repair this disk. Back up as many of your files as possible,reformat the disk, and restore your backed-up files.

The partition is unable to be mounted.

At the point, I would like to know how to recover some of my most important data from the hard drive. Thanks!

Full text of Disk Utility activity log is pasted below. I have highlighted the most important lines. Hope the log helps.

https://gist.github.com/anonymous/ecc02d53dfddf4cfb38a

2015-04-11 11:53:04 -0700: Verifying partition map for "TOSHIBA MK5065GSXF

Media"

2015-04-11 11:53:04 -0700: Starting verification tool:

2015-04-11 11:53:04 -0700: Checking prerequisites

2015-04-11 11:53:10 -0700: Checking the partition list

2015-04-11 11:53:10 -0700: Checking for an EFI system partition

2015-04-11 11:53:10 -0700: Checking the EFI system partition's size

2015-04-11 11:53:10 -0700: Checking the EFI system partition's file system

2015-04-11 11:53:23 -0700: Problems were found with the partition map which

might prevent booting

2015-04-11 11:53:23 -0700: Error: The partition map needs to be repaired because

there's a problem with the EFI system partition's file system.

2015-04-11 11:53:23 -0700:

2015-04-11 11:53:23 -0700: : The partition map needs to be repaired because

there's a problem with the EFI system partition's file system.

2015-04-11 11:53:23 -0700: Verifying volume "Macintosh HD"

2015-04-11 11:53:23 -0700: Starting verification tool:

2015-04-11 11:53:23 -0700: Verifying storage system

2015-04-11 11:53:23 -0700: Checking volume

2015-04-11 11:53:23 -0700: disk0s2: Scan for Volume Headers

2015-04-11 11:53:25 -0700: disk0s2: Scan for Disk Labels

2015-04-11 11:53:27 -0700: Invalid Disk Label @ 499239710720: cksum mismatch

2015-04-11 11:53:27 -0700: Logical Volume Group

1B3DBB0D-7858-4564-BEB2-C25BDB9CF25C on 1 device

2015-04-11 11:53:27 -0700: disk0s2: Scan for Metadata Volume

2015-04-11 11:53:27 -0700: Logical Volume Group has a 24 MB Metadata Volume with

double redundancy

2015-04-11 11:53:27 -0700: Start scanning metadata for a valid checkpoint

2015-04-11 11:53:27 -0700: Load and verify Segment Headers

2015-04-11 11:53:27 -0700: Load and verify Checkpoint Payload

2015-04-11 11:53:27 -0700: Load and verify Transaction Segment

2015-04-11 11:53:27 -0700: Incorporate 0 newer non-checkpoint transactions

2015-04-11 11:53:27 -0700: Load and verify Virtual Address Table

2015-04-11 11:53:27 -0700: Load and verify Segment Usage Table

2015-04-11 11:53:27 -0700: Load and verify Metadata Superblock

2015-04-11 11:53:33 -0700: Load and verify Logical Volumes B-Trees

2015-04-11 11:53:36 -0700: Logical Volume Group contains 1 Logical Volume

2015-04-11 11:53:36 -0700: Load and verify 33350FE3-AAD8-43EF-82B3-B0669CC8895E

2015-04-11 11:53:36 -0700: Load and verify A325582B-2E6C-45A6-A619-9F2A8D11D980

2015-04-11 11:53:36 -0700: Load and verify Freespace Summary

2015-04-11 11:53:36 -0700: Load and verify Block Accounting

2015-04-11 11:53:36 -0700: Load and verify Live Virtual Addresses

2015-04-11 11:53:36 -0700: Newest transaction commit checkpoint is valid

2015-04-11 11:53:36 -0700: Load and verify Segment Cleaning

2015-04-11 11:53:40 -0700: The volume 1B3DBB0D-7858-4564-BEB2-C25BDB9CF25C

appears to be OK

2015-04-11 11:53:40 -0700: Storage system check exit code is 0.

2015-04-11 11:53:40 -0700: Verifying file system.

2015-04-11 11:53:40 -0700: File system check exit code is 8.

2015-04-11 11:53:40 -0700: Error: This disk needs to be repaired. Click Repair

Disk.

2015-04-11 11:53:40 -0700:

2015-04-11 11:53:40 -0700: Disk Utility stopped verifying "Macintosh HD": This

disk needs to be repaired. Click Repair Disk.

2015-04-11 11:53:40 -0700:

2015-04-11 11:53:50 -0700: Verifying and repairing partition map for "TOSHIBA

MK5065GSXF Media"

2015-04-11 11:53:50 -0700: Starting repair tool:

2015-04-11 11:53:50 -0700: Checking prerequisites

2015-04-11 11:53:53 -0700: Checking the partition list

2015-04-11 11:53:53 -0700: Adjusting partition map to fit whole disk as required

2015-04-11 11:53:53 -0700: Problems were encountered during repair of the

partition map

2015-04-11 11:53:53 -0700: Error: Partition map repair failed while adjusting

structures to fit current whole disk size.

2015-04-11 11:53:53 -0700:

2015-04-11 11:53:53 -0700: : Partition map repair failed while adjusting

structures to fit current whole disk size.

2015-04-11 11:53:53 -0700: Verify and Repair volume "Macintosh HD"

2015-04-11 11:53:53 -0700: Starting repair tool:

2015-04-11 11:53:53 -0700: Repairing storage system

2015-04-11 11:53:53 -0700: The volume disk0s2 cannot be repaired when it is in

use

2015-04-11 11:53:53 -0700: Checking volume

2015-04-11 11:53:53 -0700: disk0s2: Scan for Volume Headers

2015-04-11 11:53:57 -0700: disk0s2: Scan for Disk Labels

2015-04-11 11:54:03 -0700: Invalid Disk Label @ 499239710720: cksum mismatch

2015-04-11 11:54:03 -0700: Logical Volume Group

1B3DBB0D-7858-4564-BEB2-C25BDB9CF25C on 1 device

2015-04-11 11:54:03 -0700: disk0s2: Scan for Metadata Volume

2015-04-11 11:54:03 -0700: Logical Volume Group has a 24 MB Metadata Volume with

double redundancy

2015-04-11 11:54:03 -0700: Start scanning metadata for a valid checkpoint

2015-04-11 11:54:03 -0700: Load and verify Segment Headers

2015-04-11 11:54:04 -0700: Load and verify Checkpoint Payload

2015-04-11 11:54:04 -0700: Load and verify Transaction Segment

2015-04-11 11:54:04 -0700: Incorporate 0 newer non-checkpoint transactions

2015-04-11 11:54:04 -0700: Load and verify Virtual Address Table

2015-04-11 11:54:04 -0700: Load and verify Segment Usage Table

2015-04-11 11:54:04 -0700: Load and verify Metadata Superblock

2015-04-11 11:54:04 -0700: Load and verify Logical Volumes B-Trees

2015-04-11 11:54:04 -0700: Logical Volume Group contains 1 Logical Volume

2015-04-11 11:54:04 -0700: Load and verify 33350FE3-AAD8-43EF-82B3-B0669CC8895E

2015-04-11 11:54:04 -0700: Load and verify A325582B-2E6C-45A6-A619-9F2A8D11D980

2015-04-11 11:54:04 -0700: Load and verify Freespace Summary

2015-04-11 11:54:04 -0700: Load and verify Block Accounting

2015-04-11 11:54:04 -0700: Load and verify Live Virtual Addresses

2015-04-11 11:54:04 -0700: Newest transaction commit checkpoint is valid

2015-04-11 11:54:04 -0700: Load and verify Segment Cleaning

2015-04-11 11:54:10 -0700: The volume 1B3DBB0D-7858-4564-BEB2-C25BDB9CF25C

appears to be OK

2015-04-11 11:54:10 -0700: Storage system check exit code is 0.

2015-04-11 11:54:10 -0700: Repairing file system.

2015-04-11 11:54:10 -0700: File system check exit code is 8.

2015-04-11 11:54:10 -0700: Updating boot support partitions for the volume as

required.

2015-04-11 11:55:48 -0700: Error: Disk Utility can't repair this disk. Back up

as many of your files as possible, reformat the disk, and restore your backed-up

files.

2015-04-11 11:55:48 -0700:

2015-04-11 11:55:48 -0700: Disk Utility stopped repairing "Macintosh HD": Disk

Utility can't repair this disk. Back up as many of your files as possible,

reformat the disk, and restore your backed-up files.

2015-04-11 11:55:48 -0700:

Reply

Answer 3

Linc Davis

Level 10

209,535 points

Apr 11, 2015 1:16 PM in response to initium

The startup drive is failing, or there is some other internal hardware fault.

Back up all data on the drive immediately if you don't already have a current backup. There are ways to back up a computer that isn't fully functional—ask if you need guidance.

Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.

If privacy is a concern, erase the data partition(s) with the option to write zeros* (do this only if you have at least two complete, independent backups, and you know how to restore to an empty drive from any of them.) Don’t erase the recovery partition, if present.

Keeping your confidential data secure during hardware repair

Apple also recommends that you deauthorize a device in the iTunes Store before having it serviced.

*An SSD doesn't need to be zeroed.

Reply

Answer 4

initium Author

Level 1

2 points

Apr 11, 2015 1:31 PM in response to Linc Davis

Hello Linc,

Thanks for your reply.

I would love to know how I can back up the data, given that I am able to run an OS X Live USB on the computer. The situation is Disk Utility could not repair the disk (see my post above for complete details). Instead of a hardware failure, I suspect that it's the EFI Partition Table that has been corrupted, telling from the log message. There could be bad blocks, too. I tried to mount the partition in Disk Utility but failed.

I made an appointment yesterday, but the earliest spot I could get was tomorrow afternoon. I am wondering if I could just walk in to an Apple Store.

Privacy is indeed a concern. However, retrieving/backing up the most important files is my top priority.

Thanks again for your help.

Reply

Answer 5

Linc Davis

Level 10

209,535 points

Apr 11, 2015 2:08 PM in response to initium

There are several ways to back up a Mac that is not fully functional. You need an external hard drive or other storage device to hold the data.

1. Start up from the Recovery partition, from Internet Recovery, or from a local Time Machine backup volume (option key at startup.) Launch Disk Utility and follow the instructions in this support article, under “Instructions for backing up to an external hard disk via Disk Utility.” The article refers to starting up from a DVD, but the procedure in Recovery mode is the same. You don't need a DVD if you're running OS X 10.7 or later.

If you use FileVault 2, then you must first unlock the startup volume. Select its icon ("Macintosh HD," unless you gave it a different name.) It will be nested below another disk icon, usually with the same name. Click the Unlock button in the toolbar. Enter your login password when prompted.

2. If Method 1 fails because of disk errors, then you may be able to salvage some of your files by copying them in the Finder. If you already have an external drive with OS X installed, start up from it. Otherwise, if you have Internet access, follow the instructions on this page to prepare the external drive and install OS X on it. You'll use the Recovery installer, rather than downloading it from the App Store.

3. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, start the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.

4. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

Reply

Answer 6

initium Author

Level 1

2 points

Apr 11, 2015 2:25 PM in response to Linc Davis

Hello,

thanks for your reply again. However, would you please read my post and understand my situation?

1. As I mentioned, Internal Recovery partition doesn't work. recovery through Internet does not work, either.

2. I do have OS X 10.10.3 installed on an external USB drive. I managed to boot from there and run Disk Utility. DISK UTILITY COULD NEITHER REPAIR NOR MOUNT THE HD.

3. I might try this, but I highly doubt it, since the partition is not mountable.

4. This is my third time here mentioning the partition is not mountable. how is the solution different from what I have right now, which is to run an OS X on a bootable USB?

Sorry for the rant. But I do hope I can get more specific answer here.

Reply

Answer 7

Linc Davis

Level 10

209,535 points

Apr 11, 2015 2:33 PM in response to initium

If none of the methods I suggested works, there's nothing else you can do without resorting to special software or the services of a data-recovery consultant. I have no experience in that area and I can't offer any guidance.

Reply

Answer 8

initium Author

Level 1

2 points

Apr 11, 2015 2:49 PM in response to Linc Davis

I'm sorry if it is the case. Thank you again for your attempt to help. I appreciate it.

Reply