Hi, A memory check is a fantastically simple place to start, and can prevent hours and hours of frustrating searches. An excellent memory check is available in the boot menu for (almost) every install disk around.
I know of serveral people who blame power supplies, and inadequacies there. This is kinda hard to diagnose, except by swapping out your power supply, and probably is not your problem. (it was 2.6.22-14 - the kernel version). To be honest though, it sounds a bit like your hard disk is corrupted. As to why the crash in the first place, not sure.. Derek. On Thu, 14 Feb 2008, Roger Searle wrote: > Hi, the following occurred out of the blue today, though may be the second > time it has happened. While using the machine as normal, the video cut out, > and needed a hard reset. The previous time it may have occurred was about 3 > or 4 days ago (where it re-booted fine), and that pre-dated running the Adept > Updater yesterday. One of the updates yesterday was a kernel upgrade to (from > memory) 2.6.22-something. So I can't be sure that the following is related to > the update: > > On reboot, I get the following: > > RAMDISK: ran out of compressed data > invalid compressed format (err=1) > Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block > (0,0) > > I have absolutely no idea what this is about, I'm googling but looking for any > experience from the list about how to proceed. > This email is being composed booted into Mepis - the previous installation to > the above Gutsy problem. So the hardware is functional. df isn't showing me > any full partitions. > Any pointers gratefully received! > Roger > > -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: [EMAIL PROTECTED] ph +64 3 365 6485 Web: http://www.indranet-technologies.com/
