Hi everybody.
First, i'm a french user and i'm sorry if my english is not very good.
I'm creating a DRBL server on Debian 7 and the last stable DRBL version
(2.4.19).
My aim is to use a NAS disk for the image directory : NAS 220 Black Armor on the "public" network.
Configuration :
NAS (@ip 10.xx.xx.xx) -- DRBL Eth0 (@ip 10.xx.xx.xx) / DRBL (on a Swith) Eth1 (@ip 192.168.0.1) -- DRBL client (test) : 192.168.0.2 (obtain by the DHCP of DRBL server).
On the DRBL server, i can mount the NAS disk with the fstab file like this :
montage NFS du 10.xx.xx.xx pour les images CZ
10.xx.xx.xx:/DataVolume/img-cz /NFS_disk nfs defaults 0 0
On the NAS, i have activated the NFS protocol (and CIFS protocol just for the tests).
After the server boot, i can read / write into the /NFS_disk mount with the terminal.
But, when i have specify the share into the drbl configuration (drblpush -i), i can't restore a image on client :
messages on client :
"force to mount nfs due to mountall NFS bug"
"mount.nfs : access denied by server while mounting 192.168.0.1:/NFS_disk/partimag
cmd on client :
touch test : Read-only file system.
Into the NAS configuration, the allowed IP are :
DRBL IP
Private @IP DRBL client : 192.168.0.2 (i'm not sur if it's really necessary)
On the DRBL server, the / directory say :
drwxrwxr-x 3 root jo 4096 oct. 8 10:06 NFS_disk
the /NFS_disk directory say :
drwxr-xr-x 3 nobody nogroup 4096 oct. 3 15:30 partimag
the /NFS_disk/partimag/ say :
drwxr-xr-x 2 nobody nogroup 4096 oct. 3 15:31 ubuntu_2013-09-30-16-img
What's wrong ?
In an other topic, i read "use unfs3".
I downloaded and complied the sources (tar .gz, ./configure, make, make install) but what do i do now ?
I think the DRBL server always use "nfs-kernel-server" and not the unfs3 configuration ...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The mounted NFS directory could not be exported if you use kernel-based NFS service. That's why we suggest you use ufs3 instead of the default kernel-based NFS service for your case.
As for how to use ufs3, basically it's the similar configuration as kernel-based NFS service. Just remember to disable the kernel-based NFS.
BTW, you can refer to DRBL live, which use unfs3 instead of kernel-based NFS service.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hm, i'm in trouble ...
After a server reboot,
- I have stopped the nfs service by /etc/init.d/nfs-kernel-server stop (and have checked if the service does not running by /etc/init.d/nfs-kernel-server status)
- boot my PXE client and I chosen my permanent entry : restore Windows XP
- the restoration image works, Happy.
Next test : try to create an image on NAS.
- I have install Linux Mint on client
- I booted dcs / savedisk mode on DRBL
- boot PXE client : the image creation worked. Happy.
Next test : retore the client by using an ubuntu image
- during the PXE client boot : [...]Starting NFS common utilities (why?! i believed to have disable the service ?!)
mount.nfs : access denied by ... (I don't understood, i have disabled the nfs-kernel-service before !)
error input name does not exist : i understand this error message : the client don't find the image because the NFS export fail.
Why the first time, the image restoration has worked (Windows XP) and the image creation has worked too (Mint image) but the next restoration were fail ?
Maybe the unfs service is incorrectly installed ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you find any clues in server's log files, like /var/log/syslog, /var/log/messages or /var/log/daemon.log?
You should be able to find some when clients failed to boot.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everybody.
First, i'm a french user and i'm sorry if my english is not very good.
I'm creating a DRBL server on Debian 7 and the last stable DRBL version
(2.4.19).
My aim is to use a NAS disk for the image directory : NAS 220 Black Armor on the "public" network.
Configuration :
NAS (@ip 10.xx.xx.xx) -- DRBL Eth0 (@ip 10.xx.xx.xx) / DRBL (on a Swith) Eth1 (@ip 192.168.0.1) -- DRBL client (test) : 192.168.0.2 (obtain by the DHCP of DRBL server).
On the DRBL server, i can mount the NAS disk with the fstab file like this :
montage NFS du 10.xx.xx.xx pour les images CZ
10.xx.xx.xx:/DataVolume/img-cz /NFS_disk nfs defaults 0 0
On the NAS, i have activated the NFS protocol (and CIFS protocol just for the tests).
After the server boot, i can read / write into the /NFS_disk mount with the terminal.
But, when i have specify the share into the drbl configuration (drblpush -i), i can't restore a image on client :
messages on client :
"force to mount nfs due to mountall NFS bug"
"mount.nfs : access denied by server while mounting 192.168.0.1:/NFS_disk/partimag
cmd on client :
touch test : Read-only file system.
Into the NAS configuration, the allowed IP are :
DRBL IP
Private @IP DRBL client : 192.168.0.2 (i'm not sur if it's really necessary)
On the DRBL server, the / directory say :
drwxrwxr-x 3 root jo 4096 oct. 8 10:06 NFS_disk
the /NFS_disk directory say :
drwxr-xr-x 3 nobody nogroup 4096 oct. 3 15:30 partimag
the /NFS_disk/partimag/ say :
drwxr-xr-x 2 nobody nogroup 4096 oct. 3 15:31 ubuntu_2013-09-30-16-img
What's wrong ?
In an other topic, i read "use unfs3".
I downloaded and complied the sources (tar .gz, ./configure, make, make install) but what do i do now ?
I think the DRBL server always use "nfs-kernel-server" and not the unfs3 configuration ...
The mounted NFS directory could not be exported if you use kernel-based NFS service. That's why we suggest you use ufs3 instead of the default kernel-based NFS service for your case.
As for how to use ufs3, basically it's the similar configuration as kernel-based NFS service. Just remember to disable the kernel-based NFS.
BTW, you can refer to DRBL live, which use unfs3 instead of kernel-based NFS service.
Steven.
hm, i'm in trouble ...
After a server reboot,
- I have stopped the nfs service by /etc/init.d/nfs-kernel-server stop (and have checked if the service does not running by /etc/init.d/nfs-kernel-server status)
- boot my PXE client and I chosen my permanent entry : restore Windows XP
- the restoration image works, Happy.
Next test : try to create an image on NAS.
- I have install Linux Mint on client
- I booted dcs / savedisk mode on DRBL
- boot PXE client : the image creation worked. Happy.
Next test : retore the client by using an ubuntu image
- during the PXE client boot :
[...]Starting NFS common utilities (why?! i believed to have disable the service ?!)
mount.nfs : access denied by ... (I don't understood, i have disabled the nfs-kernel-service before !)
error input name does not exist : i understand this error message : the client don't find the image because the NFS export fail.
Why the first time, the image restoration has worked (Windows XP) and the image creation has worked too (Mint image) but the next restoration were fail ?
Maybe the unfs service is incorrectly installed ?
up please !
Did you find any clues in server's log files, like /var/log/syslog, /var/log/messages or /var/log/daemon.log?
You should be able to find some when clients failed to boot.
Steven.