HOWTO: Modern FreeBSD Install (vermaden way)

Code: 
invalid vdev soecification
[red]use -f to override the following error[/red]
/dev/ad4s2 is part of potentially active pool 'basefs'

-f
 
killasmurf86 said:
uh, man then you are doing something only god knows what.....


start by checking your directory
Click to expand...
my problem is in section 1.5 , when I type ./install.sh generic , it can not find which generic must install
when I go kernel directory and type
ls
I see many generic for example
generic.aa
generic.ab
.....

and I install.sh can not detect which one must install
I use amd54
I can not continue
 
generic.aa
generic.ab
...

are one single kernel, splinted to many small archives


can you show exact error, that ./install.sh shows.... or at least screen shot or photo of screen?

It has to work, I've done this million times
 
killasmurf86 said:
generic.aa
generic.ab
...

are one single kernel, splinted to many small archives


can you show exact error, that ./install.sh shows.... or at least screen shot or photo of screen?

It has to work, I've done this million times
Click to expand...

when I type
Code: 
./install.sh generic
I see this line
Code: 
tr:not found
cat: .??: No such file or directory
 
OK, some weird problem....
tr is not found.

I don't know why it's not found because it should be available....
perhaps check your cd/dvd for errors and maybe download new cd/dvd.

or you can try
Code: 
# cat generic.* | tar xf - -C [red]/boot/[/red]
replace [red]/boot/[/red] with directory where you need to install kernel


I don't know if this will work, but I don't see why you shouldn't try

Note: I improved, and haven't tested, but you can't damage anything anyway {normally}
 
vermaden said:
@mfaridi

Only 2.4. section has info to omit it on amd64 ...
[CMD=""]2.4. Tune ZFS filesystem (only for i386)[/CMD]

@caesius

Thanks mate.



You will have to remount it as read-write mode like that: # mount -u -w / ... and then bring it back to read-only by # mount -u -r / ([CMD=""]-o rw[/CMD] | [CMD=""]-o ro[/CMD] does the same).

You may also read about some other issues on read-only / on FreeBSD here:
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/questions/2008-06/msg01029.html
Click to expand...

Ok, Think I'll give it a shot, just to be clear all I would have to do to update FreeBSD would be to update sources, buildkernel, buildworld, type the first command, installkernel, reboot, type it again, installworld, reboot, then I'm back to normal ro mode on rebooting. Is this correct?
 
in section 1.7 when I type
Code: 
umount /NEWROOT/var
I see error about /var is not root file system , so it can not unmount it
I see this error about /usr
when I want umount /NEWROOT , Isee error about /NEWROOT is busy
 
caesius said:
Ok, Think I'll give it a shot, just to be clear all I would have to do to update FreeBSD would be to update sources, buildkernel, buildworld, type the first command, installkernel, reboot, type it again, installworld, reboot, then I'm back to normal ro mode on rebooting. Is this correct?
Click to expand...

I would do that this way (binary way, far easier):
2.7. Add latest security patches
Code: 
newsystem# freebsd-update fetch
newsystem# freebsd-update install

...but Yes, the procedure for source update does not change after installing FreeBSD my way.

mfaridi said:
Code: 
umount /NEWROOT/var
I see error about /var is not root file system , so it can not unmount it
Click to expand...

Post exact error message.
 
[
I think this error happen because in section 1.4 when I type
Code: 
zpool create basefs ad4s2
Is see this error
Code: 
invalid vdev specification
use -f to override the following error :
/dev/ad4s2 is part of potentially active pool 'basefs'
so I use
Code: 
-f
option and go to next stage so I type
Code: 
zpool create -f basefs ad4s2
when I type
Code: 
umount /NEWROOT/var
I see this error
Code: 
umount: /NEWROOT/var: not a file system root directory
 
mfaridi said:
I think this error happen because in section 1.4 when I type
Code: 
zpool create basefs ad4s2
Is see this error
Code: 
invalid vdev specification
use -f to override the following error :
/dev/ad4s2 is part of potentially active pool 'basefs'
Click to expand...
You got this error message, because you already done # zpool create on that partition before, so it tells you that you can create it again (like going # newfs two times on the same device) or you may import it if its already there by # zpool import -f basefs.


mfaridi said:
Code: 
umount /NEWROOT/var
I see this error
Code: 
umount: /NEWROOT/var: not a file system root directory
Click to expand...
Show me output of # mount command just before typing that command.
 
vermaden said:
You got this error message, because you already done # zpool create on that partition before, so it tells you that you can create it again (like going # newfs two times on the same device) or you may import it if its already there by # zpool import -f basefs.



Show me output of # mount command just before typing that command.
Click to expand...

I see this when I type mount
Code: 
/dev/md0 on / (ufs,  local)
devfs on /dev (devfs,  local,  multilabel)
/dev/acd0 on /dist (cd9660,  local,  readonly)
basefs on /basefs (zfs, local)
/dev/label/rootfs on /NEWROOT (ufs, local)
basefa/usr on /usr (zfs, local)
basefa/var on /var (zfs, local)
 
mfaridi, it seams you messed everything up, I suggest you help yourself and vermaden by doing this:

Code: 
fixit# dd if=/dev/random of=/dev/da0 bs=8m
[red]this will erase everything on your hard disk (replace da0 with other disk you need to format)[/red], just remember not to erase disks, that has data, that you need :)

