Re: Boot failure after installation

2007-04-12 Thread Jerry McAllister

 Will someone please explain in detail how to run the FreeBSD fdisk util 
 outside of the freebsd installer? Please provide detailed steps.

You just type   fdisk devname   where devname is the disk device.

There are a number of flags and parameters you may need to use.
Have you read the fdisk man page?Also read the bsdlabel man page.

 What would the experts do next in this situation? I've checked and 
 double-checked BIOS (current version is same as what I have -- 1013, so did 
 not re-flash), SCSI BIOS (reset defaults and low-level formatted da0). I've 
 performed Minimal FreeBSD install per step-by-step directions, and always 
 says it's installed successfully, but can never boot from da0 (since 
 repartitioning using FreeBSD fdisk util). I've verified that I'm creating a 
 single partition (slice) on da0, making it the active partition, then 
 setting it Bootable.

I would first ignore the issue of cylinders as has been mentioned.

 
 I booted the FreeSBIE LiveCD, and tried to mount da0:
 mount /dev/da0 /mnt
 mount: /dev/da0: Operation not permitted

First of all, do you even have a da0 drive?  Maybe it is  ad0

Second, is there a file system build on da0a?I haven't seen anything
that indicates it.   You can only mount a file system.   Fdisk doesn't
have much to do with creating a file system.   That is newfs.


The standard way to build a disk is:
  Use fdisk to create slice[s] (1..4)  -- and possibly write an MBR on the disk.
  Use bsdlabel to divide the slice in to partitions (a..h) and possibly
  write a boot sector on the slice.
  Use newfs to create file systems on each of the partitions except swap  c.

Then you can mount any of those newfs created filesystems.  

You must first read the man pages for those utilities and also study the
relevant handbook sections.   Also, peruse the FreeBSD-questions archives.
I have written on this several time recently.   Find and read those.

Then, if you have further specific questions, come back and ask.  But, you
must do your homework first or our answers will be useless to you and a
waste of our time.

jerry

  
 Jerry McAllister [EMAIL PROTECTED] wrote: On Tue, Apr 10, 2007 at 
 07:48:07PM -0700, L Goodwin wrote:
 
  Is there a way to run the FDISK tool outside of the freebds installer? 
  How do I change the disk configuration without reinstalling freebsd 
  every @[EMAIL PROTECTED] time?
 
 Yes, all sysinstall does is collect the information and run fdisk for you.
 See the man page   (enter  man fdisk )
 
 It can be a little hard to read at first.  The fdisk and bsdlabel don't 
 follow the normal man page form.
 
 One thing you must know;  you cannot run fdisk on a drive that is in
 active use.  If you booted from that drive or if you are CD-ed in to 
 a file system on the drive, the system will not let you write to the
 drive using fdisk.   You can only use fdisk to read the slice table
 and run prototype setups that do not actually write out to the disk.
 
 Trying to write to a drive that is active is a very popular mistake
 when attempting to use fdisk.
 
 So, read the fdisk man page and then come back with some more specific
 questions if you need.
 
  I really want to set up a FreeBSD server and appreciate the learning 
  experience, but it's way past the point where I should have switched to an 
  OS that will actually run on my client's server. If I don't get it going 
  tonight, I'm going to install the first Linux distribution that says Hey, 
  Sailor...  =8-0
 
 Guess you will need to follow the installation instructions in the FreeBSD
 handbook more carefully.
 
  BTW, I burned a freeSBIE 2.0.1 Live CD, but have no idea what to do with 
  it. Yes, I am pathetically clueless. Thanks for your patience!
 
 Just boot it up and run it.It will give you a very basic working
 environment.Then do something like you might in a UNIX system, 
 like ls or cd or df or whatever.
 
  
  Derek Ragona  wrote:   One other thing that 
  might be happening is if the geometry of the drive isn't allowing an 
  extended translation because of the age of your hardware, you may need to 
  keep the boot partition, that is the entire boot partition (not talking 
  slices here) within the first 1024 cylinders.  In the partition tool in 
  sysinstall you can change the display to show different units, and one of 
  those will be cylinders.  The 1024 cylinder limit is from older BIOS 
  translations and if the boot partition extended beyond 1024 the system 
  will give that same error you are getting.
 
 If the machine is built any less than about 11 years ago, this doesn't apply.
 
   With older hardware you may need to use multiple partitions instead of 
  slices.  You can have 4 partitons on a drive (4 is hardcoded in the 
  partition table size and a location) so you can add additional partitions 
  for swap and /usr if you want.  Any partitions you use for filesystems 
  like /usr the boot manager will see and offer to boot them.  

