On Thu, May 7, 2009 at 8:43 AM, Per Inge Oestmoen <pioe@coldsiberia.org> wrote:
Per Jessen wrote:
Per Inge Oestmoen wrote:
Which errors? Did it just hang? How do you know that the disk became inaccessible?
I got this:
---- linux-k9na:/home/siberia # fdisk /dev/sdc
Unable to open /dev/sdc ----
It would have been nice to see the output from dmesg right after this, but if fdisk cannot access the disk, you have a hardware problem.
Here is the most recent dmesg:
Every time you reboot the dmesg data is reset to null. Your link appears to be to a dmesg shortly after booting up. It contains nothing relevant to your issue. Also, dmesg only reports a limited amount of data going back a limited amount of time. In general you want to trigger the fault, then immediately capture the dmesg. Greg -- Greg Freemyer Head of EDD Tape Extraction and Processing team Litigation Triage Solutions Specialist http://www.linkedin.com/in/gregfreemyer First 99 Days Litigation White Paper - http://www.norcrossgroup.com/forms/whitepapers/99%20Days%20whitepaper.pdf The Norcross Group The Intersection of Evidence & Technology http://www.norcrossgroup.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org