and then start ALL OVER, and don't rush

P.S.
I know there are faster ways, but this guarantees, that there will be no problems :)
 
mfaridi said:
I see this when I type mount
Code: 
/dev/md0 on / (ufs,  local)
devfs on /dev (devfs,  local,  multilabel)
/dev/acd0 on /dist (cd9660,  local,  readonly)
basefs on /basefs (zfs, local)
/dev/label/rootfs on /NEWROOT (ufs, local)
basefa/usr on /usr (zfs, local)
basefa/var on /var (zfs, local)
Click to expand...
So tell me HOW you will be able to umount /NEWROOT/var if its not mounted there?

You have now both basefs and basefa (typo propably), a mess in setup, start all over again as killasmurf86 suggests.

mfaridi said:
please help
I stop in here and can not continue
Click to expand...
You know what FORUMS is mate?

A place where anyone responds WHEN HE/SHE HAS TIME FOR IT, not immediately as someone screams, please faster I do not want to wait, I am not nailed to the chair and this is not my job to respond here to people who does not even understand what they try to do.
 
I would like to expand a little on the "tr: not found" error. I got that too when I was hand installing FreeBSD 8.0-R AMD64. In fact, the script kernels/install.sh contains this:
Code: 
        # translate per Makefile:doTARBALL XXX are we sure to have tr?
	tn=`echo ${CONFIG} | tr 'A-Z' 'a-z'`
	cat $tn.?? | tar --unlink -xpzf - -C $BOOT
Do note the first line that asks if we have tr. It appears that someone missed something.. (And yes, that line is copied verbatim -- the ":doTARBALL" part looks like the file was misedited.

And no, we don't have tr:
Code: 
[starlight] ~/mnt > find . -name tr -print
[starlight] ~/mnt >
Output is nothing. (~/mnt is 8.0-RELEASE-amd64-disc1.iso mounted via loopback).

Anyway, I worked around the problem by simply executing # cat generic.?? | tar --unlink --xpzf - -C /new-bsd/boot, /new-bsd being the mountpoint of my new system's root, of course. The installation was successful in the end, so it works.
 
@Oxyd

I have been using i386 version, after selecting Fixit --> CD/DVD I was able to use tr(1) straight away:

Code: 
fixit# /mnt2/usr/bin/tr
usage: tr [-Ccsu] string1 string2
       tr [-Ccu] -d string1
       tr [-Ccu] -s string1
       tr [-Ccu] -ds string1 string2

The tr(1) is the reason that I added also /mnt2/usr/bin to PATH (instead of only /mnt2/rescue):

vermaden said:
1.1 / 2010-01-15 / simplified PATH
+fixit# setenv PATH /mnt2/rescue:/mnt2/usr/bin
-fixit# setenv PATH /mnt2/bin:/mnt2/sbin:/mnt2/usr/bin:/mnt2/usr/sbin​
Click to expand...

I will verify that for amd64 in free time.
 
vermaden said:
So tell me HOW you will be able to umount /NEWROOT/var if its not mounted there?

You have now both basefs and basefa (typo propably), a mess in setup, start all over again as killasmurf86 suggests.


You know what FORUMS is mate?

A place where anyone responds WHEN HE/SHE HAS TIME FOR IT, not immediately as someone screams, please faster I do not want to wait, I am not nailed to the chair and this is not my job to respond here to people who does not even understand what they try to do.
Click to expand...

I do dd but I have that problem again and can not umount /NEWROOT/var
 
vermaden said:
I will verify that for amd64 in free time.
Click to expand...

Yes, tr(1) is also available on amd64 *-dvd-*/*-memstick-* media in Fixit environment:
Code: 
fixit# /mnt2/usr/bin/tr
usage: tr [-Ccsu] string1 string2
       tr [-Ccu] -d string1
       tr [-Ccu] -s string1
       tr [-Ccu] -ds string1 string2
 
You must log in or register to reply here.
Back
Top