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 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 wrote: >> On 25. sep. 2013, at 06:59, Tyler Sweet 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 wrote: > On 25. sep. 2013, at 06:59, Tyler Sweet 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 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"
FreeBSD 8.4 Boot failure
Hello all, Not sure if this is the correct list. I've run into a problem with one of my servers where it no longer boots. It uses GPT and ZFS for root. Recently, I did an upgrade from 8.2 up to 8.4. That went fine, and I rebooted a few times after that to finish installing updates. During those reboots, I also updated ZFS to the most recent version to take advantage of dedupe and the new compression algorithm. The server has two zpools, zroot which has the system on it, and data, which has everything else (except /usr/home, which is on zroot). I followed this guide a long, long time ago: https://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/RAIDZ1 While deleting several large files, the system stopped responding to SSH/HTTP/everything except ping. Thinking it was just taking a long time to finish, I let it sit for about a day. When it didn't recover, I had to do a hard power-off, as it wasn't accepting key strokes at the console. When it boots back up, it gets past POST and then goes to a black screen with just a spinner in the upper left-hand corner. No text, no logo, nothing else. The spinner used to spin around a few times, now it does nothing. I've managed to get boot zpools loaded up in the fixit console, they don't show any errors. 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. Neither one seems to change anything. I've let it sit at the (mostly) blank screen for two hours with no change. I'm at the end of my wits, and haven't been able to find any information as to what could be causing this. There are no error messages at the console, and the only output is that frozen spinner. >From what I remember, I didn't change anything on the zroot zpool during the upgrade, only the data zpool to enable the new compression and dedupe on a couple file systems where they would be useful. I've checked /boot/loader.conf and /etc/fstab, and neither one has changed since it was last working. My only though is if the zroot zpool was borked somehow, but it still loads up without any issue in the fixit console (Though I had to use the -f flag on both zpools when I first loaded them, as they were "still in use" from when the server crashed). All the disks appear to be fine. The server still boots from USB and CD without throwing any errors. Does anyone have any ideas as to what the problem could be, or how I could troubleshoot this Further? ___ 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: gpt zfs raidz1 boot failure
On 2/8/2012 12:42 PM, George Kontostanos wrote: On Wed, Feb 8, 2012 at 6:03 PM, Chris Jones wrote: If you build a zfs in degraded mode, it's not bootable. But if you build it normally, then remove a disk to put it in degraded mode, it is bootable. I might be missing something here but it looks like you are trying to boot from a degraded raidz1 pool consisted from 1 drive? Correct. I've also replicated the problem using a degraded mirror consisting of 1 drive. Chris ___ 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: gpt zfs raidz1 boot failure
On Wed, Feb 8, 2012 at 6:03 PM, Chris Jones wrote: > This actually made for an interesting bug, once I dug into it some more: > http://www.freebsd.org/cgi/query-pr.cgi?pr=164861 > > If you build a zfs in degraded mode, it's not bootable. But if you build it > normally, then remove a disk to put it in degraded mode, it is bootable. > > Chris > I might be missing something here but it looks like you are trying to boot from a degraded raidz1 pool consisted from 1 drive? -- George Kontostanos Aicom telecoms ltd http://www.aisecure.net ___ 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: gpt zfs raidz1 boot failure
This actually made for an interesting bug, once I dug into it some more: http://www.freebsd.org/cgi/query-pr.cgi?pr=164861 If you build a zfs in degraded mode, it's not bootable. But if you build it normally, then remove a disk to put it in degraded mode, it is bootable. Chris On 2/4/2012 9:56 PM, Chris Jones wrote: I have a raidz1 in degraded mode, with only 1 disk available. When I try to boot it, I get this: ZFS: can only boot from disk, mirror, raidz1, raidz2 and raidz3 vdevs ZFS: i/o error - all block copies unavailable ZFS: can't read MOS ZFS: unexpected object set type 0 ...followed by a couple of attempts to load maxroot/boot/kernel/kernel. I've carefully followed the instructions at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE -- except that I'm starting with a degraded zfs so I can transition my data from gmirror. Here's more system info: maxwell$ uname -a FreeBSD maxwell.cjones.org 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 maxwell# gpart show ada2 => 34 488281183 ada2 GPT (232G) 34128 1 freebsd-boot (64k) 162 488281055 2 freebsd-zfs (232G) maxwell# zpool status pool: maxroot state: DEGRADED status: One or more devices has been taken offline by the administrator. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Online the device using 'zpool online' or replace the device with 'zpool replace'. scan: none requested config: NAME STATE READ WRITE CKSUM maxroot DEGRADED 0 0 0 raidz1-0 DEGRADED 0 0 0 ada2p2 ONLINE 0 0 0 8747991784175675917 OFFLINE 0 0 0 was /usr/bigfile errors: No known data errors The errors seem to indicate that it's getting to the first- and second-stage bootstrap, but it's unable to load /boot/zfsloader; correct? The first line of error text seems to indicate that the bootstrap thinks my pool isn't a raidz1; but the output of zpool says otherwise. Any thoughts? Chris ___ 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"
gpt zfs raidz1 boot failure
I have a raidz1 in degraded mode, with only 1 disk available. When I try to boot it, I get this: ZFS: can only boot from disk, mirror, raidz1, raidz2 and raidz3 vdevs ZFS: i/o error - all block copies unavailable ZFS: can't read MOS ZFS: unexpected object set type 0 ...followed by a couple of attempts to load maxroot/boot/kernel/kernel. I've carefully followed the instructions at http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/9.0-RELEASE -- except that I'm starting with a degraded zfs so I can transition my data from gmirror. Here's more system info: maxwell$ uname -a FreeBSD maxwell.cjones.org 9.0-RELEASE FreeBSD 9.0-RELEASE #0: Tue Jan 3 07:15:25 UTC 2012 r...@obrian.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386 maxwell# gpart show ada2 => 34 488281183 ada2 GPT (232G) 34128 1 freebsd-boot (64k) 162 488281055 2 freebsd-zfs (232G) maxwell# zpool status pool: maxroot state: DEGRADED status: One or more devices has been taken offline by the administrator. Sufficient replicas exist for the pool to continue functioning in a degraded state. action: Online the device using 'zpool online' or replace the device with 'zpool replace'. scan: none requested config: NAME STATE READ WRITE CKSUM maxroot DEGRADED 0 0 0 raidz1-0 DEGRADED 0 0 0 ada2p2 ONLINE 0 0 0 8747991784175675917 OFFLINE 0 0 0 was /usr/bigfile errors: No known data errors The errors seem to indicate that it's getting to the first- and second-stage bootstrap, but it's unable to load /boot/zfsloader; correct? The first line of error text seems to indicate that the bootstrap thinks my pool isn't a raidz1; but the output of zpool says otherwise. Any thoughts? Chris ___ 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"
Boot failure mounting 8.0BETA4.iso.gz [SOLVED]
___ 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 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
Boot failure mounting FreeBSD-8.0beta4 DVD
Dear Sirs 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 # growisofs -dvd-compat -Z /dev/dvd=8.0-BETA4... what's wrong? ___ 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: Fwd: Boot failure
On Sat, Aug 08, 2009 at 11:29:13PM -0400, Karl Vogel wrote: > >> On Sat, 8 Aug 2009 15:38:25 +0200, Roland Smith said: > > R> At $WORK the Dell computers (both desktops and servers AFAIK) that we > R> use are ditched at the first problem after the warranty runs out which > R> is after three years, I believe. > >Interesting. I've used a Dell GX260 for my workstation since 2003, >and I've had no hardware problems running two versions of FreeBSD, >one version of OpenBSD and one version of Solaris-10. Two other 260s >have been file-servers since 2004. The hardware was retired (recently a lot of GX260s) because repairs and downtime are expensive in man-hours. At $WORK there is a group of volunteers who check out and rebuild these retired machines, so they can be donated to schools et cetera. I agree that most of those machines will last several years longer. The GX260s we had only came with 128 MB RAM standard, which is a very tight to run XP with MS office at a reasonable speed. And they came with small harddisks, because most of our storage is on the network. With added RAM and a bigger harddisk it is perfectly usable. But I agree they would probably even perform better with FreeBSD or Linux on it. For myself I tend not to buy the latest and greatest hardware. It takes time for support for new hardware to materialize, and the newest fastest hardware comes with notably reduced value for money. 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) pgpta1zbxLCtq.pgp Description: PGP signature
Re: Fwd: Boot failure
>> On Sat, 8 Aug 2009 15:38:25 +0200, Roland Smith said: R> At $WORK the Dell computers (both desktops and servers AFAIK) that we R> use are ditched at the first problem after the warranty runs out which R> is after three years, I believe. Interesting. I've used a Dell GX260 for my workstation since 2003, and I've had no hardware problems running two versions of FreeBSD, one version of OpenBSD and one version of Solaris-10. Two other 260s have been file-servers since 2004. -- Karl Vogel I don't speak for the USAF or my company If caught with pants down, redefine pants.--pissed-off KDE user ___ 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 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: Fwd: Boot failure
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 -- 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) pgp3DrTdecBdb.pgp Description: PGP signature
Fwd: Boot failure
> 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. Well, I need to focus on getting my poor customers back online, so will have to put this problem aside for the weekend. As usual, thanks for the help and support from all. FreeBSD is the best OS, and this group is the best (by far) support group I've ever belonged to. I do appreciate it and I hope someday I'll know enough to give the kind of help I've gotten here. Brgds: 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: Fwd: Boot failure
>> Looks like your hardware is dying/dead. > > Sadly, I agree. > > Reset BIOS CMOS data (hardware jumper on motherboard) > Enter RAID controller BIOS, (re)set your "boot drive" > > But it looks like a fundamental BIOS control issue is malfunctioning. > > Do you have a PCI Diagnostics card? One like the following? > > http://www.uxd.com/phdpci.shtml > > (I'm not saying that exact model, but rather a device that is able to > see BIOS codes through the PCI bus that can tell very technical detail > to tech support at the motherboard's vendor (you said Intel, right?).) > > Hardware rarely up and dies. Have you tried swapping RAM chips out, > or re-ordering them to see if it might be a RAM problem? > > Maybe we're not passing POST, or that we're passing POST but the > bootable device list is not finding bootable medium. > > These kind of issues intrigue me, because it is out of the norm, and > why did it happen. > > 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. Well, I need to focus on getting my poor customers back online, so will have to put this problem aside for the weekend. As usual, thanks for the help and support from all. FreeBSD is the best OS, and this group is the best (by far) support group I've ever belonged to. I do appreciate it and I hope someday I'll know enough to give the kind of help I've gotten here. Brgds: 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: Fwd: Boot failure
Tim Judd wrote: > On 8/7/09, Roland Smith wrote: > >> Looks like your hardware is dying/dead. > > > > Sadly, I agree. > > > Reset BIOS CMOS data (hardware jumper on motherboard) > Enter RAID controller BIOS, (re)set your "boot drive" > > But it looks like a fundamental BIOS control issue is malfunctioning. > > Do you have a PCI Diagnostics card? One like the following? > > http://www.uxd.com/phdpci.shtml > > (I'm not saying that exact model, but rather a device that is able to > see BIOS codes through the PCI bus that can tell very technical detail > to tech support at the motherboard's vendor (you said Intel, right?).) > > Hardware rarely up and dies. Have you tried swapping RAM chips out, > or re-ordering them to see if it might be a RAM problem? > > > Maybe we're not passing POST, or that we're passing POST but the > bootable device list is not finding bootable medium. > > > These kind of issues intrigue me, because it is out of the norm, and > why did it happen. Sometimes I've seen when a hard drive gets old and the head movement mechanism is worn the drive can have problems properly locating the head over track 0. I've also noted that sometimes even when it can find track 0 it couldn't read the mbr. If this happens because of a bad spot has developed in the magnetic media there's nothing at this point that can be done. If it's just worn head slop sometimes you can write out a fresh mbr and use it for a while longer, but the problem will return worse later. Using smartmontools and smartctl test/diags to get a test dump from the drive can be useful at times to decide if replacement is warranted. > 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? > > --Tim ___ 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: Fwd: Boot failure
On 8/7/09, Roland Smith wrote: > Looks like your hardware is dying/dead. Sadly, I agree. Reset BIOS CMOS data (hardware jumper on motherboard) Enter RAID controller BIOS, (re)set your "boot drive" But it looks like a fundamental BIOS control issue is malfunctioning. Do you have a PCI Diagnostics card? One like the following? http://www.uxd.com/phdpci.shtml (I'm not saying that exact model, but rather a device that is able to see BIOS codes through the PCI bus that can tell very technical detail to tech support at the motherboard's vendor (you said Intel, right?).) Hardware rarely up and dies. Have you tried swapping RAM chips out, or re-ordering them to see if it might be a RAM problem? Maybe we're not passing POST, or that we're passing POST but the bootable device list is not finding bootable medium. These kind of issues intrigue me, because it is out of the norm, and why did it happen. 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? --Tim ___ 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: Fwd: Boot failure
On Fri, Aug 07, 2009 at 11:47:58AM -0400, Identry wrote: > > Realize that if you upgrade to 7.x, you'll have to remove and reinstall > > all ports because the version number of shared system libraries will > > have changed. > > Yes, I've decided this is way too complicated. > > >> Or would it be safer to try to bring up the machine on it's own with a > >> 6.2 generic kernel, first? > > > > Seeing as how you can mount the partitions on the drive perfectly by > > hand, maybe it was just a glitch. Have you tried rebooting again? > > Yes. It won't even boot into single user or safe mode. It hangs when > it tries to mount the root partition. > > > If it still doesn't work, try getting into the boot menu and see if the > > drive looks OK from there. > > Not exactly sure what you mean... How can I see what the drive looks > like from the boot menu? Sorry if this is a total newbie question... Well, if you enter the FreeBSD boot code, you get a menu. One of the choices is "escape to loader prompt" IIRC. But from your other emails I can see that you're not even getting into the boot loader... Looks like your hardware is dying/dead. 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) pgpYAfzZvoaUU.pgp Description: PGP signature
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: Fwd: Boot failure
> Realize that if you upgrade to 7.x, you'll have to remove and reinstall > all ports because the version number of shared system libraries will > have changed. Yes, I've decided this is way too complicated. >> Or would it be safer to try to bring up the machine on it's own with a >> 6.2 generic kernel, first? > > Seeing as how you can mount the partitions on the drive perfectly by > hand, maybe it was just a glitch. Have you tried rebooting again? Yes. It won't even boot into single user or safe mode. It hangs when it tries to mount the root partition. > If it still doesn't work, try getting into the boot menu and see if the > drive looks OK from there. Not exactly sure what you mean... How can I see what the drive looks like from the boot menu? Sorry if this is a total newbie question... -- 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 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: Fwd: Boot failure
On Fri, Aug 07, 2009 at 10:08:44AM -0400, Identry wrote: > > 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. > > 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.) Realize that if you upgrade to 7.x, you'll have to remove and reinstall all ports because the version number of shared system libraries will have changed. > Or would it be safer to try to bring up the machine on it's own with a > 6.2 generic kernel, first? Seeing as how you can mount the partitions on the drive perfectly by hand, maybe it was just a glitch. Have you tried rebooting again? If it still doesn't work, try getting into the boot menu and see if the drive looks OK from there. 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) pgpGVSebzUhix.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"
Fwd: Boot failure
> 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. 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? -- John -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Identry, LLC Northport, NY 11768 Phone: (631) 754-8440 Fax: (631) 980-4262 Email: jalmb...@identry.com Member: ABA, ANA, ASDA, APS, ESA, The Coalition Against Unsolicited Commercial Email, Long Island Web Developer's Guild. Visit us on the web at www.identry.com <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> BUILDING YOU A BETTER ONLINE BUSINESS <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> ___ 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"
Boot failure
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? -- 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 7.0 Boot Failure
Hello, When I boot a Dell Optiplex 320 running FreeBSD 7.0 the boot sequence hangs at USB3: OHCI version 1.0, legacy support if a keyboard is plugged in. It will boot successfully if the keyboard is not plugged in until after the boot sequence is completed. Normally this would not be that big of deal for most people, but I have 120 of these Dell machines running FreeBSD 7.0 and unplugging keyboards before the boot sequence starts is rather problematic. Thank you, Matt Hewitt President Pacific Crest Research 801-866-1116 x111 801-866-0280 Fax Always ask for exactly what you want, you just might get it! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: Q: FreeBSD 7.1 stable boot failure
John H. Nyhuis wrote: > Greetings, > > I just re-installed an old file server from stable 6.1 to 7.1 stable, > and I'm having a problem with my 3ware 7000-2 card. > > After sysinstall completes, and I try to boot from the SCSI HDD (not > connected to the 3ware) for the first time, the system hangs immediatly > after > the POST completes. The keyboard goes dead (numlock and caps lock stop > working) and it never starts to load. I can't get the system to a point > where I can get an error to work with. > > When I remove the 3ware card, the system boot fine. FreeBSD is > installed on my system's internal SCSI drives (the 3ware card manages data > disks, not OS disks). > > I've checked the media md5, and the media checks out OK. I've tried > manually setting the boot partition to the root partition on the SCSI > drives. This problem is 100% repeatable on my system using 7.1 stable (and > I did not > experiance this with 6.1 stable). I've reinstalled several times with > different options trying to get around this problem. > > The system is a Dell poweredge 2200 (dual PIII 333Mhz procs) SCSI > drives (set to 4 and 5, controller set to 7), 128MB memory, and a 3ware > 7000-2 > card which should be supported by the twe0 driver. The drives connected > to the 3ware card are 200GB maxtor drives. > > Google mentions rebuilding your RAID array (having to wipe and rebuild the > filesystem every time I patch is not really a long-term viable option), > which I did, and this did not change the hang. > > Would someone point me in the correct direction for resolving this? > Only a few things immediately jump out at me. Some older equipment really like the bootable SCSI disk to be on ID 0, with the second disk on ID 1. It's not really supposed to matter, but I recall some older stuff being flaky about this. Back then there was usually an option in the BIOS to tell which controller to attempt boot from first. It was called something like "boot from external adapter", or something like that. What it did was to initialize the ROM in the add-in card first. This machine is probably from the pre ACPI days. You probably want to boot with ACPI disabled, and this can be done from the boot menu for testing and if it works can be hard coded to be permanent. -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"
Q: FreeBSD 7.1 stable boot failure
Greetings, I just re-installed an old file server from stable 6.1 to 7.1 stable, and I'm having a problem with my 3ware 7000-2 card. After sysinstall completes, and I try to boot from the SCSI HDD (not connected to the 3ware) for the first time, the system hangs immediatly after the POST completes. The keyboard goes dead (numlock and caps lock stop working) and it never starts to load. I can't get the system to a point where I can get an error to work with. When I remove the 3ware card, the system boot fine. FreeBSD is installed on my system's internal SCSI drives (the 3ware card manages data disks, not OS disks). I've checked the media md5, and the media checks out OK. I've tried manually setting the boot partition to the root partition on the SCSI drives. This problem is 100% repeatable on my system using 7.1 stable (and I did not experiance this with 6.1 stable). I've reinstalled several times with different options trying to get around this problem. The system is a Dell poweredge 2200 (dual PIII 333Mhz procs) SCSI drives (set to 4 and 5, controller set to 7), 128MB memory, and a 3ware 7000-2 card which should be supported by the twe0 driver. The drives connected to the 3ware card are 200GB maxtor drives. Google mentions rebuilding your RAID array (having to wipe and rebuild the filesystem every time I patch is not really a long-term viable option), which I did, and this did not change the hang. Would someone point me in the correct direction for resolving this? Thanks, John H. Nyhuis IT Manager Dept. of Pediatrics HS RR541C, Box 356320 University of Washington Desk: (206)-685-3884 jnyh...@u.washington.edu ___ freebsd-sta...@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-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: Suggestions for PII 400 boot failure
Chris Pratt wrote: On Nov 20, 2008, at 4:31 PM, Vinny wrote: Hi, A friend of mine is trying out FreeBSD and ran into a booting problem. Here is his message: "Well, that's discouraging. I have put together an old PII 400 with three 20GB drives and a CDROM that I'd like to run BSD on. Half a GB of RAM I figured would be respectable. Downloaded the ISO files, burned CDs of them and when I try to run them it starts to boot and then freezes tighter than a muskrat's arse. Three lines coming on the screen and it ends with "Starting the_" and just hangs. He might want to try downloading the floppy set and booting from there. I think that is what I did on an old Dell 200 I'm using as a bridging firewall at home. This is a pathetically old machine and won't boot the ISO (I found it when cleaning out my rental, left to throw away by the renter), but it works great once you finally get the system on it. It's on 6.2 but I imagine 7.0 will be fine. Thanks everyone for your help, Here is a message from my friend: "Well, it's been a long day but I've had some success on the BSD front. I went to a couple of used/recycling/salvage places today looking for a PIII or low-end P4 motherboard and processor. I didn't see anything that was very interesting so toodled on home and had a cup of tea. I decided since the system was essentially running fine (without an OS) that I'd give the floppy disk install a bit of a run. So I downloaded all the floppy disk image files and fdimage.exe (the utility to convert them) and created all the necessary floppy disks. I did a simple install, paritioned the drives and created a user and administrator account along with some basic network settings. It seemed to connect to the internet just fine during boot up and when I ran ping against google.ca I was receiving back valid addressing information so it appears that that is all working fine. So I ran /usr/sbin/sysinstall from the root directory to try to customize the installation a bit better. I adjusted the "media type" to an ftp server as opposed to CDROM and POOF... Bob Shurunkel... BSD is now downloading an X-Windows interface from the internet as we (or I in this case) speak. I suspect there's going to be a bit of a learning curve here but I'm looking forward to it. It could have been much simpler if I would have been able to install from CD to being with but there definitely is a workaround which, in itself, pleases me. Will keep you posted." Vinny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Suggestions for PII 400 boot failure
I have put together an old PII 400 with three 20GB drives and a CDROM that I'd like to run BSD on. Half a GB of RAM I figured would be respectable. a lot of. Downloaded the ISO files, burned CDs of them and when I try to run them it starts to boot and then freezes tighter than a muskrat's arse. Three lines coming on the screen and it ends with "Starting the_" and just hangs. I've got a PIII 1000 here that I use as a file server and the boot disks run fine on that. Just won't boot off the PII 400. are you sure machine is OK. tried memtest? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Suggestions for PII 400 boot failure
Vinny wrote: Hi, A friend of mine is trying out FreeBSD and ran into a booting problem. Here is his message: "Well, that's discouraging. I have put together an old PII 400 with three 20GB drives and a CDROM that I'd like to run BSD on. Half a GB of RAM I figured would be respectable. Downloaded the ISO files, burned CDs of them and when I try to run them it starts to boot and then freezes tighter than a muskrat's arse. Three lines coming on the screen and it ends with "Starting the_" and just hangs. I've got a PIII 1000 here that I use as a file server and the boot disks run fine on that. Just won't boot off the PII 400. Weird. Really, really weird. I tried five different CDROMs in case it was the actual drive but same thing. I tried using version 6.3 instead of release 7.0 and same thing. That system doesn't like BSD/Linux whatever. I use GParted as a partition manager all the time which is bootable and same thing on that machine. It just don't like booting to that OS." Any suggestions? Thanks Vinny Excerpt from Installers guide www.a1poweruser.com PC BIOS The first thing your PC does after being powered on or when rebooting is the motherboard BIOS ROM chip gets control and it interrogates all the hardware ports on the motherboard to determine what I/O devices are attached. This is called the POST process. As part of this POST process the user changeable BIOS values stored in a CMOS chip on the motherboard are read and used to configure the PC’s hardware. These BIOS values are changed using the BIOS setup utility. The most common BOIS chip in use today is manufactured by Award. If your PC does not use an Award BIOS chip then you have to read the manual that came with your PC for details. This summary screen information is very helpful in debugging FBSD hardware problems, because it tells you what your PC hardware is and how the IRQ numbers are assigned. IRQ stands for interrupt request. An interrupt is the doorway the I/O device uses to tell the CPU that it wants its turn at getting some processing cycles. This is how the CPU shares service time among all the devices attached to the motherboard. Starting Award BIOS setup utility During the power up/reboot POST process you will see in the lower left corner of the monitor screen the message ‘Press DEL to enter setup’. While this message is showing press the keyboard delete key and the Award BIOSs setup utility main menu displays on the screen. First time changes to PC BIOS Navigate around the menus using the keyboard arrow keys looking for the following options. Your PC BIOS may not have all of these. Virus Warning=, set this option to disable. It’s a firmware check of the hard drive boot sector looking for MS/Windows boot virus. This will stop FBSD booting from the install CDROM. plug-n-play=, set this option to disable. FBSD is not sensitive to Microsoft plug-n-play standard and may refuse to install, or cause PCI cards not to be found. Disable or set to auto any BIOS option to assign IRQ numbers to PCI expansion slots. Disable any ISA expansion slots. Operating system type=, set to ‘other’ or any Unix type of operating system, don’t set to MS/Windows. Disable all power management options. boot sequence=, set this option to (CDROM,C) Since you are installing FBSD from CDROM you must tell the PC what I/O device to boot from. Follow the BIOS menu instructions to save your changes and exit. The PC will reboot it self. Keep in mind that some older CDROM drives and older legacy PC BIOS do not support booting off CDROM. Generally with PCs manufactured after 1999 this is not a problem. If you do run into this, you have a really old PC and you will need to create boot floppies to boot from. This is outside the scope of this document. Please read the FBSD Handbook at http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html#INSTALL-FLOPPIES Legacy BIOS also are incompatible with the larger hard disk sizes and the faster 66 and 100 UDMA drives. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Suggestions for PII 400 boot failure
On Nov 20, 2008, at 4:31 PM, Vinny wrote: Hi, A friend of mine is trying out FreeBSD and ran into a booting problem. Here is his message: "Well, that's discouraging. I have put together an old PII 400 with three 20GB drives and a CDROM that I'd like to run BSD on. Half a GB of RAM I figured would be respectable. Downloaded the ISO files, burned CDs of them and when I try to run them it starts to boot and then freezes tighter than a muskrat's arse. Three lines coming on the screen and it ends with "Starting the_" and just hangs. He might want to try downloading the floppy set and booting from there. I think that is what I did on an old Dell 200 I'm using as a bridging firewall at home. This is a pathetically old machine and won't boot the ISO (I found it when cleaning out my rental, left to throw away by the renter), but it works great once you finally get the system on it. It's on 6.2 but I imagine 7.0 will be fine. FreeBSD 6.2-RELEASE-p3 #3: Mon Apr 9 09:11:48 UTC 2007 snip Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Pentium/P55C (199.43-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x544 Stepping = 4 Features=0x8001bf real memory = 100663296 (96 MB) avail memory = 93102080 (88 MB) Intel Pentium detected, installing workaround for F00F bug I've got a PIII 1000 here that I use as a file server and the boot disks run fine on that. Just won't boot off the PII 400. Weird. Really, really weird. I tried five different CDROMs in case it was the actual drive but same thing. I tried using version 6.3 instead of release 7.0 and same thing. That system doesn't like BSD/Linux whatever. I use GParted as a partition manager all the time which is bootable and same thing on that machine. It just don't like booting to that OS." Any suggestions? Thanks Vinny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions- [EMAIL PROTECTED]" ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Suggestions for PII 400 boot failure
Hi, A friend of mine is trying out FreeBSD and ran into a booting problem. Here is his message: "Well, that's discouraging. I have put together an old PII 400 with three 20GB drives and a CDROM that I'd like to run BSD on. Half a GB of RAM I figured would be respectable. Downloaded the ISO files, burned CDs of them and when I try to run them it starts to boot and then freezes tighter than a muskrat's arse. Three lines coming on the screen and it ends with "Starting the_" and just hangs. I've got a PIII 1000 here that I use as a file server and the boot disks run fine on that. Just won't boot off the PII 400. Weird. Really, really weird. I tried five different CDROMs in case it was the actual drive but same thing. I tried using version 6.3 instead of release 7.0 and same thing. That system doesn't like BSD/Linux whatever. I use GParted as a partition manager all the time which is bootable and same thing on that machine. It just don't like booting to that OS." Any suggestions? Thanks Vinny ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Boot failure - Recent Kernel(s)
I am running FreeBSD 6.3-PRERELEASE with my last successful kernel build on 11/1/07. I successfully have built two kernels, one a couple of weeks ago and one just today but when I attempt to boot them these new kernels are not able to identify my boot partition. When I query the devices that the kernel sees during the boot failure all I see is an ad14 device(Which doesn't exist) and acd0. When I select the old kernel it boots without a problem. My boot device is ad10s1 which the November 1st kernel finds without a problem. I'm running a generic SMP kernel. Any ideas on what the problem is? Mark Jacobs ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Boot failure - Recent Kernel(s)
I am running FreeBSD 6.3-PRERELEASE with my last successful kernel build of 11/1/07. I successfully have built two kernels, one a couple of weeks ago and one just today but when I attempt to boot them the kernel isn't able to identify my boot partition. I query the devices that the kernel sees are an ad14 device(Which doesn't exist) and acd0. My boot device is ad10s1 which the November 1st kernel finds without a problem. Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad10s1a 507630 9389837312220%/ I am running a generic SMP kernel. Any ideas on what the problem is? Mark Jacobs ___ 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
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 instal
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
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]"
Boot failure after installation
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?
-
No need to miss a message. Get email on-the-go
with Yahoo! Mail for Mobile. Get started.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Boot failure in installation -- not ACPI related
Looking over the installation FAQ, the only reference I see to a crash has to do with turning off ACPI in the BIOS. I have already done that, and have successfully installed Net and Open on an HP xw4300 workstation (64-bit Intel Pentium D). The amd64 bootonly 6.1RELEASE CD (burned from your .iso) boots and puts up a countdown menu. Then, whether the countdown ends or I select any of the 7 options in the menu, I immediately get the following: panic: No BIOS smap info from loader! and the system has to be power-cycled to reboot. Please point me at where I should look next. Rich Alderson ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: diskless boot failure after installing xorg
Erik Nørgaard wrote: /home -alldirs -network 192.168.0.0 -mask 255.255.255.0 /var/diskless/FreeBSD -ro -mapall=root:wheel -network 192.168.0.0 -mask 255.255.255.0 /var/diskless/192.168.0.16/var 192.168.0.16 42cm error: -mapall should be -maproot Erik -- Ph: +34.666334818 web: www.locolomo.org S/MIME Certificate: www.daemonsecurity.com/ca/8D03551FFCE04F06.crt Subject ID: 9E:AA:18:E6:94:7A:91:44:0A:E4:DD:87:73:7F:4E:82:E7:08:9C:72 Fingerprint: 5B:D5:1E:3E:47:E7:EC:1C:4C:C8:3A:19:CC:AE:14:F5:DF:18:0F:B9 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
diskless boot failure after installing xorg
Hi, I have just tried to setup 6.0BETA5 for diskless clients - just for the sport :-) I have installed the full system into /var/diskless/FreeBSD. Everything actually went fine, I could boot up, got root mounted and the home dir. So, next step was to install X.Org: chroot into /var/diskless/FreeBSD and install from ports. Now, boot ends after identifying system resources: NFS ROOT: 192.168.0.2:/var/diskless/FreeBSD sis0: link changed to up nfs_getpages: error 13 exec /sbin/init: error 5 sysctl: unknown oid 'kern.bootp_cookie' Interface sis0 IP-Address 192.168.0.16 broadcast 192.168.0.255 mount_nfs: can't update /var/db/mounttab for 192.168.0.2:/var/diskless/FreeBSD nfs server 192.168.0.2:/var/diskless/FreeBSD: not responding nfs server 192.168.0.2:/var/diskless/FreeBSD: not responding ... Booting on the hard drive, I have no problem mounting any of the exported nfs shares. It appears to me that now, somehow the diskless client looses the root device or tries to remount it, the 'kern.bootp_cookie' error seems to suggest that the bootp parameters are nolonger passed correctly to the next boot stage. But I have no idea why this occurs or what has changed. The line mount_nfs... obviously occurs if no writable /var is available when mounting a nfs device. But is not fatal, I had succesfully mounted shares before installing X despite the error. Any ideas? Thanks, Erik PS: Doing the setup, I wrote my own guide for setting up diskless clients which quite detailed describes what I have done: www.daemonsecurity.com/pxe Setup (linewrapping is mine for this mail): showmount -e: Exports list on localhost: /var/diskless/FreeBSD 192.168.0.0 /var/diskless/192.168.0.16/var 192.168.0.16 /home 192.168.0.0 /etc/exports: /home -alldirs -network 192.168.0.0 -mask 255.255.255.0 /var/diskless/FreeBSD -ro -mapall=root:wheel -network 192.168.0.0 -mask 255.255.255.0 /var/diskless/192.168.0.16/var 192.168.0.16 /var/diskless/FreeBSD/etc/fstab: # Device Mount FStype Opt Dump Pass# 192.168.0.2:/var/diskless/FreeBSD / nfs rw 0 0 proc /proc procfs rw 0 0 192.168.0.2:/home /home nfs rw 0 0 192.168.0.2:/var/diskless/192.168.0.16/var /var nfs rw 0 0 I have tried to remove the line for the root device assuming that it would then not be remounted when the other devices are mounted - no result. Also I have tried to remove it completly with no result. /var/diskless/FreeBSD/etc/rc.conf: Basically, disables mfs var and tmp, cron and sendmail and configures the console. -- Ph: +34.666334818 web: http://www.locolomo.org S/MIME Certificate: http://www.locolomo.org/crt/2004071206.crt Subject ID: A9:76:7A:ED:06:95:2B:8D:48:97:CE:F2:3F:42:C8:F2:22:DE:4C:B9 Fingerprint: 4A:E8:63:38:46:F6:9A:5D:B4:DC:29:41:3F:62:D3:0A:73:25:67:C2 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
BOOT Failure 5.4
Hi, I'm running FreeBSD on a CompaQ PL5000. I installed 5.3 which worked ok, I then CVSup'd to using RELENG_5 tag. After buildworld and build kernel the system fails to reboot. As far as I can tell, it is trying to load GEOM which fails to find any drives. I end up at a prompt - mountroot> using the ? option for a list of valid boot devices only lists the cd and floppy disk. How can I stop GEOM from loading, is there an option in the kernel conf file or do I need to put something in loader.conf? Rob ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
pxe boot failure
Hello,
I'm trying to get pxeboot running without any success so far.
I get 'BTX halted' after a register dump showing an int 6.
I read almost anything, I could find about that problem.
I tried with/without LOADER_TFTP_SUPPORT, I uncommented
those delay() lines in pxe.c and enlarged the delays.
I even doubled some of the internal buffers.
The crash is always at different locations. The last
message usually is "pxe_open: gateway ip: 10.47.11.1".
Tcpdump shows no problems.
So am I just having a buggy boot prom?
My board has an intel 82559er chip and I was told
by the board's manufacturer, that linux pxeboot
does work fine, which not really helps. They have no
newer bios update and know nothing about pxe problems.
My environment is FreeBSD 4.11 with latest ISC dhcpd.
Here are my settings:
/usr/local/dhcpd.conf:
default-lease-time 600;
max-lease-time 7200;
ddns-update-style ad-hoc;
log-facility local7;
subnet 10.47.11.0 netmask 255.255.255.0 {
range dynamic-bootp 10.47.11.10 10.47.11.99;
option routers 10.47.11.1;
filename "pxeboot";
next-server 10.47.11.1;
option root-path "10.47.11.1:/usr/local/diskless_root";
}
/etc/inetd.conf (for LOADER_TFTP_SUPPORT=yes):
tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s
/usr/local/diskless_root
/etc/exports:
/usr -ro -maproot=0 -alldirs -network 10.47.11.00 -mask 255.255.255.0
BTW, booting via etherboot disk works. I just have to replace "pxeboot" with
"kernel"
in dhcpd.conf.
Any hints?
Thank you,
Norbert
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Change to different SCSI interface causes boot failure
Danny Horne <[EMAIL PROTECTED]> writes: > I'm trying to replace the motherboard in my FreeBSD 4.11-RELEASE > server for a different one. The old board has on-board Adaptec > AIC-7896N SCSI, the new one has on-board Symbios Ultra3 SCSI, on > bootup I get the following error - > > Mounting root from ufs:/dev/da0s0a > setrootbyname failed > ffs_mountroot: can't find rootvp > Rootmount failed:6 > > Is there any way I can boot the drive on this new interface? I haven't had to think about this in a long time, but I would expect that telling the loader(8) where to find the root (root_disk_unit or rootdev) should let it progress further. You'll still need to fix /etc/fstab, I suspect. > I've searched the archives & found a similar problem in which the > solution was to use dump to create a backup & do a fresh install of > FreeBSD on the new system before restoring the backup. If I have to > take this route I might as well upgrade to 5.3, but I understand this > uses a different filesystem to 4.11, so would this give problems with > a restore from a 4.11 dump? No. The UFS2 restore(8) understands UFS1 dump files. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Change to different SCSI interface causes boot failure
Hi all, I'm trying to replace the motherboard in my FreeBSD 4.11-RELEASE server for a different one. The old board has on-board Adaptec AIC-7896N SCSI, the new one has on-board Symbios Ultra3 SCSI, on bootup I get the following error - Mounting root from ufs:/dev/da0s0a setrootbyname failed ffs_mountroot: can't find rootvp Rootmount failed:6 Is there any way I can boot the drive on this new interface? I've searched the archives & found a similar problem in which the solution was to use dump to create a backup & do a fresh install of FreeBSD on the new system before restoring the backup. If I have to take this route I might as well upgrade to 5.3, but I understand this uses a different filesystem to 4.11, so would this give problems with a restore from a 4.11 dump? Thanks for all replies ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Regarding Boot failure
If it does not continue from there (did you press return?) something went wrong during the installation process because apparently the kernel is not where the bootloader expects it. Try to do the install again and make sure the bootloader is installed on the right place. The handbooks install section covers all aspects of this faily well, so its a good idea to have access to it while installing. I hope that helps, Alex, ramuK hsiraH wrote: Hai i have removed all the disk's from their respective drives but still i have tha same problem of prompting the same message what to do then Harish --- Nagilum <[EMAIL PROTECTED]> wrote: Hi, Could it be that you forgot to remove the mfsroot floppy from the diskdrive when you rebooted? Regards, Alex. ramuK hsiraH wrote: Hai every body Recently i have installed FreeBSD5.3 the installation process is quiet nice when the system reboots it prompts with the message as follows FreeBSD .. Default : 0(1,a)/kernel boot: it stops there what to do next plz help me continue from there Bye Harish Kumar fios.sourceforge.net Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Regarding Boot failure
Hi, Could it be that you forgot to remove the mfsroot floppy from the diskdrive when you rebooted? Regards, Alex. ramuK hsiraH wrote: Hai every body Recently i have installed FreeBSD5.3 the installation process is quiet nice when the system reboots it prompts with the message as follows FreeBSD .. Default : 0(1,a)/kernel boot: it stops there what to do next plz help me continue from there Bye Harish Kumar fios.sourceforge.net Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Regarding Boot failure
Hai every body Recently i have installed FreeBSD5.3 the installation process is quiet nice when the system reboots it prompts with the message as follows FreeBSD .. Default : 0(1,a)/kernel boot: it stops there what to do next plz help me continue from there Bye Harish Kumar fios.sourceforge.net Yahoo! India Matrimony: Find your life partner online Go to: http://yahoo.shaadi.com/india-matrimony ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Boot failure: CD-ROM problem [taskqueue stalled]
I have a system here that occasionally hangs while the kernel is booting. It happens as the CD-ROM drive is being initialized. Here's the error: acd0: WARNING - MODE_SENSE_BIG interrupt was seen but taskqueue stalled This doesn't happen every time - usually if I restart the system following the error, it will start right up. When the kernel does boot okay, here's that same line: acd0: CDROM at ata1-master PIO0 I found the module responsible for generating the error message - ata-queue.c - but I don't know enough to follow the C code to understand what's happening: "http://fxr.watson.org/fxr/source/dev/ata/ata-queue.c"; I know the drive works - I used it to install the system. I would be interested to know what the cause of this error is and if there is a convenient workaround. If not, it's no tragedy if I have to pull the drive out. On the other hand, this could be symptomatic of a problem with the ata system in FreeBSD. In any case, your help is appreciated. Here's what's in and on this thing: FreeBSD 5.2.1 (problem exisits with custom and GENERIC kernels) Pentium 233 / 64 MB / Intel 430TX chipset with PIIX4 UDMA33 controller Acer 32x CD-ROM at secondary master Thanks Ryan ___ Sent via PCHG Webmail http://www.pchg.net ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9, 5.1 boot failure after install
We finally have mail working again. I heard a number of responses. though none was the actual solution, corporately they massaged one to being. From one guy who installed redhat, to someone using the live disk, to adjusting bootstraps I still couldn't get to the file system, even after installing slackware. Problem is the hologram was writing over the error prompt. It wasn't until I used the raid device format and attempted to install that I got a readable error "not close enough to boundary edge" that I caught on that I probably had a geometry problem. I installed slackware but that didn't work. Out of frustration I installed windows 2000 and successfully replaced it with 4.9. I then tried to replace that with 5.1 and it failed. I then tried to reinstall 4.9 and that failed. I then went back to installing windows 2000 then replacing it with 4.9 and writing the geometry down. On the next attempt to install 5.1 I saw the geometry changed and the install failed. I attempted to reinstall 4.9 and it failed. I again reinstalled 4.9 changing the geometry to what I'd written down and the install was successful. The geometry chosen by windows worked. Now I don't know if it is the best economy (could be windows huge blocks wasting space on small files) but it does work. Here's the rub, this geometry is a lucky guess on 17G drives, what about when I replace them with 50 or 80G drives. How do I figure out the proper geometry? I'd like to setup 5.1 before I commit this box to the network, but it needs a different geometry that I couldn't guess. Is there a requirement standard? A special offset at the start of the disk space? any help much appreciated. Dan To: [EMAIL PROTECTED] Copies to: [EMAIL PROTECTED] Send reply to: [EMAIL PROTECTED] Subject:Re: 4.9, 5.1 boot failure after install From: Lowell Gilbert <[EMAIL PROTECTED]> Date sent: 27 Dec 2003 10:11:21 -0500 > [EMAIL PROTECTED] writes: > > > Hello, > > > > I had 4.9 release working and did a clean install of 5.1 release over > > the 4.9 and ended up with boot failure after install. Using allBSD > > partition and standard MBR I get a missing operating system error. If I > > use the FreeBSD boot I just get "default F1" and a beep. Now trying to > > install the 4.9 gives the same results. > > > > I'm using a Mylex DAC960ptl (accelraid 250) with the primary disk > > setup as JBOD. I set the bootable disk as active but everytime I go > > back to config fdisk the flag is not set. > > > > I then upgraded and flashed the RAID card, reformatted the disks and > > tried a 4.9 install, again with the same results. > > > > Is there an issue with the DAC card geometry or BIOS? Or a subtle > > quirk that isn't documented yet? > > Sounds more like you're not using the option to actually write out the > results to disk. (W)rite, maybe? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9, 5.1 boot failure after install
On Sat, 27 Dec 2003 02:53 am, [EMAIL PROTECTED] wrote: > Hello, > > I had 4.9 release working and did a clean install of 5.1 release over > the 4.9 and ended up with boot failure after install. Using allBSD > partition and standard MBR I get a missing operating system error. If I > use the FreeBSD boot I just get "default F1" and a beep. Now trying to > install the 4.9 gives the same results. > > I'm using a Mylex DAC960ptl (accelraid 250) with the primary disk > setup as JBOD. I set the bootable disk as active but everytime I go > back to config fdisk the flag is not set. > > I then upgraded and flashed the RAID card, reformatted the disks and > tried a 4.9 install, again with the same results. > > Is there an issue with the DAC card geometry or BIOS? Or a subtle > quirk that isn't documented yet? > > thanks, > Dan > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "[EMAIL PROTECTED]" I have had a similar problem. I also couldnt get it to make the system bootable using the install cd. I got around it by using the live filesystem cd. I dont know how that they are different but it seemed to write out the changes when I asked not like as in the install disk. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9, 5.1 boot failure after install
Hi, I've tried both methods. Letting the install program WRITE to FDISK upon completion and writing directly after making the partitions and setting the labels. Writing during the install gives the prompt that on new installs the routine will write later, do I really want to do it now. When I click yes I get the prompt that it is successfully written. I assume that when I return to fdisk it will show a current setting (ie. active or not). Is the install operating on a ramdisk doing a final write on completion? I read one place that a person had the same problem and installed redhat successfully then reinstalled FreeBSD and the geometry was changed in fdisk. Is there a geometry issue? thanks, Dan To: [EMAIL PROTECTED] Copies to: [EMAIL PROTECTED] Send reply to: [EMAIL PROTECTED] Subject:Re: 4.9, 5.1 boot failure after install From: Lowell Gilbert <[EMAIL PROTECTED]> Date sent: 27 Dec 2003 10:11:21 -0500 > [EMAIL PROTECTED] writes: > > > Hello, > > > > I had 4.9 release working and did a clean install of 5.1 release over > > the 4.9 and ended up with boot failure after install. Using allBSD > > partition and standard MBR I get a missing operating system error. If I > > use the FreeBSD boot I just get "default F1" and a beep. Now trying to > > install the 4.9 gives the same results. > > > > I'm using a Mylex DAC960ptl (accelraid 250) with the primary disk > > setup as JBOD. I set the bootable disk as active but everytime I go > > back to config fdisk the flag is not set. > > > > I then upgraded and flashed the RAID card, reformatted the disks and > > tried a 4.9 install, again with the same results. > > > > Is there an issue with the DAC card geometry or BIOS? Or a subtle > > quirk that isn't documented yet? > > Sounds more like you're not using the option to actually write out the > results to disk. (W)rite, maybe? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.9, 5.1 boot failure after install
[EMAIL PROTECTED] writes: > Hello, > > I had 4.9 release working and did a clean install of 5.1 release over > the 4.9 and ended up with boot failure after install. Using allBSD > partition and standard MBR I get a missing operating system error. If I > use the FreeBSD boot I just get "default F1" and a beep. Now trying to > install the 4.9 gives the same results. > > I'm using a Mylex DAC960ptl (accelraid 250) with the primary disk > setup as JBOD. I set the bootable disk as active but everytime I go > back to config fdisk the flag is not set. > > I then upgraded and flashed the RAID card, reformatted the disks and > tried a 4.9 install, again with the same results. > > Is there an issue with the DAC card geometry or BIOS? Or a subtle > quirk that isn't documented yet? Sounds more like you're not using the option to actually write out the results to disk. (W)rite, maybe? ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
4.9, 5.1 boot failure after install
Hello, I had 4.9 release working and did a clean install of 5.1 release over the 4.9 and ended up with boot failure after install. Using allBSD partition and standard MBR I get a missing operating system error. If I use the FreeBSD boot I just get "default F1" and a beep. Now trying to install the 4.9 gives the same results. I'm using a Mylex DAC960ptl (accelraid 250) with the primary disk setup as JBOD. I set the bootable disk as active but everytime I go back to config fdisk the flag is not set. I then upgraded and flashed the RAID card, reformatted the disks and tried a 4.9 install, again with the same results. Is there an issue with the DAC card geometry or BIOS? Or a subtle quirk that isn't documented yet? thanks, Dan ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
boot failure on new 4.8 kernel: DPT scsi and SMP
I would welcome any suggestions on a boot problem with an SMP kernel for FreeBSD 4.8 (RELENG_4_8 obtained May 21). GENERIC (uniprocessor) kernel works fine and FreeBSD uniprocessor has worked fine on this machine for a couple years. (Opensound now supports SMP, so I'm finally trying the SMP kernel.) I configured an SMP kernel by selecting the flags for APIC and SMP, and eliminating CPU types other than my i586 (Pentium 233 MMX). I made no other changes. I used "make buildkernel KERNCONF=CUSTOM" and "make installkernel KERNCONF=CUSTOM" which gave no errors. Boot with the SMP kernel proceeds normally until it loads the second CPU followed by "Waiting 15 seconds for SCSI devices to settle." The messages that indicated a start for SMP support are: APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! At that point, both SCSI adapters and both IDE drives had already been detected. Then, there is an abnormally long pause (longer than the normal 15 second for SCSI devices to settle) followed by messages that look like it's probing 15 scsi IDs (0-14), timing out on each one, and then probing again. The boot finally just stopped with no kernel panic or final message. The GENERIC kernel boots just fine. I also tried an SMP kernel with APM commented out. I get nearly the same error messages. Motherboard: Tyan S1564D with 2 x Pentium 233MMX, 256 MB EDO RAM Hard drives: 2 x IDE (ad0,ad2); 2 x SCSI (da0,da1) on the DPT PM2044UW controller (FreeBSD is on first SCSI drive) SCSI: DPT PM 2044UW with 2 Seagate UW hard drives (da0,da1) and a Plextor cdrom (cd0); Adaptec 1542CP with a Yamaha CDRW (cd1), an external Orb removable drive (da2), and a scanner which is turned off and not used in FreeBSD. Video: ATI XPERT98 Here is the last page of boot messages for the SMP kernel with APM disabled. At this point, both SCSI cards and the IDE drives have been detected, and the system waited 15 seconds for the SCSI devices to settle. Note that the system is probing both SCSI buses. This is just the last page. There were maybe six lines before these for probing the Adaptec 1542CP (aha). (probe20:aha1:0:5:0): INQUIRY CDB: 12 1 80 0 ff 0 (probe20:aha1:0:5:0): ILLEGAL REQUEST asc:24,0 (probe20:aha1:0:5:0): Invalid field in CDB sks:c0,1 (probe0:dpt0:0:0:0): CCB 0xccce2744 - timed out (probe0:dpt0:0:0:0): CCB 0xccce2744 - timed out CCB already completed (probe1:dpt0:0:1:0): CCB 0xccce26c8 - timed out (probe1:dpt0:0:1:0): CCB 0xccce26c8 - timed out CCB already completed (probe2:dpt0:0:2:0): CCB 0xccce264c - timed out (probe3:dpt0:0:3:0): CCB 0xccce25d0 - timed out (probe4:dpt0:0:4:0): CCB 0xccce2554 - timed out (probe5:dpt0:0:5:0): CCB 0xccce24d8 - timed out (probe6:dpt0:0:6:0): CCB 0xccce245c - timed out (probe7:dpt0:0:8:0): CCB 0xccce23e0 - timed out [note: probe7 & 0:8:0] (probe8:dpt0:0:9:0): CCB 0xccce2364 - timed out (probe9:dpt0:0:10:0): CCB 0xccce22e8 - timed out (probe10:dpt0:0:11:0): CCB 0xccce226c - timed out (probe11:dpt0:0:12:0): CCB 0xccce21f0 - timed out (probe12:dpt0:0:13:0): CCB 0xccce2174 - timed out (probe13:dpt0:0:14:0): CCB 0xccce20f8 - timed out (probe14:dpt0:0:15:0): CCB 0xccce207c - timed out (probe0:dpt0:0:0:0): CCB 0xccce2744 - timed out (probe1:dpt0:0:1:0): CCB 0xccce26c8 - timed out (probe2:dpt0:0:2:0): CCB 0xccce264c - timed out (probe3:dpt0:0:3:0): CCB 0xccce25d0 - timed out There were no further messages while I copied these by hand. These messages are nearly identical to the messages from the SMP kernel with APM, but the hex codes differ by 1 in the 7th position. For example, the last line was 0xccce15d0 for the SMP kernel with APM. Thanks for any suggestions, Rick Voland [EMAIL PROTECTED] ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: 4.7-STABLE upgrade boot failure. - Semi-solved.
>
> No, I just meant that I copied MAKEDEV from /usr/src into /dev, and
> then ran ./MAKEDEV std from /dev, as per the UPDATING instructions.
hmm, does UPDATING say you should do that? all I know is
>>mergemaster
asks whether I want to have /dev/* rebuilt, and I let it do so.
UPDATING notwithstanding, you did *not* rebuild ad{4,5}*. take a
look in /dev/MAKEDEV: calling it with "std" does not touch ad* at
all. what you want is:
cd /dev && ./MAKEDEV all ad4 ad5
yeah, this updated my ad* entries just fine, which was actually the
conclusion i'd come to a little while ago, i just didn't know how to do
>it.
Silly me thinking that "all" == everything.
all of this aside, the base problem remains. Even with the updated >ad*
entries sitting in /dev, I still get a root mount failed error message >on
boot with no way I can see to load the 4.7 kernel.
Okay, just to update.. after much searching and reading, I discovered that
the way FreeBSD past a certain point is *supposed* to handle RAID hardware
arrays is to designate them as arX, and then you can use atacontrol to
attach/detach/whatever.
So basically, when I updated to 4.7-STABLE from 4.5-RC1, I was changing
the way it was looking at my current mirror setup. It now wanted to see the
array as ar0, except it wouldn't boot off of ar0s1a or anything.
I broke the mirror and promptly tried to boot with ad4 and ad5 being
individual drives instead of a mirror, and suddenly /dev/ad4s1a would boot
just fine.
Why it recognized the HPT370 as ar0 on 4.5 and worked fine while booting a
hardware mirrored drive from /dev/ad4s1a, and would not do the same under
4.7, I couldn't tell you.
So now my question is, how can I recreate the mirror? I don't want to take
down my whole system and resynch those two drives only to have it fail to
boot again. Should I just do it in software?
Anyways, thanks for all the helpful suggestions.
Aaron Lewis.
_
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
From: Roman Neuhauser <[EMAIL PROTECTED]>
> >
> >did you let mergemaster run MAKEDEV for you, or did you run
> >
> >/dev/MAKEDEV std
> >
> >while being in /usr/src? If the latter, you didn't rebuild the
> >devices in /dev/, you created them in /usr/src instead! That would
> >indeed explain your problems.
>
> No, I just meant that I copied MAKEDEV from /usr/src into /dev, and
> then ran ./MAKEDEV std from /dev, as per the UPDATING instructions.
hmm, does UPDATING say you should do that? all I know is >mergemaster
asks whether I want to have /dev/* rebuilt, and I let it do so.
UPDATING notwithstanding, you did *not* rebuild ad{4,5}*. take a
look in /dev/MAKEDEV: calling it with "std" does not touch ad* at
all. what you want is:
cd /dev && ./MAKEDEV all ad4 ad5
yeah, this updated my ad* entries just fine, which was actually the
conclusion i'd come to a little while ago, i just didn't know how to do it.
Silly me thinking that "all" == everything.
all of this aside, the base problem remains. Even with the updated ad*
entries sitting in /dev, I still get a root mount failed error message on
boot with no way I can see to load the 4.7 kernel.
the 4.5RC1 kernel still loads. scratching my head..
Thanks for the help.
Aaron Lewis.
_
MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*
http://join.msn.com/?page=features/virus
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
# [EMAIL PROTECTED] / 2003-01-21 09:42:23 -0800:
> ># [EMAIL PROTECTED] / 2003-01-21 08:36:33 -0800:
> >> >Or maybe, are you really sure you have the proper devices in /dev?
> >>
> >> No, I'm not. At this point I'm not sure of anything, seems like. All
> >I've
> >> done in /dev is a MAKEDEV std with the MAKEDEV directly from /usr/src,
> >> without removing the devices currently in there. It was my understanding
> >> that that would rebuild everything.
> >
> >did you let mergemaster run MAKEDEV for you, or did you run
> >
> >/dev/MAKEDEV std
> >
> >while being in /usr/src? If the latter, you didn't rebuild the
> >devices in /dev/, you created them in /usr/src instead! That would
> >indeed explain your problems.
>
> No, I just meant that I copied MAKEDEV from /usr/src into /dev, and
> then ran ./MAKEDEV std from /dev, as per the UPDATING instructions.
hmm, does UPDATING say you should do that? all I know is mergemaster
asks whether I want to have /dev/* rebuilt, and I let it do so.
UPDATING notwithstanding, you did *not* rebuild ad{4,5}*. take a
look in /dev/MAKEDEV: calling it with "std" does not touch ad* at
all. what you want is:
cd /dev && ./MAKEDEV all ad4 ad5
> Sorry for replying privately, this account isn't on the list. I'll be
> sure to CC it in from now on.
thanks; I *really* prefer to not receive personal copies, though.
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message.see http://www.eyrie.org./~eagle/faqs/questions.html
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
did you let mergemaster run MAKEDEV for you, or did you run /dev/MAKEDEV std while being in /usr/src? If the latter, you didn't rebuild the devices in /dev/, you created them in /usr/src instead! That >>would indeed explain your problems. No, I just meant that I copied MAKEDEV from /usr/src into /dev, and >then ran ./MAKEDEV std from /dev, as per the UPDATING instructions. I do suspect this as being related, as I just noted that as of the 20020318 entry notes an ATA change. I'm just not sure what else to try. After inspecting /dev a bit more thoroughly, I also found that after a ./MAKEDEV all, everything is updated to the current date except for all of the ad4 entries, and the ad5 entry. These remain dated May 8 2001. The MAKEDEV has been run normally, and from single-user. Seeing as how there was apparently an ATA update in March of 2002.. Is there a way I can safely remove and rebuild those entries? Or is this even related at all? I'm grasping at straws, I know. Thanks for your help. Aaron Lewis. _ The new MSN 8 is here: Try it free* for 2 months http://join.msn.com/?page=dept/dialup To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
# [EMAIL PROTECTED] / 2003-01-21 08:36:33 -0800: > >Or maybe, are you really sure you have the proper devices in /dev? > > No, I'm not. At this point I'm not sure of anything, seems like. All I've > done in /dev is a MAKEDEV std with the MAKEDEV directly from /usr/src, > without removing the devices currently in there. It was my understanding > that that would rebuild everything. did you let mergemaster run MAKEDEV for you, or did you run /dev/MAKEDEV std while being in /usr/src? If the latter, you didn't rebuild the devices in /dev/, you created them in /usr/src instead! That would indeed explain your problems. No, I just meant that I copied MAKEDEV from /usr/src into /dev, and then ran ./MAKEDEV std from /dev, as per the UPDATING instructions. I do suspect this as being related, as I just noted that as of the 20020318 entry notes an ATA change. I'm just not sure what else to try. Sorry for replying privately, this account isn't on the list. I'll be sure to CC it in from now on. I appreciate the suggestions. Aaron Lewis. _ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
please at least keep the mailing list among recipients: see my signature. # [EMAIL PROTECTED] / 2003-01-21 08:36:33 -0800: > >Or maybe, are you really sure you have the proper devices in /dev? > > No, I'm not. At this point I'm not sure of anything, seems like. All I've > done in /dev is a MAKEDEV std with the MAKEDEV directly from /usr/src, > without removing the devices currently in there. It was my understanding > that that would rebuild everything. did you let mergemaster run MAKEDEV for you, or did you run /dev/MAKEDEV std while being in /usr/src? If the latter, you didn't rebuild the devices in /dev/, you created them in /usr/src instead! That would indeed explain your problems. do: cd /dev && ./MAKEDEV all and let us know about the results. -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
Re: 4.7-STABLE upgrade boot failure.
# [EMAIL PROTECTED] / 2003-01-16 12:52:23 -0800: > Did a clean buildworld, installworld, etc. etc. on a 4.5-RC1 system up to > 4.7-STABLE release. Everything went through fine, no problems. > > Rebuilt kernel and installed the new 4.7 GENERIC kernel, no problems. > > Ran mergemaster, did a MAKEDEV, no problems. > > Rebooted.. and problems. Upon boot, it tries to load up the root partition > off of /dev/ad4s1a (which is correct), but brings up a "Mount boot failure: > 16" error, and asks for a good ufs root location. Typing in > ufs:/dev/ad4s1a does no good. > > IDE controller = Highpoint HPT370 onboard = ar0. > IDE drives = 2x IBM 60gig mirrored = ad4, ad5. > > Eventually, had to boot to 4.5-RC1 kernel which came up fine on > /dev/ad4s1a. The problem is, everything else is 4.7 now, so there's lots of > weirdness. I'm not sure what your problem is. I just recently installed 4.7-RELEASE on a HPT370A-based HighPoint card (RAID1), and the only problems I had was that for some reason disklabel put the / partition beyond the bootable area at the beggining of the disk, and I didn't notice it, and disk numbering. ATA_STATIC_ID seems to be used in 4.7's GENERIC... I'm out of ideas. Or maybe, are you really sure you have the proper devices in /dev? -- If you cc me or remove the list(s) completely I'll most likely ignore your message.see http://www.eyrie.org./~eagle/faqs/questions.html To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
4.7-STABLE upgrade boot failure.
First, let me profusely apologize if this is a dual post, as I tried to post two days ago and never saw it come up on the list. Trying now with a free webmail account. Did a clean buildworld, installworld, etc. etc. on a 4.5-RC1 system up to 4.7-STABLE release. Everything went through fine, no problems. Rebuilt kernel and installed the new 4.7 GENERIC kernel, no problems. Ran mergemaster, did a MAKEDEV, no problems. Rebooted.. and problems. Upon boot, it tries to load up the root partition off of /dev/ad4s1a (which is correct), but brings up a "Mount boot failure: 16" error, and asks for a good ufs root location. Typing in ufs:/dev/ad4s1a does no good. IDE controller = Highpoint HPT370 onboard = ar0. IDE drives = 2x IBM 60gig mirrored = ad4, ad5. Eventually, had to boot to 4.5-RC1 kernel which came up fine on /dev/ad4s1a. The problem is, everything else is 4.7 now, so there's lots of weirdness. The problem is in the kernel? No more support for Highpoint controllers? Is there something else I should be doing in /dev besides a MAKEDEV std? Help? Aaron Lewis [EMAIL PROTECTED] _ MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
