Re: no boot/loader

2008-08-08 Thread Derek Ragona

At 07:11 PM 8/8/2008, acmeinc wrote:


Excellent!  I will try this among the other things mentioned when I get back
home.

Final note, what would this BIOS MBR setting look like normally, or an idea
of where to look in the CMOS.

THanks


A lot of BIOS's have a setting for boot virus prevention, or it will just 
be to enable or disable the boot area being written.  Most BIOS's have just 
a few pages of settings, so look through them all.


-Derek





Derek Ragona wrote:
>
> At 07:00 PM 8/8/2008, acmeinc wrote:
>
>>Check things?  Which things should I be checking for?   And where should I
be
>>checking them, to be more specific, which optoin should I choose within
>>sysinstall to check the things?
>>
>>I am reading on another forum the installation is incorrect and to try
>>again, however I have tried many times.  Do you think the minimun install
is
>>not enough to allow for bootup?
>
> Before you exit sysinstall, go to the emergency shell I believe alt+F4
> will
> get you there.  Then do:
> mount
>
> The output from mount will show where the new filesystems are mounted.
> You
> can check that /boot is populated and that you have a kernel in
> /boot/kernel/kernel.  To check those you'd type:
>
> ls -al [fill in the root mount point]/boot
>
> and
>
> ls -al [fill in the root mount point]/boot/kernel/kernel
>
> Check your BIOS settings.  It is likely you have a setting in the BIOS
> preventing the boot area being written.
>
>  -Derek
>
>
>
>
>>Derek Ragona wrote:
>> >
>> > At 04:42 PM 8/8/2008, acmeinc wrote:
>> >
>> >>No /boot/loader
>> >>no /boot/kernel/kernel
>> >>
>> >>I isntalled FreeBSD 7.0 with the defaults for partiioning. I am using
>> one
>> >>hard drive in which I followed with the ASQ (auto, tag for boot, quit)
>> >>command. I choose the standard boot loader option. I installed through
>> the
>> >>master freebsd site via ethernet. Upon the congratulation screen is
>> asks
>>for
>> >>a reboot, and to remove the boot disk, I resart to the error message
>>above.
>> >>I believe it is because a boot loader is not installed, however, it
>> should
>> >>be. Is it not in the set up, it is one of the first steps.
>> >>
>> >>Following the errors I am in put into a boot prompt:
>> >>
>> >>boot:
>> >>
>> >>Are there any commands I can run from this prompt to manually boot? How
>>can
>> >>I make the boot work? Will I need to install my own boot loader? How
>> can I
>> >>install a manul boot loader? How can I check if the boot loader is
>> >>installed, but just not loading properly?
>> >
>> > You would do well do try the install again, but check things BEFORE you
>> > allow sysinstall to exit and reboot.  Also check that your BIOS has any
>> > anti-virus settings not allowing the boot area of the hard disk to be
>> > written, turned off.
>> >
>> >  -Derek
>> >
>> > --
>> > This message has been scanned for viruses and
>> > dangerous content by MailScanner, and is
>> > believed to be clean.
>> >
>> > ___
>> > freebsd-questions@freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> > To unsubscribe, send any mail to
>> > "[EMAIL PROTECTED]"
>> >
>> >
>>
>>--
>>View this message in context:
>>http://www.nabble.com/no-boot-loader-tp18899421p18900779.html
>>Sent from the freebsd-questions mailing list archive at Nabble.com.
>>
>>___
>>freebsd-questions@freebsd.org mailing list
>>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
>>
>>--
>>This message has been scanned for viruses and
>>dangerous content by MailScanner, and is
>>believed to be clean.
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
>
>

--
View this message in context: 
http://www.nabble.com/no-boot-loader-tp18899421p18900844.html

Sent from the freebsd-questions mailing list archive at Nabble.com.

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

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


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

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


Re: no boot/loader

2008-08-08 Thread Polytropon
On Fri, 8 Aug 2008 17:00:54 -0700 (PDT), acmeinc <[EMAIL PROTECTED]> wrote:
> Check things?  Which things should I be checking for?   And where should I be
> checking them, to be more specific, which optoin should I choose within
> sysinstall to check the things?  

