October 11th, 2001, 08:43 AM
Help w FreeBSD 4.3 install
Hello forum, hello freebsd!
My Dual-ISDN suckt madly on the 4.3 ISO-file. Yesterday evening i smacked it on cd, put my old 2 GB HHD as primary slave into the system, and bootet from the fresh toasted FreeBSD-CD.
Config went fine, but i always got an disk-full error. Are 2 GB not enough for a usual instal (option 9, bin and x, no src)?
Or did i misconfigure the filesystem? I used the auto-option which assigned / 100 MB, /var 20, swap ~ 300 and ~1,5 GB to /usr.
When FreeBSD attemted to build the filesystem, it always warned me bout an error (cant remember the text, was late at night ), and started a emergency script. Them when it tries to copy the ports n stuff it says disk full.
Did i misconfigure the filesystem? If i did, what size should i assign the slices and how to mount them? Or could it be my HDD kissed it's arse good bye and passed away silently?
Woah i feel like a newbie again, reminds me to the time when i deleted *.vxd from my W95 machine accidently... *sigh*
October 11th, 2001, 08:55 AM
>> Are 2 GB not enough for a usual instal
Check this -> can you help out newbie? :)
>> I used the auto-option which assigned
Don't set / to 100mb, 50mb is more than enough.
>> swap ~ 300
How much physical memory do you have? Usually you set (swap = physical ram x 2).
>> Did i misconfigure the filesystem?
Do not install X during initial install. If you need to install X later on, install from /usr/ports and get the latest version. Note: FreeBSD comes with XF86 3.3.6 by default.
>> it always warned me bout an error (cant remember the text
If you don't even know what error, how do we solve it?
October 11th, 2001, 09:13 AM
K, thx, will try a smaller install. If this fails im gonna toss that HDD out of the window.
BTW: 160 MB phsyical RAM.
October 11th, 2001, 04:41 PM
It starts creating the filesystem, then aborts with:
The a window pops up for a moment and tells me a emergency script is starting, then a message on the screenbottom appears which tells me the filesystem has been setup successfully.
The copy-process starts and aborts after a while:
October 12th, 2001, 08:38 AM
Why you have two disks? What partition did you set (with the device name)?
October 12th, 2001, 08:50 AM
I statet in another thread some time ago i will buy a little machine thought to be a dedicatet server. Since i will buy it in 3 weeks when i get my next salary, and i wanted to be prepared for that install, i decided to put my old 2GB f&%)ing slow HDD into my workstation and install FreeBSD on it. It's the primary slave.
I didn't partion the old (15 GB) because i do not want that the systems (W2K / FreeBSD) collide in some way. Probably a way wich will take my ultrarare MP3s to valhalla.
I hope i understand your 2nd question right. I dedicated the whole 2GB to FreeBSD with the auto-config. It's ad1s1[a|b|d|e|f]. The primary 15 GB disk remains untouched - no bootmanager or sumthin'.
October 12th, 2001, 07:02 PM
>> because i do not want that the systems (W2K / FreeBSD) collide in some way
Even they are not on the same disk, you are still dualbooting and it's possible to fsck up your ad0 disk (with win2k in it).
>> The primary 15 GB disk remains untouched
>> no bootmanager or sumthin
You need a boot loader either on win2k or FreeBSD. Did you read my other post about the bad thing of dualboot? Why are you not listening? I know while waiting for your upcoming dedicated server, you just wanted to test FreeBSD out in the meantime. But still, I don't suggest that either. Say you install a bootloader in FreeBSD, when your dedicated server is ready, you probably will unplug this drive, then it's gonna cause your win2k disk a big problem. If you must dualboot, install a bootloader on win2k.
October 13th, 2001, 06:42 AM
I just swap the boot-device-sequence in the BIOS-menu. If i need to boot W2K, the system will boot from HDD-0, if i need FreeBSD, i boot from HDD-1, and if i need to install from CD i will boot from CDROM.
Both drives work without the other, i've tested it.
Since i do not allow FreeBSD to access the first HDD at all, i do not mind about fakkups. My BIOS warns me anyways if something is going to modify the MBR.
I have read your previous posts and that is why i chose to do it this way.