On Fri, Aug 27, 2010 at 12:48 PM, Joseph Jezak <[email protected]> wrote:
> On 08/27/10 12:19, Mark Knecht wrote:
>> On Thu, Aug 26, 2010 at 10:27 PM, Terin Stock <[email protected]>
>> wrote:
>>> If it's just going to be sitting in a closet collecting Apple-dust, then I'd
>>> say yes, it's certainly worth the extra effort.
<SNIP>
>>
>>
> I think the kernel might have gotten renamed, but missed in the
> documentation. Please try using ppc32 instead of apple. I suspect it's
> trying to boot a 64 bit kernel instead of the 32 bit one.
>
> -Joe
Thanks Joe. That worked fine with the most recent 2009 install CD. It
would be good if someone reading could add the Mac Mini to one of the
lists of supported machines and update the docs to explain this a bit
more.
I can now see the old partition and fsck ran cleanly. (I think...)
livecd ~ # mac-fdisk /dev/hda
/dev/hda
Command (? for help): Command (? for help): p
/dev/hda
# type name length base
( size ) system
/dev/hda1 Apple_partition_map Apple 63 @ 1
( 31.5k) Partition map
/dev/hda2 Apple_Bootstrap bootstrap 1600 @ 64
(800.0k) NewWorld bootblock
/dev/hda3 Apple_UNIX_SVR2 swap 2097152 @ 1664
( 1.0G) Linux swap
/dev/hda4 Apple_UNIX_SVR2 root 154202672 @
2098816 ( 73.5G) Linux native
Block size=512, Number of Blocks=156301488
DeviceType=0x0, DeviceId=0x0
Command (? for help): q
livecd ~ # fsck -t ext3 /dev/hda4
fsck 1.40.4 (31-Dec-2007)
e2fsck 1.40.4 (31-Dec-2007)
/dev/hda4: clean, 352751/9650176 files, 16137329/19275334 blocks
livecd ~ #
Now, when I try rebooting with the current hard drive installation I get to
* Checking root filesystem...
fsck.ext3: No such file or directory while trying to open /dev/hda4
/dev/hda4:
The superblock could not be read or does not describe........
Where does this suggest the problem might be? The partition is 'good'
when I boot from the CD but bad when I boot from the current kernel?
Strange to me.
Anyway, if it's hard to fix no big deal. At least if I can read it
using the CD then I can copy anything I need off and just do a new
install, assuming there isn't anything really had happening with the
hard drive.
Thanks,
Mark