Be sure to write your settings. In the partition editor, make
sure your desired FreeBSD slice is marked "active" and ensure
you have selected to install the standard MBR loader. (If you
want to be able to boot into more than one OS, you need to
install the boot manager.) Afterwards, when creating the
partitions within the slice, I assume you've done everything
correctly, else no installation success would be able to
happen.



> I am reading on another forum the installation is incorrect and to try
> again, however I have tried many times.

There seems to be something you've missed, but at this point,
I can't guess what it could be.



> Do you think the minimun install is
> not enough to allow for bootup?

It is, if done correctly.

To boot, a correct modification of the boot record is essential.
As it has been mentioned, there are some BIOS variants that
prohibit any modification of these hard disk areas. But that
does not seem to be the problem. The message you gave seems to
indicat that something is already in the boot area, but the
loader itself cannot be run. The loader is placed into your
FreeBSD slice (partition), it resides in /boot; if started,
the loader invokes the kernel from /boot/kernel, but that's
to be happing after you could solve the problem in question.

This is what yould happen, summarized:

1. BIOS runs loader found in MBR (standard loader)
2. Standard loader runs /boot/loader
3. /boot/loader runs /boot/kernel/kernel (GENERIC)
4. Kernel initializes system, runs rc script
5. rc script controls system startup
6. System is up and running

While number 1 is connected to the hard disk "infront of" any
partitions, numbers 2 and 3 depend on the FreeBSD's slice and
its partitions (usually /dev/ad0s1a). If the required content
of this partition is not present, the error you mentioned is
completely understandable.


-- 
Polytropon
>From Magdeburg, Germany
Happy FreeBSD user since 4.0
Andra moi ennepe, Mousa, ...
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"


Re: no boot/loader

2008-08-08 Thread acmeinc

Excellent!  I will try this among the other things mentioned when I get back
home.

Final note, what would this BIOS MBR setting look like normally, or an idea
of where to look in the CMOS.

THanks


Derek Ragona wrote:
> 
> At 07:00 PM 8/8/2008, acmeinc wrote:
> 
>>Check things?  Which things should I be checking for?   And where should I
be
>>checking them, to be more specific, which optoin should I choose within
>>sysinstall to check the things?
>>
>>I am reading on another forum the installation is incorrect and to try
>>again, however I have tried many times.  Do you think the minimun install
is
>>not enough to allow for bootup?
> 
> Before you exit sysinstall, go to the emergency shell I believe alt+F4
> will 
> get you there.  Then do:
> mount
> 
> The output from mount will show where the new filesystems are mounted. 
> You 
> can check that /boot is populated and that you have a kernel in 
> /boot/kernel/kernel.  To check those you'd type:
> 
> ls -al [fill in the root mount point]/boot
> 
> and
> 
> ls -al [fill in the root mount point]/boot/kernel/kernel
> 
> Check your BIOS settings.  It is likely you have a setting in the BIOS 
> preventing the boot area being written.
> 
>  -Derek
> 
> 
> 
> 
>>Derek Ragona wrote:
>> >
>> > At 04:42 PM 8/8/2008, acmeinc wrote:
>> >
>> >>No /boot/loader
>> >>no /boot/kernel/kernel
>> >>
>> >>I isntalled FreeBSD 7.0 with the defaults for partiioning. I am using
>> one
>> >>hard drive in which I followed with the ASQ (auto, tag for boot, quit)
>> >>command. I choose the standard boot loader option. I installed through
>> the
>> >>master freebsd site via ethernet. Upon the congratulation screen is
>> asks
>>for
>> >>a reboot, and to remove the boot disk, I resart to the error message
>>above.
>> >>I believe it is because a boot loader is not installed, however, it
>> should
>> >>be. Is it not in the set up, it is one of the first steps.
>> >>
>> >>Following the errors I am in put into a boot prompt:
>> >>
>> >>boot:
>> >>
>> >>Are there any commands I can run from this prompt to manually boot? How
>>can
>> >>I make the boot work? Will I need to install my own boot loader? How
>> can I
>> >>install a manul boot loader? How can I check if the boot loader is
>> >>installed, but just not loading properly?
>> >
>> > You would do well do try the install again, but check things BEFORE you
>> > allow sysinstall to exit and reboot.  Also check that your BIOS has any
>> > anti-virus settings not allowing the boot area of the hard disk to be
>> > written, turned off.
>> >
>> >  -Derek
>> >
>> > --
>> > This message has been scanned for viruses and
>> > dangerous content by MailScanner, and is
>> > believed to be clean.
>> >
>> > ___
>> > freebsd-questions@freebsd.org mailing list
>> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> > To unsubscribe, send any mail to
>> > "[EMAIL PROTECTED]"
>> >
>> >
>>
>>--
>>View this message in context: 
>>http://www.nabble.com/no-boot-loader-tp18899421p18900779.html
>>Sent from the freebsd-questions mailing list archive at Nabble.com.
>>
>>___
>>freebsd-questions@freebsd.org mailing list
>>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
>>
>>--
>>This message has been scanned for viruses and
>>dangerous content by MailScanner, and is
>>believed to be clean.
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
> 
> 

