Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
The only thing that I can think of is try mounting the slice then cd to the /boot/kernel dir and gzip -9 kernel.gz Then reboot and see if it finds the kernel.We are still not sure why this happens but it doesn't seem to happen when you install from a 0.80+ iso and then upgrade. Scott On 9/15/05, Xtian <[EMAIL PROTECTED]> wrote: > > Howdy pfSensers, > > I've been running 0.70.8 just fine on a normal PC with 3Com NICs for months > now. I did the 0.80.4 > Upgrade and rebooted the box and I get: > > (bootloader loads fine, fives me the option of "F1 FreeBSD" and then duly > loads): > > Can't work out which disk we are booting from. > Guessed BIOS device 0x not found by probes, defaulting to disk0: > > can't load 'kernel' > > lsdev: > disk devices: > disk0: BIOS drive A: > disk1: BIOS drive C: > > Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and > everything looks fine in the > filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. > > So I don't know what happened. > > I am a Linux guy, so I don't enough to figure out what FreeBSD decided to > magically not find my drive > anymore. The Hardware must be okay, or else I wouldn't have been able to > mount it from the Live CD. > > Any ideas? > > Many thanks, > > Christian > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
Hi, this is exactly the problem I expericed a few days ago. See my message http://www.mail-archive.com/support@pfsense.com/msg01022.html It could be that the /boot/loader.rc is corrupted. Please have a look at it and, if appropriate, grep out the non-empty lines into a new loader.rc in order to make it boot again. Oliver -Original Message- From: Xtian [mailto:[EMAIL PROTECTED] Sent: September 15, 2005 4:54 PM Cc: support@pfsense.com Subject: [pfSense Support] Upgrade to 80.4 causes problems finding kernel Howdy pfSensers, I've been running 0.70.8 just fine on a normal PC with 3Com NICs for months now. I did the 0.80.4 Upgrade and rebooted the box and I get: (bootloader loads fine, fives me the option of "F1 FreeBSD" and then duly loads): Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' lsdev: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and everything looks fine in the filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. So I don't know what happened. I am a Linux guy, so I don't enough to figure out what FreeBSD decided to magically not find my drive anymore. The Hardware must be okay, or else I wouldn't have been able to mount it from the Live CD. Any ideas? Many thanks, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
Howdy, yeah, this seems to be it. Booted from LiveCD, mounted drive: # pwd /mnt/moo/boot # grep -v '^$' loader.rc > loader.rc.new # ls -l loader.rc* -r--r--r-- 1 root wheel 7504 Sep 10 17:41 loader.rc -rw-r--r-- 1 root wheel 346 Sep 15 22:17 loader.rc.new Copying the "new" file over the old one and rebooting took care of the boot up issue. Thanks! -C On Thu, 15 Sep 2005, Oliver Stark wrote: Hi, this is exactly the problem I expericed a few days ago. See my message http://www.mail-archive.com/support@pfsense.com/msg01022.html It could be that the /boot/loader.rc is corrupted. Please have a look at it and, if appropriate, grep out the non-empty lines into a new loader.rc in order to make it boot again. Oliver -Original Message- From: Xtian [mailto:[EMAIL PROTECTED] Sent: September 15, 2005 4:54 PM Cc: support@pfsense.com Subject: [pfSense Support] Upgrade to 80.4 causes problems finding kernel Howdy pfSensers, I've been running 0.70.8 just fine on a normal PC with 3Com NICs for months now. I did the 0.80.4 Upgrade and rebooted the box and I get: (bootloader loads fine, fives me the option of "F1 FreeBSD" and then duly loads): Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' lsdev: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and everything looks fine in the filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. So I don't know what happened. I am a Linux guy, so I don't enough to figure out what FreeBSD decided to magically not find my drive anymore. The Hardware must be okay, or else I wouldn't have been able to mount it from the Live CD. Any ideas? Many thanks, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- devo dot com - "Where the future is only a memory." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
Just reporting, this problem happen to me too. At first I installed version 74 and upgrading to 80.x After 6 days, i try to reboot it, and reported kernel not found. Cause it is on production network, i do not have time to trace. So i just re-installed the iso i had (v 74) and reconfuguring it all manually. I tried the configuration.xml I downloaded 1 day before, it could not work. After all work properly, I upgraded it to 83.2 and now the /boot/loader.rc is in size 784 i just tried: # grep -v '^$' loader.rc > loader.rc.new and have loader.rc.new is in size 346 So I think it is dangerous to reboot the gateway right now, unless the problem is well known to be solved. Xtian wrote: Howdy, yeah, this seems to be it. Booted from LiveCD, mounted drive: # pwd /mnt/moo/boot # grep -v '^$' loader.rc > loader.rc.new # ls -l loader.rc* -r--r--r-- 1 root wheel 7504 Sep 10 17:41 loader.rc -rw-r--r-- 1 root wheel 346 Sep 15 22:17 loader.rc.new Copying the "new" file over the old one and rebooting took care of the boot up issue. Thanks! -C On Thu, 15 Sep 2005, Oliver Stark wrote: Hi, this is exactly the problem I expericed a few days ago. See my message http://www.mail-archive.com/support@pfsense.com/msg01022.html It could be that the /boot/loader.rc is corrupted. Please have a look at it and, if appropriate, grep out the non-empty lines into a new loader.rc in order to make it boot again. Oliver -Original Message- From: Xtian [mailto:[EMAIL PROTECTED] Sent: September 15, 2005 4:54 PM Cc: support@pfsense.com Subject: [pfSense Support] Upgrade to 80.4 causes problems finding kernel Howdy pfSensers, I've been running 0.70.8 just fine on a normal PC with 3Com NICs for months now. I did the 0.80.4 Upgrade and rebooted the box and I get: (bootloader loads fine, fives me the option of "F1 FreeBSD" and then duly loads): Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' lsdev: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and everything looks fine in the filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. So I don't know what happened. I am a Linux guy, so I don't enough to figure out what FreeBSD decided to magically not find my drive anymore. The Hardware must be okay, or else I wouldn't have been able to mount it from the Live CD. Any ideas? Many thanks, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
Hi, I can only confirm that having stripped out the blank lines from loader.rc took care of the boot issue, exactly as it was described by the previous poster. Cheers, -C PS. I forget to say this now and then, but as always: pfSense is a really great piece of software! Yay for good stuff!! =) On Fri, 16 Sep 2005, Paulus Edwin Prasetya wrote: Just reporting, this problem happen to me too. At first I installed version 74 and upgrading to 80.x After 6 days, i try to reboot it, and reported kernel not found. Cause it is on production network, i do not have time to trace. So i just re-installed the iso i had (v 74) and reconfuguring it all manually. I tried the configuration.xml I downloaded 1 day before, it could not work. After all work properly, I upgraded it to 83.2 and now the /boot/loader.rc is in size 784 i just tried: # grep -v '^$' loader.rc > loader.rc.new and have loader.rc.new is in size 346 So I think it is dangerous to reboot the gateway right now, unless the problem is well known to be solved. Xtian wrote: Howdy, yeah, this seems to be it. Booted from LiveCD, mounted drive: # pwd /mnt/moo/boot # grep -v '^$' loader.rc > loader.rc.new # ls -l loader.rc* -r--r--r-- 1 root wheel 7504 Sep 10 17:41 loader.rc -rw-r--r-- 1 root wheel 346 Sep 15 22:17 loader.rc.new Copying the "new" file over the old one and rebooting took care of the boot up issue. Thanks! -C On Thu, 15 Sep 2005, Oliver Stark wrote: Hi, this is exactly the problem I expericed a few days ago. See my message http://www.mail-archive.com/support@pfsense.com/msg01022.html It could be that the /boot/loader.rc is corrupted. Please have a look at it and, if appropriate, grep out the non-empty lines into a new loader.rc in order to make it boot again. Oliver -Original Message- From: Xtian [mailto:[EMAIL PROTECTED] Sent: September 15, 2005 4:54 PM Cc: support@pfsense.com Subject: [pfSense Support] Upgrade to 80.4 causes problems finding kernel Howdy pfSensers, I've been running 0.70.8 just fine on a normal PC with 3Com NICs for months now. I did the 0.80.4 Upgrade and rebooted the box and I get: (bootloader loads fine, fives me the option of "F1 FreeBSD" and then duly loads): Can't work out which disk we are booting from. Guessed BIOS device 0x not found by probes, defaulting to disk0: can't load 'kernel' lsdev: disk devices: disk0: BIOS drive A: disk1: BIOS drive C: Hmm... booting from the Live CD (0.70.8) I am able to mount /dev/ad0s1a and everything looks fine in the filesystem. Kernel is there in /boot/kernel/kernel.gz and all that. So I don't know what happened. I am a Linux guy, so I don't enough to figure out what FreeBSD decided to magically not find my drive anymore. The Hardware must be okay, or else I wouldn't have been able to mount it from the Live CD. Any ideas? Many thanks, Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- devo dot com - "Where the future is only a memory." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
There seems to be definitely a glitch in the upgrade procedure, at least on the older versions. Blank lines are inserted in the loader.rc making it grow above a size where the loader cannot handle it any more. I guess, with a file size of 784 bytes, you should be below this limit (Christian's loader.rc was over 7kb, mine was over 14kb). Anyway, stripping out the blank lines shouldn't cause you any harm. It might also be interesting that people with recent installs have a look at their loader.rc just after upgrades to make sure that the newer versions don't behave the same way. Oliver -Original Message- From: Paulus Edwin Prasetya [mailto:[EMAIL PROTECTED] Sent: September 16, 2005 1:07 AM To: support@pfsense.com Subject: Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel Just reporting, this problem happen to me too. At first I installed version 74 and upgrading to 80.x After 6 days, i try to reboot it, and reported kernel not found. Cause it is on production network, i do not have time to trace. So i just re-installed the iso i had (v 74) and reconfuguring it all manually. I tried the configuration.xml I downloaded 1 day before, it could not work. After all work properly, I upgraded it to 83.2 and now the /boot/loader.rc is in size 784 i just tried: # grep -v '^$' loader.rc > loader.rc.new and have loader.rc.new is in size 346 So I think it is dangerous to reboot the gateway right now, unless the problem is well known to be solved. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
These problems should be fixed on newer versions. I think the danger still is present when you upgrade from 0.70<. Scott On 9/16/05, Oliver Stark <[EMAIL PROTECTED]> wrote: > There seems to be definitely a glitch in the upgrade procedure, at least on > the older versions. Blank lines are inserted in the loader.rc making it grow > above a size where the loader cannot handle it any more. I guess, with a > file size of 784 bytes, you should be below this limit (Christian's > loader.rc was over 7kb, mine was over 14kb). Anyway, stripping out the blank > lines shouldn't cause you any harm. > > It might also be interesting that people with recent installs have a look at > their loader.rc just after upgrades to make sure that the newer versions > don't behave the same way. > > Oliver > > -Original Message- > From: Paulus Edwin Prasetya [mailto:[EMAIL PROTECTED] > Sent: September 16, 2005 1:07 AM > To: support@pfsense.com > Subject: Re: [pfSense Support] Upgrade to 80.4 causes problems finding > kernel > > > Just reporting, this problem happen to me too. > > At first I installed version 74 and upgrading to 80.x > After 6 days, i try to reboot it, and reported kernel not found. > > Cause it is on production network, i do not have time to trace. > So i just re-installed the iso i had (v 74) and reconfuguring it > all manually. > I tried the configuration.xml I downloaded 1 day before, > it could not work. > > After all work properly, I upgraded it to 83.2 > and now the /boot/loader.rc is in size 784 > > i just tried: > # grep -v '^$' loader.rc > loader.rc.new > and have loader.rc.new is in size 346 > > So I think it is dangerous to reboot the gateway right now, > unless the problem is well known to be solved. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
Scott, My system was installed from scratch as 0.79.4 or 0.80. I don't remember the exact release but I installed it from CD by the very end of August. Than I upgraded to 0.82.4 and finally to 0.84. This is the 0.84 upgrade that broke my boot up. The .70< estimate doesn't seem to fit my case... Oliver -Original Message- From: Scott Ullrich [mailto:[EMAIL PROTECTED] Sent: September 16, 2005 10:40 AM To: support@pfsense.com Subject: Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel These problems should be fixed on newer versions. I think the danger still is present when you upgrade from 0.70<. Scott On 9/16/05, Oliver Stark <[EMAIL PROTECTED]> wrote: > There seems to be definitely a glitch in the upgrade procedure, at least on > the older versions. Blank lines are inserted in the loader.rc making it grow > above a size where the loader cannot handle it any more. I guess, with a > file size of 784 bytes, you should be below this limit (Christian's > loader.rc was over 7kb, mine was over 14kb). Anyway, stripping out the blank > lines shouldn't cause you any harm. > > It might also be interesting that people with recent installs have a look at > their loader.rc just after upgrades to make sure that the newer versions > don't behave the same way. > > Oliver - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
At 04:24 PM 9/16/2005, you wrote: Scott, My system was installed from scratch as 0.79.4 or 0.80. I don't remember the exact release but I installed it from CD by the very end of August. Than I upgraded to 0.82.4 and finally to 0.84. This is the 0.84 upgrade that broke my boot up. The .70< estimate doesn't seem to fit my case... I had a similar occurence. I think it might have been a 0.79. I did a fresh install from 0.82 I think and it never came back. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
Sorry, I meant 0.79. There was a race condition on shutdown that we corrected. Scott On 9/16/05, Dan Swartzendruber <[EMAIL PROTECTED]> wrote: > At 04:24 PM 9/16/2005, you wrote: > >Scott, > > > >My system was installed from scratch as 0.79.4 or 0.80. I don't remember the > >exact release but I installed it from CD by the very end of August. Than I > >upgraded to 0.82.4 and finally to 0.84. This is the 0.84 upgrade that broke > >my boot up. The .70< estimate doesn't seem to fit my case... > > I had a similar occurence. I think it might have been a 0.79. I did > a fresh install from 0.82 I think and it never came back. > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] Upgrade to 80.4 causes problems finding kernel
Alright, we just reproduced this problem in house (one of the devs). However, I'm still not sure whats causing it, but I do have a workaround that should prevent this from happening again. Everyone if you can go to a shell (option 8, and issue): chmod a-w /boot/loader.rc chflags schg /boot/loader.rc If the file gets trashed again then we have some type of MAJOR kernel issue going on. Scott On 9/16/05, Scott Ullrich <[EMAIL PROTECTED]> wrote: > Sorry, I meant 0.79. There was a race condition on shutdown that we > corrected. > > Scott > > On 9/16/05, Dan Swartzendruber <[EMAIL PROTECTED]> wrote: > > At 04:24 PM 9/16/2005, you wrote: > > >Scott, > > > > > >My system was installed from scratch as 0.79.4 or 0.80. I don't remember > > >the > > >exact release but I installed it from CD by the very end of August. Than I > > >upgraded to 0.82.4 and finally to 0.84. This is the 0.84 upgrade that broke > > >my boot up. The .70< estimate doesn't seem to fit my case... > > > > I had a similar occurence. I think it might have been a 0.79. I did > > a fresh install from 0.82 I think and it never came back. > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]