From owner-freebsd-mobile Thu Oct 15 09:03:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12777 for freebsd-mobile-outgoing; Thu, 15 Oct 1998 09:03:02 -0700 (PDT) (envelope-from owner-freebsd-mobile@FreeBSD.ORG) Received: from exchangeserver.mpainc.com ([198.246.145.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12772 for ; Thu, 15 Oct 1998 09:03:00 -0700 (PDT) (envelope-from RickSiple@mpainc.com) Received: by EXCHANGESERVER with Internet Mail Service (5.5.1960.3) id <4VF8G2M4>; Thu, 15 Oct 1998 12:03:28 -0400 Message-ID: <50D018439050D211AFB1006008CEB82D0615D9@EXCHANGESERVER> From: Rick Siple To: "'Kenneth Ingham'" , freebsd-mobile@FreeBSD.ORG Subject: RE: 2.2.7 and suspend or sleep Date: Thu, 15 Oct 1998 12:03:08 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can you tell if your laptop is trying to suspend to disk? (Meaning it is trying to write the contents of RAM out to the disk.) If it is and you have not reserved space for the memory dump, the BIOS will simply overwrite whatever happens to be stored in that area of the disk, which could very well be some or all of your root partition. I have never had to do this myself so I can't really help your there, but this might put you on the right track for a solution. __________ Rick Siple ricksiple@mpainc.com > -----Original Message----- > From: Kenneth Ingham [SMTP:ingham@i-pi.com] > Sent: Thursday, October 15, 1998 11:29 AM > To: freebsd-mobile@FreeBSD.ORG > Subject: 2.2.7 and suspend or sleep > > I have (had?) a 2.2.7 system from the CD on a Dell Latitude 486-100. > The power supply became unplugged and it appears to have suspended > or something similar when the batery died. So far, so good. > > However, when I got it power again and woke it up, it paniced saying > a block on the disk was bad (a block with a large negative value, > unsigned it would be way beyond the end of the disk). Then it > tried to reboot and fails with the message: > Can't find file boot.config > Can't find file boot.help > When I press return at the boot: prompt, I get: > Can't find kernel > > I have never tried to make this machine sleep while using 2.2.7. > 2.2.6 was > destroyed in a similar manner on this machine when I closed the lid. > Older > versions of FreeBSD went to sleep with no problems. I had planned at > some > point of looking into the problem, but never had time to deal with the > damage > that might occur (maybe I've got the opportunity now :-). > > Can someone tell me what device to try to fsck to recover what I > can (if I can recover anything)? This machine was configured with > a single partition in ``dangerously dedicated'' mode. Booting with > a rescue floppy (Sorry, no CD on this ancient beast) I could not > find anything in /mnt2/dev which seemed to contain a filesystem. > > Is there a kernel or other config I missed relating to power > management that > says, ``don't clobber the filesystem when you go to sleep''? :-) > > Luckily, my last backup was made a couple of hours before the > machine died, and I'm restoring to another machine as I write this. > > Kenneth > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-mobile" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message