Booting problem
Dear Sir, Please be kind enough to provide solution to the following problem. I have an old, assembled desk top loaded with win7 ultimate. It has got 80 GB hard disk and 1 GB RAM. Earlier there was XP. That time CD drive was not working at all. Subsequently I upgraded to win7. After few days suddenly I discovered that CD drive was working. I could burn files also through this drive. Though booting was not possible from CD. After few days suddenly, system stopped loading win7. I wanted to re install win7, but was not possible without the option of booting from CD. Whenever I tried to boot, one welcome screen and another screen came after one beep each and then it halts with a blank screen. I prepared a bootable USB drive with XP with an intention to install XP and thereafter upgrade to win7 (instructions for XP alone was available in the internet). After preparing the USB, I checked it in another system to see if it was working. In the BIOS there is no option to boot from USB. So I disabled all three boot options (Floppy, CD, HDD) and enabled “other” boot option and tried to boot from USB. Out of my nearly ten attempts, only twice, USB drive was displayed in the boot menu as a boot option, though it did not boot from it. Presently system does not boot either from HDD or from CD or from USB.(Floppy drive is not active since the relative cable is missing). My question is:- 1.Why should the boot menu display the USB drive only twice? Only in case of a loose connection such things can happen. I believe there is no question of any loose connection here. So either it should display all the time or it should not display at all. There is no specific option in the BIOS for booting from USB. If that means system does not support USB booting, then it should not have come in the boot menu at all. Fact that it appeared in the boot menu, means system supports booting from USB. 2. Why does not the system boot? I have a feeling that perhaps there is a component which is responsible for detecting drives or booting in general was failing slowly because of which CD drive was not working (when XP was there) and there after it was not booting from CD and again there after it stopped booting altogether from all the drives. Can there be a problem with mother board? 3. Someone told me that, in case of RAM failure, system will not start the boot process at all. Here since boot process goes few steps producing two screens and two beeps, perhaps it is trying to boot but why unable to detect the drives. 4. There are two separate cables for hard disk and CD drive. CD drive is primary and hard disk secondary. When I exchange the cables, it is reflected in the BIOS that is CD drive becomes secondary and vice versa. That means BIOS is recognizing the drives. 5. I tried with different boot order in the BIOS as well as by making the BIOS setting as default. 6. I tried the installation CD, so there is no question of whether the CD is bootable or not. Similarly if MBR is corrupt, it should give problem only for HDD booting and not for others like CD and USB. Then where is the problem? 7. Why doesn’t any error message displayed during boot process? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting Problem
On 29 January 2013, at 20:25, d...@safeport.com wrote: On Tue, 29 Jan 2013, Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. What is the system you are using? What external devices does it have built-in support for? In the absence of any data - how about trying an external hard drive? 9.1 release - Generic. Basically the disk1. Don't have an extra external drive. Why not remove the hard drive, use another system to put FreeBSD on the drive, and put it back. From that point on you should be able to use the network to upgrade. I have done that before and it does work. However, with the various changes to the system, the root partition I had previously built that way for 8.2 is just not large enough for 9.1. Also, I wanted to go to a single partition (the 9.1 default). Probably freebsd-update will take me through major releases after this, but I was hoping for a better solution so I could avoid having to transport the machine a long way twice to be able to update it. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting Problem
On 1/29/2013 10:25 PM, d...@safeport.com wrote: What is the system you are using? What external devices does it have built-in support for? In the absence of any data - how about trying an external hard drive? Why not remove the hard drive, use another system to put FreeBSD on the drive, and put it back. From that point on you should be able to use the network to upgrade. I had to do something like this to try out PC-BSD years ago. I had one computer that wouldn't boot the install CD. I moved the hard drive to a computer that would boot the install CD. The catch was the computer that could boot the install CD wouldn't boot PC-BSD from the hard drive. Sometimes you just find hardware that doesn't behave. I'd also double check your BIOS settings for USB emulation. Most external CD drives are just an IDE or SATA drive with an adapter. If you take it apart, you can put the drive into the computer and see if skipping the USB helps it to boot. It's also a nice way to find a cheap drive. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting Problem
Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? Not so far. The drive works fine on other systems. You said in your orginal post The bios will not boot from USB stick. I see no reason why you would think your PC would BOOT from any USB attached devices. Since you have another PC that does boot off of usb cd drive, swap hard drives and use that pc to load FreeBSD to the hard drive. This method will work for you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting Problem
On 30 January 2013, at 05:16, Fbsd8 wrote: Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? Not so far. The drive works fine on other systems. You said in your orginal post The bios will not boot from USB stick. I see no reason why you would think your PC would BOOT from any USB attached devices. Since you have another PC that does boot off of usb cd drive, swap hard drives and use that pc to load FreeBSD to the hard drive. This method will work for you. Yes that works now. But starting this weekend it will be about 100 miles away. That no longer will be practical. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting Problem
On Wed, 30 Jan 2013, Doug Hardie wrote: On 30 January 2013, at 05:16, Fbsd8 wrote: Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? Not so far. The drive works fine on other systems. You said in your orginal post The bios will not boot from USB stick. I see no reason why you would think your PC would BOOT from any USB attached devices. Since you have another PC that does boot off of usb cd drive, swap hard drives and use that pc to load FreeBSD to the hard drive. This method will work for you. Yes that works now. But starting this weekend it will be about 100 miles away. That no longer will be practical. The CD will not be of much help then either. The problem started with the root partition being too small. Just repartition to make sure that does not come up for a while. While you have you hands of the machine you should see if you can figure out if it can do a pixe boot. You should also see if you can arrange for a serial console into the system. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting Problem
On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? -- Mario Lobo http://www.mallavoodoo.com.br FreeBSD since 2.2.8 [not Pro-Audio YET!!] (99% winblows FREE) ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting Problem
On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org Can you boot a different OS (Win, Ububtu, gparted, etc ...) from the same drive on the same machine? Not so far. The drive works fine on other systems. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Booting Problem
On Tue, 29 Jan 2013, Doug Hardie wrote: On 29 January 2013, at 07:18, Mario Lobo wrote: On Mon, 28 Jan 2013 15:16:14 -0800 Doug Hardie bc...@lafn.org wrote: I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. What is the system you are using? What external devices does it have built-in support for? In the absence of any data - how about trying an external hard drive? Why not remove the hard drive, use another system to put FreeBSD on the drive, and put it back. From that point on you should be able to use the network to upgrade. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Booting Problem
I have a relatively old machine that I am trying to boot 9.1 on. The bios will not boot from USB stick. I am using an external CD drive. It starts the boot process fine and gets to the Bootstrap loader message with revision 1.1. Then it puts out the machine, date, time the CD was created and starts the spinner. It spins around about 2 times and stops. The system continues to read from the drive for another couple minutes. Then everything stops. Nothing more happens. The CD is good. I can boot it just fine using the same external drive on another machine. While I could remove the drive and temporarily mount in in the working machine and build it there, I would like to find a way to successfully boot from CD. This will become a remote machine and taking it apart later is not a viable option. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Hardware booting problem
I encountered a situation today that I do not understand. This is a very old i386 PC that does not have a usable CD drive. The existing drive uses a very funky SCSI connector that I have nothing for. The system disk is SCSI and there was one additional PATA drive used for additional storage. The PATA drive failed. It won't even stick around in /dev for more than a couple minutes after boot and there are lots of messages about bad sectors. The data is completely backed up and the that drive is over 5 years old. I removed the old drive and installed a new one. System will not boot. It hangs in the BIOS. Never gets around to installing the SCSI BIOS. My first guess was there was no boot sector on the SCSI drive. That seems unusual since my other systems boot off the SCSI drives just fine. This one used to also before I added the PATA drive. However, if I put the dead drive back in along with the new one, then it boots. This also implies that the boot sector was only on the PATA drive. But the PATA drive is for all intents and purposes dead. So how is it booting? Is there any way to look into the SCSI drive and see if there is a boot sector there? This is more a curiosity item as there are additional failures starting to occur in that computer. We are going to replace it. Its around 10 years old. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Hardware booting problem
At 03:34 AM 9/15/2011, Doug Hardie wrote: I encountered a situation today that I do not understand. This is a very old i386 PC that does not have a usable CD drive. The existing drive uses a very funky SCSI connector that I have nothing for. The system disk is SCSI and there was one additional PATA drive used for additional storage. The PATA drive failed. It won't even stick around in /dev for more than a couple minutes after boot and there are lots of messages about bad sectors. The data is completely backed up and the that drive is over 5 years old. I removed the old drive and installed a new one. System will not boot. It hangs in the BIOS. Never gets around to installing the SCSI BIOS. My first guess was there was no boot sector on the SCSI drive. That seems unusual since my other systems boot off the SCSI drives just fine. This one used to also before I added the PATA drive. However, if I put the dead drive back in along with the new one, then it boots. This also implies that the boot sector was only on the PATA drive. But the PATA drive is for all intents and purposes dead. So how is it booting? Is there any way to look into the SCSI drive and see if there is a boot sector there? This is more a curiosity item as there are additional failures starting to occur in that computer. We are going to replace it. Its around 10 years old. Depending on your SCSI card BIOS, some allow you to set which LUN it boots. You may want to explore the SCSI settings, and try to set the new drive as the first boot device, then try removing the old drive. -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 freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.0 Booting Problem on ZV5320US Laptop
richard.delaur...@gmail.com wrote: Are you able to get to the FreeBSD splash screen (where you get a countdown to startup with a menu of 6 selections)? Yes, It doesn't go beyond that selection most of the time. One of the choices there is boot w/o ACPI; you could try that if you get that far. That is exactly where I am, at that screen when I make the selection (any selection) it just pauses for about 30 Secs before the computer shuts down. Tried all options including 'set hint.acpi.0.disabled=1' followed by 'boot' at the loader prompt. Its more or less 1 successful boot in 7 attempts, totally random, not dependent on w/o ACPI is picked or not, sometimes it just works with verbose logging or normal boot. It is definitely something to do with the RESET BIOS timer (If at all there is anything like that) expiring before FreeBSD kernel can fully load or something... Thank you HP ! -Anoop Good luck-- Richard On Fri, Mar 19, 2010 at 11:55 AM, Anoop Kumar Narayanan anoop...@gmail.com wrote: On Fri, Mar 19, 2010 at 7:49 PM, Richard DeLaurell richard.delaur...@gmail.com wrote: On Fri, Mar 19, 2010 at 8:20 AM, Anoop Kumar Narayanan anoop...@gmail.comwrote: I have recently installed FreeBSD8.0 on my 5 year old HP laptop with absolute 0 battery backup (behaviour same when batter removed). Installation works fine but when I try to boot into FreeBSD I get to the BTX loader screen, after having made any selection and it pauses for about 15 secs and the computer suddenly powers down. I was able to boot into the system occasionally lets say about 1 in 5 boots. I am able to install and boot into Linux without any problem. So then you are attempting to startup using a power adaptor (i.e. your computer is plugged in to a wall socket)? Yes. I don't know if its a specific Athlon XP related problem as I did observe a similar post some years ago. And, Apparently its the same thing. http://osdir.com/ml/os.freebsd.devel.hardware/2004-10/msg00044.html In this case its the installation. In my case its after the installation. I had the reverse problem a while ago with Slackware shutting down in the middle of installation onto a Toshiba laptop while FreeBSD has always been no problem. My guess is that these issues reflect power management settings, perhaps even something in the bios. Maybe its something in the BIOS, but the thing is that Linux boots fine on the machine. Maybe some driver is crashing and is causing a reboot of the machine. Are there any critical drivers in the system that can result in such a problem. Does this occur when you use the installation or boot-only disks? I can install it just fine, but can't seem to to boot into the installed version (Once its been installed). I did create the FreeBSD swap partition before the root file-system (and it still seems to label the root file-system as 'a'), Would this affect the system boot up in anyway ? Sorry this is not more help to you. Richard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.0 Booting Problem on ZV5320US Laptop
I have recently installed FreeBSD8.0 on my 5 year old HP laptop with absolute 0 battery backup (behaviour same when batter removed). Installation works fine but when I try to boot into FreeBSD I get to the BTX loader screen, after having made any selection and it pauses for about 15 secs and the computer suddenly powers down. I was able to boot into the system occasionally lets say about 1 in 5 boots. I am able to install and boot into Linux without any problem. On successful boot, I did see a message battery0: battery initialization failed 1. Is there any way to increase the amount of debug messages printed on the screen to figure out what's happening ? 2. Has it got to do with some module crashing as, I am able to install and run LINUX without any problem ? 3. Why is there a pause of 15 secs after making the selection ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.0 Booting Problem on ZV5320US Laptop
On Fri, Mar 19, 2010 at 8:20 AM, Anoop Kumar Narayanan anoop...@gmail.comwrote: I have recently installed FreeBSD8.0 on my 5 year old HP laptop with absolute 0 battery backup (behaviour same when batter removed). Installation works fine but when I try to boot into FreeBSD I get to the BTX loader screen, after having made any selection and it pauses for about 15 secs and the computer suddenly powers down. I was able to boot into the system occasionally lets say about 1 in 5 boots. I am able to install and boot into Linux without any problem. So then you are attempting to startup using a power adaptor (i.e. your computer is plugged in to a wall socket)? I had the reverse problem a while ago with Slackware shutting down in the middle of installation onto a Toshiba laptop while FreeBSD has always been no problem. My guess is that these issues reflect power management settings, perhaps even something in the bios. Does this occur when you use the installation or boot-only disks? Sorry this is not more help to you. Richard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.0 Booting Problem on ZV5320US Laptop
On Fri, Mar 19, 2010 at 7:49 PM, Richard DeLaurell richard.delaur...@gmail.com wrote: On Fri, Mar 19, 2010 at 8:20 AM, Anoop Kumar Narayanan anoop...@gmail.comwrote: I have recently installed FreeBSD8.0 on my 5 year old HP laptop with absolute 0 battery backup (behaviour same when batter removed). Installation works fine but when I try to boot into FreeBSD I get to the BTX loader screen, after having made any selection and it pauses for about 15 secs and the computer suddenly powers down. I was able to boot into the system occasionally lets say about 1 in 5 boots. I am able to install and boot into Linux without any problem. So then you are attempting to startup using a power adaptor (i.e. your computer is plugged in to a wall socket)? Yes. I don't know if its a specific Athlon XP related problem as I did observe a similar post some years ago. And, Apparently its the same thing. http://osdir.com/ml/os.freebsd.devel.hardware/2004-10/msg00044.html In this case its the installation. In my case its after the installation. I had the reverse problem a while ago with Slackware shutting down in the middle of installation onto a Toshiba laptop while FreeBSD has always been no problem. My guess is that these issues reflect power management settings, perhaps even something in the bios. Maybe its something in the BIOS, but the thing is that Linux boots fine on the machine. Maybe some driver is crashing and is causing a reboot of the machine. Are there any critical drivers in the system that can result in such a problem. Does this occur when you use the installation or boot-only disks? I can install it just fine, but can't seem to to boot into the installed version (Once its been installed). I did create the FreeBSD swap partition before the root file-system (and it still seems to label the root file-system as 'a'), Would this affect the system boot up in anyway ? Sorry this is not more help to you. Richard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD 8.0 Booting Problem on ZV5320US Laptop
Are you able to get to the FreeBSD splash screen (where you get a countdown to startup with a menu of 6 selections)? One of the choices there is boot w/o ACPI; you could try that if you get that far. Good luck-- Richard On Fri, Mar 19, 2010 at 11:55 AM, Anoop Kumar Narayanan anoop...@gmail.comwrote: On Fri, Mar 19, 2010 at 7:49 PM, Richard DeLaurell richard.delaur...@gmail.com wrote: On Fri, Mar 19, 2010 at 8:20 AM, Anoop Kumar Narayanan anoop.kn@ gmail.comwrote: I have recently installed FreeBSD8.0 on my 5 year old HP laptop with absolute 0 battery backup (behaviour same when batter removed). Installation works fine but when I try to boot into FreeBSD I get to the BTX loader screen, after having made any selection and it pauses for about 15 secs and the computer suddenly powers down. I was able to boot into the system occasionally lets say about 1 in 5 boots. I am able to install and boot into Linux without any problem. So then you are attempting to startup using a power adaptor (i.e. your computer is plugged in to a wall socket)? Yes. I don't know if its a specific Athlon XP related problem as I did observe a similar post some years ago. And, Apparently its the same thing. http://osdir.com/ml/os.freebsd.devel.hardware/2004-10/msg00044.html In this case its the installation. In my case its after the installation. I had the reverse problem a while ago with Slackware shutting down in the middle of installation onto a Toshiba laptop while FreeBSD has always been no problem. My guess is that these issues reflect power management settings, perhaps even something in the bios. Maybe its something in the BIOS, but the thing is that Linux boots fine on the machine. Maybe some driver is crashing and is causing a reboot of the machine. Are there any critical drivers in the system that can result in such a problem. Does this occur when you use the installation or boot-only disks? I can install it just fine, but can't seem to to boot into the installed version (Once its been installed). I did create the FreeBSD swap partition before the root file-system (and it still seems to label the root file-system as 'a'), Would this affect the system boot up in anyway ? Sorry this is not more help to you. Richard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD 8.0 Booting Problem on ZV5320US Laptop
I have recently installed FreeBSD8.0 on my 5 year old HP laptop with absolute 0 battery backup (behaviour same when batter removed). Installation works fine but when I try to boot into FreeBSD I get to the BTX loader screen, after having made any selection and it pauses for about 15 secs and the computer suddenly powers down. I was able to boot into the system occasionally lets say about 1 in 5 boots. I am able to install and boot into Linux without any problem. On successful boot, I did see a message battery0: battery initialization failed 1. Is there any way to increase the amount of debug messages printed on the screen to figure out what's happening ? 2. Has it got to do with some module crashing as, I am able to install and run LINUX without any problem ? 3. Why is there a pause of 15 secs after making the selection ? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: slice/booting problem
The third party boot manager does play nice, I've had this setup working before (with the same BM [smartboot]), and everything worked fine. Thanks -- In Response to your message - Date: Fri, 2 Mar 2007 16:45:51 -0500 To: J. W. Ballantine [EMAIL PROTECTED] From: Jerry McAllister [EMAIL PROTECTED] Subject: Re: slice/booting problem On Fri, Mar 02, 2007 at 03:12:55PM -0500, J. W. Ballantine wrote: I have a two disk system, and I'm trying to install FBSD6.2 on slice 2 of the second disk, a configuration that I've had working in the past. I'm using the Standard installation, select the second disk (ad1) and create a slice (ad1s2) and then create the partitions within that slice. On that disk, I install the FreeBSD Boot Manager (I have a third party boot manager installed on ad0 that boots FreeBSD). During the install, I ls /dev and find the ad1s2 partitions created. After the install, when I try to re-boot, it fails when it trys to mountroot. When I enter ?, I get a listr of GEOM managed disks, but the partitions are not listed, while the slice is. Any ideas on what I'm missing??? Just a wild guess: That either the first or second disk didn't really get an MBR written to it - or the third party boot manager on the first disk might not play nicely with the one on the second disk. Try using fdisk (from the install CD fixit if necessary) to write the FreeBSD MBR to both disks. You can put the other third party booter back afterward if desired/needed. jerry Thanks Jim Ballantine ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] g ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
slice/booting problem
I have a two disk system, and I'm trying to install FBSD6.2 on slice 2 of the second disk, a configuration that I've had working in the past. I'm using the Standard installation, select the second disk (ad1) and create a slice (ad1s2) and then create the partitions within that slice. On that disk, I install the FreeBSD Boot Manager (I have a third party boot manager installed on ad0 that boots FreeBSD). During the install, I ls /dev and find the ad1s2 partitions created. After the install, when I try to re-boot, it fails when it trys to mountroot. When I enter ?, I get a listr of GEOM managed disks, but the partitions are not listed, while the slice is. Any ideas on what I'm missing??? Thanks Jim Ballantine ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: slice/booting problem
On Fri, Mar 02, 2007 at 03:12:55PM -0500, J. W. Ballantine wrote: I have a two disk system, and I'm trying to install FBSD6.2 on slice 2 of the second disk, a configuration that I've had working in the past. I'm using the Standard installation, select the second disk (ad1) and create a slice (ad1s2) and then create the partitions within that slice. On that disk, I install the FreeBSD Boot Manager (I have a third party boot manager installed on ad0 that boots FreeBSD). During the install, I ls /dev and find the ad1s2 partitions created. After the install, when I try to re-boot, it fails when it trys to mountroot. When I enter ?, I get a listr of GEOM managed disks, but the partitions are not listed, while the slice is. Any ideas on what I'm missing??? Just a wild guess: That either the first or second disk didn't really get an MBR written to it - or the third party boot manager on the first disk might not play nicely with the one on the second disk. Try using fdisk (from the install CD fixit if necessary) to write the FreeBSD MBR to both disks. You can put the other third party booter back afterward if desired/needed. jerry Thanks Jim Ballantine ___ 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: Booting problem
On Tuesday 27 June 2006 14:07, Winston wrote: I tried to boot via a serial console, so I modified/added the following config files: --- /boot/loader.conf: boot_multicons=YES boot_serial=YES console=comconsole --- /boot.config # wyt: added -Dh --- Changed /etc/ttys: ttyd0 /usr/libexec/getty std.9600 dialup off secure to ttyd0 /usr/libexec/getty std.9600 xterm on secure However, I got the following messages while booting: /boot.config: # FreeBSD/i386 boot Default: 0:ad(0,a)boot boot: I think I prob. made a mistake by putting a line of comment #wyt: added at the beginning of /boot.conf and the boot loader doesn't like it. But if I specify /boot/kernel/kernel after the line boot: I got a bunch of reg dumps and finally: BTX halted The kernel was booting fine before I make the changes. I now have the chicken and egg problem: I need to get rid of the line of comment in boot.conf for it to boot, but I can't access it without booting into it. Any hint? Use /boot/loader rather than /boot/kernel/kernel at the boot2 prompt. -- John Baldwin ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Booting problem
I tried to boot via a serial console, so I modified/added the following config files: --- /boot/loader.conf: boot_multicons=YES boot_serial=YES console=comconsole --- /boot.config # wyt: added -Dh --- Changed /etc/ttys: ttyd0 /usr/libexec/getty std.9600 dialup off secure to ttyd0 /usr/libexec/getty std.9600 xterm on secure However, I got the following messages while booting: /boot.config: # FreeBSD/i386 boot Default: 0:ad(0,a)boot boot: I think I prob. made a mistake by putting a line of comment #wyt: added at the beginning of /boot.conf and the boot loader doesn't like it. But if I specify /boot/kernel/kernel after the line boot: I got a bunch of reg dumps and finally: BTX halted The kernel was booting fine before I make the changes. I now have the chicken and egg problem: I need to get rid of the line of comment in boot.conf for it to boot, but I can't access it without booting into it. Any hint? WT ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
5.2.1 booting problem - hardware, software?
Witam I got problem with installing 5.2.1 RC2 after i've changed my MBO. Earlier I've used MSI kt4v on VIA chipset and there was no problem. Now I got ABIT NF7-SL on nForce2 chipset and I'm wondering what's goin' on? When I try to install fbsd, installation stops every time at this same point. The last thing in the output is: # Timocounters tick every 10.000 msec //or something like this in the next step, there should be /root/mfs... mounted, but install stops. I've tried to change my RAM, hd, cdrom with no result. I found in the output some lines like this: pci0: memory, RAM at device 0.1 on pci 0 (driver not attached) pci0: memory, RAM at device 0.2 on pci 0 (driver not attached) pci0: memory, RAM at device 0.3 on pci 0 (driver not attached) .. the same with some other devices. Anyone got idea what could be wrong? -- Pozdrowienia, Grzegorz mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 5.2.1 booting problem - hardware, software?
Hi, I've got the same chipset in my mobo. There is some kind of problem with ACPI, so its better to boot without it (either disable it in bios/either choose the right boot option). Later on you will have some more problems with onboard NIC and (if you have one) nvidia gfx. Write to me if you will have the problems that I think you will. Przemyslaw Ceglowski --- Grzegorz Burzyñski [EMAIL PROTECTED] wrote: Witam I got problem with installing 5.2.1 RC2 after i've changed my MBO. Earlier I've used MSI kt4v on VIA chipset and there was no problem. Now I got ABIT NF7-SL on nForce2 chipset and I'm wondering what's goin' on? When I try to install fbsd, installation stops every time at this same point. The last thing in the output is: # Timocounters tick every 10.000 msec //or something like this in the next step, there should be /root/mfs... mounted, but install stops. I've tried to change my RAM, hd, cdrom with no result. I found in the output some lines like this: pci0: memory, RAM at device 0.1 on pci 0 (driver not attached) pci0: memory, RAM at device 0.2 on pci 0 (driver not attached) pci0: memory, RAM at device 0.3 on pci 0 (driver not attached) .. the same with some other devices. Anyone got idea what could be wrong? -- Pozdrowienia, Grzegorz mailto:[EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] __ Do you Yahoo!? Get better spam protection with Yahoo! Mail. http://antispam.yahoo.com/tools ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem After Power Loss (fsck)?
Good news and bad news: Good News: System seems to have recovered. Booting into single user mode and running fsck worked great for / and /var, but did nothing for my /usr partition with all my data. After letting fsck run on my /usr partition for 4 days, the raid controller appeared to stall and the machine did not return to a prompt. Regular boot (multi-user mode) somehow worked where it would not work before, and background fsck on the /usr partition eventually ended. The system is now up and reachable, which is all I care about. Bad News: No one who read my last message offered to help. I suppose you can draw your own conclusions about the community-like nature of FreeBSD use in the Bay Area (home to UC Berkeley, FreeBSD Mall, and birthplace of the FreeBSD movement.) -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra Rishi Chopra wrote: I do not have the FIX-IT CD or another FreeBSD machine. Is there another fellow FreeBSD'er in the Bay Area, CA that can volunteer to help me troubleshoot the card as described below (e.g. plug in the card and break to debugger to gather info)? I can drive over to your place or you can come over to my house (directions on my homepage). If it helps, my perspective is that meeting up is totally positve and the only thing left keeping me involved with computing - allow me to explain: The server was totally idle when the power was cut, and I didn't make any changes while the server was down. I've seen some crazy things working on computers before (I can show you a list, post one to the newsgroup, or if you're curious you can try searching the google groups link on my homepage.) This would by far have to the most stubborn, underhanded, mean, nasty and implausable error I've ever come accross. I could really use some help getting the filesytem up again; my heart can't take another failure like this, and I'm ready to give up computers (recreationally and professionally) if I can't get this problem fixed. I had just finished recovering from a 2 year reconsolidation of life and data (a 75GXP/Raid-0 failure and data loss occurred while I was studying at UC Berkeley and triggered a very nasty chain of events culminating in this problem.) I can't handle going through another data consolidation; recovering from a recent thyroid removal and a 12-hour neck dissection/removal is a full-time affair, and the 30 some-odd staples in my neck greatly limit my ability to sit at the computer. Looks like the important thing is for me to make a new friend in the FreeBSD community and a new start on computing, or bid y'all adieu. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem After Power Loss (fsck)?
On Sun, 08 Feb 2004 21:12:51 -0800 Rishi Chopra [EMAIL PROTECTED] wrote: Here's a summary of my problem so far: Server was idle (e.g. absolutely no processes running aside from csh, ttyv0 and ps) when power was cut; server reports a problem mounting /usr partition upon reboot. I have since tried the following: (1) Booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes After letting the system 'do its thing' for 5+ days, the output did not change. (2) I tried an 'fsck -p' and got the following message: /dev/da0s1a: 1128 files, 36058 used, 47059 free (261 frags, 58771 blocks, 0.1% fragmentations) Do you get the prompt back ? Try fsck -p on / then on /var /tmp and last /usr. At least you will know what partitions are ok. Better yet I suggest you boot from the second aka Fixit CD and run fsck from there; you fsck binary may be broken. Also boot verbose (I don't know if safe-mode applies to SCSI, but if it does, try that also). The display has been stuck with that same output for countless hours now. Do you have disk activity when fsck seems to be stuck ? Questions I have: (1) Have I suffered a total loss or is this still some way to revover my filesystem? After suffering a similar loss with a hardware raid-0 failure under win2k, I was assuming the FreeBSD setup would be more durable. I would hate to walk away thinking that a simple power loss could wipe out a freebsd server under nothing more than one terminal login. Generally this doesn't happen. From my experience, it happens if either there are problems with the disk access infrastructure (a la timeouts, etc. on ata) or something bad elsewhere in the kernel. (2) Why would a simple fsck of the filesystem not work in my case? If you have the kernel with options DDB options BREAK_TO_DEBUGGER and no disk activity I suggest that you break to debugger hitting Ctrl+Esc and try to gather some info from there. Note that in case fsck is actually running this could further damage you fs, but since you can't do anything else I would say to give it a try. To summarize: 1. See if you have disk activity when fsck seems to be stuck. 2. Try fsck (-p) first on root, the on tmp, /var, /usr, /home. 3. Esp. if fsck / doesn't go ok try booting verbose with Fixit CD and run fsck from there. 4. If 1 gets you the same results try putting the disk in another machine where you have debugging options in the kernel, break to debugger and gather info from there (esp. if you're running 5.x try asking on current@ what exactly to look for in the debugger). -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem After Power Loss (fsck)?
On Mon, 9 Feb 2004 11:44:46 +0200 Ion-Mihai Tetcu [EMAIL PROTECTED] wrote: On Sun, 08 Feb 2004 21:12:51 -0800 Rishi Chopra [EMAIL PROTECTED] wrote: Here's a summary of my problem so far: [..] To summarize: 1. See if you have disk activity when fsck seems to be stuck. 2. Try fsck (-p) first on root, the on tmp, /var, /usr, /home. 3. Esp. if fsck / doesn't go ok try booting verbose with Fixit CD and run fsck from there. 4. If 1 gets you the same results try putting the disk in another If 3 gets ... machine where you have debugging options in the kernel, break to debugger and gather info from there (esp. if you're running 5.x try asking on current@ what exactly to look for in the debugger). -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem After Power Loss (fsck)?
Please see my reply below: Ion-Mihai Tetcu wrote: On Sun, 08 Feb 2004 21:12:51 -0800 Rishi Chopra [EMAIL PROTECTED] wrote: Here's a summary of my problem so far: Server was idle (e.g. absolutely no processes running aside from csh, ttyv0 and ps) when power was cut; server reports a problem mounting /usr partition upon reboot. I have since tried the following: (1) Booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes After letting the system 'do its thing' for 5+ days, the output did not change. (2) I tried an 'fsck -p' and got the following message: /dev/da0s1a: 1128 files, 36058 used, 47059 free (261 frags, 58771 blocks, 0.1% fragmentations) Do you get the prompt back ? Try fsck -p on / then on /var /tmp and last /usr. At least you will know what partitions are ok. Better yet I suggest you boot from the second aka Fixit CD and run fsck from there; you fsck binary may be broken. Also boot verbose (I don't know if safe-mode applies to SCSI, but if it does, try that also). This is exactly the problem. The 'fsck' command does not return to a prompt. The display has been stuck with that same output for countless hours now. Do you have disk activity when fsck seems to be stuck ? Questions I have: (1) Have I suffered a total loss or is this still some way to revover my filesystem? After suffering a similar loss with a hardware raid-0 failure under win2k, I was assuming the FreeBSD setup would be more durable. I would hate to walk away thinking that a simple power loss could wipe out a freebsd server under nothing more than one terminal login. Generally this doesn't happen. From my experience, it happens if either there are problems with the disk access infrastructure (a la timeouts, etc. on ata) or something bad elsewhere in the kernel. (2) Why would a simple fsck of the filesystem not work in my case? If you have the kernel with options DDB options BREAK_TO_DEBUGGER and no disk activity I suggest that you break to debugger hitting Ctrl+Esc and try to gather some info from there. Note that in case fsck is actually running this could further damage you fs, but since you can't do anything else I would say to give it a try. To summarize: 1. See if you have disk activity when fsck seems to be stuck. 2. Try fsck (-p) first on root, the on tmp, /var, /usr, /home. 3. Esp. if fsck / doesn't go ok try booting verbose with Fixit CD and run fsck from there. 4. If 1 gets you the same results try putting the disk in another machine where you have debugging options in the kernel, break to debugger and gather info from there (esp. if you're running 5.x try asking on current@ what exactly to look for in the debugger). -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem After Power Loss (fsck)?
I do not have the FIX-IT CD or another FreeBSD machine. Is there another fellow FreeBSD'er in the Bay Area, CA that can volunteer to help me troubleshoot the card as described below (e.g. plug in the card and break to debugger to gather info)? I can drive over to your place or you can come over to my house (directions on my homepage). If it helps, my perspective is that meeting up is totally positve and the only thing left keeping me involved with computing - allow me to explain: The server was totally idle when the power was cut, and I didn't make any changes while the server was down. I've seen some crazy things working on computers before (I can show you a list, post one to the newsgroup, or if you're curious you can try searching the google groups link on my homepage.) This would by far have to the most stubborn, underhanded, mean, nasty and implausable error I've ever come accross. I could really use some help getting the filesytem up again; my heart can't take another failure like this, and I'm ready to give up computers (recreationally and professionally) if I can't get this problem fixed. I had just finished recovering from a 2 year reconsolidation of life and data (a 75GXP/Raid-0 failure and data loss occurred while I was studying at UC Berkeley and triggered a very nasty chain of events culminating in this problem.) I can't handle going through another data consolidation; recovering from a recent thyroid removal and a 12-hour neck dissection/removal is a full-time affair, and the 30 some-odd staples in my neck greatly limit my ability to sit at the computer. Looks like the important thing is for me to make a new friend in the FreeBSD community and a new start on computing, or bid y'all adieu. -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra Ion-Mihai Tetcu wrote: On Sun, 08 Feb 2004 21:12:51 -0800 Rishi Chopra [EMAIL PROTECTED] wrote: Here's a summary of my problem so far: Server was idle (e.g. absolutely no processes running aside from csh, ttyv0 and ps) when power was cut; server reports a problem mounting /usr partition upon reboot. I have since tried the following: (1) Booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes After letting the system 'do its thing' for 5+ days, the output did not change. (2) I tried an 'fsck -p' and got the following message: /dev/da0s1a: 1128 files, 36058 used, 47059 free (261 frags, 58771 blocks, 0.1% fragmentations) Do you get the prompt back ? Try fsck -p on / then on /var /tmp and last /usr. At least you will know what partitions are ok. Better yet I suggest you boot from the second aka Fixit CD and run fsck from there; you fsck binary may be broken. Also boot verbose (I don't know if safe-mode applies to SCSI, but if it does, try that also). The display has been stuck with that same output for countless hours now. Do you have disk activity when fsck seems to be stuck ? Questions I have: (1) Have I suffered a total loss or is this still some way to revover my filesystem? After suffering a similar loss with a hardware raid-0 failure under win2k, I was assuming the FreeBSD setup would be more durable. I would hate to walk away thinking that a simple power loss could wipe out a freebsd server under nothing more than one terminal login. Generally this doesn't happen. From my experience, it happens if either there are problems with the disk access infrastructure (a la timeouts, etc. on ata) or something bad elsewhere in the kernel. (2) Why would a simple fsck of the filesystem not work in my case? If you have the kernel with options DDB options BREAK_TO_DEBUGGER and no disk activity I suggest that you break to debugger hitting Ctrl+Esc and try to gather some info from there. Note that in case fsck is actually running this could further damage you fs, but since you can't do anything else I would say to give it a try. To summarize: 1. See if you have disk activity when fsck seems to be stuck. 2. Try fsck (-p) first on root, the on tmp, /var, /usr, /home. 3. Esp. if fsck / doesn't go ok try booting verbose with Fixit CD and run fsck from there. 4. If 1 gets you the same results try putting the disk in another machine where you have debugging options in the kernel, break to debugger and gather info from there (esp. if you're running 5.x try asking on current@ what exactly to look for in the debugger). ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Booting Problem After Power Loss (fsck)?
Here's a summary of my problem so far: Server was idle (e.g. absolutely no processes running aside from csh, ttyv0 and ps) when power was cut; server reports a problem mounting /usr partition upon reboot. I have since tried the following: (1) Booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes After letting the system 'do its thing' for 5+ days, the output did not change. (2) I tried an 'fsck -p' and got the following message: /dev/da0s1a: 1128 files, 36058 used, 47059 free (261 frags, 58771 blocks, 0.1% fragmentations) The display has been stuck with that same output for countless hours now. Questions I have: (1) Have I suffered a total loss or is this still some way to revover my filesystem? After suffering a similar loss with a hardware raid-0 failure under win2k, I was assuming the FreeBSD setup would be more durable. I would hate to walk away thinking that a simple power loss could wipe out a freebsd server under nothing more than one terminal login. (2) Why would a simple fsck of the filesystem not work in my case? Thanks, Rishi Ion-Mihai Tetcu wrote: On Tue, 03 Feb 2004 01:09:22 -0800 Rishi Chopra [EMAIL PROTECTED] wrote: I booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes FILE SYSTEM STILL DIRTY Can't be only this. It should have outputted something else between Phase 1 and FILE SYSTEM STILL DIRTY. Will fsck continue attempting to fix the filesystem? Have I suffered a total loss or is fsck still doing its thing? Read man fsck and its see also section. -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem
On Tue, 03 Feb 2004 22:35:35 -0800 Rishi Chopra [EMAIL PROTECTED] wrote: Here's some questions: If the server was idle (e.g. absolutely no processes running aside from login shell and terminal and no disk access occurring) does it make sense that the filesystem would have had a problem after being improperly unmounted? Each file system would be at least marked as being used, so fsck -p on boot will print that and check them. Usually if the system is idle the fs will be ok. But you have processes that are active in regard the fs, even if not logged in (cron, ntp/ntpdate, syslog to name a few); /tmp and /var usually have problems after an unclean shutdown. Note two things about disks: 1. hw.ata.wc=0 disables write caching - bad for performance good for integrity. When a disk does wc it holds data in its buffer and report it as being written to the OS and this delay could go up to 60 seconds (and even more) depending on the HDD and the load. atacontrol cap channel unit should tell you the state of write caching; on my system I have wc=0 but atacontrol shows it turned on, so I might be wrong here or this is not supported on all HDDs. 2. kern.filedelay=30, kern.dirdelay=29, kern.metadelay=28 sets how often the respective data is flushed ( synced(8) ) to disk when using soft-updates; note the descending order, it is important. You might want to decrease them, which will degrade performance, but could help a more consistent fs in case of a crash. When I test a new HDD, CDROM, kernel and world I usually decrease them to 15,14,13 or even 10,9,8 until everything seems OK. Also, how long should an 'fsck' on a 500GB partition take? It's been running for almost 12 hours now, and the latest output is still Phase 1 - check blocks and sizes; is something wrong or is fsck still doing its thing? My largest was about 80G and it takes a few minutes with UDMA100 for a small amount of errors, so I don't really know. But it depends on how much the file system is damaged, the access speed of the disk/controller and the processor/memory; I have the feeling the size - time progression is not at all arithmetical. As a note, if you don't really need a fs that big, use smaller partitions and mount / symlink them where you need them where you need. This will give you better chances in case of crash. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem
I booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes FILE SYSTEM STILL DIRTY Will fsck continue attempting to fix the filesystem? Have I suffered a total loss or is fsck still doing its thing? If this is a total loss, can I do anything to get my data back? -Rishi Rishi Chopra wrote: I'm getting the following error message during startup: /usr: mount pending error: blocks 16 files 1 I'm guessing this orrcured due to a shutdown during background fsck of the filesystem. Will the error fix itself (e.g. will the boot process continue and finally proceed to a prompt) or do I need to intervene? If intervention is required, how would I go about setting things right? -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem
On Tue, 03 Feb 2004 01:09:22 -0800 Rishi Chopra [EMAIL PROTECTED] wrote: I booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes FILE SYSTEM STILL DIRTY Can't be only this. It should have outputted something else between Phase 1 and FILE SYSTEM STILL DIRTY. Will fsck continue attempting to fix the filesystem? Have I suffered a total loss or is fsck still doing its thing? Read man fsck and its see also section. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem
Here's some questions: If the server was idle (e.g. absolutely no processes running aside from login shell and terminal and no disk access occurring) does it make sense that the filesystem would have had a problem after being improperly unmounted? Also, how long should an 'fsck' on a 500GB partition take? It's been running for almost 12 hours now, and the latest output is still Phase 1 - check blocks and sizes; is something wrong or is fsck still doing its thing? Ion-Mihai Tetcu wrote: On Tue, 03 Feb 2004 01:09:22 -0800 Rishi Chopra [EMAIL PROTECTED] wrote: I booted into single-user mode and ran 'fsck' - the latest output to the terminal says: FILE SYSTEM MARKED CLEAN /dev/da0s1e Last Mounted on /usr Phase 1 - check blocks and sizes FILE SYSTEM STILL DIRTY Can't be only this. It should have outputted something else between Phase 1 and FILE SYSTEM STILL DIRTY. Will fsck continue attempting to fix the filesystem? Have I suffered a total loss or is fsck still doing its thing? Read man fsck and its see also section. -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem
On Mon, 02 Feb 2004 19:49:50 -0800 Rishi Chopra [EMAIL PROTECTED] wrote: I'm getting the following error message during startup: /usr: mount pending error: blocks 16 files 1 I'm guessing this orrcured due to a shutdown during background fsck of the filesystem. Not necessarily during a bgfsck, just the filesystem is not clean, so bgfsck will run. Will the error fix itself (e.g. will the boot process continue and finally proceed to a prompt) or do I need to intervene? Usually it will continue, if not, you will be the first or know ;) If intervention is required, how would I go about setting things right? Watch (tail -F) /var/log/messages, after login, if you get something strange there (like unexpected softupdate inconsistency, run fsck manually or fsck drops core) or if on the next reboot it happens again boot is single user and run fsck. -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Booting Problem
Thank you! Ion-Mihai Tetcu wrote: On Mon, 02 Feb 2004 19:49:50 -0800 Rishi Chopra [EMAIL PROTECTED] wrote: I'm getting the following error message during startup: /usr: mount pending error: blocks 16 files 1 I'm guessing this orrcured due to a shutdown during background fsck of the filesystem. Not necessarily during a bgfsck, just the filesystem is not clean, so bgfsck will run. Will the error fix itself (e.g. will the boot process continue and finally proceed to a prompt) or do I need to intervene? Usually it will continue, if not, you will be the first or know ;) If intervention is required, how would I go about setting things right? Watch (tail -F) /var/log/messages, after login, if you get something strange there (like unexpected softupdate inconsistency, run fsck manually or fsck drops core) or if on the next reboot it happens again boot is single user and run fsck. -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- Rishi Chopra http://www.ocf.berkeley.edu/~rchopra ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
diskless/pxe booting problem cont. aka cannot open /dev/ttyv0
Ok, the last problem I was experiencing when the console would just freeze while the kernel was attempting to do the nfs mount was due to a firewall rule. At least, that's what I gathered after scrolling through a tcpdump capture. I don't have the message handy, but it seemed to have been due to expecting an icmp response that never came. Anyways, I'm past this part now. My problem now is that the boot process is hanging during what appears to be rc.i386 initialization. I tried looking through the archives but only found one recent posting that never got answered. All the other (few) where somewhat dated (circa 1999). For the record, I'm trying to pxeboot a soekris net4501. There's no vga or keyboard adapter as everythings handled through the serial console. Can anyone provide any suggestions at what I should be looking at next. Thanks, dso dmesg -- [snip] Mounting NFS file systems:. Additional daemons: syslogd. Doing additional network setup:. Starting final network daemons:. ELF ldconfig path: /usr/lib /usr/lib/compat a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout Starting standard daemons: cron. Initial rc.i386 nnitialization:. Configuring syscons: blanktime/etc/rc.syscons: cannot open /dev/ttyv0: no such d evice or address . Additional ABI support:. Starting local daemons:. Additional TCP options:. Thu Jan 10 00:35:03 GMT 1980 /usr/src/sys/i386/conf/DISKLESS -- machine i386 cpu I486_CPU ident DISKLESS maxusers0 options INET#InterNETworking options FAST_IPSEC #new IPsec options FFS #Berkeley Fast Filesystem options FFS_ROOT#FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options UFS_DIRHASH #Improve performance on big directories options MFS #Memory Filesystem #optionsMD_ROOT #MD is a potential root device options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM#Rate limit bad replies options KBD_INSTALL_CDEV# install a CDEV entry in /dev options NO_SWAPPING # Disable swapping # Debugging options options DDB # Enable the kernel debugger. # Options for pxe booting options BOOTP options BOOTP_NFSROOT options BOOTP_COMPAT options NFS options NFS_ROOT options IPFILTER#ipfilter support options IPFILTER_LOG#ipfilter logging options CLK_USE_I8254_CALIBRATION options CPU_ELAN options HZ=250 device isa device pci # ATA and ATAPI devices device ata0at isa? port IO_WD1 irq 14 device ata1at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device vga0at isa? device sc0 at isa? flags 0x100 # splash screen/screen saver pseudo-device splash # Floating point support - do not disable. device npx0at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support #device card #device pcic0 at isa? irq 0 port 0x3e0 iomem 0xd #device pcic1 at isa? irq 0 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0at isa? port IO_COM1 flags 0x10 irq 4 device sio1at isa? port IO_COM2 irq 3 # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device sis # Silicon Integrated Systems SiS 900/SiS 7016 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop# Network loopback pseudo-device ether # Ethernet support pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) #pseudo-device md
diskless/pxe booting problem...
I've been experiencing a problem getting a soekris to pxe boot properly.
I've tried this with both RELENG_4_8 and RELENG_4 and it still gives
me the same problem. I've read and re-read the diskless operation, nfs,
and freebsd booting process sections in the handbook, as well as tried
to read and understand both the rc.diskless[12] scripts and the
clone_root script.
I'm exporting /tmp on the dhcp server since that was the only way I
could get the -alldirs option to work, though in retrospect, I don't
seem to need it. I've used both the clone_root method to create a
proper root to export, as well as using the method described in jail(8).
The soekris is able to pxe boot off of the server, but it always hangs
in the same spot. Does anyone have any idea what I should be looking
at? Here is my configuration. For the sake of space, I didn't include
the entire configuration files, only what I believe is pertinent. If I
should provide any more info, I'm welcome to suggestions.
/etc/exports
/tmp -alldirs -ro -maproot=0:0 172.16.34.98 172.16.34.99
/usr/local/etc/dhcpd.conf
host soekris1 {
hardware ethernet 00:00:24:c1:2f:64;
fixed-address 172.16.34.98;
filename pxeboot;
next-server 172.16.34.1;
option root-path 172.16.34.1:/tmp;
}
host soekris2 {
hardware ethernet 00:00:24:c1:2f:84;
fixed-address 172.16.34.99;
filename pxeboot;
next-server 172.16.34.1;
option root-path 172.16.34.1:/tmp;
}
/tmp/conf/base/etc/fstab /tmp/etc/fstab
# DeviceMountpoint FStype Options DumpPass#
172.16.34.1:/tmp/ nfs ro 0 0
proc/proc procfs rw 0 0
/usr/src/sys/i386/conf/DISKLESS
# Options for pxe booting
options BOOTP
options BOOTP_NFSROOT
options BOOTP_COMPAT
options NFS
options NFS_ROOT
dmesg
FreeBSD/i386 bootstrap loader, Revision 0.8
([EMAIL PROTECTED], Mon Oct 13 17:25:56 CDT 2003)
pxe_open: server addr: 172.16.34.1
pxe_open: server path: /tmp
pxe_open: gateway ip: 172.16.34.1
Loading /boot/defaults/loader.conf
/kernel text=0x1b91dd data=0x20a74+0x1f598 -
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
[verbose dmesg snipped]
bpf: lo0 attached
IPsec: Initialized Security Association Processing.
IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled
Sending DHCP Discover packet from interface sis0 (00:00:24:c1:2f:64)
Sending DHCP Discover packet from interface sis1 (00:00:24:c1:2f:65)
Sending DHCP Discover packet from interface sis2 (00:00:24:c1:2f:66)
Received DHCP Offer packet on sis0 from 172.16.34.1 (accepted) (no root
path)
Sending DHCP Request packet from interface sis0 (00:00:24:c1:2f:64)
Received DHCP Ack packet on sis0 from 172.16.34.1 (accepted) (got root path)
DHCP timeout for interface sis1
DHCP timeout for interface sis2
sis0 at 172.16.34.98 server 172.16.34.1 boot file pxeboot
subnet mask 255.255.255.0 router 172.16.34.1 rootfs 172.16.34.1:/tmp
Adjusted interface sis0
Shutdown interface sis1
Shutdown interface sis2
Mounting root from nfs:172.16.34.1:/tmp
missing device name
setrootbyname failed
NFS ROOT: 172.16.34.1:/tmp
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskless/pxe booting problem...
Are you sure that you have a kernel at /tmp ? Your config says that the
root / for this boot is really at /tmp
--Wes
On Oct 14, 2003, at 12:09 PM, Dave O wrote:
I've been experiencing a problem getting a soekris to pxe boot
properly. I've tried this with both RELENG_4_8 and RELENG_4 and it
still gives me the same problem. I've read and re-read the diskless
operation, nfs, and freebsd booting process sections in the handbook,
as well as tried to read and understand both the rc.diskless[12]
scripts and the clone_root script.
I'm exporting /tmp on the dhcp server since that was the only way I
could get the -alldirs option to work, though in retrospect, I don't
seem to need it. I've used both the clone_root method to create a
proper root to export, as well as using the method described in
jail(8). The soekris is able to pxe boot off of the server, but it
always hangs in the same spot. Does anyone have any idea what I
should be looking at? Here is my configuration. For the sake of
space, I didn't include the entire configuration files, only what I
believe is pertinent. If I should provide any more info, I'm welcome
to suggestions.
/etc/exports
/tmp -alldirs -ro -maproot=0:0 172.16.34.98 172.16.34.99
/usr/local/etc/dhcpd.conf
host soekris1 {
hardware ethernet 00:00:24:c1:2f:64;
fixed-address 172.16.34.98;
filename pxeboot;
next-server 172.16.34.1;
option root-path 172.16.34.1:/tmp;
}
host soekris2 {
hardware ethernet 00:00:24:c1:2f:84;
fixed-address 172.16.34.99;
filename pxeboot;
next-server 172.16.34.1;
option root-path 172.16.34.1:/tmp;
}
/tmp/conf/base/etc/fstab /tmp/etc/fstab
# DeviceMountpoint FStype Options DumpPass#
172.16.34.1:/tmp/ nfs ro 0 0
proc/proc procfs rw 0 0
/usr/src/sys/i386/conf/DISKLESS
# Options for pxe booting
options BOOTP
options BOOTP_NFSROOT
options BOOTP_COMPAT
options NFS
options NFS_ROOT
dmesg
FreeBSD/i386 bootstrap loader, Revision 0.8
([EMAIL PROTECTED], Mon Oct 13 17:25:56 CDT 2003)
pxe_open: server addr: 172.16.34.1
pxe_open: server path: /tmp
pxe_open: gateway ip: 172.16.34.1
Loading /boot/defaults/loader.conf
/kernel text=0x1b91dd data=0x20a74+0x1f598 -
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993,
1994
The Regents of the University of California. All rights
reserved.
[verbose dmesg snipped]
bpf: lo0 attached
IPsec: Initialized Security Association Processing.
IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled
Sending DHCP Discover packet from interface sis0 (00:00:24:c1:2f:64)
Sending DHCP Discover packet from interface sis1 (00:00:24:c1:2f:65)
Sending DHCP Discover packet from interface sis2 (00:00:24:c1:2f:66)
Received DHCP Offer packet on sis0 from 172.16.34.1 (accepted) (no
root path)
Sending DHCP Request packet from interface sis0 (00:00:24:c1:2f:64)
Received DHCP Ack packet on sis0 from 172.16.34.1 (accepted) (got root
path)
DHCP timeout for interface sis1
DHCP timeout for interface sis2
sis0 at 172.16.34.98 server 172.16.34.1 boot file pxeboot
subnet mask 255.255.255.0 router 172.16.34.1 rootfs 172.16.34.1:/tmp
Adjusted interface sis0
Shutdown interface sis1
Shutdown interface sis2
Mounting root from nfs:172.16.34.1:/tmp
missing device name
setrootbyname failed
NFS ROOT: 172.16.34.1:/tmp
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskless/pxe booting problem...
Wes Zuber wrote: Are you sure that you have a kernel at /tmp ? Your config says that the root / for this boot is really at /tmp --Wes Yes, I've placed a stripped and gzipped kernel in both /tmp and, just to be on the safe side, in the /tftpboot directory as well. It seems to me that it loads the kernel ok, but I'm not sure what it gets stuck on. Fyi, I did make sure that md0 exists in /dev, and the diskless /etc exists in both /tmp/etc and /tmp/conf/base/etc. Here is a more complete dmesg. Please excuse the verbosity :) Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader Console: internal video/keyboard PXE version 2.1, real mode entry point @9e79:0106 BIOS 577kB/64512kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 ([EMAIL PROTECTED], Mon Oct 13 17:25:56 CDT 2003) pxe_open: server addr: 172.16.34.1 pxe_open: server path: /tmp pxe_open: gateway ip: 172.16.34.1 Loading /boot/defaults/loader.conf /kernel text=0x1b91dd data=0x20a74+0x1f598 - Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-RC #0: Mon Oct 13 17:30:48 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DISKLESS Calibrating clock(s) ... i8254 clock: 1189161 Hz Timecounter i8254 frequency 1189161 Hz CPU: AMD Enhanced Am486DX4/Am5x86 Write-Back (486-class CPU) Origin = AuthenticAMD Id = 0x494 Stepping = 4 Features=0x1FPU real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x01000 - 0x8, 585728 bytes (143 pages) 0x000323000 - 0x003ff7fff, 63787008 bytes (15573 pages) avail memory = 62291968 (60832K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f0080 bios32: Entry = 0xf00c0 (c00f00c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xe1 Other BIOS signatures found: ACPI: Preloaded elf kernel kernel at 0xc02fc000. crypto: crypto core Creating DISK md0 md0: Malloc disk pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=30001022) Doing h0h0magic for AMD Elan sc520 sysctl machdep.i8254_freq=1189161 returns 0 Timecounter ELAN frequency 833 Hz npx0: math processor on motherboard npx0: INT 16 interface pcib0: AMD Elan SC520 host to PCI bridge on motherboard found- vendor=0x1022, dev=0x3000, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found- vendor=0x100b, dev=0x0020, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base e000, size 8 map[14]: type 1, range 32, base a000, size 12 found- vendor=0x100b, dev=0x0020, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base e100, size 8 map[14]: type 1, range 32, base a0001000, size 12 found- vendor=0x100b, dev=0x0020, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=5 map[10]: type 1, range 32, base e200, size 8 map[14]: type 1, range 32, base a0002000, size 12 pci0: PCI bus on pcib0 sis0: NatSemi DP83815 10/100BaseTX port 0xe000-0xe0ff mem 0xa000-0xaff f irq 10 at device 18.0 on pci0 sis0: Ethernet address: 00:00:24:c1:2f:64 miibus0: MII bus on sis0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: OUI 0x080017, model 0x0002, rev. 1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: sis0 attached sis1: NatSemi DP83815 10/100BaseTX port 0xe100-0xe1ff mem 0xa0001000-0xa0001ff f irq 11 at device 19.0 on pci0 sis1: Ethernet address: 00:00:24:c1:2f:65 miibus1: MII bus on sis1 ukphy1: Generic IEEE 802.3u media interface on miibus1 ukphy1: OUI 0x080017, model 0x0002, rev. 1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: sis1 attached sis2: NatSemi DP83815 10/100BaseTX port 0xe200-0xe2ff mem 0xa0002000-0xa0002ff f irq 5 at device 20.0 on pci0 sis2: Ethernet address: 00:00:24:c1:2f:66 miibus2: MII bus on sis2 ukphy2: Generic IEEE 802.3u media interface on miibus2 ukphy2: OUI 0x080017, model 0x0002, rev. 1 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: sis2 attached isa0: ISA bus on motherboard Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: Option ROM at iomem 0xc8000-0xd1fff on isa0 pmtimer0 on isa0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x ata0: mask=03 ostat0=7f ostat2=7f ata0-master: ATAPI 7f 7f
Re: diskless/pxe booting problem...
What about the /tmp/conf/default/etc/fstab ? --Wes On Oct 14, 2003, at 12:37 PM, Dave O wrote: Wes Zuber wrote: Are you sure that you have a kernel at /tmp ? Your config says that the root / for this boot is really at /tmp --Wes Yes, I've placed a stripped and gzipped kernel in both /tmp and, just to be on the safe side, in the /tftpboot directory as well. It seems to me that it loads the kernel ok, but I'm not sure what it gets stuck on. Fyi, I did make sure that md0 exists in /dev, and the diskless /etc exists in both /tmp/etc and /tmp/conf/base/etc. Here is a more complete dmesg. Please excuse the verbosity :) Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader Console: internal video/keyboard PXE version 2.1, real mode entry point @9e79:0106 BIOS 577kB/64512kB available memory FreeBSD/i386 bootstrap loader, Revision 0.8 ([EMAIL PROTECTED], Mon Oct 13 17:25:56 CDT 2003) pxe_open: server addr: 172.16.34.1 pxe_open: server path: /tmp pxe_open: gateway ip: 172.16.34.1 Loading /boot/defaults/loader.conf /kernel text=0x1b91dd data=0x20a74+0x1f598 - Copyright (c) 1992-2003 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.9-RC #0: Mon Oct 13 17:30:48 CDT 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/DISKLESS Calibrating clock(s) ... i8254 clock: 1189161 Hz Timecounter i8254 frequency 1189161 Hz CPU: AMD Enhanced Am486DX4/Am5x86 Write-Back (486-class CPU) Origin = AuthenticAMD Id = 0x494 Stepping = 4 Features=0x1FPU real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x01000 - 0x8, 585728 bytes (143 pages) 0x000323000 - 0x003ff7fff, 63787008 bytes (15573 pages) avail memory = 62291968 (60832K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f0080 bios32: Entry = 0xf00c0 (c00f00c0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xe1 Other BIOS signatures found: ACPI: Preloaded elf kernel kernel at 0xc02fc000. crypto: crypto core Creating DISK md0 md0: Malloc disk pci_open(1):mode 1 addr port (0x0cf8) is 0x pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=30001022) Doing h0h0magic for AMD Elan sc520 sysctl machdep.i8254_freq=1189161 returns 0 Timecounter ELAN frequency 833 Hz npx0: math processor on motherboard npx0: INT 16 interface pcib0: AMD Elan SC520 host to PCI bridge on motherboard found- vendor=0x1022, dev=0x3000, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 found- vendor=0x100b, dev=0x0020, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base e000, size 8 map[14]: type 1, range 32, base a000, size 12 found- vendor=0x100b, dev=0x0020, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base e100, size 8 map[14]: type 1, range 32, base a0001000, size 12 found- vendor=0x100b, dev=0x0020, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0secondarybus=0 intpin=a, irq=5 map[10]: type 1, range 32, base e200, size 8 map[14]: type 1, range 32, base a0002000, size 12 pci0: PCI bus on pcib0 sis0: NatSemi DP83815 10/100BaseTX port 0xe000-0xe0ff mem 0xa000-0xaff f irq 10 at device 18.0 on pci0 sis0: Ethernet address: 00:00:24:c1:2f:64 miibus0: MII bus on sis0 ukphy0: Generic IEEE 802.3u media interface on miibus0 ukphy0: OUI 0x080017, model 0x0002, rev. 1 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: sis0 attached sis1: NatSemi DP83815 10/100BaseTX port 0xe100-0xe1ff mem 0xa0001000-0xa0001ff f irq 11 at device 19.0 on pci0 sis1: Ethernet address: 00:00:24:c1:2f:65 miibus1: MII bus on sis1 ukphy1: Generic IEEE 802.3u media interface on miibus1 ukphy1: OUI 0x080017, model 0x0002, rev. 1 ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: sis1 attached sis2: NatSemi DP83815 10/100BaseTX port 0xe200-0xe2ff mem 0xa0002000-0xa0002ff f irq 5 at device 20.0 on pci0 sis2: Ethernet address: 00:00:24:c1:2f:66 miibus2: MII bus on sis2 ukphy2: Generic IEEE 802.3u media interface on miibus2 ukphy2: OUI 0x080017, model 0x0002, rev. 1 ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bpf: sis2 attached isa0: ISA bus on motherboard Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices orm0: Option ROM at iomem 0xc8000-0xd1fff on isa0 pmtimer0 on isa0 ata0:
Re: diskless/pxe booting problem...
Wes Zuber wrote: What about the /tmp/conf/default/etc/fstab ? --Wes Initially I didn't have anything, not even that directory created. I've created and removed the /conf directory many times and must've confused /conf/base with /conf/default. Re-reading diskless(8) I see that that is indeed where that file is supposed to be (thanks). I went ahead and copied [/tmp]/etc to [/tmp]/conf/default/etc and still the same result. One thing that's been puzzling me that I haven't seen in the archives is the message missing device name. Mounting root from nfs:172.16.34.1:/tmp missing device name -- setrootbyname failed NFS ROOT: 172.16.34.1:/tmp I've enabled debugging in rc.diskless1 and haven't seen the results of that so I assume that control hasn't been passed on to rc.diskless1. Should I call rc.diskless1 explicitly in rc.conf? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: diskless/pxe booting problem...
Wes Zuber wrote: Ah, ok I don't think you can just copy /etc/ straight over without changing a couple of things. We have our setup working but as I recall there were many details. We had to uncover one detail at a time (like you are doing). Here is our rc.conf in /tmp/conf/default/etc/ # -- sysinstall generated deltas -- # Wed Mar 6 00:34:08 2002 # Created: Wed Mar 6 00:34:08 2002 # Enable network daemons for user convenience. # Please make all changes to this file, not to /etc/defaults/rc.conf. # This file now contains just the overrides from /etc/defaults/rc.conf. hostname=somebox.someplace.net #ifconfig_fxp0=inet 10.50.0.71 netmask 255.255.255.0 kern_securelevel_enable=NO nfs_reserved_port_only=YES sendmail_enable=NO sshd_enable=YES usbd_enable=NO inetd_enable=NO syslogd_flags=-ss # Flags to syslogd (if enabled). swapfile=/swap/fwbuild.swap local_startup= --Wes Thanks Wes. My rc.conf is not too different from yours.I do have ssh disabled, at least until I get this working and I don't have local_startup. I'll give that a try though. I'll probably be re-reading the documentation tonight to see if I've missed anything and take another stab at it tomorrow. Too bad there isn't anything (that I know of) to allow stepping through the boot process. Thanks again for all the help. do ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
booting problem after installation of new disk controller
I recently added a new disk controller (promise ultra 133) to act as a replacement for the motherboard's controller. I also moved everything from the systems old hard drive to a new hard drive. All is well, except that I can not boot any kernel other than the one specified in /boot/defaults/loader.confFor example, if kernel.GENERIC is specified in /boot/defaults/loader.conf, it can boot that without a problem. However, if that entry is switched to kernel, and I can no longer interrupt the boot, and boot kernel.GENERIC. (situation exists with any good kernel as long as its not declared in loader.conf). At the beginning of the boot of an alternate kernel, the system displays a message WARNING: loader(8) metadata is missing!. It will continue booting until it gets to the point where it mounts root. At that point, the mount fails, and manually mounting the correct partition (ufs:/dev/ad4s1a) fails also. When booting the kernel specified, it does display what appears to be the metadata, the BTX info on the A and C partitions, etc. I have already done an fdisk -B -b, boot0cfg -B -s 1 to the new drive. The old drive, on the new controller CAN boot alternate kernels without a problem! What have I missed?? Regards, Casey ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
