Benches macOS

5

Spinning Beach Ball Freeze with HFS: err 5

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Ever since I upgraded to 10.5.x my iMac has been freezing more and more often. I noticed that every time the machine froze with the beach ball spinning so was the Time Machine indicator. I reformatted my LaCie HD that I was using to GUID and most (but not all) of the freezes have subsided. I have a second LaCie HD that I use for video (named Video HD)which along with my internal HD is part of my Time Machine back-up. Last evening my machine froze in the usual manner. I grabbed the console messages and saw:

7/7/08 7:48:13 PM kernel disk1s2: I/O error.

7/7/08 7:48:13 PM kernel HFS: err 5 reading VH blk (Video HD)

7/7/08 7:49:43 PM kernel disk1s2: I/O error.

7/7/08 7:52:13 PM kernel disk1s2: I/O error.

7/7/08 7:52:13 PM /System/Library/CoreServices/backupd[4279] Starting standard backup

7/7/08 7:56:43 PM kernel disk1s2: I/O error.

7/7/08 7:56:43 PM kernel HFS: err 5 reading VH blk (Video HD)

7/7/08 7:57:13 PM kernel disk1s2: I/O error.

7/7/08 7:59:43 PM kernel disk1s2: I/O error.

7/7/08 7:59:43 PM /System/Library/CoreServices/backupd[4279] Backing up to: /Volumes/TM HD/Backups.backupdb

7/7/08 8:04:13 PM kernel disk1s2: I/O error.

7/7/08 8:04:13 PM kernel HFS: err 5 reading VH blk (Video HD)

7/7/08 8:04:43 PM kernel disk1s2: I/O error.

7/7/08 8:07:13 PM kernel disk1s2: I/O error.

7/7/08 8:09:43 PM kernel disk1s2: I/O error.

7/7/08 8:12:13 PM kernel disk1s2: I/O error.

7/7/08 8:16:43 PM kernel disk1s2: I/O error.

7/7/08 8:16:43 PM kernel HFS: err 5 reading VH blk (Video HD)

7/7/08 8:17:13 PM kernel disk1s2: I/O error.

7/7/08 8:19:43 PM kernel disk1s2: I/O error.

7/7/08 8:22:13 PM kernel disk1s2: I/O error.

7/7/08 8:24:43 PM kernel disk1s2: I/O error.

7/7/08 8:29:13 PM kernel disk1s2: I/O error.

7/7/08 8:29:13 PM kernel HFS: err 5 reading VH blk (Video HD)

7/7/08 8:29:43 PM kernel disk1s2: I/O error.

7/7/08 8:32:13 PM kernel disk1s2: I/O error.

7/7/08 8:32:13 PM /System/Library/CoreServices/backupd[4279] No pre-backup thinning needed: 614.0 MB requested (including padding), 136.86 GB available

7/7/08 8:32:18 PM /System/Library/CoreServices/backupd[4279] Copied 2940 files (4.1 MB) from volume Shapiro HD.

7/7/08 8:36:43 PM kernel disk1s2: I/O error.

7/7/08 8:36:43 PM kernel HFS: err 5 reading VH blk (Video HD)

7/7/08 8:37:13 PM kernel disk1s2: I/O error.

7/7/08 8:39:43 PM kernel disk1s2: I/O error.

7/7/08 8:39:43 PM /System/Library/CoreServices/backupd[4279] Error: (-36) copying /Volumes/Video HD to (null)

7/7/08 8:39:43 PM /System/Library/CoreServices/backupd[4279] Copied 2941 files (4.1 MB) from volume Video HD.

7/7/08 8:44:13 PM kernel disk1s2: I/O error.

7/7/08 8:44:13 PM kernel HFS: err 5 reading VH blk (Video HD)

7/7/08 8:44:43 PM kernel disk1s2: I/O error.

Any help decoding HFS: err 5 would be greatly appreciated. Oh, I've updated to the latest system (using the Combo updater and have already run Disk Utility and Disk Warrior on the Video HD.

Thanks

5 replies

Sign in or join Beachball Help to reply.

  1. 0

    glsmith

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Error 5 is an I/O error, which you're getting back from the filesystem after an attempted read (the reason you see explicit I/O errors and error 5's is that likely the driver is reporting one, and the filesystem is reporting the other). IMO, whatever is mounted at device disk1s2 is bad. Your reformats, repairs, etc may have remapped some bad sectors on that disk, but clearly hasn't repaired all of them (or, the disk is continuing to fail with new bad spots).

    I would suggest that you make a backup of your system somewhere other than whatever is on disk1s2. I'd then retire that disk...

  2. 0

    glsmith

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Error 5 is an I/O error, which you're getting back from the filesystem after an attempted read (the reason you see explicit I/O errors and error 5's is that likely the driver is reporting one, and the filesystem is reporting the other). IMO, whatever is mounted at device disk1s2 is bad. Your reformats, repairs, etc may have remapped some bad sectors on that disk, but clearly hasn't repaired all of them (or, the disk is continuing to fail with new bad spots).

    I would suggest that you make a backup of your system somewhere other than whatever is on disk1s2. I'd then retire that disk...

  3. 0

    Lance!

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for your post.

    I suspected what you were saying and removed disk1s2 from the TM back-up. Much to my surprise I had a beach ball event following. I went and examined the console and found Spotlight had been indexing disk1s2 and got what appears to be the same errors. I pulled the plug last evening so disk1s2 won't be the cause of any more beach balls.

    Why do you think Disk Warrior and Disk Utility didn't find anything? Do you think reformatting disk1s2 would correct it?

  4. 0

    glsmith

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Why do you think Disk Warrior and Disk Utility didn't find anything? Do you think reformatting disk1s2 would correct it?

    I don't know why DW wouldn't have found any problems, but I don't honestly know too much about that utility. As for your second question, reformatting would certainly change the landscape, but wouldn't fix anything. The disk could be beyond just remapping sectors. The safest thing to do is to think of that disk as bad and replace it. Depending on its age, you might still be under warranty...

  5. 0

    Lance!

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I disconnected the offending drive and my iMac is running perfectly. I'm going to give the bad drive one more chance by reformatting it before I retire it.

    Thanks for your help!