-- 
View this message in context: 
http://www.nabble.com/no-boot-loader-tp18899421p18900844.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

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


Re: no boot/loader

2008-08-08 Thread Derek Ragona

At 07:00 PM 8/8/2008, acmeinc wrote:


Check things?  Which things should I be checking for?   And where should I be
checking them, to be more specific, which optoin should I choose within
sysinstall to check the things?

I am reading on another forum the installation is incorrect and to try
again, however I have tried many times.  Do you think the minimun install is
not enough to allow for bootup?


Before you exit sysinstall, go to the emergency shell I believe alt+F4 will 
get you there.  Then do:

mount

The output from mount will show where the new filesystems are mounted.  You 
can check that /boot is populated and that you have a kernel in 
/boot/kernel/kernel.  To check those you'd type:


ls -al [fill in the root mount point]/boot

and

ls -al [fill in the root mount point]/boot/kernel/kernel

Check your BIOS settings.  It is likely you have a setting in the BIOS 
preventing the boot area being written.


-Derek





Derek Ragona wrote:
>
> At 04:42 PM 8/8/2008, acmeinc wrote:
>
>>No /boot/loader
>>no /boot/kernel/kernel
>>
>>I isntalled FreeBSD 7.0 with the defaults for partiioning. I am using one
>>hard drive in which I followed with the ASQ (auto, tag for boot, quit)
>>command. I choose the standard boot loader option. I installed through the
>>master freebsd site via ethernet. Upon the congratulation screen is asks
for
>>a reboot, and to remove the boot disk, I resart to the error message
above.
>>I believe it is because a boot loader is not installed, however, it should
>>be. Is it not in the set up, it is one of the first steps.
>>
>>Following the errors I am in put into a boot prompt:
>>
>>boot:
>>
>>Are there any commands I can run from this prompt to manually boot? How
can
>>I make the boot work? Will I need to install my own boot loader? How can I
>>install a manul boot loader? How can I check if the boot loader is
>>installed, but just not loading properly?
>
> You would do well do try the install again, but check things BEFORE you
> allow sysinstall to exit and reboot.  Also check that your BIOS has any
> anti-virus settings not allowing the boot area of the hard disk to be
> written, turned off.
>
>  -Derek
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
>
>

--
View this message in context: 
http://www.nabble.com/no-boot-loader-tp18899421p18900779.html

Sent from the freebsd-questions mailing list archive at Nabble.com.

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

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


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

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


Re: no boot/loader

2008-08-08 Thread acmeinc

Check things?  Which things should I be checking for?   And where should I be
checking them, to be more specific, which optoin should I choose within
sysinstall to check the things?  

