Re: FreeBSD 8.4 Boot failure
Well, I wasn't able to continue troubleshooting. I took the opportunity that the server was already down to upgrade the BIOS. HP kindly does not provide any checks or warnings letting you know that you need to do a stepped upgrade, so the server is bricked. *sigh*. So this likely won't get investigated more. I'll be setting up a new server and attempting to import the zpools there. Thank for your advice anyhow! If this happens again on another server, I'll see about trying more things. On Wed, Sep 25, 2013 at 3:46 AM, Tyler Sweet ty...@tsweet.net wrote: Luckily, in this case, I had set a cron job long, long ago to do daily snapshots. So I have a snapshot from before the upgrade - There are indeed two different loaders. The newer one matches zfs when grepped, the older one does not... But, since it was working before, I restored the older loader and tried to boot again. No dice - it still sticks at that screen where all I see is / in the upper left. I also tried putting the older zfsboot and zfsloader back in place (with the old loader) to try and get a different error - still no dice. I'm still stuck wondering if that screen is from FreeBSD attempting to boot, or from the BIOS - but nothing changed for booting, as far as I know. I'll poke through the BIOS more tomorrow as well to see if some option got reset during a power-off. I'll get a more thorough look at what all changed in /boot tomorrow too, and get a list of all the files. It's almost 4am here and I have to work tomorrow :) (well, today I suppose). I'll also check to see if I can find anything about if zfs boot works differently in 8.4 vs 8.3 and older, as I may not have rebooted after the final freebsd-update install command (I *think* I did, but my memory gets fuzzy). Thanks for the input! I hope you have a good morning, and I'll let you know tomorrow/later today with anything new and interesting I find :) On Wed, Sep 25, 2013 at 1:45 AM, Terje Elde te...@elde.net wrote: On 25. sep. 2013, at 06:59, Tyler Sweet ty...@tsweet.net wrote: I tried reinstalling the boot blocks from both the fixit live filesystem and also mounting zroot and using the files there in case they were different. Disclaimer: I haven't gotten (enough) morning-coffee yet, but... Disclaimer 2: at times tracking how zfs-booting is done in the different versions can be a bit tricky. This is a moving target, and I've lost track of the 8-branch. That said, assuming you have the correct bootcode (gptzfsboot), here's what might have happened: You installed 8.2, with a loader supporting zfs. Then you upgraded your /boot-stuffs, and bootcode on disk (correctly), but got left with a loader without zfs support. Then tried to upgrade the bootcode, but you're still left with a loader not supporting zfs. If I recall correctly, then the zfs-bootcode for 9+ will use zfsloader (supporting zfs and built by default), while earlier versions depend on loader with zfs support (built without by default). If that's the case, you could dump LOADER_ZFS_SUPPORT into /etc/make.conf and rebuild/reinstall it, or install /boot/loader from the fixit (if it has zfs support in 8.4). That's my first thought at least... If that doesn't fix it (remember backups of any files you replace or upgrade), it'd be interesting to see the output of: ls -l /boot/*loader /boot/*boot On the /boot you're using. Anything that didn't get built or installed? Also, did you snapshot your zfs before upgrading? Could be a working /boot/loader there, which might be the easiest way to get the system up, before rebuilding with ZFS-capable loader... if I'm right, which isn't a given (ref disclaimers). Terje ___ 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.4 Boot failure
On 25. sep. 2013, at 06:59, Tyler Sweet ty...@tsweet.net wrote: I tried reinstalling the boot blocks from both the fixit live filesystem and also mounting zroot and using the files there in case they were different. Disclaimer: I haven't gotten (enough) morning-coffee yet, but... Disclaimer 2: at times tracking how zfs-booting is done in the different versions can be a bit tricky. This is a moving target, and I've lost track of the 8-branch. That said, assuming you have the correct bootcode (gptzfsboot), here's what might have happened: You installed 8.2, with a loader supporting zfs. Then you upgraded your /boot-stuffs, and bootcode on disk (correctly), but got left with a loader without zfs support. Then tried to upgrade the bootcode, but you're still left with a loader not supporting zfs. If I recall correctly, then the zfs-bootcode for 9+ will use zfsloader (supporting zfs and built by default), while earlier versions depend on loader with zfs support (built without by default). If that's the case, you could dump LOADER_ZFS_SUPPORT into /etc/make.conf and rebuild/reinstall it, or install /boot/loader from the fixit (if it has zfs support in 8.4). That's my first thought at least... If that doesn't fix it (remember backups of any files you replace or upgrade), it'd be interesting to see the output of: ls -l /boot/*loader /boot/*boot On the /boot you're using. Anything that didn't get built or installed? Also, did you snapshot your zfs before upgrading? Could be a working /boot/loader there, which might be the easiest way to get the system up, before rebuilding with ZFS-capable loader... if I'm right, which isn't a given (ref disclaimers). Terje ___ 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.4 Boot failure
Luckily, in this case, I had set a cron job long, long ago to do daily snapshots. So I have a snapshot from before the upgrade - There are indeed two different loaders. The newer one matches zfs when grepped, the older one does not... But, since it was working before, I restored the older loader and tried to boot again. No dice - it still sticks at that screen where all I see is / in the upper left. I also tried putting the older zfsboot and zfsloader back in place (with the old loader) to try and get a different error - still no dice. I'm still stuck wondering if that screen is from FreeBSD attempting to boot, or from the BIOS - but nothing changed for booting, as far as I know. I'll poke through the BIOS more tomorrow as well to see if some option got reset during a power-off. I'll get a more thorough look at what all changed in /boot tomorrow too, and get a list of all the files. It's almost 4am here and I have to work tomorrow :) (well, today I suppose). I'll also check to see if I can find anything about if zfs boot works differently in 8.4 vs 8.3 and older, as I may not have rebooted after the final freebsd-update install command (I *think* I did, but my memory gets fuzzy). Thanks for the input! I hope you have a good morning, and I'll let you know tomorrow/later today with anything new and interesting I find :) On Wed, Sep 25, 2013 at 1:45 AM, Terje Elde te...@elde.net wrote: On 25. sep. 2013, at 06:59, Tyler Sweet ty...@tsweet.net wrote: I tried reinstalling the boot blocks from both the fixit live filesystem and also mounting zroot and using the files there in case they were different. Disclaimer: I haven't gotten (enough) morning-coffee yet, but... Disclaimer 2: at times tracking how zfs-booting is done in the different versions can be a bit tricky. This is a moving target, and I've lost track of the 8-branch. That said, assuming you have the correct bootcode (gptzfsboot), here's what might have happened: You installed 8.2, with a loader supporting zfs. Then you upgraded your /boot-stuffs, and bootcode on disk (correctly), but got left with a loader without zfs support. Then tried to upgrade the bootcode, but you're still left with a loader not supporting zfs. If I recall correctly, then the zfs-bootcode for 9+ will use zfsloader (supporting zfs and built by default), while earlier versions depend on loader with zfs support (built without by default). If that's the case, you could dump LOADER_ZFS_SUPPORT into /etc/make.conf and rebuild/reinstall it, or install /boot/loader from the fixit (if it has zfs support in 8.4). That's my first thought at least... If that doesn't fix it (remember backups of any files you replace or upgrade), it'd be interesting to see the output of: ls -l /boot/*loader /boot/*boot On the /boot you're using. Anything that didn't get built or installed? Also, did you snapshot your zfs before upgrading? Could be a working /boot/loader there, which might be the easiest way to get the system up, before rebuilding with ZFS-capable loader... if I'm right, which isn't a given (ref disclaimers). Terje ___ 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.1 - boot failures (upgrades and clean installs) - root FS corrupt?
On 18/09/2010 6:19 PM, I wrote: Any suggestions on debugging what's going on? I'd really like to be able to get current. Dave. Hmm. Further diagnosis is even more interesting. The output from the installation (console 2 - Alt-F2) shows segmentation faults and core dumps for mv, rm and ln commands - and the list gets longer if I try to do anything on the emergency shell (Alt-F4). Adding a user doesn't auto-populate the UID nor the shell, then claims that the user already exists. I also neglected to say that I am installing the AMD64 version - perhaps this is useful information :) Dave. -- David Rawling Principal Consultant PD Consulting And Security 20 Goodin Road Baulkham Hills, NSW 2153 Australia Mob: +61 412 135 513 Email: d...@pdconsec.net Please note that whilst we take all care, neither PD Consulting and Security nor the sender accepts any responsibility for viruses and it is your responsibility to scan for viruses. The contents are intended only for use by the addressee and may contain confidential and/or privileged material and any use by other than the intended recipient is prohibited. If you received this in error, please inform the sender and/or addressee immediately and delete the material. ___ 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 6.2 Boot Issue
Sorry if this is obvious but I just did this myself with similar problems. Is your /boot a seperate partition? If so, bsd will not boot. It will happily install but will come back with a no kernel found error or similar. I believe this is because only the / partition is mounted at that point. Hope this helps. Craig Russell --- [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Jay ___ 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: FreeBSD 6.2 Boot Issue
At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Boot Issue
Both of those checked OK. Is it possible I have specified the C/H/S incorrectly during setup? Thanks, Jay At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Boot Issue
At 12:52 PM 4/26/2007, [EMAIL PROTECTED] wrote: Both of those checked OK. Is it possible I have specified the C/H/S incorrectly during setup? Thanks, What is your type and model hard drive? Did you specify the geometry when you ran sysinstall? How did you partition and slice the hard drive? -Derek Jay At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Boot Issue
At 12:52 PM 4/26/2007, [EMAIL PROTECTED] wrote: Both of those checked OK. Is it possible I have specified the C/H/S incorrectly during setup? Thanks, What is your type and model hard drive? Did you specify the geometry when you ran sysinstall? How did you partition and slice the hard drive? -Derek Derek, In the server I currently have three 376595-001 drives (146 GB serial SCSI) and three 432146-001 drives (300 GB serial SCSI). These drives are configured as a single drive in a RAID 5 configuration. I did not specify any geometry during the installation. I have the hard drive configured as a single partition with the appropriate lables (/, /var, /usr, /tmp and a swap area). Thanks for your help. Jay Jay At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Boot Issue
At 01:16 PM 4/26/2007, [EMAIL PROTECTED] wrote: At 12:52 PM 4/26/2007, [EMAIL PROTECTED] wrote: Both of those checked OK. Is it possible I have specified the C/H/S incorrectly during setup? Thanks, What is your type and model hard drive? Did you specify the geometry when you ran sysinstall? How did you partition and slice the hard drive? -Derek Derek, In the server I currently have three 376595-001 drives (146 GB serial SCSI) and three 432146-001 drives (300 GB serial SCSI). These drives are configured as a single drive in a RAID 5 configuration. I did not specify any geometry during the installation. I have the hard drive configured as a single partition with the appropriate lables (/, /var, /usr, /tmp and a swap area). Thanks for your help. Sounds like your system is not booting, but you're not getting any error message. Check the boot order in your BIOS, and turn on diagnostic boot messages if they are not turned on. Does they system boot from a CD ok? -Derek Jay Jay At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Boot Issue
At 01:16 PM 4/26/2007, [EMAIL PROTECTED] wrote: At 12:52 PM 4/26/2007, [EMAIL PROTECTED] wrote: Both of those checked OK. Is it possible I have specified the C/H/S incorrectly during setup? Thanks, What is your type and model hard drive? Did you specify the geometry when you ran sysinstall? How did you partition and slice the hard drive? -Derek Derek, In the server I currently have three 376595-001 drives (146 GB serial SCSI) and three 432146-001 drives (300 GB serial SCSI). These drives are configured as a single drive in a RAID 5 configuration. I did not specify any geometry during the installation. I have the hard drive configured as a single partition with the appropriate lables (/, /var, /usr, /tmp and a swap area). Thanks for your help. Sounds like your system is not booting, but you're not getting any error message. Check the boot order in your BIOS, and turn on diagnostic boot messages if they are not turned on. Does they system boot from a CD ok? -Derek Yes, the system boots from CD just fine. And, it is able to run newfs during the install without any problems. The total size of the drive is 683.5 GB. The boot order in the BIOS is CD and then E200i controller. Thanks, Jay Jay Jay At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Boot Issue
At 01:31 PM 4/26/2007, [EMAIL PROTECTED] wrote: At 01:16 PM 4/26/2007, [EMAIL PROTECTED] wrote: At 12:52 PM 4/26/2007, [EMAIL PROTECTED] wrote: Both of those checked OK. Is it possible I have specified the C/H/S incorrectly during setup? Thanks, What is your type and model hard drive? Did you specify the geometry when you ran sysinstall? How did you partition and slice the hard drive? -Derek Derek, In the server I currently have three 376595-001 drives (146 GB serial SCSI) and three 432146-001 drives (300 GB serial SCSI). These drives are configured as a single drive in a RAID 5 configuration. I did not specify any geometry during the installation. I have the hard drive configured as a single partition with the appropriate lables (/, /var, /usr, /tmp and a swap area). Thanks for your help. Sounds like your system is not booting, but you're not getting any error message. Check the boot order in your BIOS, and turn on diagnostic boot messages if they are not turned on. Does they system boot from a CD ok? -Derek Yes, the system boots from CD just fine. And, it is able to run newfs during the install without any problems. The total size of the drive is 683.5 GB. The boot order in the BIOS is CD and then E200i controller. Thanks, Jay Can you boot the CD, mount the root filesystem and check that everything is there (/boot /kernel, etc.) -Derek Jay Jay At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Boot Issue
I have been able to make the system boot. I had to change one of the Array options to Max Boot enabled 8gb. I found this in an older post concerning a different controller, but it worked. Specifically, my server is an ML350 with the E200i controller. Thanks to everyone for your help. Jay At 01:31 PM 4/26/2007, [EMAIL PROTECTED] wrote: At 01:16 PM 4/26/2007, [EMAIL PROTECTED] wrote: At 12:52 PM 4/26/2007, [EMAIL PROTECTED] wrote: Both of those checked OK. Is it possible I have specified the C/H/S incorrectly during setup? Thanks, What is your type and model hard drive? Did you specify the geometry when you ran sysinstall? How did you partition and slice the hard drive? -Derek Derek, In the server I currently have three 376595-001 drives (146 GB serial SCSI) and three 432146-001 drives (300 GB serial SCSI). These drives are configured as a single drive in a RAID 5 configuration. I did not specify any geometry during the installation. I have the hard drive configured as a single partition with the appropriate lables (/, /var, /usr, /tmp and a swap area). Thanks for your help. Sounds like your system is not booting, but you're not getting any error message. Check the boot order in your BIOS, and turn on diagnostic boot messages if they are not turned on. Does they system boot from a CD ok? -Derek Yes, the system boots from CD just fine. And, it is able to run newfs during the install without any problems. The total size of the drive is 683.5 GB. The boot order in the BIOS is CD and then E200i controller. Thanks, Jay Can you boot the CD, mount the root filesystem and check that everything is there (/boot /kernel, etc.) -Derek Jay Jay At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Boot Issue
On Thu, Apr 26, 2007 at 06:31:05PM -, [EMAIL PROTECTED] wrote: At 01:16 PM 4/26/2007, [EMAIL PROTECTED] wrote: At 12:52 PM 4/26/2007, [EMAIL PROTECTED] wrote: Both of those checked OK. Is it possible I have specified the C/H/S incorrectly during setup? Thanks, What is your type and model hard drive? Did you specify the geometry when you ran sysinstall? How did you partition and slice the hard drive? -Derek Derek, In the server I currently have three 376595-001 drives (146 GB serial SCSI) and three 432146-001 drives (300 GB serial SCSI). These drives are configured as a single drive in a RAID 5 configuration. I did not specify any geometry during the installation. I have the hard drive configured as a single partition with the appropriate lables (/, /var, /usr, /tmp and a swap area). Thanks for your help. Sounds like your system is not booting, but you're not getting any error message. Check the boot order in your BIOS, and turn on diagnostic boot messages if they are not turned on. Does they system boot from a CD ok? -Derek Yes, the system boots from CD just fine. And, it is able to run newfs during the install without any problems. The total size of the drive is 683.5 GB. The boot order in the BIOS is CD and then E200i controller. One question you didn't quite answer. Someone asked 'how did you partition the device. I think the intent was to ask what process did you use - for example sysinstall or manual fdisk/bsdabel/newfs? Did you first create a single slice on the drive and then divide that slice in to partitions? In either case, you must tell either sysinstall or fdisk bsdlabel to make the drive and slice bootable, to write either a generic boot record or the FreeBSD MBR in fdisk or the fdisk portion of sysinstall and then select make the slice bootable in bsdlabel or the bsdlabel part of sysinstall. If you don't, it won't find a bootable device there. If you have done those things, then, back to the drawing board. jerry Thanks, Jay Jay Jay At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Boot Issue
On Thu, Apr 26, 2007 at 06:31:05PM -, [EMAIL PROTECTED] wrote: At 01:16 PM 4/26/2007, [EMAIL PROTECTED] wrote: At 12:52 PM 4/26/2007, [EMAIL PROTECTED] wrote: Both of those checked OK. Is it possible I have specified the C/H/S incorrectly during setup? Thanks, What is your type and model hard drive? Did you specify the geometry when you ran sysinstall? How did you partition and slice the hard drive? -Derek Derek, In the server I currently have three 376595-001 drives (146 GB serial SCSI) and three 432146-001 drives (300 GB serial SCSI). These drives are configured as a single drive in a RAID 5 configuration. I did not specify any geometry during the installation. I have the hard drive configured as a single partition with the appropriate lables (/, /var, /usr, /tmp and a swap area). Thanks for your help. Sounds like your system is not booting, but you're not getting any error message. Check the boot order in your BIOS, and turn on diagnostic boot messages if they are not turned on. Does they system boot from a CD ok? -Derek Yes, the system boots from CD just fine. And, it is able to run newfs during the install without any problems. The total size of the drive is 683.5 GB. The boot order in the BIOS is CD and then E200i controller. One question you didn't quite answer. Someone asked 'how did you partition the device. I think the intent was to ask what process did you use - for example sysinstall or manual fdisk/bsdabel/newfs? Did you first create a single slice on the drive and then divide that slice in to partitions? In either case, you must tell either sysinstall or fdisk bsdlabel to make the drive and slice bootable, to write either a generic boot record or the FreeBSD MBR in fdisk or the fdisk portion of sysinstall and then select make the slice bootable in bsdlabel or the bsdlabel part of sysinstall. If you don't, it won't find a bootable device there. If you have done those things, then, back to the drawing board. jerry I used sysinstall to partition the device. And, I selected boot mgr for the boot manager. When the system booted, it would boot to the point to where I had to press F1 to boot FreeBSD. When F1 was pressed, or the timeout was waited for, the system would just beep, the drive lights would flash, and nothing else would happen. Sorry for the confusion. Jay Thanks, Jay Jay Jay At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.2 Boot Issue
On Thu, 26 Apr 2007 [EMAIL PROTECTED] wrote: On Thu, Apr 26, 2007 at 06:31:05PM -, [EMAIL PROTECTED] wrote: At 01:16 PM 4/26/2007, [EMAIL PROTECTED] wrote: At 12:52 PM 4/26/2007, [EMAIL PROTECTED] wrote: Both of those checked OK. Is it possible I have specified the C/H/S incorrectly during setup? Thanks, What is your type and model hard drive? Did you specify the geometry when you ran sysinstall? How did you partition and slice the hard drive? -Derek Derek, In the server I currently have three 376595-001 drives (146 GB serial SCSI) and three 432146-001 drives (300 GB serial SCSI). These drives are configured as a single drive in a RAID 5 configuration. I did not specify any geometry during the installation. I have the hard drive configured as a single partition with the appropriate lables (/, /var, /usr, /tmp and a swap area). Thanks for your help. Sounds like your system is not booting, but you're not getting any error message. Check the boot order in your BIOS, and turn on diagnostic boot messages if they are not turned on. Does they system boot from a CD ok? -Derek Yes, the system boots from CD just fine. And, it is able to run newfs during the install without any problems. The total size of the drive is 683.5 GB. The boot order in the BIOS is CD and then E200i controller. One question you didn't quite answer. Someone asked 'how did you partition the device. I think the intent was to ask what process did you use - for example sysinstall or manual fdisk/bsdabel/newfs? Did you first create a single slice on the drive and then divide that slice in to partitions? In either case, you must tell either sysinstall or fdisk bsdlabel to make the drive and slice bootable, to write either a generic boot record or the FreeBSD MBR in fdisk or the fdisk portion of sysinstall and then select make the slice bootable in bsdlabel or the bsdlabel part of sysinstall. If you don't, it won't find a bootable device there. If you have done those things, then, back to the drawing board. jerry I used sysinstall to partition the device. And, I selected boot mgr for the boot manager. When the system booted, it would boot to the point to where I had to press F1 to boot FreeBSD. When F1 was pressed, or the timeout was waited for, the system would just beep, the drive lights would flash, and nothing else would happen. Sorry for the confusion. Jay Thanks, Jay Jay Jay At 10:49 AM 4/26/2007, [EMAIL PROTECTED] wrote: I have installed FreeBSD 6.2 on an HP Proliant G5 server with an E200i Smart Controller installed. The installation was flawless. When I reboot the server after the installation, the boot loader screen is displayed. I press F1 and the system beeps and comes back to the boot loader prompt. What should I be looking at? I am at a loss since I usually end up with leftover hardware and this time I acutally got to purchase new hardware just for this project. Any suggestions would be greatly appreciated. Thanks for your help. Check your BIOS that you are ALLOWING the boot sector to be written. If that is OK, try disabling hyperthreading if that is turned on in your BIOS. -Derek Jay, Try another bootloader, such as GAG (http://gag.sf.net) or Grub (this requires a BSD slice write capable LiveCD unfortunately to install grub via ports). I've come across some cases with some computers where GAG worked where Grub and the BSD That isn't a long term solution to your problem, but it's a workaround until the actual root cause can be determined. HTT shouldn't be the cause, unless the hardware architects that designed your PATA EIDE controller did something fubar'ed in the design, I'd think. Also, please bottom-post, not top-post on this list. Thanks! -Garrett ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FREEBSD I386 BOOT HANG
On Mon, 5 Jun 2006 03:45:47 -0700 (PDT) CATHERINE LORENZ [EMAIL PROTECTED] wrote: I HAVE A TOSHIBA LAPTOP I HAVE TRIED EVERYTHING TO LOAD THE CD VERSION 5.2.1 FREEBSD ONTO MY LAPTOP WITH NO LUCK. IT FREEZES AFTER THE IT BOOTS, I DID DISABLE THE ACPI BUT IT STILL FROZE. IS THERE A WAY TO FIX THIS PROBLEM? First of all, are you able to try a supported / non-dev version of FreeBSD (I'd strongly suggest 6.1-RELEASE)? If not, where does it get to before freezing? Last message on the screen? You've tried leaving it there for more than 30 seconds (my (rather old) CD drive takes half a minute or so to be probed)? THANKS IOTA By the way, you might wanna check your caps lock / read up on netiquette (see RFC 1855) :-) -- Nick Withers email: [EMAIL PROTECTED] Web: http://www.nickwithers.com Mobile: +61 414 397 446 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FREEBSD I386 BOOT HANG
CATHERINE LORENZ wrote: I HAVE A TOSHIBA LAPTOP I HAVE TRIED EVERYTHING TO LOAD THE CD VERSION 5.2.1 FREEBSD ONTO MY LAPTOP WITH NO LUCK. IT FREEZES AFTER THE IT BOOTS, I DID DISABLE THE ACPI BUT IT STILL FROZE. IS THERE A WAY TO FIX THIS PROBLEM? 5.2.1 is so old that it is no longer supported: please try either FreeBSD 6.1 or 5.5 instead... (You also have a stuck CAPSLOCK key.) -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD-multi-boot
Vlad GURDIGA wrote: Hello all, I have these slices on my HDD: - /dev/ad0s1 - Windows XP - /dev/ad0s2 - FreeBSD/i386 - /dev/ad0s3 - FreeBSD/amd64 and I want them all in my boot.ini. Till now I succeeded with FreeBSD/i386 (first did dd if=/dev/ad0s2 of=boot.bsd bs=512 count=1 from FreeBSD/i386, then copied the resulted boot.bsd file to Windows C:\) I did the same trick with FreeBSD/amd64 (first did dd if=/dev/ad0s3 of=boot64.bsd bs=512 count=1 from FreeBSD/amd64, then copied the resulted boot64.bsd file to Windows C:\) so, my boot.ini looks like this: ---cut here-- [boot loader] timeout=3 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS=Microsoft Windows XP Professional /noexecute=optin /fastdetect C:\boot.bsd=UNIX FreeBSD/i386 C:\boot64.bsd=UNIX FreeBSD/amd64 ---cut here-- Now, the problem is that when I choose UNIX FreeBSD/amd64 from the boot menu, it boots UNIX FreeBSD/i386!!! What did I missed? this page may help:- http://www.ubergeek.co.uk/howtos/grub-freebsd-windowsxp.html Cheers Danny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Windows Boot?
If for what ever reason the FreeBSD boot loader does load windows, is there a way to repair the windows boot sector? I remember trying this in the past with ill results. Probably depends on what is wrong. Probably there is some MS utility that can repair it. Someone else will have to talk the MS stuff. Make sure you understand the different parts. Your terminology wanders a bit. The FreeBSD MBR and not the boot loader would be the only part that has anything to do with booting a Windos or any non FreeBSD OS. I think that is what you mean by boot loader though. The MBR only just recognized that the slice is bootable and reads in the boot sector and turns over control to it. It does nothing else with the Win sector or loader. jerry ___ 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: FreeBSD Windows Boot?
Jerry McAllister wrote: If for what ever reason the FreeBSD boot loader does load windows, is there a way to repair the windows boot sector? I remember trying this in the past with ill results. Probably depends on what is wrong. Probably there is some MS utility that can repair it. Someone else will have to talk the MS stuff. Make sure you understand the different parts. Your terminology wanders a bit. The FreeBSD MBR and not the boot loader would be the only part that has anything to do with booting a Windos or any non FreeBSD OS. I think that is what you mean by boot loader though. The MBR only just recognized that the slice is bootable and reads in the boot sector and turns over control to it. It does nothing else with the Win sector or loader. jerry I could be wrong, but I believe using the MS version of 'fdisk' fixes the problem. Run this command from the C: prompt: fdisk /mbr See if that corrects the problem. -- Gerard ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 Boot issues - reposted
On Saturday 21 May 2005 03:42, the author Thomas Hurst contributed to the dialogue on Re: FreeBSD 5.3 Boot issues - reposted: * Vizion ([EMAIL PROTECTED]) wrote: This system has been built in a mini ATX case and has a Proxim Harmony 802.11a Model 8150 PCI card on (I am on a boat - then intention is to be able to disconnect it from the ships network, lug it to a position in range of a wireless network and do a portupgrade as the need arises chuckles). Is this card recognized by freebsd. Is there a suitable driver? How do I set it up? Looks like it's based on the Prism2 chipset, which should be supported by the wi(4) driver (man wi). kldload if_wi and see if it's detected, and follow the examples in the driver manpage to set it up. Aha -- actually I found it is based on the Atheros chips BUT is configured on the pci card to be recognized as fw!!! anyway your input made me get the card out and I now have it working.. Thanks David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 Boot issues - reposted
* Vizion ([EMAIL PROTECTED]) wrote: This system has been built in a mini ATX case and has a Proxim Harmony 802.11a Model 8150 PCI card on (I am on a boat - then intention is to be able to disconnect it from the ships network, lug it to a position in range of a wireless network and do a portupgrade as the need arises chuckles). Is this card recognized by freebsd. Is there a suitable driver? How do I set it up? Looks like it's based on the Prism2 chipset, which should be supported by the wi(4) driver (man wi). kldload if_wi and see if it's detected, and follow the examples in the driver manpage to set it up. 2. Uhicio [GIANT LOCKED] What does this mean? It means the uhci (USB Host Controller) driver isn't multi-processor safe, and thus needs to grab the Big Giant Lock around the kernel when it's doing stuff to operate safely. Don't worry about it; if you really want to get rid of it, it looks like it's been made MPSAFE in 5.4. 3. (da1:umass-sim0:0:0:1): Unretryable error What is the significance if any of these lines? USB mass storage devices use the SCSI Direct Access (da) driver. You don't have any memory cards in your card reader, so attempts to read from them to determine the size of the disks are producing an unretryable error. Again, this is normal. 4. I want to use energy saving (mainly to protect the drive from unnecessary risk of damage in rough weather) to turn off the hard drive when access is not required. How do I do that? Look at sysutils/ataidle. Taking measures to avoid unnecessary disk access is left as an exercise for the reader ;) -- Thomas 'Freaky' Hurst http://hur.st/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 5.3 Boot issues - reposted
On Saturday 21 May 2005 03:42, the author Thomas Hurst contributed to the dialogue on Re: FreeBSD 5.3 Boot issues - reposted: * Vizion ([EMAIL PROTECTED]) wrote: This system has been built in a mini ATX case and has a Proxim Harmony 802.11a Model 8150 PCI card on (I am on a boat - then intention is to be able to disconnect it from the ships network, lug it to a position in range of a wireless network and do a portupgrade as the need arises chuckles). Is this card recognized by freebsd. Is there a suitable driver? How do I set it up? Looks like it's based on the Prism2 chipset, which should be supported by the wi(4) driver (man wi). kldload if_wi and see if it's detected, and follow the examples in the driver manpage to set it up. 2. Uhicio [GIANT LOCKED] What does this mean? It means the uhci (USB Host Controller) driver isn't multi-processor safe, and thus needs to grab the Big Giant Lock around the kernel when it's doing stuff to operate safely. Don't worry about it; if you really want to get rid of it, it looks like it's been made MPSAFE in 5.4. 3. (da1:umass-sim0:0:0:1): Unretryable error What is the significance if any of these lines? USB mass storage devices use the SCSI Direct Access (da) driver. You don't have any memory cards in your card reader, so attempts to read from them to determine the size of the disks are producing an unretryable error. Again, this is normal. 4. I want to use energy saving (mainly to protect the drive from unnecessary risk of damage in rough weather) to turn off the hard drive when access is not required. How do I do that? Look at sysutils/ataidle. Taking measures to avoid unnecessary disk access is left as an exercise for the reader ;) Thankl you very much for a very helpful posting David -- 40 yrs navigating and computing in blue waters. English Owner Captain of British Registered 60' bluewater Ketch S/V Taurus. Currently in San Diego, CA. Sailing May bound for Europe via Panama Canal. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: freebsd not boot
Hi, Thanks for the reply. My PC Hardware is as follows : Intel Pentium pro . 128K Ram, npx0 : math processor PCI Bus ATI Mach64-GZ graphics accelerator Intel PIIX4ATA33 Controller USD Controller 4G disk 2 3COM 3C90 Network Cards CD - ROM USB Keyboard / Mouse The interrupts are as follows : 1 Keyboard 3 and 4 Serial Ports 5 and 10 3Com Network Cards 9 USB Controller 11 Graphics Card 12 Mouse 14 15 IDE hard disk The PC boots and displays the Devices and interrupt list : IDE Controller 14/15 Serial Bus controller 9 N/W controller 5 N/W controller 10 display console 11 it then tries to boot off CD - fail (No CD in) it then performs another hard reset (I think when trying to boot of Hard Drive) I have tried to install FreeBSD onto a 2G Partition. I have played around with the Kernel configuration but it still resets at same point even when I don't delete any drivers and don't perform Kernel Configuration!!! Through the Fixit CD , I performed a Disklabel . Here are the results : bytes / sector :512 sectors / track :63 tracks / cylinders:255 sectors / cylinder:16065 cylinders : 259 sectors / unit : 4768387 8 partitions : sizeoffset fstype fsize bsize - a 262144 0 4.2BSD 204894 b 1017008 262144 swap c 4176837 0 unused e 524288 1279152 4.2BSD 204816384 f 524288 1803440 4.2BSD 204816384 g 1849109 2327728 4.2BSD 204816384 But I notice there is no /etc/fstab file. Hope this helps!! Pat -Original Message- From: Vulpes Velox [mailto:[EMAIL PROTECTED] Sent: 20 February 2004 19:00 To: Pat Saunders Cc: '[EMAIL PROTECTED]' Subject: Re: freebsd not boot On Fri, 20 Feb 2004 16:21:43 - Pat Saunders [EMAIL PROTECTED] wrote: Hi, I am trying to run freebsd 4.9 on a PC / IDE architecture. I have one IDE drive and two 3COM 3c90 Network Cards and CD-ROM The PC will be a dedicated FreeBSD box. I have installed freebsd v4.9 , using the whole 4G disk which is bootable and installed 'Standard MBR - no boot manager' and disabled all the drivers (SCSI) that I do not use. The problem is when I reboot nothing happens apart from another hard reset. The PC then does a Hard reset and the same recursive process occurs again. No, useful messages appear at all !!! I have created bootable floppies which I can boot from but I am not sure what to perform next , apart from re-install with different options which result in the same depressing results. I am not sure what to do regarding the 'Fixit' option as most shell commands do not work. Any help would be appreciated. Pat Well more info on the hardware would be useful... How far does it get befor it reboots? Given that you went throught removing all the scsi drivers, I am guessing this means you made a custom kernel config, could you post that too. It sounds sorta like something important got removed from the kernel or something... _ This message has been checked for all known viruses on behalf of Vivista by MessageLabs. http://www.messagelabs.com or Email: [EMAIL PROTECTED] Vivista formerly Securicor Information Systems for further information http://www.vivista.co.uk ** The information contained in this e-mail message is intended only for the individuals named above. If you are not the intended recipient, you should be aware that any dissemination, distribution, forwarding or other duplication of this communication is strictly prohibited. The views expressed in this e-mail are those of the individual author and not necessarily those of Vivista Limited. Prior to taking any action based upon this e-mail message you should seek appropriate confirmation of its authenticity. If you have received this e-mail in error, please immediately notify the sender by using the e-mail reply facility. ** _ This message has been checked for all known viruses on behalf of Vivista by MessageLabs. http://www.messagelabs.com or Email: [EMAIL PROTECTED] Vivista formerly Securicor Information Systems for further information http://www.vivista.co.uk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: freebsd not boot
On Fri, 20 Feb 2004 16:21:43 - Pat Saunders [EMAIL PROTECTED] wrote: Hi, I am trying to run freebsd 4.9 on a PC / IDE architecture. I have one IDE drive and two 3COM 3c90 Network Cards and CD-ROM The PC will be a dedicated FreeBSD box. I have installed freebsd v4.9 , using the whole 4G disk which is bootable and installed 'Standard MBR - no boot manager' and disabled all the drivers (SCSI) that I do not use. The problem is when I reboot nothing happens apart from another hard reset. The PC then does a Hard reset and the same recursive process occurs again. No, useful messages appear at all !!! I have created bootable floppies which I can boot from but I am not sure what to perform next , apart from re-install with different options which result in the same depressing results. I am not sure what to do regarding the 'Fixit' option as most shell commands do not work. Any help would be appreciated. Pat Well more info on the hardware would be useful... How far does it get befor it reboots? Given that you went throught removing all the scsi drivers, I am guessing this means you made a custom kernel config, could you post that too. It sounds sorta like something important got removed from the kernel or something... ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Wont Boot
Matt wrote: I have a freeBSD machine that wont boot due To the fact that its checking an ethernet port that does not exist. How can i disable it, or get rid of it? Can you be more specific in describing your problem? Do you get an error message? Does the system stop responding during boot? How far into the boot does it get? What makes you think that an ethernet port is the problem? For future reference, you might want to look at http://www.lemis.com/questions.html in order to help you ask more effective questions in future. Thanks. Andrew. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-questions in the body of the message
