Date: Tue, 3 Mar 1998 20:25:33 -0800 (PST) From: Doug White <dwhite@gdi.uoregon.edu> To: Stunt Pope <markjr@shmOOze.net> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: superblock corrupted (is BROKEN_KEYNOARD_RESET still applica Message-ID: <Pine.BSF.3.96.980303202435.21429P-100000@gdi.uoregon.edu> In-Reply-To: <XFMail.980303151212.markjr@shmOOze.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 3 Mar 1998, Stunt Pope wrote: > >Are these disks runing in dedicated mode or compatibility mode, i.e. do > >they have a proper partition table? > > > > These are dedicated unix boxes. No multiple boot images, no other o/s. So there is no partition table on this disk? > >I can't see how BROKEN_KEYBOARD_RESET would have anything to do with it; > >it just controls how the system is restarted during a reboot. I.e., if > >your system sticks up at the `Rebooting...' on a shutdown, then you need > >it. > > > > Date: Wed, 2 Oct 1996 00:52:40 -0700 (PDT) > From: "Bryan K. Ogawa" <bkogawa@primenet.com> > To: freebsd-questions@freebsd.org > Subject: 2.1.5, BROKEN_KEYBOARD_RESET, and \ > AHA-2840 VLB = overwrite super , block on reboot > > which mentions: > > <quote> > With the new kernel in place, the system works fine. Unfortunately, > whenever FreeBSD triggers a reboot (e.g. shutdown -r or pressing a key on > the console after shutdown -h), the SCSI drive loses its super block. Hm, thanks for dredging this up. The sync code must have a problem in the BROKEN* case. I suppose this is one for -hackers. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.96.980303202435.21429P-100000>