Thank you for your reply. Let me clarify a bit.
I know I should not put testing on a production server, but testing at
that point (January a year ago) was almost the stable sarge and I took a
chance. Woody was just too old. I didn't think of using dist-upgrade
as I was going from the old testing-sarge to stable-sarge. All the
security updates that I did over the last year were done with just the
security update line in sources.list.
In January this year, I replaced the commented out testing lines from
the original install with uncommented sarge lines in sources.list, left
the security one, did an aptitude update followed by an aptitude
upgrade. I then installed the 2.6.8-2-686-smp kernel from
stable-Sarge. That one as well as the original testing-sarge one
(2.6.8-1-686-smp)are both crashing when doing the backups.
Any other ideas?
Karen
Kevin Mark wrote:
On Mon, Feb 20, 2006 at 03:12:31PM -0600, Karen Larson wrote:
A dual CPU Intel machine was installed with Debian testing on 1/14/05
with a 2.6.8-1-686-smp kernel. Security updates were applied over the
next year as they became available. Machine was backed up to an
unpartitioned USB external hard drive at /dev/sdb with a tar command
(similar to backing up to tape).
On 1/9/06, in addition to applying security patches, I added the lines
for sarge main in the sources.list file and upgraded (aptitude upgrade)
43 packages to turn it into a stable Sarge. The kernel-image was
changed to 2.6.8-2-686-smp. Since that date, the machine crashes while
backing up. The backup may run for anywhere from 25 minutes to an hour
before the machine crashes. Different USB harddrives have all crashed
during backups. Booting back into the old kernel did not make a
difference -- machine still crashed during backup.
Hi Karen,
it sounds like this is a production server, as such it is not
recommended to use testing. But you mentioned that you added lines for
Sarge which is good but I would remove any lines for testing, add the
lines for 'security updates' and 'apt-get update' and 'apt-get
dist-upgrade'. Investiage what stable,testing, and unstable are and know
why you should only be using stable. As for the issue, after you get the
latest stable kernel from Sarge, see if it still happends and tell us if
it still happens. Also did the person upgrading read the release notes
for Sarge. If not, check the debian.org web site.
Cheers,
Kev
--
Karen Larson UW - Parkside 262-595-2450
System Administrator 900 Wood Road [EMAIL PROTECTED]
Computer Science Dept Kenosha, WI 53141-2000
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