Re: Boot failure after installation

2007-04-12 Thread L Goodwin
I have BOTH ad0 (IDE HDD) AND da0 (SCSI device #0). I posted detailed BIOS 
settings and install steps in previous emails. I've attached the BIOS and SCSI 
BIOS settings (with footnotes).

I have installed FreeBSD on da0 multiple times, each time creating a single 
slice/partition on da0, and setting da0 as bootable, and installing the FreeBSD 
boot manager on da0. OK?

I also found an IDE HDD yesterday, and installed Linux on ad0 (the IDE HDD), 
but am getting the exact same boot failure. 

I tried setting my bios to try booting from IDE drives first (before SCSI), and 
vice-versa (SCSI first, which is what it was set to), with no change.

I also tried removing the IDE HDD and booting, but boot from CD-ROM drive 
hangs, and boot from C fails.
I did not change BIOS settings re the (removed) IDE HDD. I've never worked on a 
machine that has both SCSI and IDE controller/drive configuration, and am not 
sure how to disentangle the IDE hard drive from the system without causing new 
problems. Ended up reinstalling the IDE HDD for now, but would like to remove 
it for use elsewhere (this machine has 5 SCSI drives, so don't need it).

Jerry McAllister [EMAIL PROTECTED] wrote: 
 Will someone please explain in detail how to run the FreeBSD fdisk util 
 outside of the freebsd installer? Please provide detailed steps.

You just type   fdisk devname   where devname is the disk device.

There are a number of flags and parameters you may need to use.
Have you read the fdisk man page?Also read the bsdlabel man page.

 What would the experts do next in this situation? I've checked and 
 double-checked BIOS (current version is same as what I have -- 1013, so did 
 not re-flash), SCSI BIOS (reset defaults and low-level formatted da0). I've 
 performed Minimal FreeBSD install per step-by-step directions, and always 
 says it's installed successfully, but can never boot from da0 (since 
 repartitioning using FreeBSD fdisk util). I've verified that I'm creating a 
 single partition (slice) on da0, making it the active partition, then 
 setting it Bootable.

I would first ignore the issue of cylinders as has been mentioned.

 
 I booted the FreeSBIE LiveCD, and tried to mount da0:
 mount /dev/da0 /mnt
 mount: /dev/da0: Operation not permitted

First of all, do you even have a da0 drive?  Maybe it is  ad0

Second, is there a file system build on da0a?I haven't seen anything
that indicates it.   You can only mount a file system.   Fdisk doesn't
have much to do with creating a file system.   That is newfs.


The standard way to build a disk is:
  Use fdisk to create slice[s] (1..4)  -- and possibly write an MBR on the disk.
  Use bsdlabel to divide the slice in to partitions (a..h) and possibly
  write a boot sector on the slice.
  Use newfs to create file systems on each of the partitions except swap  c.

Then you can mount any of those newfs created filesystems.  

You must first read the man pages for those utilities and also study the
relevant handbook sections.   Also, peruse the FreeBSD-questions archives.
I have written on this several time recently.   Find and read those.

Then, if you have further specific questions, come back and ask.  But, you
must do your homework first or our answers will be useless to you and a
waste of our time.

jerry

  
 Jerry McAllister  wrote: On Tue, Apr 10, 2007 at 07:48:07PM -0700, L Goodwin 
 wrote:
 
  Is there a way to run the FDISK tool outside of the freebds installer? 
  How do I change the disk configuration without reinstalling freebsd 
  every @[EMAIL PROTECTED] time?
 
 Yes, all sysinstall does is collect the information and run fdisk for you.
 See the man page   (enter  man fdisk )
 
 It can be a little hard to read at first.  The fdisk and bsdlabel don't 
 follow the normal man page form.
 
 One thing you must know;  you cannot run fdisk on a drive that is in
 active use.  If you booted from that drive or if you are CD-ed in to 
 a file system on the drive, the system will not let you write to the
 drive using fdisk.   You can only use fdisk to read the slice table
 and run prototype setups that do not actually write out to the disk.
 
 Trying to write to a drive that is active is a very popular mistake
 when attempting to use fdisk.
 
 So, read the fdisk man page and then come back with some more specific
 questions if you need.
 
  I really want to set up a FreeBSD server and appreciate the learning 
  experience, but it's way past the point where I should have switched to an 
  OS that will actually run on my client's server. If I don't get it going 
  tonight, I'm going to install the first Linux distribution that says Hey, 
  Sailor...  =8-0
 
 Guess you will need to follow the installation instructions in the FreeBSD
 handbook more carefully.
 
  BTW, I burned a freeSBIE 2.0.1 Live CD, but have no idea what to do with 
  it. Yes, I am pathetically clueless. Thanks for your patience!
 
 Just boot it up and run it.It will give you a very basic 

Re: Boot failure after installation

2007-04-11 Thread Jerry McAllister
On Tue, Apr 10, 2007 at 07:48:07PM -0700, L Goodwin wrote:

 Is there a way to run the FDISK tool outside of the freebds installer? 
 How do I change the disk configuration without reinstalling freebsd 
 every @[EMAIL PROTECTED] time?

Yes, all sysinstall does is collect the information and run fdisk for you.
See the man page   (enter  man fdisk )

It can be a little hard to read at first.  The fdisk and bsdlabel don't 
follow the normal man page form.

One thing you must know;  you cannot run fdisk on a drive that is in
active use.  If you booted from that drive or if you are CD-ed in to 
a file system on the drive, the system will not let you write to the
drive using fdisk.   You can only use fdisk to read the slice table
and run prototype setups that do not actually write out to the disk.

Trying to write to a drive that is active is a very popular mistake
when attempting to use fdisk.

So, read the fdisk man page and then come back with some more specific
questions if you need.

 I really want to set up a FreeBSD server and appreciate the learning 
 experience, but it's way past the point where I should have switched to an OS 
 that will actually run on my client's server. If I don't get it going 
 tonight, I'm going to install the first Linux distribution that says Hey, 
 Sailor...  =8-0

Guess you will need to follow the installation instructions in the FreeBSD
handbook more carefully.

 BTW, I burned a freeSBIE 2.0.1 Live CD, but have no idea what to do with it. 
 Yes, I am pathetically clueless. Thanks for your patience!

Just boot it up and run it.It will give you a very basic working
environment.Then do something like you might in a UNIX system, 
like ls or cd or df or whatever.

 
 Derek Ragona [EMAIL PROTECTED] wrote:   One other thing that 
 might be happening is if the geometry of the drive isn't allowing an 
 extended translation because of the age of your hardware, you may need to 
 keep the boot partition, that is the entire boot partition (not talking 
 slices here) within the first 1024 cylinders.  In the partition tool in 
 sysinstall you can change the display to show different units, and one of 
 those will be cylinders.  The 1024 cylinder limit is from older BIOS 
 translations and if the boot partition extended beyond 1024 the system 
 will give that same error you are getting.

If the machine is built any less than about 11 years ago, this doesn't apply.

  With older hardware you may need to use multiple partitions instead of 
 slices.  You can have 4 partitons on a drive (4 is hardcoded in the 
 partition table size and a location) so you can add additional partitions 
 for swap and /usr if you want.  Any partitions you use for filesystems 
 like /usr the boot manager will see and offer to boot them.  They won't 
 boot of course.  Swap partitions are ignored by the boot manager. 
 
This is mostly incorrect and even backwards.

First of all, there are 4 slices possible on a drive (or raid set for all
that matters).   Microsoft tends to call slices Primary Partitions.
Slices are created and managed by the fdisk utility.  Fdisk also writes
the Master Boot Record (MBR) (but not the boot sector).

In FreeBSD you can divide each slice up in to partitions which are
identified as a..h, although 'c' is reserved.   These partitions are
created and managed by the FreeBSD bsdlabel utility (or disklabel in
older versions).   Bsdlabel also writes the boot sector.

  Otherwise, I'd suspect it is a problem with the 6.2 you are using then.  
 If you try with a boot within the 1024 (I wouldn't push that to the 
 limit I'd say try like 950 cylinders) then I would try an earlier 
 version such as 6.1 or 6.0.
 

The whole issue of 1024 cylinders limit for bootable file systems
went away with improved BIOS about 11 years ago.
If you have a system old enough to have the problem, you should be
updating the BIOS rather than trying to accomodate the limit.

jerry

  -Derek
  
 --  
 This message has been scanned for viruses and 
 dangerous content by MailScanner, and is 
 believed to be clean. 
 MailScanner thanks transtec Computers for their support. 
 
  
 -
 It's here! Your new message!
 Get new email alerts with the free Yahoo! Toolbar.
 ___
 freebsd-questions@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-questions
 To unsubscribe, send any mail to [EMAIL PROTECTED]
 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Boot failure after installation

2007-04-11 Thread L Goodwin
Will someone please explain in detail how to run the FreeBSD fdisk util outside 
of the freebsd installer? Please provide detailed steps.

What would the experts do next in this situation? I've checked and 
double-checked BIOS (current version is same as what I have -- 1013, so did not 
re-flash), SCSI BIOS (reset defaults and low-level formatted da0). I've 
performed Minimal FreeBSD install per step-by-step directions, and always 
says it's installed successfully, but can never boot from da0 (since 
repartitioning using FreeBSD fdisk util). I've verified that I'm creating a 
single partition (slice) on da0, making it the active partition, then setting 
it Bootable.

I booted the FreeSBIE LiveCD, and tried to mount da0:
mount /dev/da0 /mnt
mount: /dev/da0: Operation not permitted
 
Jerry McAllister [EMAIL PROTECTED] wrote: On Tue, Apr 10, 2007 at 07:48:07PM 
-0700, L Goodwin wrote:

 Is there a way to run the FDISK tool outside of the freebds installer? 
 How do I change the disk configuration without reinstalling freebsd 
 every @[EMAIL PROTECTED] time?

Yes, all sysinstall does is collect the information and run fdisk for you.
See the man page   (enter  man fdisk )

It can be a little hard to read at first.  The fdisk and bsdlabel don't 
follow the normal man page form.

One thing you must know;  you cannot run fdisk on a drive that is in
active use.  If you booted from that drive or if you are CD-ed in to 
a file system on the drive, the system will not let you write to the
drive using fdisk.   You can only use fdisk to read the slice table
and run prototype setups that do not actually write out to the disk.

Trying to write to a drive that is active is a very popular mistake
when attempting to use fdisk.

So, read the fdisk man page and then come back with some more specific
questions if you need.

 I really want to set up a FreeBSD server and appreciate the learning 
 experience, but it's way past the point where I should have switched to an OS 
 that will actually run on my client's server. If I don't get it going 
 tonight, I'm going to install the first Linux distribution that says Hey, 
 Sailor...  =8-0

Guess you will need to follow the installation instructions in the FreeBSD
handbook more carefully.

 BTW, I burned a freeSBIE 2.0.1 Live CD, but have no idea what to do with it. 
 Yes, I am pathetically clueless. Thanks for your patience!

Just boot it up and run it.It will give you a very basic working
environment.Then do something like you might in a UNIX system, 
like ls or cd or df or whatever.

 
 Derek Ragona  wrote:   One other thing that 
 might be happening is if the geometry of the drive isn't allowing an 
 extended translation because of the age of your hardware, you may need to 
 keep the boot partition, that is the entire boot partition (not talking 
 slices here) within the first 1024 cylinders.  In the partition tool in 
 sysinstall you can change the display to show different units, and one of 
 those will be cylinders.  The 1024 cylinder limit is from older BIOS 
 translations and if the boot partition extended beyond 1024 the system 
 will give that same error you are getting.

If the machine is built any less than about 11 years ago, this doesn't apply.

  With older hardware you may need to use multiple partitions instead of 
 slices.  You can have 4 partitons on a drive (4 is hardcoded in the 
 partition table size and a location) so you can add additional partitions 
 for swap and /usr if you want.  Any partitions you use for filesystems 
 like /usr the boot manager will see and offer to boot them.  They won't 
 boot of course.  Swap partitions are ignored by the boot manager. 
 
This is mostly incorrect and even backwards.

First of all, there are 4 slices possible on a drive (or raid set for all
that matters).   Microsoft tends to call slices Primary Partitions.
Slices are created and managed by the fdisk utility.  Fdisk also writes
the Master Boot Record (MBR) (but not the boot sector).

In FreeBSD you can divide each slice up in to partitions which are
identified as a..h, although 'c' is reserved.   These partitions are
created and managed by the FreeBSD bsdlabel utility (or disklabel in
older versions).   Bsdlabel also writes the boot sector.

  Otherwise, I'd suspect it is a problem with the 6.2 you are using then.  
 If you try with a boot within the 1024 (I wouldn't push that to the 
 limit I'd say try like 950 cylinders) then I would try an earlier 
 version such as 6.1 or 6.0.
 

The whole issue of 1024 cylinders limit for bootable file systems
went away with improved BIOS about 11 years ago.
If you have a system old enough to have the problem, you should be
updating the BIOS rather than trying to accomodate the limit.

jerry

  -Derek
  
 --  
 This message has been scanned for viruses and 
 dangerous content by MailScanner, and is 
 believed to be clean. 
 MailScanner thanks transtec Computers for their support. 
 
  
 

Re: Boot failure after installation

2007-04-10 Thread Derek Ragona

At 08:14 PM 4/9/2007, L Goodwin wrote:

Derek Ragona said:

 Go into the SCSI BIOS and reset the SCSI to default values.
 If it still gives the same error on bootup, I would go into the SCSI 
BIOS and

 low-level format that first drive, and reinstall FreeBSD.
 On the reinstall, I would just do the partioning for that drive, and 
then install everything.
 That way it will run mostly by itself, you can just check on it for the 
last few prompts of the

 install finishing up.

Derek, I just did the following, expecting that this would fix the glitch:

1) Reset the SCSI BIOS to Host Adapter Defaults: Matches prior 
configuration exactly.

2) Run a low-level format on SCSI device #0: No errors.
3) Install FreeBSD 6.2 from scratch. Note: I answered Yes to the prompt
ACPI was disabled during boot. Would you like to disable it 
permanently?.