I am reading on another forum the installation is incorrect and to try
again, however I have tried many times.  Do you think the minimun install is
not enough to allow for bootup?


Derek Ragona wrote:
> 
> At 04:42 PM 8/8/2008, acmeinc wrote:
> 
>>No /boot/loader
>>no /boot/kernel/kernel
>>
>>I isntalled FreeBSD 7.0 with the defaults for partiioning. I am using one
>>hard drive in which I followed with the ASQ (auto, tag for boot, quit)
>>command. I choose the standard boot loader option. I installed through the
>>master freebsd site via ethernet. Upon the congratulation screen is asks
for
>>a reboot, and to remove the boot disk, I resart to the error message
above.
>>I believe it is because a boot loader is not installed, however, it should
>>be. Is it not in the set up, it is one of the first steps.
>>
>>Following the errors I am in put into a boot prompt:
>>
>>boot:
>>
>>Are there any commands I can run from this prompt to manually boot? How
can
>>I make the boot work? Will I need to install my own boot loader? How can I
>>install a manul boot loader? How can I check if the boot loader is
>>installed, but just not loading properly?
> 
> You would do well do try the install again, but check things BEFORE you 
> allow sysinstall to exit and reboot.  Also check that your BIOS has any 
> anti-virus settings not allowing the boot area of the hard disk to be 
> written, turned off.
> 
>  -Derek
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 
> ___
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to
> "[EMAIL PROTECTED]"
> 
> 

-- 
View this message in context: 
http://www.nabble.com/no-boot-loader-tp18899421p18900779.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

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


Re: no boot/loader

2008-08-08 Thread Derek Ragona

At 04:42 PM 8/8/2008, acmeinc wrote:


No /boot/loader
no /boot/kernel/kernel

I isntalled FreeBSD 7.0 with the defaults for partiioning. I am using one
hard drive in which I followed with the ASQ (auto, tag for boot, quit)
command. I choose the standard boot loader option. I installed through the
master freebsd site via ethernet. Upon the congratulation screen is asks for
a reboot, and to remove the boot disk, I resart to the error message above.
I believe it is because a boot loader is not installed, however, it should
be. Is it not in the set up, it is one of the first steps.

Following the errors I am in put into a boot prompt:

boot:

Are there any commands I can run from this prompt to manually boot? How can
I make the boot work? Will I need to install my own boot loader? How can I
install a manul boot loader? How can I check if the boot loader is
installed, but just not loading properly?


You would do well do try the install again, but check things BEFORE you 
allow sysinstall to exit and reboot.  Also check that your BIOS has any 
anti-virus settings not allowing the boot area of the hard disk to be 
written, turned off.


-Derek

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

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


no boot/loader

2008-08-08 Thread acmeinc

No /boot/loader
no /boot/kernel/kernel

I isntalled FreeBSD 7.0 with the defaults for partiioning. I am using one
hard drive in which I followed with the ASQ (auto, tag for boot, quit)
command. I choose the standard boot loader option. I installed through the
master freebsd site via ethernet. Upon the congratulation screen is asks for
a reboot, and to remove the boot disk, I resart to the error message above.
I believe it is because a boot loader is not installed, however, it should
be. Is it not in the set up, it is one of the first steps.

Following the errors I am in put into a boot prompt:

boot:

Are there any commands I can run from this prompt to manually boot? How can
I make the boot work? Will I need to install my own boot loader? How can I
install a manul boot loader? How can I check if the boot loader is
installed, but just not loading properly?
-- 
View this message in context: 
http://www.nabble.com/no-boot-loader-tp18899421p18899421.html
Sent from the freebsd-questions mailing list archive at Nabble.com.

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


No /boot/loader

2007-11-21 Thread Amarendra Godbole
Hi,

I installed FreeBSD 7.0-current snapshot [200710] on my laptop. I have
two issues,
of which second is major:
1. It could not find any X filesets
2. After rebooting, it tells me something like "No /boot/loader", and
does not boot.

I tried to google for #2, but found no solution. I am surely making a
mistake somewhere,
but am unable to figure out. Any help regarding this is much
appreciated. Thanks!

