From owner-freebsd-bugs Thu Feb 8 16:22:47 1996 Return-Path: owner-bugs Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA12123 for bugs-outgoing; Thu, 8 Feb 1996 16:22:47 -0800 (PST) Received: from hauki.clinet.fi (root@hauki.clinet.fi [194.100.0.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA12103 for ; Thu, 8 Feb 1996 16:22:35 -0800 (PST) Received: from katiska.clinet.fi (root@katiska.clinet.fi [194.100.0.4]) by hauki.clinet.fi (8.7.3/8.6.4) with ESMTP id CAA02931; Fri, 9 Feb 1996 02:21:36 +0200 (EET) Received: (hsu@localhost) by katiska.clinet.fi (8.7.3/8.6.4) id CAA26455; Fri, 9 Feb 1996 02:21:35 +0200 (EET) Date: Fri, 9 Feb 1996 02:21:35 +0200 (EET) Message-Id: <199602090021.CAA26455@katiska.clinet.fi> From: Heikki Suonsivu To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: bde@zeta.org.au (Bruce Evans), hsu@clinet.fi, freebsd-bugs@FreeBSD.org Subject: Re: bin/984 In-Reply-To: <199602082334.AAA12608@uriah.heep.sax.de> References: <199602081756.EAA28874@godzilla.zeta.org.au> <199602082334.AAA12608@uriah.heep.sax.de> Organization: Clinet Ltd, Espoo, Finland Sender: owner-bugs@FreeBSD.org Precedence: bulk J. Wunsch writes: > As Bruce Evans wrote: > > > > Actually it should be possible to fix it by running fdisk to set the new > > C/H/S values. > > Ok, this might be possible. Anyway, the least we would need to know > is whether my suggested manual fix did really fix the problem. > Neither Heikki (sp?) nor some other guy whom i've been suggesting this > method did get back with _any_ feedback however. All these systems I have trouble with are in some kind of production use, so I'm pretty much deadlocked until I happen to be awake at suitable morning hour to be able to experiment (when they crash during peak hours, I have to just get them up as fast as possible). I was also trying to read some boot code source to learn more about this and how it could be worked around (but I haven't had much time lately). About the suggested fdisk fix, if C/H/S values are changed wouldn't this break the partition limits, or are the partitions encoded just as block offsets? > Guys, it's not only that you should complain here, you should rather > _co-operate_. Our ideas are worthless without getting feedback. > > (No, i'm not going to buy just another motherboard to see your > problems fixed. Even if i did -- i wouldn't had the problem in the > first place, or whaddaya think why i've been inventing the > ``dangerously dedicated'' mode? :) Install an Intel Plato system in dangerously dedicated mode with BT ISA controller and replace it with a NCR PCI controller, and it may/will not boot (too large cylinder number 1040 > 1024, BIOS limit). This is actually quite weird, as the root partition is about 200Mbytes which should be below 1024 cylinder, no matter what geometry is used. This isn't that serious, I'll reinstall on another machine and copy the files over and switch the root disk to see if it fixes the problem. The previously mentioned Plato to ASUS switch was worse as it was the primary server which can't be kept down for long, and it takes some time to move services out of it so that I can start experimenting with it. -- Heikki Suonsivu, T{ysikuu 10 C 83/02210 Espoo/FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-0-4375360 fax -4555276 home -8031121