I don't think it will boot if I enable ACPI.
RESULT: FAIL - Still getting DISK BOOT FAILURE, INSERT SYSTEM DISK AND 
PRESS ENTER


4) Ran Verify Disk Media on SCSI ID #0: Disk Verification Complete

What else could it possibly be? Are there any other diagnostics I can run?
What do you think of the fact that this machine was booting Windows 2000 
from the same

SCSI drive prior to installing FreeBSD 6.2?

In case it matters, all SCSI drives are IBM DNES-309170W ULTRA2-LVD.

Thanks!


One other thing that might be happening is if the geometry of the drive 
isn't allowing an extended translation because of the age of your hardware, 
you may need to keep the boot partition, that is the entire boot partition 
(not talking slices here) within the first 1024 cylinders.  In the 
partition tool in sysinstall you can change the display to show different 
units, and one of those will be cylinders.  The 1024 cylinder limit is from 
older BIOS translations and if the boot partition extended beyond 1024 the 
system will give that same error you are getting.


With older hardware you may need to use multiple partitions instead of 
slices.  You can have 4 partitons on a drive (4 is hardcoded in the 
partition table size and a location) so you can add additional partitions 
for swap and /usr if you want.  Any partitions you use for filesystems like 
/usr the boot manager will see and offer to boot them.  They won't boot of 
course.  Swap partitions are ignored by the boot manager.


