Proxy server question

Jamerson

The second hard disk should show up as /dev/da1. If that isn't present then pfSense isn't detecting it.

The general syntax of the mount command is:

mount -options /dev/device_name# /folder_name

/folder_name must already exist. You can leave options blank for testing.

Here is how to add a disk to FreeBSD.

Note that the disk naming scheme is different so when they talk about /dev/ada1 and /dev/adap1, you should use /dev/da1 and /dev/da1s1 respectively.

thank you
i believe this for Sata Disk ,
i've ISCI Drive to the VM .
when i run df -h it doesn't shows the drive
i've deleted the disk and add it twice but the same result
Filesystem Size Used Avail Capacity Mounted on

/dev/da0s1a 5.8G 1.1G 4.3G 20% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/md0 3.4M 116K 3.0M 4% /var/run
devfs 1.0K 1.0K 0B 100% /var/dhcpd/dev

KOM

i've ISCI Drive to the VM .

??? DO you mean SCSI or iSCSI? In my lab with VMware Workstation, I added a SCSI disk and it appeared as /dev/da1.

Jamerson

@KOM:

i've ISCI Drive to the VM .

??? DO you mean SCSI or iSCSI? In my lab with VMware Workstation, I added a SCSI disk and it appeared as /dev/da1.

yes i meant the SCSI disk separate than the VM Disk, and is Thick Provision
after i updated to 2.2 i beleive it starts showing up the attached disks

df -h still doesn't shows the attached hdd
what i am doing wrong

KOM

df -h still doesn't shows the attached hdd
what i am doing wrong

I think df only shows mounted filesystems. Did you partition, format & mount your disk using the directions in the links I posted?

Jamerson

@KOM:

df -h still doesn't shows the attached hdd
what i am doing wrong

I think df only shows mounted filesystems. Did you partition, format & mount your disk using the directions in the links I posted?

i am stuck at the first step when i run the command /var/run/dmesg.boot its said /var/run/dmesg.boot:not found
i already added to the disk

KOM

dmseg.boot is a log file. You don't run it; you view it with cat or a text editor.

OK, firs things first. What output do you get when you run the command:

ls /dev/da*

We need to see if pfSense even sees your disk at all. You are specifically looking for /dev/da1.

Jamerson

@KOM:

dmseg.boot is a log file. You don't run it; you view it with cat or a text editor.

OK, firs things first. What output do you get when you run the command:

ls /dev/da*

We need to see if pfSense even sees your disk at all. You are specifically looking for /dev/da1.

this what i get .

[2.2-RELEASE][root@firewall.pfsense.lan]/root: ls /dev/da*
/dev/da0    /dev/da0s1  /dev/da0s1a /dev/da0s1b /dev/da1

KOM

Ok, so it sees your disk. I'm not sure what your problem is then. Just partition, format and mount it as per the guide I linked to:

# gpart create -s GPT da1
# gpart add -t freebsd-ufs da1
# newfs -U /dev/da1s1
# mkdir /newdisk
# mount /dev/da1s1 /newdisk

Add this to /etc/fstab so that it mounts at boot:

/dev/da1s1	/newdisk	ufs	rw	2	2

Jamerson

@KOM:

Ok, so it sees your disk. I'm not sure what your problem is then. Just partition, format and mount it as per the guide I linked to:
# gpart create -s GPT da1
# gpart add -t freebsd-ufs da1
# newfs -U /dev/da1s1
# mkdir /newdisk
# mount /dev/da1s1 /newdisk
Add this to /etc/fstab so that it mounts at boot:
/dev/da1s1	/newdisk	ufs	rw	2	2

Thank you KOM
the problem is when i run the command

newfs -U /dev/da1s1

it said command not found !

[2.2-RELEASE][root@firewall.pfsense.lan]/root: # newfs -U /dev/da1s1
#: Command not found.
[2.2-RELEASE][root@firewall.pfsense.lan]/root:

KOM

#: Command not found.

The # character is meant to represent your shell prompt. You don't actually type that part. No wonder you've been having trouble.

Jamerson

@KOM:

#: Command not found.

The # character is meant to represent your shell prompt. You don't actually type that part. No wonder you've been having trouble.

sorry mommy mistake
does the commands that has /dev/da1s1 means /dev/da1 for me right ?
i believe dev/da1 is my current install pfsense and dev/da1pl1 is the attached disk ?

KOM

I did explain earlier that when they reference /dev/ada1, you would use/dev/da1. When they use /dev/ada1p1, you would use /dev/da1s1. p means partition, s means slice, but they are basically the same.

Jamerson

@KOM:

I did explain earlier that when they reference /dev/ada1, you would use/dev/da1. When they use /dev/ada1p1, you would use /dev/da1s1. p means partition, s means slice, but they are basically the same.

is exactly what i am doing
[2.2-RELEASE][root@firewall.pfsense.lan]/root: newfs -U /dev/da1s1
newfs: /dev/da1s1: could not find special device
[2.2-RELEASE][root@firewall.pfsense.lan]/root:

kejianshi

I lost track. Are you still trying to figure out how to cache dynamic content? Don't waste too much time. OK?

KOM

newfs: /dev/da1s1: could not find special device

OK, this one's on me. When using gpart, it will make a partition, not a slice. Try:

newfs -U /dev/da1p1
mkdir /newdisk
mount /dev/da1p1 /newdisk

I lost track. Are you still trying to figure out how to cache dynamic content?

We're still going over Unix disk basics at this point.

kejianshi

Yeah - Its a nice mental exercise and is good to know (-:

Jamerson

@KOM:

newfs: /dev/da1s1: could not find special device

OK, this one's on me. When using gpart, it will make a partition, not a slice. Try:
newfs -U /dev/da1p1
mkdir /newdisk
mount /dev/da1p1 /newdisk
I lost track. Are you still trying to figure out how to cache dynamic content?

We're still going over Unix disk basics at this point.

Thank you so much for this KOM,
the Disk is mapped now going to configured it for the cache
Mucht appreciate really and your patients as well

when i try to navigate to the new mounted disk i get "access denied "
trying to create a folder for the cashing.

KOM

You probably have to give the proxy user ownership of the folder:

chown proxy:proxy /your_disk_mount_point

Jamerson

@KOM:

You probably have to give the proxy user ownership of the folder:
chown proxy:proxy /your_disk_mount_point

KOM you are the man,
thank you