[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Qube Update Qube3-All-Kernel-2.0.1-2.216C32-2III killed my Std Qube3
- Subject: Re: [cobalt-users] Qube Update Qube3-All-Kernel-2.0.1-2.216C32-2III killed my Std Qube3
- From: Malcolm McLeary <mmcleary@xxxxxxx>
- Date: Tue May 21 00:27:50 2002
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
Hi Guys,
on 21/5/02 10:41 PM, Malcolm McLeary wrote:
> I have a Std Qube3 which I got around to updating today ... the first update
> went ok, the Qube rebooted and all services appeared to be ok. After the
> second update (Qube3-All-Kernel-2.0.1-2.216C32-2III), the Qube3 did not come
> back ... it just sat there saying its booting.
I've installed a fresh disk in slot A of my Qube3 Pro Ed and done a Std
Qube3 OS restore. It appears to be working fine except that I don't think
the partitions add up to 10G.
Anyway, if I install the "dead" disk in slot B how do I mount the partitions
so I can either recover data or fix the problem?
I think its likely that I was unlucky and the disk crashed, or the update
didn't go well and I have a corrupt kernel.
I guess if I can mount the disk then I can assume it didn't crash.
What does that update actually install? Could I simply copy good versions
from the disk I just restored?
Cheers, Malcolm
-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
Information Alchemy Pty Ltd
ACN 089 239 305
Canberra, Australia
Malcolm McLeary Mobile: 0412 636 086
Managing Director Email: mmcleary@xxxxxxx
This message was sent using Outlook Express 5.0 for Macintosh.