Backing is always a good idea, and another HD is on the list, so unfortunately 
are other things, for now :( 

Critical stuff is backed tho, and on stored a network drive rather than this 
machine :)

I didn't make my self clear.
I can fire up the machine, use it for some time, and then within a few minutes 
have all manner of misbehaviour in front of me that ultimately brings the 
machine to it's knees. The common factor with all error messages is the 
inability to write any files as everything becomes read only - within 
minutes - on 3 separate drives, one of which is a network drive. Upon reboot, 
or more likely, upon me hitting the power button as it wont even finish 
shutting down, all becomes good again, till next time.

Running the machine hard seems to speed up the process, however i am yet to 
figure what, if any, program is more likely to bring it all down that others.

I really don't think it's a hardware issue given that all 3 drives magicly 
fail at the same time and then magicly come right after i restart the 
machine.




On Thu, 11 Sep 2008 09:09:12 Roger Searle wrote:
> dmesg is full of info about all your memory, bios, power management, 
> hardware (cpu, usb, video, keyboard, cd drive etc) hence so long and 
> scary.  the trick is looking for lines about your hard drive(s) or file 
> systems.  i'm not experienced enough to comment about my viewing of it 
> and will leave that to others, but am interested to know how the machine 
> is performing or behaving now that it has rebooted?  are you still 
> seeing the issues? 
> 
> and are you paying attention to the hints about backing up your data?  
> you can always buy another hard drive and install another distro, but 
> your data is another matter . . .
> 
> Roger
> 
> 
> Chris wrote:
> > I don't actually think it a hard drive issue as the sudden wealth of 
errors 
> > seem to apply to 3 separate drives
> > /var/whatever is hda1
> > ~/.kde/whatever is hdb
> > /music and all the bulk storage is a network drive on another machine.
> >
> > Look in /var/log/syslog, /var/log/syslog, and the output from dmesg | more
> > well there is no /var/log/syslog to look into, and the output of dmesg | 
more 
> > (below) scares the willies out of me.
> >
> >   
> 



-- 
:D
+6421374115
www.millerton.co.nz

Reply via email to