This laptop already had a FreeBSD slice, so I did no create new
partitions inside it,
but just mounted and formatted the existing ones.

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


Re: no /boot/loader - after installation

2007-07-23 Thread Derek Ragona

At 02:06 PM 7/23/2007, John Clement wrote:

So I got a copy of boot-only 6.2 onto cd and went back into the bios and
changed a few options:

LBA mode: off
Multi-sector transfers: auto
Fast PIO: auto
32 bit transfer mode: on
Ultra DMA: auto

then ran the 6.2 install using dangerously dedicated which went fine and
then on reboot now it comes up with

Not ufs
no /boot/loader

so a slightly different message now, but still no go

anyone? - jc


I've never used the boot-only version.  So let me ask if you saw any issues 
with sysinstall?  Did you partition the disk and did newfs run without error?


Before you exit sysinstall you can check and see what is on the disks from 
the emergency shell on vtty4.  You can do a mount command and see what and 
where things are mounted and do an ls on those filesystems.


-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: no /boot/loader - after installation

2007-07-23 Thread John Clement

So I got a copy of boot-only 6.2 onto cd and went back into the bios and
changed a few options:

LBA mode: off
Multi-sector transfers: auto
Fast PIO: auto
32 bit transfer mode: on
Ultra DMA: auto

then ran the 6.2 install using dangerously dedicated which went fine and
then on reboot now it comes up with

Not ufs
no /boot/loader

so a slightly different message now, but still no go

anyone? - jc


On 20/07/07, John Clement <[EMAIL PROTECTED]> wrote:


The burner's been playing up recently so I've just been using the copy of
6.1 I've got.  Maybe I'll get a copy of 6.2 burnt at work to try after the
weekend.

The locked MBR hadn't occured to me, but having checked, unfortunately it
wasn't that.  So back to the drawing board.  If anyone's got any other idea,
I'de love to hear them!

cheers -jc

On 19/07/07, Derek Ragona <[EMAIL PROTECTED]> wrote:
>
>  At 03:31 AM 7/19/2007, John Clement wrote:
>
> I'm installing 6.1 on an HP Vectra VL420, I've been in the BIOS to set
> the
> C/H/S as per what the install reports (I've tried an 80GB Seagate and a
> 250GB WD), the install all seems to go fine.  I've tried the FreeBSD
> boot
> manager, a standard MBR and even setting the disk as dedicated, but
> regardless I end up with the same 'no /boot/loader' when it reboots.
>
> I suspect (and hope) I'm making a simple mistake, I just haven't seen
> this
> happen before.
>
> Thanks in advance!!
>
>
> First you should try 6.2 which is the latest release.
>
> Check your BIOS that you are allowing to write to the boot area.  Many
> BIOS have a setting to not allow this to prevent a virus writing to the boot
> area.
>
> -Derek
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and
> is
> believed to be clean.
> MailScanner thanks transtec Computers <http://www.transtec.co.uk/> 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: no /boot/loader - after installation

2007-07-19 Thread John Clement

The burner's been playing up recently so I've just been using the copy of
6.1 I've got.  Maybe I'll get a copy of 6.2 burnt at work to try after the
weekend.

The locked MBR hadn't occured to me, but having checked, unfortunately it
wasn't that.  So back to the drawing board.  If anyone's got any other idea,
I'de love to hear them!

cheers -jc

On 19/07/07, Derek Ragona <[EMAIL PROTECTED]> wrote:


 At 03:31 AM 7/19/2007, John Clement wrote:

I'm installing 6.1 on an HP Vectra VL420, I've been in the BIOS to set the
C/H/S as per what the install reports (I've tried an 80GB Seagate and a
250GB WD), the install all seems to go fine.  I've tried the FreeBSD boot
manager, a standard MBR and even setting the disk as dedicated, but
regardless I end up with the same 'no /boot/loader' when it reboots.

I suspect (and hope) I'm making a simple mistake, I just haven't seen this
happen before.

