On 3 August 2011 18:15, Mehma Sarja <[email protected]> wrote: > On 8/3/11 1:29 AM, Nick Upson wrote: > > > > On 2 August 2011 17:09, Mehma Sarja <[email protected]> wrote: > >> On 8/2/11 8:22 AM, Nick Upson wrote: >> >>> ok, I'm close to giving up with installing pfsense 1.2.3 or 2.0rc3 onto >>> the FX5624 harddrive, >>> >>> Does anyone have suggestions for similiar hardware (6 lan ports, >>> preferably rack mount) that is available in the UK >>> >>> -- >>> Nick Upson (01799 533252) >>> >>> We really need more info than provided. What is a FX5624? Is it a >> drive or a system? Who makes it? Googling it, "Fanless Celeron M CPU and 1GB >> DDR2 RAM. 2x RTL8111C Chipset Gigabit LAN and 4x Realtek 8100C Chipset >> 10/100 LAN" >> >> Now we know something. How are you booting it? Spinning drive, SSD, CF >> card? I ran into a problem installing onto a SSD drive, which turned out to >> be a minor issue. I don't understand when you say it "hangs at the spinner >> after boot prompt." So, a better description is warranted. > > > I'm installing onto a seagate 320GB 2.5" hard drive, from a CD, both > connected via sata. I boot from the CD and have attempted to install > directly (press I) and continue (press C) into the liveCD boot, do a minimal > configuration (1 lan & 1 wan) and install from there (option 99). I'm using > the non-embedded version, both 1.2.3 and 2.0rc3. > > I have 2 possible outcomes when I boot from disk, depending upon the > options used to install > > - A menu is visible on the screen which after a few seconds attempts to > boot, this is what I finish up with on the screen > F1 pfSense > Boot: F1 > \ <----- non-moving spinner > > - the other outcome is that I get an error message like this: > default 0:ad(0,a)/boot/kernel/kernel > no /boot/loader > boot: > > > Nick, > > Dug up the old message where my install got stuck - below. That's not your > issue. Have you tried the usual things like booting from external cd, switch > disk drives, boot from a live Linux cd - anything to isolate the problem? > > Mehma > === >
Hi Mehma, I posted again yesterday describing what I did that seems to fix it, basicly formatting the HD on a windows bos first -- Nick Upson (01799 533252)