Otherwise, I'd suspect it is a problem with the 6.2 you are using then.  If 
you try with a boot within the 1024 (I wouldn't push that to the limit I'd 
say try like 950 cylinders) then I would try an earlier version such as 6.1 
or 6.0.


-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Boot failure after installation

2007-04-10 Thread Christian Walther

it looks as if you've an IDE Interface onboard, too. Is it possible
that there are two ATA disks installed? Because the SCSI BIOS is only
installed when there are less then two ATA *disks* installed. Having
one Disk and one CD ROM should be fine, though.

Either try removing the ATA disks, or check your system BIOS if you
can select SCSI as boot device.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Boot failure after installation

2007-04-10 Thread L Goodwin
Is there a way to run the FDISK tool outside of the freebds installer? How do 
I change the disk configuration without reinstalling freebsd every @[EMAIL 
PROTECTED] time?

I really want to set up a FreeBSD server and appreciate the learning 
experience, but it's way past the point where I should have switched to an OS 
that will actually run on my client's server. If I don't get it going tonight, 
I'm going to install the first Linux distribution that says Hey, Sailor...  
=8-0

BTW, I burned a freeSBIE 2.0.1 Live CD, but have no idea what to do with it. 
Yes, I am pathetically clueless. Thanks for your patience!

Derek Ragona [EMAIL PROTECTED] wrote:   One other thing that might be 
happening is if the geometry of the drive isn't allowing an extended 
translation because of the age of your hardware, you may need to keep the boot 
partition, that is the entire boot partition (not talking slices here) within 
the first 1024 cylinders.  In the partition tool in sysinstall you can change 
the display to show different units, and one of those will be cylinders.  The 
1024 cylinder limit is from older BIOS translations and if the boot partition 
extended beyond 1024 the system will give that same error you are getting.

 With older hardware you may need to use multiple partitions instead of slices. 
 You can have 4 partitons on a drive (4 is hardcoded in the partition table 
size and a location) so you can add additional partitions for swap and /usr if 
you want.  Any partitions you use for filesystems like /usr the boot manager 
will see and offer to boot them.  They won't boot of course.  Swap partitions 
are ignored by the boot manager. 

 Otherwise, I'd suspect it is a problem with the 6.2 you are using then.  If 
