OK so I bought a Mac mini about 6 months ago. I updated to OSX Tiger about a month ago (erased and install, not upgrade). Today I'm having my first real problem with the computer. The mini has been very reliable up to now.
I set TomatoTorrent to run a download last night before going to bed and when I got up this morning TT said "I/O Error." Any application I clicked on got the color wait wheel spinning away. None of the command interrupts worked. Basically I had to power it off.
Now when the computer is turned on it locks up. The Apple logo part goes by, then the blue "Loading Mac OS X" screen comes up. The progress bar gets about 1/6 completed before the screen turns medium blue and it locks up again. I can't get it to boot off the Tiger install disc to reinstall and I can't get into the safe boot mode. I suspect this may be due to the mini being hooked up to a KVM switchbox (I do not have a USB keyboard) which converts ps/2 keyboard input to USB.
Any ideas?
August 15 2005, 15:54:55 UTC 6 years ago
August 15 2005, 16:05:11 UTC 6 years ago
August 15 2005, 16:09:22 UTC 6 years ago
The trick is that it only comes with 90 days of *support*. If you call, you have to pay the support fee, but I think they refund it if it turns out to be a warrantied hardware failure.
August 15 2005, 20:03:31 UTC 6 years ago
Betcha I pop this open and find a crappy Toshiba drive instead of a better model like a Hitachi. (they gotta keep tht price low somehow) Looked up the procedure to replace the drive and it's no small task.
Drive isn't a total loss as it does spin up. Maybe just a few bad blocks. Know if OS-X handles bad block mapping adequately or not? I can always pop the drive in my laptop and run SpinRite to map out the failed blocks..
August 15 2005, 20:38:13 UTC 6 years ago
But keep in mind that all modern embedded-controller drives (i.e., anything IDE or SCSI) have automatic sparing. Any time the drive has difficulty reading or writing a sector, the sector will normally be automatically relocated. If you get I/O errors on the drive, it generally indicates severe damage that is beyond the capability of automatic sparing to correct.
There is only two cases when automatic sparing will fail. The first is the obvious case when the drive runs out of spare sectors. The second is if the sector is damaged to the point that it cannot be read at all (i.e., beyond the ability of the embedded error-correction codes and automatic retries to recover). In this case, the drive will not move the sector, so that if in the future the sector becomes readable or if you send the drive to a recovery business, the associated data will still be recoverable.
If this is the case, then forcing a write to that sector should allow the sector to be automatically relocated, and may bypass the problem.
However, I would not trust any drive that has ever returned a bad sector error with data that I did not want to lose.
August 16 2005, 02:59:47 UTC 6 years ago
Once I got into the first aid console things looked a bit better. Unfortunately I got the dreaded "incorrect number of threads" error on the file system because the kernel had a panic moment. The drive was OK but the whole file system was toast and couldn't even mount the volume. Had to totally erase the disk and reinstall Tiger all over again. Lost a bunch of files. :-( Couldn't even copy them off due to the unmountable volume problem.
August 15 2005, 20:42:50 UTC 6 years ago
August 15 2005, 16:21:43 UTC 6 years ago
friend says:
August 15 2005, 16:23:27 UTC 6 years ago
To boot into single user hold down openapple and s while powering on.
To boot off the cd hold down the c key. When you boot into the install run repair permissions from the disk util before reinstalling.
If neither work then try plugging a keyboard directly info the mini.
August 15 2005, 20:04:31 UTC 6 years ago
August 15 2005, 20:34:50 UTC 6 years ago
August 16 2005, 02:31:33 UTC 6 years ago