Thanks in advance!!


First you should try 6.2 which is the latest release.

Check your BIOS that you are allowing to write to the boot area.  Many
BIOS have a setting to not allow this to prevent a virus writing to the boot
area.

-Derek

--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
MailScanner thanks transtec Computers <http://www.transtec.co.uk/> 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: no /boot/loader - after installation

2007-07-19 Thread Derek Ragona

At 03:31 AM 7/19/2007, John Clement wrote:

I'm installing 6.1 on an HP Vectra VL420, I've been in the BIOS to set the
C/H/S as per what the install reports (I've tried an 80GB Seagate and a
250GB WD), the install all seems to go fine.  I've tried the FreeBSD boot
manager, a standard MBR and even setting the disk as dedicated, but
regardless I end up with the same 'no /boot/loader' when it reboots.

I suspect (and hope) I'm making a simple mistake, I just haven't seen this
happen before.

Thanks in advance!!


First you should try 6.2 which is the latest release.

Check your BIOS that you are allowing to write to the boot area.  Many BIOS 
have a setting to not allow this to prevent a virus writing to the boot area.


-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]"


no /boot/loader - after installation

2007-07-19 Thread John Clement

I'm installing 6.1 on an HP Vectra VL420, I've been in the BIOS to set the
C/H/S as per what the install reports (I've tried an 80GB Seagate and a
250GB WD), the install all seems to go fine.  I've tried the FreeBSD boot
manager, a standard MBR and even setting the disk as dedicated, but
regardless I end up with the same 'no /boot/loader' when it reboots.

I suspect (and hope) I'm making a simple mistake, I just haven't seen this
happen before.

Thanks in advance!!

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


no /boot/loader error 16

2005-05-08 Thread Ben Haysom
hi

I have an AMD Duron 700Mhz running FreeBSD 5.3.

When I turn it on I get

error 16 lba 287
error 16 lba 287
No /boot/loader

I've found:

http://lists.freebsd.org/pipermail/freebsd-questions/2005-March/081879.html

but the instructions don't do  anything.

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


Re: No /boot/loader

2004-06-14 Thread freebsd
Hi all.

A little over a month ago I posted the following:

> I just installed 4.9 on a 8 x 4.3GB SCSI disk AMI MegaRAID array (RAID 5,
> 30GB).  The card's a HP NetRAID (aka AMI/LSI Enterprise 1200 or Series
> 428).  I set up slices as I have previously with 30GB+ IDE drives:
>
>  1GBswap
> 29GB/
>
> Fdisk, label and the rest of install went fine, but on reboot I get the
> following error:
>
> Disk error 0x1 (lba=0x21fc09f)
> No /boot/loader
>
>>> FreeBSD/i386 BOOT
> Default: 0:ad(0,a)/kernel
> boot:
>
>
> If I hit enter, it spits out this error:
>
>
> WARNING: loader(8) metadata is missing!
>
>
> and starts the boot process.  After finding all the devices, including the
> RAID controller (amr0) and the logical drive (amrd0), it displays a
> 'mountroot>' prompt.  If I give it the logical drive slice a:
> (ufs:/dev/amrd0s1a) it finishes the boot.

Over the last few days I've added some new drives in RAID0 configuration
and installed 4.10-RELEASE, and had the identical problem.

I got around the problem by doing two things:

1.  Created a /boot.config containing "0:da(0,a)/kernel"

After doing this, the boot2 stopped complaining about a missing /boot/loader.

2.  Built a new kernel and defined ROOTDEVNAME=\"ufs:amrd0s1a\"

Now I'm no longer prompted to specify the root slice.

So things are good.  My machine boots w/out interaction.

But I'm still perplexed as to why it didn't before.  If boot2 can find
/kernel, why can't it find /boot/loader?

I copied /boot/loader to / and changed /boot.config to '0:da(0,a)/loader'
and whaddya know?  It now runs the BTX loader properly.

So what's going on?  Can anyone answer this stumper?

Thanks again,

Brad

(CC me please, I'm not subbed)

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