[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] 550 resynchronization/reboot loop
- Subject: RE: [cobalt-users] 550 resynchronization/reboot loop
- From: "Richard Sidlin" <richard@xxxxxxxxxxxxxxxxxx>
- Date: Fri Jun 6 13:30:00 2003
- List-id: Mailing list for users to share thoughts on Sun Cobalt products. <cobalt-users.list.cobalt.com>
>Subject: [cobalt-users] 550 resynchronization/reboot loop
>
>
>Ugh, problem started earyly this morning.
>I have a dual 80GB Raq550 that is stuck in this resync, reboot loop.
>
>All was working fine up till now, and haven't done any
>patching, and avoided the 3 latest ones, though did the All
>Security V-3 one a few weeks ago, which has the DNS with new
>vsite issue.
>
>>From previous posts, looks like this is one solution:
>"I have had a service request with Sun for 3 weeks now. They
>have about 4 customers with the same problem. It has now
>escalated to the US team. Still no answer so I got fed up and
>rolled back to the previous kernel and it is now back to normal."
>
>Any other solutions?
>
>How does one roll back to the previous kernel?
>
>thnx, Manny
>
cd /tmp
wget
ftp://ftp.cobalt.sun.com/pub/products/raq550/RPMS/kernel-2.4.16C12_V-1.i
386.rpm
wget
ftp://ftp.cobalt.sun.com/pub/products/raq550/RPMS/kernel-headers-2.4.16C
12_V-1.i386.rpm
wget
ftp://ftp.cobalt.sun.com/pub/products/raq550/RPMS/bwmgmt-1.0.0_2.4.16C12
_V-1.i386.rpm
rpm --install --force kernel-2.4.16C12_V-1.i386.rpm
rpm --install --force kernel-headers-2.4.16C12_V-1.i386.rpm
rpm --install --force bwmgmt-1.0.0_2.4.16C12_V-1.i386.rpm
/sbin/reboot
After it rebooted, it started the sync again and told me that the 2nd
drive was dead. I rebooted again via the GUI and it started syncing from
about 80% and has been fine ever since. It has also taken all of the
updates since then.
Richard Sidlin
--
This message has been scanned for viruses and dangerous content by the Help Internet Virus Spam Defence, and is
believed to be clean. For details on having your email scanned email support@xxxxxxxxxxxxxxxxxx