Alex Holden (alex_holden) wrote,
Alex Holden
alex_holden

Doh

I realised this morning that I hadn't backed up my home Mac Mini for a few weeks, so I kicked off a fresh clone to the external Firewire drive. The backup disk ran out of space part way through (it shouldn't really do this because the backup partition is bigger than the internal disk), so I wiped it and tried again. Naturally the machine chose this moment to totally crap out. Rebooting in single user mode revealed that the internal disk has corrupted itself in a new and entertaining fashion that fsck doesn't know how to fix[1]. I've persuaded it to boot into graphical mode again but it's acting very flaky (applications not starting or running for a bit then crashing, the whole machine randomly freezing for thirty seconds at a time...). I'm trying to back up as much data as I can to the Firewire disk before I attempt to reinstall it tomorrow. Annoyingly this is the third time this particular machine has corrupted its internal disk - I suspect it must have a hardware fault. Luckily there is very little on it that isn't also stored elsewhere.

ETA: Google suggests the disk error code I'm getting basically means "the disk is about to die." I'd better order a replacement in the morning...

[1]
localhost:/ root# /sbin/fsck -fy
** /dev/rdisk0s2
** Root file system
** Checking HFS Plus volume.
** Checking Extents Overflow file.
** Checking Catalog file.
disk 0s2: 0xe0030005 (UNDEFINED).
Invalid node structure
(4, 898)
** Rebuilding Catalog B-tree.
** The volume Dors could not be repaired.
Tags: apple
Subscribe
  • Post a new comment

    Error

    default userpic

    Your reply will be screened

    Your IP address will be recorded 

    When you submit the form an invisible reCAPTCHA check will be performed.
    You must follow the Privacy Policy and Google Terms of use.
  • 4 comments