elliott-brennan <[EMAIL PROTECTED]> writes:
> Well, it would seem the problem was a dying HDD!
>
> My SECOND Western Digital HDD has just died. I only bought it about 14
> months ago. I had another which died 14 months ago (replaced under
> warranty - it was a couple of months short of three years
Well, it would seem the problem was a dying HDD!
My SECOND Western Digital HDD has just died. I only bought it about 14
months ago. I had another which died 14 months ago (replaced under
warranty - it was a couple of months short of three years old).
My machine is on 24/7, I do a fair bit of vide
> "elliott-brennan" == elliott-brennan <[EMAIL PROTECTED]> writes:
elliott-brennan> Hi all I use Dapper at the present.
elliott-brennan> On the weekend I was copying images from my DSLR
elliott-brennan> (common event) to my machine using Digikam.
elliott-brennan> I was running a few other t
Hi,
I would suspect something at application-level data file corruption.
Try moving .kde aside.
Also what does the X server log and .xsession-errors files say when
you try to login?
About hardaware level errors - do you see anything suspicious in
dmesg's output? If it's hardware or OS error trigg
On Wed, Oct 29, 2008 at 01:27:45AM +1100, elliott-brennan wrote:
> Hi all
>
> I use Dapper at the present.
[snip]
> Could someone please provide me with some
> information about what this may mean?
I would try using smartctl something like
smartctl -t long -d sat /dev/sda -T permissive
smartc
Hi all
I use Dapper at the present.
On the weekend I was copying images from my DSLR
(common event) to my machine using Digikam.
I was running a few other things and suddenly the
whole system froze. Ctrl-Alt-Backspace didn't
work. Nor did Alt-Shift-sysrq-S-U-B.
So I held in the power button and
