Re: Boot failure mounting FreeBSD-8.0beta4 DVD
On Thu, Sep 17, 2009 at 05:13:26PM -0300, LuizBCampos wrote: > > After I had downloaded 8.0beta4 amd64 and recorded it on DVD on my > Linux, I dont get booting this OS from DVD. I've followed all the info > from man growisofs but it's unable to boot Can you be somewhat more specific? What is the error that you get? Is your system set up to boot from DVD? ># growisofs -dvd-compat -Z /dev/dvd=8.0-BETA4... what's > wrong? Does the checksum of the DVD image match the one that you can find on the FTP site? If you run 'file' on the image, does it say that it is a bootable ISO 9660 filesystem? Ditto for the burned DVD? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpOuAvLx20aI.pgp Description: PGP signature
Re: Boot failure
On Sat, Aug 08, 2009 at 10:12:16AM -0400, Jerry wrote: > On Sat, 8 Aug 2009 15:38:25 +0200 > Roland Smith wrote: > > > On Sat, Aug 08, 2009 at 07:53:40AM -0400, Identry wrote: > > > >> Looks like your hardware is dying/dead. > > > > > > > > Sadly, I agree. > > > > > > I'd get to the point of swapping hardware one at a time until it > > > > fixes, or until you exhaust your options. Have any kind of > > > > support contract with the OEM? > > > > > > I do have a support contract and I'm going to dump this right in > > > their lap. Two machines we bought from them -- pretty expensive > > > ones -- and both have had hardware failures. And they are only a > > > couple of years old. I'm not too happy with them at the moment. > > > > For computers, that is already old these days. At $WORK the Dell > > computers (both desktops and servers AFAIK) that we use are ditched at > > the first problem after the warranty runs out which is after three > > years, I believe. > > > > Roland > > Given the concept of: "Planned (?) Obsolescence", that is probably a > wise decision. The problem is that FBSD does not always either partially > or fully support new hardware. Updating in such a scenario should > therefore be undertaken with extreme care. True. Therefore I don't like getting systems from builders like Dell who focus on MS windows. I prefer specifying which parts go into my machines, because I can check for compatibility beforehand. > For example, nVidia cards > with 64 bit drivers are not supported in FBSD. Personally, I love nVidia > cards; however, this problem has caused me to put off updating my > systems temporarily. However, if this problem is not rectified soon, I > might have to consider a different OS. Considering that nVidia is > already shipping drivers for Win7, both 32 & 64 bit, the fact that they > are not supported in FBSD is rather pathetic. To be fair, nvidia requested (and were waiting for) some changes made to the FreeBSD amd64 kernel. I think these changes are now in 8-CURRENT, but I'm not sure. However, NVidia choose to create their own unified 3D support infrastructure instead of supporting the X developers with documentation and specifications. That means that nobody but NVidia can maintain their drivers. So instead of wielding the collaborative power of open source, they choose to go their own way. IMHO that is not very smart. (and yes, they doubtlessly have their reasons; NDAs with suppliers, "IP" borrowed from others, whatever) I suspect they'll tire one day of doing all this work themselves. But until that day, I'll buy ATI or intel graphics hardware that _is_ supported by open-source drivers. So I'll not be left with unsupported hardware if the hardware supplier chooses to focus his attentions elswhere. Nor will I face bugs that we cannot fix because of binary-only drivers. Since I find it unacceptable to be a hostage to the whims of a hardware supplier, I will not support manufacturers who stick to closed-source drivers, and I would implore others to do the same. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgp1KNzr2thhs.pgp Description: PGP signature
Re: Boot failure
On Sat, 8 Aug 2009 15:38:25 +0200 Roland Smith wrote: > On Sat, Aug 08, 2009 at 07:53:40AM -0400, Identry wrote: > > >> Looks like your hardware is dying/dead. > > > > > > Sadly, I agree. > > > > I'd get to the point of swapping hardware one at a time until it > > > fixes, or until you exhaust your options. Have any kind of > > > support contract with the OEM? > > > > I do have a support contract and I'm going to dump this right in > > their lap. Two machines we bought from them -- pretty expensive > > ones -- and both have had hardware failures. And they are only a > > couple of years old. I'm not too happy with them at the moment. > > For computers, that is already old these days. At $WORK the Dell > computers (both desktops and servers AFAIK) that we use are ditched at > the first problem after the warranty runs out which is after three > years, I believe. > > Roland Given the concept of: "Planned (?) Obsolescence", that is probably a wise decision. The problem is that FBSD does not always either partially or fully support new hardware. Updating in such a scenario should therefore be undertaken with extreme care. For example, nVidia cards with 64 bit drivers are not supported in FBSD. Personally, I love nVidia cards; however, this problem has caused me to put off updating my systems temporarily. However, if this problem is not rectified soon, I might have to consider a different OS. Considering that nVidia is already shipping drivers for Win7, both 32 & 64 bit, the fact that they are not supported in FBSD is rather pathetic. -- Jerry ges...@yahoo.com Most people in this society who aren't actively mad are, at best, reformed or potential lunatics. Susan Sontag ___ 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: Boot failure
On Fri, Aug 07, 2009 at 04:41:57PM -0400, Identry wrote: > > Okay, back in the data center. I ran fsck_ffs -fp on my root file > > system and it returned with no errors. It just printed some > > information about number of files, used, free space, etc., ending with > > the interesting fact of .3% fragmentation. > > > > Then I reran it without the -fp and it printed Phase 1 - Phase 5, no > > errors, and again some info on the files. That's good news. Then at least your filesystems are OK. > > So, it looks like there is nothing wrong with the root partition. > > Which again raises the question, why won't it mount during the boot > > process? > > > > I'm going to try booting with verbose logging and see what that last > > line printed is... > > Well, something got worse. After running fsck_ffs with no errors, I > tried to boot the machine. It got to the point where it printed: > > > Booting from BIOS Partition 0 > PS2 keyboard detected > PS2 mouse detected > > and it just hangs at that point. Well, if it won't load the OS from disk, but you can mount the partitions when booting from CD, I'd guess that there could be some issue with your MegaRAID card. It could be that the megaraid card needs more time to get ready than a normal boot gives it. Are you sure that the card is OK? If you can get your hands on a spare megaRAID card, maybe you should try to switch them? If not, you're booting from the drives attached to this card, yes? So reboot and try to get inside the BIOS of the card and see if that can tell you something... When booting the card should display a message about how to enter the cards setup. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpr9q5nB4G1P.pgp Description: PGP signature
Re: Boot failure
> Well, something got worse. After running fsck_ffs with no errors, I > tried to boot the machine. It got to the point where it printed: > > > Booting from BIOS Partition 0 > PS2 keyboard detected > PS2 mouse detected > > and it just hangs at that point. Worse and worse... The machine won't boot from the CD anymore. I can't even get it into SETUP. It just hangs on this screen: (I had hit F2 to enter setup) Version 1.17.1057 Copyright 2005-2007 American Megatrends, Inc Entering SETUP Bios Version: S5000.86B ... etc Platform ID: S5000PAL 8 GB system memory found Current Memory Speed: 667 MT/s (333 MHz) Intel Xeon CPU E5345 @ 2.33Ghz Intel Xeon CPU E5345 @ 2.33 Ghz Booting from BIOS Partition 0 PS2 keyboard detected PS2 mouse detected The same thing happens if I don't hit F2, except it says Hit F2 to enter SETUP at the top. Well... I guess we are back to hardware problem? I'm not sure what else to try at this point. -- John ___ 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: Boot failure
> Okay, back in the data center. I ran fsck_ffs -fp on my root file > system and it returned with no errors. It just printed some > information about number of files, used, free space, etc., ending with > the interesting fact of .3% fragmentation. > > Then I reran it without the -fp and it printed Phase 1 - Phase 5, no > errors, and again some info on the files. > > So, it looks like there is nothing wrong with the root partition. > Which again raises the question, why won't it mount during the boot > process? > > I'm going to try booting with verbose logging and see what that last > line printed is... Well, something got worse. After running fsck_ffs with no errors, I tried to boot the machine. It got to the point where it printed: Booting from BIOS Partition 0 PS2 keyboard detected PS2 mouse detected and it just hangs at that point. -- John ___ 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: Boot failure
> Non-printable-character (NPC) > > NPCs may be a culprit for a file that used to work, now doesn't. Or a > inode oddity. > > I've been following this thread but haven't chipped in because of > timing (you driving to the datacenter). > > Here's what I'd consider: > # mv /etc/fstab /etc/old-fstab > > and recreate a fstab from hand. Example: > > /dev/mfid0s1a / ufs rw 1 1 I guess I could use the existing fstab as a model... just retype it using vi. I checked the date on fstab... it hasn't been changed since the server was installed, but I guess it's worth a try. Thanks for the idea. > I doubt controller or disk problems, since a livecd can mount it. a > fsck -y on a clean filesystem won't report anything. You were right about this. -- John ___ 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: Boot failure
>> > I think you should start by reading the manual pages for fsck and >> > fsck_ffs. I would start with 'fsck_ffs -fp /dev/yourdevicenode'. Okay, back in the data center. I ran fsck_ffs -fp on my root file system and it returned with no errors. It just printed some information about number of files, used, free space, etc., ending with the interesting fact of .3% fragmentation. Then I reran it without the -fp and it printed Phase 1 - Phase 5, no errors, and again some info on the files. So, it looks like there is nothing wrong with the root partition. Which again raises the question, why won't it mount during the boot process? I'm going to try booting with verbose logging and see what that last line printed is... -- John ___ 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: Boot failure
On 8/7/09, Identry wrote: >> If you did not touch the kernel, there is no need to boot GENERIC! Plus >> you >> have said that this box is running PF, which is not in the GENERIC kernel! >> Personally, I am interested in knowing why the system does not mount the >> root partition on its own when you can do it by hand and it does not >> complain. > > Me too. > >> Did you by any chance change anyting in /etc/fstab? > > No, this has never changed since original install. > Non-printable-character (NPC) NPCs may be a culprit for a file that used to work, now doesn't. Or a inode oddity. I've been following this thread but haven't chipped in because of timing (you driving to the datacenter). Here's what I'd consider: # mv /etc/fstab /etc/old-fstab and recreate a fstab from hand. Example: /dev/mfid0s1a / ufs rw 1 1 If you dumpfs the other bsd partitions, you can see "last mounted on". That might reflect the live-cd mountpoints, but it might help. Reconstruct the fstab. The existing one, which may have NPC or some other corruption is still there, inode hasn't changed. we did create a new file (hence, new inode) and know we don't have a NPC in it. I doubt controller or disk problems, since a livecd can mount it. a fsck -y on a clean filesystem won't report anything. HTH, good luck. >> What entries you do have in /etc/sysctl.conf? > > None. It is just the default file with some comments, but no uncommented > lines. > >> Please try "fsck -y" option first although I am not quite optimistic about >> it, given that mounting by hand works so far. > > Okay. > >> If I were to upgrade, I'd go to 6.4-STABLE first and wait there while >> thinking about the next move. > > Right... I'm going to try getting this machine up first, before > fussing with upgrades. > >> What does your /etc/rc.conf contain? > $ cat rc.conf > #$Id: rc.conf,v 1.4 2008/03/31 23:44:10 root Exp root $ > > # -- sysinstall generated deltas -- # Sat Dec 1 16:23:45 2007 > # Created: Sat Dec 1 16:23:45 2007 > # 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. > defaultrouter="66.111.0.193" > hostname="on.identry.com" > keyrate="fast" > moused_enable="YES" > monit_enable="YES" > ntpd_enable="YES" > ntpd_program="/usr/sbin/ntpd" > ntpd_config="/etc/ntp.conf" > ntpd_sync_on_start="YES" > ntpd_flags="-p /var/run/ntpd.pid" > saver="green" > pf_enable="YES" > pf_rules="/etc/pf.conf" > pf_flags="" # additional flags for pfctl startup > pflog_enable="YES" > pflog_logfile="/var/log/pflog" > pflog_flags="" # additional flags for pflogd startup > sshd_enable="YES" > #inetd_enable="YES" > usbd_enable="YES" > mysql_enable="YES" > apache22_enable="YES" > apache22_flags="-DSSL" > apache22_http_accept_enable="YES" > sendmail_enable="NONE" > spamd_enable="YES" > spamd_flags="-v -x -u vpopmail" > courier_authdaemond_enable="YES" > courier_imap_imapd_enable="YES" > courier_imap_imapdssl_enable="YES" > courier_imap_imapd_ssl_enable="YES" > courier_imap_pop3d_enable="YES" > courier_imap_pop3dssl_enable="YES" > courier_imap_pop3d_ssl_enable="YES" > clamav_clamd_enable="YES" > clamav_freshclam_enable="YES" > svscan_enable="YES" > snmpd_enable="NO" > pureftpd_enable="YES" > autossh_enable="YES" > mongrel_cluster_enable="YES" > mongrel_cluster_config="/usr/local/etc/mongrel_cluster" > > # added by xorg-libraries port > local_startup="/usr/local/etc/rc.d" > ___ > 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: Boot failure
On Fri, Aug 07, 2009 at 12:26:10PM -0400, Identry wrote: > >> Should I use any flags? Should I mount the filesystems read write or read > >> only? > > > > You should never fsck a filesystem when its mounted! > > Ah... glad I asked. Actually it is only when a filesystem is mounted read-write that you must not run fsck on it. Running it on a filesystem which is mounted read-only should be OK. (Otherwise we would all be in a lot of trouble since when fsck is run normally during the startup sequence the root filesystem (/) is mounted read-only, and is in fact where the fsck binary is loaded from.) > > > I think you should start by reading the manual pages for fsck and > > fsck_ffs. I would start with 'fsck_ffs -fp /dev/yourdevicenode'. > > Okay, that makes sense, and is simpler than what I was planning. I > have a long train ride, so I'm going to print out and read those man > pages, and whatever I can find in the Handbook, and maybe there's some > info in my Absolute FreeBSD book... > > > If this command quits with errors, you might try fsck_ffs without flags, > > or 'fsck_ffs -y' to have it try and repair all damage that it finds. > > Excellent. Thanks for all your advice Roland. > ___ > 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" -- Erik Trulsson ertr1...@student.uu.se ___ 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: Boot failure
>> Should I use any flags? Should I mount the filesystems read write or read >> only? > > You should never fsck a filesystem when its mounted! Ah... glad I asked. > I think you should start by reading the manual pages for fsck and > fsck_ffs. I would start with 'fsck_ffs -fp /dev/yourdevicenode'. Okay, that makes sense, and is simpler than what I was planning. I have a long train ride, so I'm going to print out and read those man pages, and whatever I can find in the Handbook, and maybe there's some info in my Absolute FreeBSD book... > If this command quits with errors, you might try fsck_ffs without flags, > or 'fsck_ffs -y' to have it try and repair all damage that it finds. Excellent. Thanks for all your advice Roland. ___ 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: Boot failure
> fsck is run when all file systems are unmounted! > > If you can, choose single use mode, press enter when it says something like > "/bin/sh" (I don't remember the wordings) and then on the subsequent > prompt,, > # fsck -y [Press enter here] > > That is all you need. Once it completes, it will bring back the prompt (the > hash prompt). If there are no major problems detected, you can simply go > ahead and type "exit" at the prompt and press enter and see what happens. But it doesn't boot into single user mode, so I can't just do fsck -y. And I'm wondering if -y is too dangerous. -- John ___ 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: Boot failure
On Fri, Aug 7, 2009 at 6:25 PM, Identry wrote: > >> So I guess the question now is, if I can mount it manually, why > >> doesn't it mount during the boot process? > >> > > I'd give it an fsck or two (more than one has been needed once or > > twice) > > So I've been thinking about how to run fsck... > > At the moment, I have to boot from an install cd, go into fixit mode, > and mount filesystems by hand. I am mounting them to a mount point > like /mnt/root and /mnt/home, etc. > > Do I just do a command like: > > fsck /mnt/root > > Should I use any flags? Should I mount the filesystems read write or read > only? fsck is run when all file systems are unmounted! If you can, choose single use mode, press enter when it says something like "/bin/sh" (I don't remember the wordings) and then on the subsequent prompt,, # fsck -y [Press enter here] That is all you need. Once it completes, it will bring back the prompt (the hash prompt). If there are no major problems detected, you can simply go ahead and type "exit" at the prompt and press enter and see what happens. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube ___ 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: Boot failure
On Fri, Aug 07, 2009 at 11:25:48AM -0400, Identry wrote: > >> So I guess the question now is, if I can mount it manually, why > >> doesn't it mount during the boot process? > >> > > I'd give it an fsck or two (more than one has been needed once or > > twice) > > So I've been thinking about how to run fsck... > > At the moment, I have to boot from an install cd, go into fixit mode, > and mount filesystems by hand. I am mounting them to a mount point > like /mnt/root and /mnt/home, etc. > > Do I just do a command like: > > fsck /mnt/root > > Should I use any flags? Should I mount the filesystems read write or read > only? You should never fsck a filesystem when its mounted! I think you should start by reading the manual pages for fsck and fsck_ffs. I would start with 'fsck_ffs -fp /dev/yourdevicenode'. If this command quits with errors, you might try fsck_ffs without flags, or 'fsck_ffs -y' to have it try and repair all damage that it finds. Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpX1bkrO3QxH.pgp Description: PGP signature
Re: Boot failure
>> So I guess the question now is, if I can mount it manually, why >> doesn't it mount during the boot process? >> > I'd give it an fsck or two (more than one has been needed once or > twice) So I've been thinking about how to run fsck... At the moment, I have to boot from an install cd, go into fixit mode, and mount filesystems by hand. I am mounting them to a mount point like /mnt/root and /mnt/home, etc. Do I just do a command like: fsck /mnt/root Should I use any flags? Should I mount the filesystems read write or read only? Thanks: John ___ 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: Boot failure
> If you did not touch the kernel, there is no need to boot GENERIC! Plus you > have said that this box is running PF, which is not in the GENERIC kernel! > Personally, I am interested in knowing why the system does not mount the > root partition on its own when you can do it by hand and it does not > complain. Me too. > Did you by any chance change anyting in /etc/fstab? No, this has never changed since original install. > What entries you do have in /etc/sysctl.conf? None. It is just the default file with some comments, but no uncommented lines. > Please try "fsck -y" option first although I am not quite optimistic about > it, given that mounting by hand works so far. Okay. > If I were to upgrade, I'd go to 6.4-STABLE first and wait there while > thinking about the next move. Right... I'm going to try getting this machine up first, before fussing with upgrades. > What does your /etc/rc.conf contain? $ cat rc.conf #$Id: rc.conf,v 1.4 2008/03/31 23:44:10 root Exp root $ # -- sysinstall generated deltas -- # Sat Dec 1 16:23:45 2007 # Created: Sat Dec 1 16:23:45 2007 # 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. defaultrouter="66.111.0.193" hostname="on.identry.com" keyrate="fast" moused_enable="YES" monit_enable="YES" ntpd_enable="YES" ntpd_program="/usr/sbin/ntpd" ntpd_config="/etc/ntp.conf" ntpd_sync_on_start="YES" ntpd_flags="-p /var/run/ntpd.pid" saver="green" pf_enable="YES" pf_rules="/etc/pf.conf" pf_flags="" # additional flags for pfctl startup pflog_enable="YES" pflog_logfile="/var/log/pflog" pflog_flags="" # additional flags for pflogd startup sshd_enable="YES" #inetd_enable="YES" usbd_enable="YES" mysql_enable="YES" apache22_enable="YES" apache22_flags="-DSSL" apache22_http_accept_enable="YES" sendmail_enable="NONE" spamd_enable="YES" spamd_flags="-v -x -u vpopmail" courier_authdaemond_enable="YES" courier_imap_imapd_enable="YES" courier_imap_imapdssl_enable="YES" courier_imap_imapd_ssl_enable="YES" courier_imap_pop3d_enable="YES" courier_imap_pop3dssl_enable="YES" courier_imap_pop3d_ssl_enable="YES" clamav_clamd_enable="YES" clamav_freshclam_enable="YES" svscan_enable="YES" snmpd_enable="NO" pureftpd_enable="YES" autossh_enable="YES" mongrel_cluster_enable="YES" mongrel_cluster_config="/usr/local/etc/mongrel_cluster" # added by xorg-libraries port local_startup="/usr/local/etc/rc.d" ___ 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: Boot failure
On Fri, Aug 07, 2009 at 10:59:13AM -0400, Identry wrote: > > Try this: > > > > # strings /boot/kernel/kernel ? ? | grep ':/usr/obj/usr/src/sys/' > > # strings /boot/kernel.old/kernel | grep ':/usr/obj/usr/src/sys/' > > $ strings kernel/kernel |grep ':/usr/obj/usr/src/sys' > r...@on.identry.com:/usr/obj/usr/src/sys/INET_ON > > $ strings kernel.old/kernel |grep ':/usr/obj/usr/src/sys' > r...@on.identry.com:/usr/obj/usr/src/sys/INET_ON So both are (probably) custom kernels. Just run a diff between: /usr/src/sys/$ARCH/conf/GENERIC and /usr/src/sys/$ARCH/conf/INET_ON (with ARCH being one of i386, amd64, etc...) GENERIC and INET_ON may be equal; then you're running GENERIC. If not, they you're running a customized kernel. -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: Boot failure
> Try this: > > # strings /boot/kernel/kernel | grep ':/usr/obj/usr/src/sys/' > # strings /boot/kernel.old/kernel | grep ':/usr/obj/usr/src/sys/' $ strings kernel/kernel |grep ':/usr/obj/usr/src/sys' r...@on.identry.com:/usr/obj/usr/src/sys/INET_ON $ strings kernel.old/kernel |grep ':/usr/obj/usr/src/sys' r...@on.identry.com:/usr/obj/usr/src/sys/INET_ON ___ 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: Boot failure
On Fri, Aug 7, 2009 at 5:31 PM, Identry wrote: > >Are you using the GENERIC kernel > > After more research, I think the answer to this is no. There is a > directory called /boot/kernel.old. From my reading, I believe this is > the original generic kernel? > > > if not have you tried it? > > Not yet. Section "24.2.3 Major and Minor Upgrades" of the Handbook > says I can load the generic kernel by renaming /boot/kernel.old to > /boot/GENERIC. > > I think this is what I need to do to boot the generic kernel? > > -- > If the system was running with a custom kernel, use the nextboot(8) > command to set the kernel for the next boot to /boot/GENERIC (which > was updated): > > # nextboot -k GENERIC > >Warning: Before rebooting with the GENERIC kernel, make sure it > contains all drivers required for your system to boot properly (and > connect to the network, if the machine that is being updated is > accessed remotely). In particular, if the previously running custom > kernel contained built-in functionality usually provided by kernel > modules, make sure to temporarily load these modules into the GENERIC > kernel using the /boot/loader.conf facility. You may also wish to > disable non-essential services, disk and network mounts, etc. until > the upgrade process is complete. > > The machine should now be restarted with the updated kernel: > > # shutdown -r now > --- > > So, it sounds like the safe move is to try to get the Generic kernel > up and running, and then think about doing an upgrade. > > Unfortunately, I need to drive back to the server... another 2 hr > commute. Gotta find a closer data center :-) If you did not touch the kernel, there is no need to boot GENERIC! Plus you have said that this box is running PF, which is not in the GENERIC kernel! Personally, I am interested in knowing why the system does not mount the root partition on its own when you can do it by hand and it does not complain. Did you by any chance change anyting in /etc/fstab? What entries you do have in /etc/sysctl.conf? Please try "fsck -y" option first although I am not quite optimistic about it, given that mounting by hand works so far. If I were to upgrade, I'd go to 6.4-STABLE first and wait there while thinking about the next move. What does your /etc/rc.conf contain? -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube ___ 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: Boot failure
On Fri, Aug 07, 2009 at 10:31:01AM -0400, Identry wrote: > >Are you using the GENERIC kernel > > After more research, I think the answer to this is no. There is a > directory called /boot/kernel.old. From my reading, I believe this is > the original generic kernel? Try this: # strings /boot/kernel/kernel | grep ':/usr/obj/usr/src/sys/' # strings /boot/kernel.old/kernel | grep ':/usr/obj/usr/src/sys/' -cpghost. -- Cordula's Web. http://www.cordula.ws/ ___ 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: Boot failure
On Fri, Aug 7, 2009 at 5:08 PM, Identry wrote: > > I'd give it an fsck or two (more than one has been needed once or > > twice), > > I was afraid to run fsck before backing up everything I might possibly > need, so I spent most of last night mounting all the partitions and > backing up things. > > I was able to manually mount all the partitions and all the data seemed > fine. > > At this point, I'm ready to risk an fsck or pretty much anything. > > > also has anything changed with the server (updates etc etc) for > > example why was it rebooted? > > Because of a stupid mistake on my part. I was trying to add an address > to the NIC card, and rather than *add* the address to a long list of > addresses (used for https websites), I made that the only address. I > was only experimenting, so the file in /etc that I use to set up the > addresses (using ifconfig) was unchanged. I figured a quick reboot > would solve the problem, so I logged in via the console and did a > clean shutdown. When I turned the machine back on, it would not boot. > > I seem to recall a verbose boot mode in the > > boot menu. does that give any hints beyond the freeze you see when you > > try and boot? > > It prints one line, which I cannot recall, unfortunately. > > > Are you using the GENERIC kernel > > I don't know. This is the oldest freebsd machine that I run. I didn't > install the OS, myself. It's a 6.2 machine that had been running in > production mode without any updates for over a year when I took it > over. I am embarrassed to say I never had the nerve to do any updates > on it, either, because when I started on it, I didn't know enough > about FreeBSD to risk the 40 websites that were running on it. > > I've been meaning to update it for awhile, but it is locked down tight > with PF and has had zero problems up until now. Famous last words... > > > if not have you tried it? > > No. I need to figure out how to do that, and I didn't have enough > brain power last night after doing all those backups. Boot to single user mode and just run: fsck -y You don't need any special options the first time. fsck should tell you if there are further problems. > > After sleeping on it, I am wondering if I can kill two birds with one > stone... by using 7.2 install CDs to upgrade the machine? I believe > there is an 'upgrade' option on the install menu (I'm burning some 7.2 > CDs right now to double check.) > > Or would it be safer to try to bring up the machine on it's own with a > 6.2 generic kernel, first? Please don't even think of doing that! You might go mad with the several issues you may end up facing. And upgrading a production system from an install CD is something that I will never do. I always use csup/cvsup, but perhaps you can also use freebsd-update. I advise you get to fix the problem at hand before thinking of updating. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ "If you have nothing good to say about someone, just shut up!." -- Lucky Dube ___ 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: Boot failure
>Are you using the GENERIC kernel After more research, I think the answer to this is no. There is a directory called /boot/kernel.old. From my reading, I believe this is the original generic kernel? > if not have you tried it? Not yet. Section "24.2.3 Major and Minor Upgrades" of the Handbook says I can load the generic kernel by renaming /boot/kernel.old to /boot/GENERIC. I think this is what I need to do to boot the generic kernel? -- If the system was running with a custom kernel, use the nextboot(8) command to set the kernel for the next boot to /boot/GENERIC (which was updated): # nextboot -k GENERIC Warning: Before rebooting with the GENERIC kernel, make sure it contains all drivers required for your system to boot properly (and connect to the network, if the machine that is being updated is accessed remotely). In particular, if the previously running custom kernel contained built-in functionality usually provided by kernel modules, make sure to temporarily load these modules into the GENERIC kernel using the /boot/loader.conf facility. You may also wish to disable non-essential services, disk and network mounts, etc. until the upgrade process is complete. The machine should now be restarted with the updated kernel: # shutdown -r now --- So, it sounds like the safe move is to try to get the Generic kernel up and running, and then think about doing an upgrade. Unfortunately, I need to drive back to the server... another 2 hr commute. Gotta find a closer data center :-) Thanks: John ___ 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: Boot failure
Identry wrote: >> Try downloading and booting the livefs environment (I think you need cd1 >> and the livefs cd or just the DVD) and see if you can mount it from >> that, if not it could be a controller issue. If you can then its >> probably your OS/kernel but at least you now have access to your >> data/configs etc etc not to mention you could try extracting the GENERIC >> kernel from the install media (use the install.sh script in the kernels >> directory.) > > Okay! Good news, I think. I used the 'fixit' mode, that is available > through the installation disk, to mount the disk that fails to mount > during boot up. > > What I did was: > > mount /dev/mfid0s1a /test > > It mounts successfully and I can see everything in that partition. > > So I guess the question now is, if I can mount it manually, why > doesn't it mount during the boot process? > I'd give it an fsck or two (more than one has been needed once or twice), also has anything changed with the server (updates etc etc) for example why was it rebooted? I seem to recall a verbose boot mode in the boot menu. does that give any hints beyond the freeze you see when you try and boot? Are you using the GENERIC kernel, if not have you tried it? Vince > -- John > ___ > 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: Boot failure
> Try downloading and booting the livefs environment (I think you need cd1 > and the livefs cd or just the DVD) and see if you can mount it from > that, if not it could be a controller issue. If you can then its > probably your OS/kernel but at least you now have access to your > data/configs etc etc not to mention you could try extracting the GENERIC > kernel from the install media (use the install.sh script in the kernels > directory.) Okay! Good news, I think. I used the 'fixit' mode, that is available through the installation disk, to mount the disk that fails to mount during boot up. What I did was: mount /dev/mfid0s1a /test It mounts successfully and I can see everything in that partition. So I guess the question now is, if I can mount it manually, why doesn't it mount during the boot process? -- John ___ 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: Boot failure
On Thu, 6 Aug 2009 18:31:12 -0400, Identry wrote: > I've booted the install CD1 and found something called 'fixit' mode. > I've been googling, but can't seem to find any info on 'fixit'. Is it > possible to use this instead of a livefs disk? As far as I remember, that's correct. CD1 contains the fixit shell. If you want a full-featured live file system (including X), you can download FreeSBIE. To me, it has become a helpful tool in problematic cases. -- Polytropon >From Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ... ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Boot failure
Identry wrote: >> Try downloading and booting the livefs environment (I think you need cd1 >> and the livefs cd or just the DVD) and see if you can mount it from >> that, if not it could be a controller issue. If you can then its >> probably your OS/kernel but at least you now have access to your >> data/configs etc etc not to mention you could try extracting the GENERIC >> kernel from the install media (use the install.sh script in the kernels >> directory.) > > Well, I am in the data center (2 hr drive, unfortunately)... > > This is an Intel mother board. The front panel light labeled '!' is > lit. It isn't lit on the working server. I'm googling right now for > the meaning of this light, but if anyone knows off hand, please let me > know... > > I have the cd1 and cd2, but not the livefs cd. I'm going to try to > find that right now. > I do not know exactly what the light is indicating, such things are usually located in the hardware docs that came with the server. I would hazard a guess that it is indicating a hardware failure. If you are exceedingly lucky it might not be a FreeBSD issue as long as the data on the hard drive(s) has not been corrupted. If it were me, the very first thing I'd do is power down and disconnect the drives. I'd install for temporary testing purposes any old spare blank hard drive I had laying around. If it is a brand name server there may have been included a diagnostics CD. Boot from that and see what happens. Next up is a boot to the BIOS configuration screen. When you power up the first item normally displayed is the text from the video ROM initialization. After this should be some form of announcement on how to get into BIOS config. Press whatever key and enter. Look for one of the preconfigured options such as "BIOS Defaults". If you can select this and save the board will be set to a fairly fail-safe set of defaults. Note that what this is telling you is the video and motherboard are initializing. If you cannot get to this point you may have a dead motherboard. Most boards will emit some form of beep code if the video ROM fails to initialize. Next up is if the board proceeds past this point watch for drive controller initialization. Most (most notably RAID) server controllers may have a message display when the controller ROM initializes indicating some form of key-press combo to enter the controller configuration. An example would be "press Ctrl-A" you'll see from an Adaptec card/chip. If you cannot get to any of these stages consider either dead motherboard or power supply problem. Easiest way to confirm/eliminate a power supply is to substitute a known 100% functional one and see if you can now get to the afore mentioned stage(s) of boot. Power supply problems can sometimes manifest as hard drives that don't want to spin up. Listen and you can usually tell if they spin up, or not. Your trouble sounds most like hardware failure. And because in your first email you did indicate a "Trying to mount root..." error most of the above described basic troubleshooting will end up being either dead hard drive(s) or malfunctioning controller. The reason I would have substituted a known good "scratch" drive earlier is twofold: if it can boot or install or otherwise initialize the controller it is indicative that the controller is OK and the problem is most likely dead drive(s). Secondly, you don't want to take any chances on damaging the data yourself with all this mucking about. If there has been drive failure you will need to replace, reinstall, and restore. If it has been a controller failure you will never have any success either booting, or installing a minimum system to the "scratch" drive. A controller failure also has the possibility of having already destroyed your data. Again, replace, reinstall, restore will be the order of the day. This is just some quickly thrown out stuff in hopes it may be useful to you. It sounds like a hardware failure and not only do you have to deal with that first, you may also have to reinstall and/or restore from backup as well. I typed this up rather in a hurry, (so it's a little 'scrambled') but I think if read in totality you get the idea on things you can do to isolate and resolve. Good luck to you in any event. -Mike ___ 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: Boot failure
On Thu, Aug 06, 2009 at 05:31:49PM -0400, Identry wrote: > > Try downloading and booting the livefs environment (I think you need cd1 > > and the livefs cd or just the DVD) and see if you can mount it from > > that, if not it could be a controller issue. If you can then its > > probably your OS/kernel but at least you now have access to your > > data/configs etc etc not to mention you could try extracting the GENERIC > > kernel from the install media (use the install.sh script in the kernels > > directory.) > > Well, I am in the data center (2 hr drive, unfortunately)... > > This is an Intel mother board. The front panel light labeled '!' is > lit. It isn't lit on the working server. I'm googling right now for > the meaning of this light, but if anyone knows off hand, please let me > know... If it won't boot from the MegaRAID, and there is a red exclamation mark showing on the front panel, I'd say there is a good chance that you've got a hardware problem... Maybe try another RAID card, if you have one available? Roland -- R.F.Smith http://www.xs4all.nl/~rsmith/ [plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated] pgp: 1A2B 477F 9970 BA3C 2914 B7CE 1277 EFB0 C321 A725 (KeyID: C321A725) pgpAWzAPS5Dl5.pgp Description: PGP signature
Re: Boot failure
> Identry wrote: >> >> During the boot sequence, it freezes at the statement: >> >> Trying to mount root from ufs:/dev/mfid0s1a >> > Try downloading and booting the livefs environment (I think you need cd1 > and the livefs cd or just the DVD) and see if you can mount it from > that, if not it could be a controller issue. If you can then its > probably your OS/kernel but at least you now have access to your > data/configs etc etc not to mention you could try extracting the GENERIC > kernel from the install media (use the install.sh script in the kernels > directory.) I've booted the install CD1 and found something called 'fixit' mode. I've been googling, but can't seem to find any info on 'fixit'. Is it possible to use this instead of a livefs disk? BTW, this is a 6.3 system. -- John ___ 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: Boot failure
> Try downloading and booting the livefs environment (I think you need cd1 > and the livefs cd or just the DVD) and see if you can mount it from > that, if not it could be a controller issue. If you can then its > probably your OS/kernel but at least you now have access to your > data/configs etc etc not to mention you could try extracting the GENERIC > kernel from the install media (use the install.sh script in the kernels > directory.) Well, I am in the data center (2 hr drive, unfortunately)... This is an Intel mother board. The front panel light labeled '!' is lit. It isn't lit on the working server. I'm googling right now for the meaning of this light, but if anyone knows off hand, please let me know... I have the cd1 and cd2, but not the livefs cd. I'm going to try to find that right now. Thanks: John ___ 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: Boot failure
Identry wrote: > Well, the bad day has come... My primary server won't boot. I have > backups of databases and user directories, but I need to try to get > this server back up again. > > During the boot sequence, it freezes at the statement: > > Trying to mount root from ufs:/dev/mfid0s1a > > I tried booting into single user mode, but same issue (of course). > > I don't want to just start hacking at this for fear of making things > work... what is my best, most conservative next step? Try downloading and booting the livefs environment (I think you need cd1 and the livefs cd or just the DVD) and see if you can mount it from that, if not it could be a controller issue. If you can then its probably your OS/kernel but at least you now have access to your data/configs etc etc not to mention you could try extracting the GENERIC kernel from the install media (use the install.sh script in the kernels directory.) Vince > > -- John > ___ > 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: Boot failure after installation
I have BOTH "ad0" (IDE HDD) AND "da0" (SCSI device #0). I posted detailed BIOS settings and install steps in previous emails. I've attached the BIOS and SCSI BIOS settings (with footnotes). I have installed FreeBSD on da0 multiple times, each time creating a single slice/partition on da0, and setting da0 as bootable, and installing the FreeBSD boot manager on da0. OK? I also found an IDE HDD yesterday, and installed Linux on ad0 (the IDE HDD), but am getting the exact same boot failure. I tried setting my bios to try booting from IDE drives first (before SCSI), and vice-versa (SCSI first, which is what it was set to), with no change. I also tried removing the IDE HDD and booting, but boot from CD-ROM drive hangs, and boot from "C" fails. I did not change BIOS settings re the (removed) IDE HDD. I've never worked on a machine that has both SCSI and IDE controller/drive configuration, and am not sure how to disentangle the IDE hard drive from the system without causing new problems. Ended up reinstalling the IDE HDD for now, but would like to remove it for use elsewhere (this machine has 5 SCSI drives, so don't need it). Jerry McAllister <[EMAIL PROTECTED]> wrote: > Will someone please explain in detail how to run the FreeBSD fdisk util > outside of the freebsd installer? Please provide detailed steps. You just type fdisk devname where devname is the disk device. There are a number of flags and parameters you may need to use. Have you read the fdisk man page?Also read the bsdlabel man page. > What would the experts do next in this situation? I've checked and > double-checked BIOS (current version is same as what I have -- 1013, so did > not re-flash), SCSI BIOS (reset defaults and low-level formatted da0). I've > performed "Minimal" FreeBSD install per step-by-step directions, and always > says it's installed successfully, but can never boot from da0 (since > repartitioning using FreeBSD "fdisk" util). I've verified that I'm creating a > single partition (slice) on da0, making it the "active" partition, then > setting it Bootable. I would first ignore the issue of cylinders as has been mentioned. > > I booted the FreeSBIE LiveCD, and tried to mount da0: > mount /dev/da0 /mnt > mount: /dev/da0: Operation not permitted First of all, do you even have a da0 drive? Maybe it is ad0 Second, is there a file system build on da0a?I haven't seen anything that indicates it. You can only mount a file system. Fdisk doesn't have much to do with creating a file system. That is newfs. The standard way to build a disk is: Use fdisk to create slice[s] (1..4) -- and possibly write an MBR on the disk. Use bsdlabel to divide the slice in to partitions (a..h) and possibly write a boot sector on the slice. Use newfs to create file systems on each of the partitions except swap & c. Then you can mount any of those newfs created filesystems. You must first read the man pages for those utilities and also study the relevant handbook sections. Also, peruse the FreeBSD-questions archives. I have written on this several time recently. Find and read those. Then, if you have further specific questions, come back and ask. But, you must do your homework first or our answers will be useless to you and a waste of our time. jerry > > Jerry McAllister wrote: On Tue, Apr 10, 2007 at 07:48:07PM -0700, L Goodwin > wrote: > > > Is there a way to run the "FDISK" tool outside of the freebds installer? > > How do I change the disk configuration without reinstalling freebsd > > every @[EMAIL PROTECTED] time? > > Yes, all sysinstall does is collect the information and run fdisk for you. > See the man page (enter man fdisk ) > > It can be a little hard to read at first. The fdisk and bsdlabel don't > follow the normal man page form. > > One thing you must know; you cannot run fdisk on a drive that is in > active use. If you booted from that drive or if you are CD-ed in to > a file system on the drive, the system will not let you write to the > drive using fdisk. You can only use fdisk to read the slice table > and run prototype setups that do not actually write out to the disk. > > Trying to write to a drive that is active is a very popular mistake > when attempting to use fdisk. > > So, read the fdisk man page and then come back with some more specific > questions if you need. > > > I really want to set up a FreeBSD server and appreciate the learning > > experience, but it's way past the point where I should have switched to an > > OS that will actually run on my client's server. If I don't get it going > > tonight, I'm going to install the first Linux distribution that says "Hey, > > Sailor"... =8-0 > > Guess you will need to follow the installation instructions in the FreeBSD > handbook more carefully. > > > BTW, I burned a freeSBIE 2.0.1 Live CD, but have no idea what to do with > > it. Yes, I am pathetically clueless. Thanks for yo
Re: Boot failure after installation
> Will someone please explain in detail how to run the FreeBSD fdisk util > outside of the freebsd installer? Please provide detailed steps. You just type fdisk devname where devname is the disk device. There are a number of flags and parameters you may need to use. Have you read the fdisk man page?Also read the bsdlabel man page. > What would the experts do next in this situation? I've checked and > double-checked BIOS (current version is same as what I have -- 1013, so did > not re-flash), SCSI BIOS (reset defaults and low-level formatted da0). I've > performed "Minimal" FreeBSD install per step-by-step directions, and always > says it's installed successfully, but can never boot from da0 (since > repartitioning using FreeBSD "fdisk" util). I've verified that I'm creating a > single partition (slice) on da0, making it the "active" partition, then > setting it Bootable. I would first ignore the issue of cylinders as has been mentioned. > > I booted the FreeSBIE LiveCD, and tried to mount da0: > mount /dev/da0 /mnt > mount: /dev/da0: Operation not permitted First of all, do you even have a da0 drive? Maybe it is ad0 Second, is there a file system build on da0a?I haven't seen anything that indicates it. You can only mount a file system. Fdisk doesn't have much to do with creating a file system. That is newfs. The standard way to build a disk is: Use fdisk to create slice[s] (1..4) -- and possibly write an MBR on the disk. Use bsdlabel to divide the slice in to partitions (a..h) and possibly write a boot sector on the slice. Use newfs to create file systems on each of the partitions except swap & c. Then you can mount any of those newfs created filesystems. You must first read the man pages for those utilities and also study the relevant handbook sections. Also, peruse the FreeBSD-questions archives. I have written on this several time recently. Find and read those. Then, if you have further specific questions, come back and ask. But, you must do your homework first or our answers will be useless to you and a waste of our time. jerry > > Jerry McAllister <[EMAIL PROTECTED]> wrote: On Tue, Apr 10, 2007 at > 07:48:07PM -0700, L Goodwin wrote: > > > Is there a way to run the "FDISK" tool outside of the freebds installer? > > How do I change the disk configuration without reinstalling freebsd > > every @[EMAIL PROTECTED] time? > > Yes, all sysinstall does is collect the information and run fdisk for you. > See the man page (enter man fdisk ) > > It can be a little hard to read at first. The fdisk and bsdlabel don't > follow the normal man page form. > > One thing you must know; you cannot run fdisk on a drive that is in > active use. If you booted from that drive or if you are CD-ed in to > a file system on the drive, the system will not let you write to the > drive using fdisk. You can only use fdisk to read the slice table > and run prototype setups that do not actually write out to the disk. > > Trying to write to a drive that is active is a very popular mistake > when attempting to use fdisk. > > So, read the fdisk man page and then come back with some more specific > questions if you need. > > > I really want to set up a FreeBSD server and appreciate the learning > > experience, but it's way past the point where I should have switched to an > > OS that will actually run on my client's server. If I don't get it going > > tonight, I'm going to install the first Linux distribution that says "Hey, > > Sailor"... =8-0 > > Guess you will need to follow the installation instructions in the FreeBSD > handbook more carefully. > > > BTW, I burned a freeSBIE 2.0.1 Live CD, but have no idea what to do with > > it. Yes, I am pathetically clueless. Thanks for your patience! > > Just boot it up and run it.It will give you a very basic working > environment.Then do something like you might in a UNIX system, > like ls or cd or df or whatever. > > > > > Derek Ragona wrote: One other thing that > > might be happening is if the geometry of the drive isn't allowing an > > extended translation because of the age of your hardware, you may need to > > keep the boot partition, that is the entire boot partition (not talking > > slices here) within the first 1024 cylinders. In the partition tool in > > sysinstall you can change the display to show different units, and one of > > those will be cylinders. The 1024 cylinder limit is from older BIOS > > translations and if the boot partition extended beyond 1024 the system > > will give that same error you are getting. > > If the machine is built any less than about 11 years ago, this doesn't apply. > > > With older hardware you may need to use multiple partitions instead of > > slices. You can have 4 partitons on a drive (4 is hardcoded in the > > partition table size and a location) so you can add additional partitions > > for swap and /usr if you wa
Re: Boot failure after installation
Will someone please explain in detail how to run the FreeBSD fdisk util outside of the freebsd installer? Please provide detailed steps. What would the experts do next in this situation? I've checked and double-checked BIOS (current version is same as what I have -- 1013, so did not re-flash), SCSI BIOS (reset defaults and low-level formatted da0). I've performed "Minimal" FreeBSD install per step-by-step directions, and always says it's installed successfully, but can never boot from da0 (since repartitioning using FreeBSD "fdisk" util). I've verified that I'm creating a single partition (slice) on da0, making it the "active" partition, then setting it Bootable. I booted the FreeSBIE LiveCD, and tried to mount da0: mount /dev/da0 /mnt mount: /dev/da0: Operation not permitted Jerry McAllister <[EMAIL PROTECTED]> wrote: On Tue, Apr 10, 2007 at 07:48:07PM -0700, L Goodwin wrote: > Is there a way to run the "FDISK" tool outside of the freebds installer? > How do I change the disk configuration without reinstalling freebsd > every @[EMAIL PROTECTED] time? Yes, all sysinstall does is collect the information and run fdisk for you. See the man page (enter man fdisk ) It can be a little hard to read at first. The fdisk and bsdlabel don't follow the normal man page form. One thing you must know; you cannot run fdisk on a drive that is in active use. If you booted from that drive or if you are CD-ed in to a file system on the drive, the system will not let you write to the drive using fdisk. You can only use fdisk to read the slice table and run prototype setups that do not actually write out to the disk. Trying to write to a drive that is active is a very popular mistake when attempting to use fdisk. So, read the fdisk man page and then come back with some more specific questions if you need. > I really want to set up a FreeBSD server and appreciate the learning > experience, but it's way past the point where I should have switched to an OS > that will actually run on my client's server. If I don't get it going > tonight, I'm going to install the first Linux distribution that says "Hey, > Sailor"... =8-0 Guess you will need to follow the installation instructions in the FreeBSD handbook more carefully. > BTW, I burned a freeSBIE 2.0.1 Live CD, but have no idea what to do with it. > Yes, I am pathetically clueless. Thanks for your patience! Just boot it up and run it.It will give you a very basic working environment.Then do something like you might in a UNIX system, like ls or cd or df or whatever. > > Derek Ragona wrote: One other thing that > might be happening is if the geometry of the drive isn't allowing an > extended translation because of the age of your hardware, you may need to > keep the boot partition, that is the entire boot partition (not talking > slices here) within the first 1024 cylinders. In the partition tool in > sysinstall you can change the display to show different units, and one of > those will be cylinders. The 1024 cylinder limit is from older BIOS > translations and if the boot partition extended beyond 1024 the system > will give that same error you are getting. If the machine is built any less than about 11 years ago, this doesn't apply. > With older hardware you may need to use multiple partitions instead of > slices. You can have 4 partitons on a drive (4 is hardcoded in the > partition table size and a location) so you can add additional partitions > for swap and /usr if you want. Any partitions you use for filesystems > like /usr the boot manager will see and offer to boot them. They won't > boot of course. Swap partitions are ignored by the boot manager. This is mostly incorrect and even backwards. First of all, there are 4 slices possible on a drive (or raid set for all that matters). Microsoft tends to call slices "Primary Partitions". Slices are created and managed by the fdisk utility. Fdisk also writes the Master Boot Record (MBR) (but not the boot sector). In FreeBSD you can divide each slice up in to partitions which are identified as a..h, although 'c' is reserved. These partitions are created and managed by the FreeBSD bsdlabel utility (or disklabel in older versions). Bsdlabel also writes the boot sector. > Otherwise, I'd suspect it is a problem with the 6.2 you are using then. > If you try with a boot within the 1024 (I wouldn't push that to the > limit I'd say try like 950 cylinders) then I would try an earlier > version such as 6.1 or 6.0. > The whole issue of 1024 cylinders limit for bootable file systems went away with improved BIOS about 11 years ago. If you have a system old enough to have the problem, you should be updating the BIOS rather than trying to accomodate the limit. jerry > -Derek > > -- > This message has been scanned for viruses and > dangerous content by MailScanner, and is > believed to be clean. > MailScanner thanks transtec
Re: Boot failure after installation
On Tue, Apr 10, 2007 at 07:48:07PM -0700, L Goodwin wrote: > Is there a way to run the "FDISK" tool outside of the freebds installer? > How do I change the disk configuration without reinstalling freebsd > every @[EMAIL PROTECTED] time? Yes, all sysinstall does is collect the information and run fdisk for you. See the man page (enter man fdisk ) It can be a little hard to read at first. The fdisk and bsdlabel don't follow the normal man page form. One thing you must know; you cannot run fdisk on a drive that is in active use. If you booted from that drive or if you are CD-ed in to a file system on the drive, the system will not let you write to the drive using fdisk. You can only use fdisk to read the slice table and run prototype setups that do not actually write out to the disk. Trying to write to a drive that is active is a very popular mistake when attempting to use fdisk. So, read the fdisk man page and then come back with some more specific questions if you need. > I really want to set up a FreeBSD server and appreciate the learning > experience, but it's way past the point where I should have switched to an OS > that will actually run on my client's server. If I don't get it going > tonight, I'm going to install the first Linux distribution that says "Hey, > Sailor"... =8-0 Guess you will need to follow the installation instructions in the FreeBSD handbook more carefully. > BTW, I burned a freeSBIE 2.0.1 Live CD, but have no idea what to do with it. > Yes, I am pathetically clueless. Thanks for your patience! Just boot it up and run it.It will give you a very basic working environment.Then do something like you might in a UNIX system, like ls or cd or df or whatever. > > Derek Ragona <[EMAIL PROTECTED]> wrote: One other thing that > might be happening is if the geometry of the drive isn't allowing an > extended translation because of the age of your hardware, you may need to > keep the boot partition, that is the entire boot partition (not talking > slices here) within the first 1024 cylinders. In the partition tool in > sysinstall you can change the display to show different units, and one of > those will be cylinders. The 1024 cylinder limit is from older BIOS > translations and if the boot partition extended beyond 1024 the system > will give that same error you are getting. If the machine is built any less than about 11 years ago, this doesn't apply. > With older hardware you may need to use multiple partitions instead of > slices. You can have 4 partitons on a drive (4 is hardcoded in the > partition table size and a location) so you can add additional partitions > for swap and /usr if you want. Any partitions you use for filesystems > like /usr the boot manager will see and offer to boot them. They won't > boot of course. Swap partitions are ignored by the boot manager. This is mostly incorrect and even backwards. First of all, there are 4 slices possible on a drive (or raid set for all that matters). Microsoft tends to call slices "Primary Partitions". Slices are created and managed by the fdisk utility. Fdisk also writes the Master Boot Record (MBR) (but not the boot sector). In FreeBSD you can divide each slice up in to partitions which are identified as a..h, although 'c' is reserved. These partitions are created and managed by the FreeBSD bsdlabel utility (or disklabel in older versions). Bsdlabel also writes the boot sector. > Otherwise, I'd suspect it is a problem with the 6.2 you are using then. > If you try with a boot within the 1024 (I wouldn't push that to the > limit I'd say try like 950 cylinders) then I would try an earlier > version such as 6.1 or 6.0. > The whole issue of 1024 cylinders limit for bootable file systems went away with improved BIOS about 11 years ago. If you have a system old enough to have the problem, you should be updating the BIOS rather than trying to accomodate the limit. jerry > -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. > > > - > It's here! Your new message! > Get new email alerts with the free Yahoo! Toolbar. > ___ > 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: Boot failure after installation
Is there a way to run the "FDISK" tool outside of the freebds installer? How do I change the disk configuration without reinstalling freebsd every @[EMAIL PROTECTED] time? I really want to set up a FreeBSD server and appreciate the learning experience, but it's way past the point where I should have switched to an OS that will actually run on my client's server. If I don't get it going tonight, I'm going to install the first Linux distribution that says "Hey, Sailor"... =8-0 BTW, I burned a freeSBIE 2.0.1 Live CD, but have no idea what to do with it. Yes, I am pathetically clueless. Thanks for your patience! Derek Ragona <[EMAIL PROTECTED]> wrote: One other thing that might be happening is if the geometry of the drive isn't allowing an extended translation because of the age of your hardware, you may need to keep the boot partition, that is the entire boot partition (not talking slices here) within the first 1024 cylinders. In the partition tool in sysinstall you can change the display to show different units, and one of those will be cylinders. The 1024 cylinder limit is from older BIOS translations and if the boot partition extended beyond 1024 the system will give that same error you are getting. With older hardware you may need to use multiple partitions instead of slices. You can have 4 partitons on a drive (4 is hardcoded in the partition table size and a location) so you can add additional partitions for swap and /usr if you want. Any partitions you use for filesystems like /usr the boot manager will see and offer to boot them. They won't boot of course. Swap partitions are ignored by the boot manager. Otherwise, I'd suspect it is a problem with the 6.2 you are using then. If you try with a boot within the 1024 (I wouldn't push that to the limit I'd say try like 950 cylinders) then I would try an earlier version such as 6.1 or 6.0. -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. - It's here! Your new message! Get new email alerts with the free Yahoo! Toolbar. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot failure after installation
it looks as if you've an IDE Interface onboard, too. Is it possible that there are two ATA disks installed? Because the SCSI BIOS is only installed when there are less then two ATA *disks* installed. Having one Disk and one CD ROM should be fine, though. Either try removing the ATA disks, or check your system BIOS if you can select SCSI as boot device. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot failure after installation
At 08:14 PM 4/9/2007, L Goodwin wrote: Derek Ragona said: > Go into the SCSI BIOS and reset the SCSI to default values. > If it still gives the same error on bootup, I would go into the SCSI BIOS and > low-level format that first drive, and reinstall FreeBSD. > On the reinstall, I would just do the partioning for that drive, and then install everything. > That way it will run mostly by itself, you can just check on it for the last few prompts of the > install finishing up. Derek, I just did the following, expecting that this would fix the glitch: 1) Reset the SCSI BIOS to Host Adapter Defaults: Matches prior configuration exactly. 2) Run a low-level format on SCSI device #0: No errors. 3) Install FreeBSD 6.2 from scratch. Note: I answered Yes to the prompt "ACPI was disabled during boot. Would you like to disable it permanently?". I don't think it will boot if I enable ACPI. RESULT: FAIL - Still getting "DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER" 4) Ran "Verify Disk Media" on SCSI ID #0: "Disk Verification Complete" What else could it possibly be? Are there any other diagnostics I can run? What do you think of the fact that this machine was booting Windows 2000 from the same SCSI drive prior to installing FreeBSD 6.2? In case it matters, all SCSI drives are IBM DNES-309170W ULTRA2-LVD. Thanks! One other thing that might be happening is if the geometry of the drive isn't allowing an extended translation because of the age of your hardware, you may need to keep the boot partition, that is the entire boot partition (not talking slices here) within the first 1024 cylinders. In the partition tool in sysinstall you can change the display to show different units, and one of those will be cylinders. The 1024 cylinder limit is from older BIOS translations and if the boot partition extended beyond 1024 the system will give that same error you are getting. With older hardware you may need to use multiple partitions instead of slices. You can have 4 partitons on a drive (4 is hardcoded in the partition table size and a location) so you can add additional partitions for swap and /usr if you want. Any partitions you use for filesystems like /usr the boot manager will see and offer to boot them. They won't boot of course. Swap partitions are ignored by the boot manager. Otherwise, I'd suspect it is a problem with the 6.2 you are using then. If you try with a boot within the 1024 (I wouldn't push that to the limit I'd say try like 950 cylinders) then I would try an earlier version such as 6.1 or 6.0. -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: Boot failure after installation
Derek Ragona said: > Go into the SCSI BIOS and reset the SCSI to default values. > If it still gives the same error on bootup, I would go into the SCSI BIOS and > low-level format that first drive, and reinstall FreeBSD. > On the reinstall, I would just do the partioning for that drive, and then > install everything. > That way it will run mostly by itself, you can just check on it for the last > few prompts of the > install finishing up. Derek, I just did the following, expecting that this would fix the glitch: 1) Reset the SCSI BIOS to Host Adapter Defaults: Matches prior configuration exactly. 2) Run a low-level format on SCSI device #0: No errors. 3) Install FreeBSD 6.2 from scratch. Note: I answered Yes to the prompt "ACPI was disabled during boot. Would you like to disable it permanently?". I don't think it will boot if I enable ACPI. RESULT: FAIL - Still getting "DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER" 4) Ran "Verify Disk Media" on SCSI ID #0: "Disk Verification Complete" What else could it possibly be? Are there any other diagnostics I can run? What do you think of the fact that this machine was booting Windows 2000 from the same SCSI drive prior to installing FreeBSD 6.2? In case it matters, all SCSI drives are IBM DNES-309170W ULTRA2-LVD. Thanks! - Now that's room service! Choose from over 150,000 hotels in 45,000 destinations on Yahoo! Travel to find your fit. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot failure after installation
Derek, Boot Virus Protection is Disabled in the BIOS. How to I make sure my SCSI BIOS is set to be bootable and has the correct disk set for booting from? Please see my SCSI BIOS settings below and advise... (I don't think this is the problem, as this machine was booting Windows 2000 Server from same drive prior to repartioning and installing FreeBSD 6.2. This machine has an ASUS P2B-D ACPI BIOS rev 1013 (AWARD BIOS, single Pentium III/550) with onboard Adaptec 7890 SCSI BIOS.) My apologies for replying directly to those who took the time to respond. I'm used to working with forums that have list servers set up. Thanks! SCSI BIOS SETTINGS: 1) Host Adapter Settings: Configuration SCSI Bus Interface Definitions Host Adapter SCSI ID: 7 SCSI Parity Checking: Enabled Host Adapter SCSI Termination: Press Ultra2-LVD/SE Connector: Auto Fast/Ultra-SE Connector: Enabled Additional Options SCSI Device Configuration: Press Settings for SCSI Device #0 (identical for #1-15): -- Initiate Sync Negotiation: yes Maximum Transfer Rate: 80.0 Enable Disconnnection: yes Initiate Wide Negotiation: yes Send Start Unit Command: yes Include in BIOS Scan: yes -- Array1000 BIOS: Enabled BIOS Support for Bootable CD-ROM: Enabled 2) SCSI Disk Utilities: Select SCSI Disk and press SCSI ID #0:IBMDNES-309170WULTRA2-LVD SCSI ID #1:IBMDNES-309170WULTRA2-LVD SCSI ID #2:IBMDNES-309170WULTRA2-LVD SCSI ID #3:IBMDNES-309170WULTRA2-LVD SCSI ID #4:IBMDNES-309170WULTRA2-LVD SCSI ID #5:ECRIXVXA-1Fast/Ultra-SE SCSI ID #6:No device SCSI ID #7:Array1000 Family SCSI ID #8:No device SCSI ID #9:No device SCSI ID #10:No device SCSI ID #11:No device SCSI ID #12:No device SCSI ID #13:No device SCSI ID #14:No device SCSI ID #15:No device Derek Ragona <[EMAIL PROTECTED]> wrote: At 12:56 AM 4/9/2007, L Goodwin wrote: I'm having trouble getting FreeBSD 6.2 to boot after installation. After a "successful" install, (re-)boot always fails with "DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER". Make sure your System BIOS is not set to not allow writing to the boot area, often this is called boot sector virus protection in some BIOS's. Go into your SCSI BIOS and make sure it is set to be bootable and has the correct disk set for booting from. - Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Boot failure after installation
At 12:56 AM 4/9/2007, L Goodwin wrote:
Hello. I tried posting this issue a few hours ago, but it did not appear
in my inbox, so I'm
trying once more. I've included details of the install in case it matters
(sorry about length).
I'm having trouble getting FreeBSD 6.2 to boot after installation. After a
"successful" install,
(re-)boot always fails with "DISK BOOT FAILURE, INSERT SYSTEM DISK AND
PRESS ENTER".
In order to boot the install CD on this machine, I have to disable ACPI by
selecting
"2. Boot FreeBSD with ACPI disabled" from the boot loader menu (the AWARD
BIOS does not allow
for disabling ACPI from the BIOS setup program).
At the end of a "successful" install, the installer asks "ACPI was
disabled during boot.
Would you like to disable it permanently?", to which I choose "Yes".
I am choosing to perform a "Standard" install.
Here are my FDISK selections:
Select Drive(s): "da0" (first SCSI drive of 6 9GB drives)
These are my selections in FDISK Partition Editor (before entering "Q"):
--
Disk name:da0FDISK Partition Editor
DISK Geometry:1115 cyls/255 heads/63 sectors = 17912475 sectors (8746MB)
OffsetSize(ST)EndNamePTypeDescSubtype
Flags
06362-12unused0
631791241217912474da0s18freebsd165A
17912475376517916239-12unused0
--
Install Boot Manager for drive da0?: Selected "BootMgr" (Install the
FreeBSD Boot Manager)
Select Drive(s): "da0" selected for Boot Manager (tab to "OK", press ENTER).
FreeBSD Disklabel Editor (create BSD Paritions): Select "A" (Auto Defaults)...
--
Disk: da0Partition name da0s1Free: 17912412 blocks (8746MB)
PartMountSizeNewfsPartMountSizeNewfs
----
da0s1a/512MBUFS2Y
da0s1bswap486MBSWAP
da0s1d/var1267MBUFS2+sY
da0s1e/tmp512MBUFS2+sY
da0s1f/usr5968MBUFS2+sY
--
...then enter "Q" (Finish).
Choose Distributions: Select "A Minimal".
Choose Installation Media: "1 CD/DVD" (burned my own from
FreeBSD-6.2-disk1 ISO image)
"All filesystem information written correctly"...
Distribution extracted successfully...
"Congratulations! You now have FreeBSD installed on your system" (but
can't boot!).
Final Configuration: "No" to most questions (configure later). Yes to these:
Ethernet or SLIP/PPP network devices: fxp0 (Intel EtherExpress
Pro/100B PCI Fast Ethernet card
IPv6 configuration of the interfaces?: No
DHCP: No
Bring up fxp0 interface right now?: Yes Failed (only entered hostname
--will complete later)
Network gateway?: No
inetd?: No
SSH login?: Yes
anonymous FTP?: No
NFS server?: No
NFS client?: No
customize system console settings?: No
machine's time zone?: Yes
CMOS clock set to UTC?: No
Region: "2 America -- North and South"
Country or Region: "45 United States"
Time zone: "19 Pacific Time" ("PDT")
Linux binary compatibility?: No
PS/2 mouse?: Yes (test OK)
"ACPI was disabled during boot. Would you like to diswable it
parmanently?": Yes
Browse FreeBSD package collection?: No
Add initial user accounts?: No
set system manager's password: (done)
Visit general configuration menu one more time?: No
FreeBSD/i386 6.2-RELEASE - sysinstall Main Menu: Exit Install
Last thing to print to screen:
-
Boot from ATAPI CD-ROM : Failure ...
DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
-
The first message is expected, as there is no disk in the CD-ROM drive.
If I set Boot Sequence to "C only" in BIOS setup, only the second message
appears.
Am I doing something wrong here?
Make sure your System BIOS is not set to not allow writing to the boot
area, often this is called boot sector virus protection in some BIOS's.
Go into your SCSI BIOS and make sure it is set to be bootable and has the
correct disk set for booting from.
-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-ques
Re: Boot failure after installation
L Goodwin wrote:
> Hello. I tried posting this issue a few hours ago, but it did not appear in
> my inbox, so I'm
> trying once more. I've included details of the install in case it matters
> (sorry about length).
>
> I'm having trouble getting FreeBSD 6.2 to boot after installation. After a
> "successful" install,
> (re-)boot always fails with "DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS
> ENTER".
>
> In order to boot the install CD on this machine, I have to disable ACPI by
> selecting
> "2. Boot FreeBSD with ACPI disabled" from the boot loader menu (the AWARD
> BIOS does not allow
> for disabling ACPI from the BIOS setup program).
> At the end of a "successful" install, the installer asks "ACPI was disabled
> during boot.
> Would you like to disable it permanently?", to which I choose "Yes".
>
> I am choosing to perform a "Standard" install.
>
> Here are my FDISK selections:
>
> Select Drive(s): "da0" (first SCSI drive of 6 9GB drives)
>
> These are my selections in FDISK Partition Editor (before entering "Q"):
> --
> Disk name:da0FDISK Partition Editor
> DISK Geometry:1115 cyls/255 heads/63 sectors = 17912475 sectors (8746MB)
>
> OffsetSize(ST)EndNamePTypeDescSubtype
> Flags
>
> 06362-12unused0
> 631791241217912474da0s18freebsd165A
> 17912475376517916239-12unused0
> --
>
> Install Boot Manager for drive da0?: Selected "BootMgr" (Install the FreeBSD
> Boot Manager)
> Select Drive(s): "da0" selected for Boot Manager (tab to "OK", press ENTER).
>
> FreeBSD Disklabel Editor (create BSD Paritions): Select "A" (Auto Defaults)...
> --
> Disk: da0Partition name da0s1Free: 17912412 blocks (8746MB)
>
> PartMountSizeNewfsPartMountSizeNewfs
> ----
> da0s1a/512MBUFS2Y
> da0s1bswap486MBSWAP
> da0s1d/var1267MBUFS2+sY
> da0s1e/tmp512MBUFS2+sY
> da0s1f/usr5968MBUFS2+sY
> --
> ...then enter "Q" (Finish).
>
> Choose Distributions: Select "A Minimal".
> Choose Installation Media: "1 CD/DVD" (burned my own from FreeBSD-6.2-disk1
> ISO image)
> "All filesystem information written correctly"...
> Distribution extracted successfully...
> "Congratulations! You now have FreeBSD installed on your system" (but can't
> boot!).
> Final Configuration: "No" to most questions (configure later). Yes to these:
> Ethernet or SLIP/PPP network devices: fxp0 (Intel EtherExpress Pro/100B
> PCI Fast Ethernet card
> IPv6 configuration of the interfaces?: No
> DHCP: No
> Bring up fxp0 interface right now?: Yes Failed (only entered hostname
> --will complete later)
> Network gateway?: No
> inetd?: No
> SSH login?: Yes
> anonymous FTP?: No
> NFS server?: No
> NFS client?: No
> customize system console settings?: No
> machine's time zone?: Yes
> CMOS clock set to UTC?: No
> Region: "2 America -- North and South"
> Country or Region: "45 United States"
> Time zone: "19 Pacific Time" ("PDT")
> Linux binary compatibility?: No
> PS/2 mouse?: Yes (test OK)
> "ACPI was disabled during boot. Would you like to diswable it
> parmanently?": Yes
> Browse FreeBSD package collection?: No
> Add initial user accounts?: No
> set system manager's password: (done)
> Visit general configuration menu one more time?: No
>
> FreeBSD/i386 6.2-RELEASE - sysinstall Main Menu: Exit Install
>
> Last thing to print to screen:
> -
> Boot from ATAPI CD-ROM : Failure ...
> DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
> -
>
> The first message is expected, as there is no disk in the CD-ROM drive.
> If I set Boot Sequence to "C only" in BIOS setup, only the second message
> appears.
>
> Am I doing something wrong here?
>
Just from the size of the drives I'm guessing this is older
hardware. Is the machine capable of booting from SCSI? Is the scsi
controller itself bootable?
--
Thanks,
Josh Paetzel
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
