Re: Boot failure mounting FreeBSD-8.0beta4 DVD

2009-09-17 Thread Roland Smith
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 t

Re: Boot failure

2009-08-08 Thread Roland Smith
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 swa

Re: Boot failure

2009-08-08 Thread Jerry
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 y

Re: Boot failure

2009-08-07 Thread Roland Smith
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% f

Re: Boot failure

2009-08-07 Thread Identry
> 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

Re: Boot failure

2009-08-07 Thread Identry
> 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

Re: Boot failure

2009-08-07 Thread Identry
> 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

Re: Boot failure

2009-08-07 Thread Identry
>> > 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 fil

Re: Boot failure

2009-08-07 Thread Tim Judd
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 yo

Re: Boot failure

2009-08-07 Thread Erik Trulsson
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

Re: Boot failure

2009-08-07 Thread Identry
>> 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'

Re: Boot failure

2009-08-07 Thread Identry
> 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 br

Re: Boot failure

2009-08-07 Thread Odhiambo ワシントン
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.

Re: Boot failure

2009-08-07 Thread Roland Smith
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

Re: Boot failure

2009-08-07 Thread Identry
>> 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

Re: Boot failure

2009-08-07 Thread Identry
> 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 no

Re: Boot failure

2009-08-07 Thread cpghost
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

Re: Boot failure

2009-08-07 Thread Identry
> 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

Re: Boot failure

2009-08-07 Thread Odhiambo ワシントン
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 y

Re: Boot failure

2009-08-07 Thread cpghost
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/kern

Re: Boot failure

2009-08-07 Thread Odhiambo ワシントン
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. >

Re: Boot failure

2009-08-07 Thread Identry
>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 sa

Re: Boot failure

2009-08-07 Thread Vincent Hoffman
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 >

Re: Boot failure

2009-08-06 Thread Identry
> 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 e

Re: Boot failure

2009-08-06 Thread Polytropon
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

Re: Boot failure

2009-08-06 Thread Michael Powell
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

Re: Boot failure

2009-08-06 Thread Roland Smith
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/ker

Re: Boot failure

2009-08-06 Thread Identry
> 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 c

Re: Boot failure

2009-08-06 Thread Identry
> 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 e

Re: Boot failure

2009-08-06 Thread Vincent Hoffman
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 >

Re: Boot failure after installation

2007-04-12 Thread L Goodwin
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 s

Re: Boot failure after installation

2007-04-12 Thread Jerry McAllister
> 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

Re: Boot failure after installation

2007-04-11 Thread L Goodwin
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),

Re: Boot failure after installation

2007-04-11 Thread Jerry McAllister
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 ru

Re: Boot failure after installation

2007-04-10 Thread L Goodwin
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

Re: Boot failure after installation

2007-04-10 Thread Christian Walther
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 chec

Re: Boot failure after installation

2007-04-10 Thread Derek Ragona
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 d

Re: Boot failure after installation

2007-04-09 Thread L Goodwin
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 t

Re: Boot failure after installation

2007-04-09 Thread L Goodwin
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

Re: Boot failure after installation

2007-04-09 Thread Derek Ragona
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.

Re: Boot failure after installation

2007-04-09 Thread Josh Paetzel
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 >