you try with a boot within the 1024 (I wouldn't push that to the limit I'd say 
try like 950 cylinders) then I would try an earlier version such as 6.1 or 6.0.

 -Derek
 
--  
This message has been scanned for viruses and 
dangerous content by MailScanner, and is 
believed to be clean. 
MailScanner thanks transtec Computers for their support. 

 
-
It's here! Your new message!
Get new email alerts with the free Yahoo! Toolbar.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Boot failure after installation

2007-04-09 Thread Josh Paetzel
L Goodwin wrote:
 Hello. I tried posting this issue a few hours ago, but it did not appear in 
 my inbox, so I'm
 trying once more. I've included details of the install in case it matters 
 (sorry about length).
 
 I'm having trouble getting FreeBSD 6.2 to boot after installation. After a 
 successful install,
 (re-)boot always fails with DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS 
 ENTER.
 
 In order to boot the install CD on this machine, I have to disable ACPI by 
 selecting
 2. Boot FreeBSD with ACPI disabled from the boot loader menu (the AWARD 
 BIOS does not allow
 for disabling ACPI from the BIOS setup program).
 At the end of a successful install, the installer asks ACPI was disabled 
 during boot. 
 Would you like to disable it permanently?, to which I choose Yes.
 
 I am choosing to perform a Standard install.
 
 Here are my FDISK selections:
 
 Select Drive(s): da0 (first SCSI drive of 6 9GB drives)
 
 These are my selections in FDISK Partition Editor (before entering Q):
 --
 Disk name:da0FDISK Partition Editor
 DISK Geometry:1115 cyls/255 heads/63 sectors = 17912475 sectors (8746MB)
 
 OffsetSize(ST)EndNamePTypeDescSubtype
 Flags
 
 06362-12unused0
 631791241217912474da0s18freebsd165A
 17912475376517916239-12unused0
 --
 
 Install Boot Manager for drive da0?: Selected BootMgr (Install the FreeBSD 
 Boot Manager)
 Select Drive(s): da0 selected for Boot Manager (tab to OK, press ENTER).
 
 FreeBSD Disklabel Editor (create BSD Paritions): Select A (Auto Defaults)...
 --
 Disk: da0Partition name da0s1Free: 17912412 blocks (8746MB)
 
 PartMountSizeNewfsPartMountSizeNewfs
 ----
 da0s1a/512MBUFS2Y
 da0s1bswap486MBSWAP
 da0s1d/var1267MBUFS2+sY
 da0s1e/tmp512MBUFS2+sY
 da0s1f/usr5968MBUFS2+sY
 --
 ...then enter Q (Finish).
 
 Choose Distributions: Select A Minimal.
 Choose Installation Media: 1 CD/DVD (burned my own from FreeBSD-6.2-disk1 
 ISO image)
 All filesystem information written correctly...
 Distribution extracted successfully...
 Congratulations! You now have FreeBSD installed on your system (but can't 
 boot!).
 Final Configuration: No to most questions (configure later). Yes to these:
 Ethernet or SLIP/PPP network devices: fxp0 (Intel EtherExpress Pro/100B 
 PCI Fast Ethernet card
 IPv6 configuration of the interfaces?: No
 DHCP: No
 Bring up fxp0 interface right now?: Yes Failed (only entered hostname 
 --will complete later)
 Network gateway?: No
 inetd?: No
 SSH login?: Yes
 anonymous FTP?: No
 NFS server?: No
 NFS client?: No
 customize system console settings?: No
 machine's time zone?: Yes
 CMOS clock set to UTC?: No
 Region: 2 America -- North and South
 Country or Region: 45 United States
 Time zone: 19 Pacific Time (PDT)
 Linux binary compatibility?: No
 PS/2 mouse?: Yes (test OK)
 ACPI was disabled during boot. Would you like to diswable it 
 parmanently?: Yes
 Browse FreeBSD package collection?: No
 Add initial user accounts?: No
 set system manager's password: (done)
 Visit general configuration menu one more time?: No
 
 FreeBSD/i386 6.2-RELEASE - sysinstall Main Menu: Exit Install
 
 Last thing to print to screen:
 -
 Boot from ATAPI CD-ROM :  Failure ... 
 DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
 -
 
 The first message is expected, as there is no disk in the CD-ROM drive.
 If I set Boot Sequence to C only in BIOS setup, only the second message 
 appears.
 
 Am I doing something wrong here?
  

Just from the size of the drives I'm guessing this is older 
hardware.  Is the machine capable of booting from SCSI?  Is the scsi 
controller itself bootable?

-- 
Thanks,

Josh Paetzel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Boot failure after installation

2007-04-09 Thread Derek Ragona

At 12:56 AM 4/9/2007, L Goodwin wrote:
Hello. I tried posting this issue a few hours ago, but it did not appear 
in my inbox, so I'm
trying once more. I've included details of the install in case it matters 
(sorry about length).


I'm having trouble getting FreeBSD 6.2 to boot after installation. After a 
successful install,
(re-)boot always fails with DISK BOOT FAILURE, INSERT SYSTEM DISK AND 
PRESS ENTER.


In order to boot the install CD on this machine, I have to disable ACPI by 
selecting
2. Boot FreeBSD with ACPI disabled from the boot loader menu (the AWARD 
BIOS does not allow

for disabling ACPI from the BIOS setup program).
At the end of a successful install, the installer asks ACPI was 
disabled during boot.

Would you like to disable it permanently?, to which I choose Yes.

I am choosing to perform a Standard install.

Here are my FDISK selections:

Select Drive(s): da0 (first SCSI drive of 6 9GB drives)

These are my selections in FDISK Partition Editor (before entering Q):
--
Disk name:da0FDISK Partition Editor
DISK Geometry:1115 cyls/255 heads/63 sectors = 17912475 sectors (8746MB)

OffsetSize(ST)EndNamePTypeDescSubtype 
  Flags


06362-12unused0
631791241217912474da0s18freebsd165A
17912475376517916239-12unused0
--

Install Boot Manager for drive da0?: Selected BootMgr (Install the 
FreeBSD Boot Manager)

Select Drive(s): da0 selected for Boot Manager (tab to OK, press ENTER).

FreeBSD Disklabel Editor (create BSD Paritions): Select A (Auto Defaults)...
--
Disk: da0Partition name da0s1Free: 17912412 blocks (8746MB)

PartMountSizeNewfsPartMountSizeNewfs
----
da0s1a/512MBUFS2Y
da0s1bswap486MBSWAP
da0s1d/var1267MBUFS2+sY
da0s1e/tmp512MBUFS2+sY
da0s1f/usr5968MBUFS2+sY
--
...then enter Q (Finish).

Choose Distributions: Select A Minimal.
Choose Installation Media: 1 CD/DVD (burned my own from 
FreeBSD-6.2-disk1 ISO image)

All filesystem information written correctly...
Distribution extracted successfully...
Congratulations! You now have FreeBSD installed on your system (but 
can't boot!).

Final Configuration: No to most questions (configure later). Yes to these:
Ethernet or SLIP/PPP network devices: fxp0 (Intel EtherExpress 
Pro/100B PCI Fast Ethernet card

IPv6 configuration of the interfaces?: No
DHCP: No
Bring up fxp0 interface right now?: Yes Failed (only entered hostname 
--will complete later)

Network gateway?: No
inetd?: No
SSH login?: Yes
anonymous FTP?: No
NFS server?: No
NFS client?: No
customize system console settings?: No
machine's time zone?: Yes
CMOS clock set to UTC?: No
Region: 2 America -- North and South
Country or Region: 45 United States
Time zone: 19 Pacific Time (PDT)
Linux binary compatibility?: No
PS/2 mouse?: Yes (test OK)
ACPI was disabled during boot. Would you like to diswable it 
parmanently?: Yes

Browse FreeBSD package collection?: No
Add initial user accounts?: No
set system manager's password: (done)
Visit general configuration menu one more time?: No

FreeBSD/i386 6.2-RELEASE - sysinstall Main Menu: Exit Install

Last thing to print to screen:
-
Boot from ATAPI CD-ROM :  Failure ...
DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
-

The first message is expected, as there is no disk in the CD-ROM drive.
If I set Boot Sequence to C only in BIOS setup, only the second message 
appears.


Am I doing something wrong here?


Make sure your System BIOS is not set to not allow writing to the boot 
area, often this is called boot sector virus protection in some BIOS's.


Go into your SCSI BIOS and make sure it is set to be bootable and has the 
correct disk set for booting from.


-Derek

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL 

Re: Boot failure after installation

2007-04-09 Thread L Goodwin
Derek, Boot Virus Protection is Disabled in the BIOS.

How to I make sure my SCSI BIOS is set to be bootable and has the correct disk 
set for booting from? Please see my SCSI BIOS settings below and advise...
(I don't think this is the problem, as this machine was booting Windows 2000 
Server from same drive prior to repartioning and installing FreeBSD 6.2.
This machine has an ASUS P2B-D ACPI BIOS rev 1013 (AWARD BIOS, single Pentium 
III/550) with onboard Adaptec 7890 SCSI BIOS.)

My apologies for replying directly to those who took the time to respond. I'm 
used to working with forums that have list servers set up.

Thanks!

SCSI BIOS SETTINGS:

1) Host Adapter Settings:

Configuration

SCSI Bus Interface Definitions
Host Adapter SCSI ID: 7
SCSI Parity Checking: Enabled
Host Adapter SCSI Termination: Press Enter
Ultra2-LVD/SE Connector: Auto
Fast/Ultra-SE Connector: Enabled

Additional  Options
SCSI Device Configuration: Press Enter
Settings for SCSI Device #0 (identical for #1-15):
 
--
Initiate Sync Negotiation: yes
Maximum Transfer Rate: 80.0
Enable Disconnnection: yes
Initiate Wide Negotiation: yes
Send Start Unit Command: yes
Include in BIOS Scan: yes
 
--  
  
Array1000 BIOS: Enabled
BIOS Support for Bootable CD-ROM:  Enabled


2) SCSI Disk Utilities:

Select SCSI Disk and press Enter

SCSI ID #0:IBMDNES-309170WULTRA2-LVD
SCSI ID #1:IBMDNES-309170WULTRA2-LVD
SCSI ID #2:IBMDNES-309170WULTRA2-LVD
SCSI ID #3:IBMDNES-309170WULTRA2-LVD
SCSI ID #4:IBMDNES-309170WULTRA2-LVD
SCSI ID #5:ECRIXVXA-1Fast/Ultra-SE
SCSI ID #6:No  device
SCSI ID #7:Array1000 Family
SCSI ID #8:No device
SCSI ID #9:No device
SCSI ID #10:No device
SCSI ID #11:No device
SCSI ID #12:No device
SCSI ID #13:No device
SCSI ID #14:No device
SCSI ID #15:No device




Derek Ragona [EMAIL PROTECTED] wrote:   At 12:56 AM 4/9/2007, L Goodwin wrote:
 I'm having trouble getting FreeBSD 6.2 to  boot after installation. After a 
successful install,
 (re-)boot always fails with DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS 
ENTER.
Make sure your System BIOS is not set to not allow writing to the boot area, 
often this is called boot sector virus protection in some BIOS's.

 Go into your SCSI BIOS and make sure it is set to be bootable and has the 
correct disk set for booting from.

 
-
Bored stiff? Loosen up...
Download and play hundreds of games for free on Yahoo! Games.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Boot failure after installation

2007-04-09 Thread L Goodwin
Derek Ragona said:

 Go into the SCSI BIOS and reset the SCSI to default values.  
 If it still gives the same error on bootup, I would go into the SCSI BIOS and 
 low-level format that first drive, and reinstall FreeBSD.  
 On the reinstall, I would just do the partioning for that drive, and then 
 install everything.  
 That way it will run mostly by itself, you can just check on it for the last 
 few prompts of the 
 install finishing up.

Derek, I just did the following, expecting that this would fix the glitch:

1) Reset the SCSI BIOS to Host Adapter Defaults: Matches prior configuration 
exactly.
2) Run a low-level format on SCSI device #0: No errors.
3) Install FreeBSD 6.2 from scratch. Note: I answered Yes to the prompt
ACPI was disabled during boot. Would you like to disable it permanently?.
I don't think it will boot if I enable ACPI.
RESULT: FAIL - Still getting DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS 
ENTER

4) Ran Verify Disk Media on SCSI ID #0: Disk Verification Complete

What else could it possibly be? Are there any other diagnostics I can run?
What do you think of the fact that this machine was booting Windows 2000 from 
the same
SCSI drive prior to installing FreeBSD 6.2?

In case it matters, all SCSI drives are IBM DNES-309170W ULTRA2-LVD.

Thanks!

 
-
Now that's room service! Choose from over 150,000 hotels 
in 45,000 destinations on Yahoo! Travel to find your fit.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]