From owner-freebsd-questions Thu Mar 23 1: 7:58 2000 Delivered-To: freebsd-questions@freebsd.org Received: from emu.prod.itd.earthlink.net (emu.prod.itd.earthlink.net [207.217.121.31]) by hub.freebsd.org (Postfix) with ESMTP id 3306637BA5B for ; Thu, 23 Mar 2000 01:07:55 -0800 (PST) (envelope-from bduk@arthlink.net) Received: from arthlink.net (sdn-ar-006orportP078.dialsprint.net [63.178.66.166]) by emu.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id BAA04458; Thu, 23 Mar 2000 01:07:52 -0800 (PST) Received: (from bduk@localhost) by arthlink.net (8.9.3/8.9.3) id BAA01522; Thu, 23 Mar 2000 01:07:54 -0800 (PST) (envelope-from bduk) Date: Thu, 23 Mar 2000 01:07:54 -0800 (PST) Message-Id: <200003230907.BAA01522@arthlink.net> From: Derrick Baumer To: tracker@worldy.com Cc: questions@FreeBSD.ORG In-reply-to: <38D96D1D.167EB0E7@worldy.com> (message from David Banning on Thu, 23 Mar 2000 01:02:21 +0000) Subject: Re: how to set Freebsd boot bisk as secondary drive Reply-To: bduk@earthlink.net Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > From: David Banning [big snip] > > > What I did notice however is this; the emergency read-only shell it > > > brings up it calls simply wd1s1a (a dev that does not exist). When > > > I do a df it shows the / file system as 512 byte blocks, while when > > > I boot the disk without errors in the wired wd0 position, it comes > > > up as 1024 byte blocks. It is the same file system - same ratio of > > > total to used to available blocks. Just double the size of each > > > block. That got me wondering if there is some config place where > > > the machine is told what size blocks to use. I did grepped "512" and > > > "1024" in /boot /boot/defaults and /usr/src/sys/i386/conf to see if > > > anything is configed as such - no luck. > > > > I have a device /dev/ws1s1a on my system, but the install might have > > put it there based on what it detected or something. If you intend to > > boot from that drive, I'm sure FreeBSD would like to be able to access > > it through its device entries, though! It seems to me the system > > should come to a screeching halt if it's required to access a device > > for which it has no device entry, especially if it's the boot drive. > > That it boots at all is either testament to greatness or indication of > > folly. Try > > > > cd /dev > > ./MAKEDEV wd1 > > here is where the answer lay I didn't get anyehere > trying to do batchs of drivers with MAKEDEV but once > I made the dev's individually eg ./MAKEDEV wd1s1a > all was well! > > Thanks for hanging on till we got it working - Cheers! My first right answer, y'all. Neat. :) -- Derrick Baumer bduk@earthlink.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message