Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 6 May 2005 00:19:45 +0100
From:      "Alan Jay" <alan_jay_uk@yahoo.co.uk>
To:        <freebsd-questions@freebsd.org>
Subject:   Re: Disable loader.conf when booting? Can't boot because of it ..
Message-ID:  <20050505231948.C01C254860@buxton.digitalspy.co.uk>

next in thread | raw e-mail | index | archive | help
 

> On Thursday 31 March 2005 08:36 am, Daniel Johansson wrote:
> > Hi, I really need some help here. I'm running a raid0, with
> > vinum, and read the errata about adding geom_vinum_load="YES"
> > to loader.conf because vinim_start="YES" in rc.conf paniced my
> > system when booting. I'm running 5.3-RELEASE and the errata
> > mentioned that one too.
> >
> > So I added gvinum to loader.conf and now I can't boot. All I
> > get is a lot of scrolling text that says something about gvinum
> > error, can't remember the exact message but it can't boot
> > anyway. Tried single mode to delete this line but can't boot
> > into single mode either. Tried disable-module geom_vinum in the
> > loader but that didn't help either. It loaded the module
> > anyway.
> >
> > So I'm really desperate here .. is there any way to tell my
> > system to completly ignore loader.conf when booting so that I
> > at least can access the system and edit loader.conf?
> >
> > Please CC to me if you reply.
 
> I'm not sure if you can disable loader.conf during boot (would be 
> a cool thing to know, though).  The only thing I know to do is 
> boot from a live filesystem or from the install floppies and 
> ttyv2(?) to get a shell.  You can then mount your 
> slices/partitions and comment the vinum_start line out.
 
> HTH,
 
> WizLayer

 

Hi,

 

Anyone have any other ideas I colleague of mine added a line to
/boot/loader.conf

 

I rebooted today after changing one of the boot-time variables (maximum data
size) in /boot/loader.conf.  I took it from 512MB to 2GB of RAM in order to
improve the MySQL performance on the server.

 

However, upon reboot, the following error comes up:

 

Fatal trap 9: general protection fault while in kernel mode cpuid = 0; apic id
= 00

instruction pointer     = 0x58:0x8bc

stack pointer           = 0x10:0xf80

frame pointer           = 0x10:0x0

code segment            = base 0xc00f0000, limit 0xffff, type 0x1b

                        = DPL 0, pres 1, def32 0, gran 0

processor eflags        = interrupt enabled, resume, IOPL = 0

current process         = 0 (swapper)

trap number             = 9

panic: general protection fault

cpuid = 0

Uptime: 1s

 

1) I tried resetting kern.maxdsiz backto 512MB by pressing 6 at the boot menu
and doing:

      unset kern.maxdsiz

      set kern.maxdsiz=536870912

      show kern.maxdsiz

    - this did not have any effect.

2) The above error message is not similar to ones reported by other users who
set their maxdsiz too high.

 

I have subsequently also tried to overwrite from the loader the memory
variable to no effect I always get the above error and even going back to the
original generic kernel does not help.  We are running 5.4-RC4 on this
machine.  

 

Just to make things worse the machine is in a remote data center so getting in
a rebooting with a CD is possible but requires a long drive in :-)

 

Is there any way to unset the settings placed in the /boot/loader.conf while
in the interactive loader which is obviously loaded after /boot/loader.conf

 

I assume there is no way to overwrite the /boot/loader.conf with a nul file?

 

Any thoughts gratefully received.

 

ALan



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050505231948.C01C254860>