I am new to Clonezilla. In about a week, I will be left with 100 R51's (4 year old IBMs) to put a copy of XP Home on to return to the students who bought them. Right now, the process is done by taking the 5 recovery disks and running them. We tried ghost, but there is some security issue it runs into. I am the first person at school to really start using Linux, so I thought I would try clonzilla since it uses dd. Security should not be a problem since the issue should get coppied strait. I need to backup a home machine anyway, so I thought I would test it out. I het the following problem.
I can not seem to figure out why no machine can access the TFTP boot folder. I made the file readable adn writable to anyone who wants to. I added this line to my hosts.allow folder
ALL: 192.168.2.0/255.255.255.0 where my Clonezilla server is 192.168.3.254. I turned off my firewall (firestarter) and yet the machine still can not boot. I did a full restart of the server to make sure the line in hosts.allow got picked up.I check my daemon log and the last entry is
May 16 14:56:11 HOST mountd[4377]: mount request from unknown host 192.168.3.2 for /tftpboot/node_root (/tftpboot/node_root)
The machine I am booting got the address 192.168.3.2. I am at a loss. Any help would ba appricated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
user@lists.sourceforge.net (English). You may also post them in the DRBL forum (http://sourceforge.net/forum/?group_id=73280) (English)."
-------CUT BEGIN HERE--------------------------------------------
Description of problem:
Clients can not access their root filesystem in the server. Every time I try to boot a client, I get the error Failed to mount root filesystem!!! System dameon log has entry telling me host 192.168.3.2 is unrecognized even though I added the line ALL:192.168.3.0/255.255.255.0 to my host.allow file and restarted the system.
How reproducible:
Every time I have tried to boot a client
Steps to Reproduce:
Try to boot a client in clonezilla or DRBL mode
Actual results:
Debugging shell appears after a list of steps to try to recover from the fatal error Failed to mount root filesystem!!!
Expected results:
My computer to boot up and start creating an image of its HDD.
Some info about the DRBL environment (PLEASE DO NOT EDIT THEM!):
OS version: Debian 5.0.1
Server arch: i686
Server CPU: Intel(R) Celeron(R) CPU 2.80GHz
Server memory size: 507920 kB
Server Kernel version: 2.6.26-2-686
Installed DRBL-related packages: drbl-1.9.3-43 clonezilla-2.3.2-80 mkswap-uuid-0.1.1-1 drbl-partimage-0.6.7-1drbl drbl-ntfsprogs-2.0.0-4 partclone-0.0.9-4 drbl-chntpw-0.0.20040818-7 drbl-lzop-1.02-0.8drbl pigz-2.1.4-1drbl pbzip2-1.0.5-1drbl mkpxeinitrd-net-1.2-37 udpcast-20081213-1drbl drbl-etherboot-5.4.3-2 gpxe-0.9.7-1drbl freedos-1.0-11drbl
Client kernel version: 2.6.26-2-686
Client kernel arch: i686
NICs with private IP address in server: eth1 eth2
Private IP address in server: 192.168.2.80 192.168.3.254
Total client no: 10
Client IP address: 192.168.3.1 192.168.3.10 192.168.3.2 192.168.3.3 192.168.3.4 192.168.3.5 192.168.3.6 192.168.3.7 192.168.3.8 192.168.3.9
===
-------CUT END HERE----------------------------------------------
Sorry about the long post before. Maybe this will be a little clearer. I also want to note that I tried the steps listed to recover from this error.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I can not figure it out why there is such a problem there. However, since there is another stable DRBL released yesterday, maybe you can give that a try.
Please follow http://drbl.sourceforge.net/one4all/#upgrade
to upgrade.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Looks like there are some lib are missing.
Did you follow http://drbl.sourceforge.net/one4all
to setup the server instead of manually editing config files ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Found part of my problem. I missed an installation step for setting up my /etc/exports file. Now my client will get to the point of creating /opt/drbl. Then it tells me
grep: /etc/hosts: no such file or directory
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
warning: can't open /etc/fstab: no such file or directory
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
Try to remove nosharecache in /etc/fstab
grep: /etc/fstab: No such file or directory
Done. NFS-root directories are mounted.
Let original init take over...
INIT: version 2.86 booting
INIT: no inittab file found
INIT: Entering runlevel: 1
INIT no more processes left in this runlevel
At this point, the client just sits there for a while and then goes to a black screen. Do I need to give clonezilla access to my fstab file?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am new to Clonezilla. In about a week, I will be left with 100 R51's (4 year old IBMs) to put a copy of XP Home on to return to the students who bought them. Right now, the process is done by taking the 5 recovery disks and running them. We tried ghost, but there is some security issue it runs into. I am the first person at school to really start using Linux, so I thought I would try clonzilla since it uses dd. Security should not be a problem since the issue should get coppied strait. I need to backup a home machine anyway, so I thought I would test it out. I het the following problem.
I can not seem to figure out why no machine can access the TFTP boot folder. I made the file readable adn writable to anyone who wants to. I added this line to my hosts.allow folder
ALL: 192.168.2.0/255.255.255.0 where my Clonezilla server is 192.168.3.254. I turned off my firewall (firestarter) and yet the machine still can not boot. I did a full restart of the server to make sure the line in hosts.allow got picked up.I check my daemon log and the last entry is
May 16 14:56:11 HOST mountd[4377]: mount request from unknown host 192.168.3.2 for /tftpboot/node_root (/tftpboot/node_root)
The machine I am booting got the address 192.168.3.2. I am at a loss. Any help would ba appricated.
Could you please follow
http://drbl.sourceforge.net/one4all/#bug-report
to provide more info ? It would be easier for us to see why.
Steven.
user@lists.sourceforge.net (English). You may also post them in the DRBL forum (http://sourceforge.net/forum/?group_id=73280) (English)."
-------CUT BEGIN HERE--------------------------------------------
Description of problem:
Clients can not access their root filesystem in the server. Every time I try to boot a client, I get the error Failed to mount root filesystem!!! System dameon log has entry telling me host 192.168.3.2 is unrecognized even though I added the line ALL:192.168.3.0/255.255.255.0 to my host.allow file and restarted the system.
How reproducible:
Every time I have tried to boot a client
Steps to Reproduce:
Try to boot a client in clonezilla or DRBL mode
Actual results:
Debugging shell appears after a list of steps to try to recover from the fatal error Failed to mount root filesystem!!!
Expected results:
My computer to boot up and start creating an image of its HDD.
Some info about the DRBL environment (PLEASE DO NOT EDIT THEM!):
OS version: Debian 5.0.1
Server arch: i686
Server CPU: Intel(R) Celeron(R) CPU 2.80GHz
Server memory size: 507920 kB
Server Kernel version: 2.6.26-2-686
Installed DRBL-related packages: drbl-1.9.3-43 clonezilla-2.3.2-80 mkswap-uuid-0.1.1-1 drbl-partimage-0.6.7-1drbl drbl-ntfsprogs-2.0.0-4 partclone-0.0.9-4 drbl-chntpw-0.0.20040818-7 drbl-lzop-1.02-0.8drbl pigz-2.1.4-1drbl pbzip2-1.0.5-1drbl mkpxeinitrd-net-1.2-37 udpcast-20081213-1drbl drbl-etherboot-5.4.3-2 gpxe-0.9.7-1drbl freedos-1.0-11drbl
Client kernel version: 2.6.26-2-686
Client kernel arch: i686
NICs with private IP address in server: eth1 eth2
Private IP address in server: 192.168.2.80 192.168.3.254
Total client no: 10
Client IP address: 192.168.3.1 192.168.3.10 192.168.3.2 192.168.3.3 192.168.3.4 192.168.3.5 192.168.3.6 192.168.3.7 192.168.3.8 192.168.3.9
===
-------CUT END HERE----------------------------------------------
Sorry about the long post before. Maybe this will be a little clearer. I also want to note that I tried the steps listed to recover from this error.
I can not figure it out why there is such a problem there. However, since there is another stable DRBL released yesterday, maybe you can give that a try.
Please follow
http://drbl.sourceforge.net/one4all/#upgrade
to upgrade.
Steven.
Looks like there are some lib are missing.
Did you follow
http://drbl.sourceforge.net/one4all
to setup the server instead of manually editing config files ?
Found part of my problem. I missed an installation step for setting up my /etc/exports file. Now my client will get to the point of creating /opt/drbl. Then it tells me
grep: /etc/hosts: no such file or directory
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
warning: can't open /etc/fstab: no such file or directory
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
perl: /lib/tls/i686/cmov/libc.so.6: version 'GLIBC_2.4' not foud (required by pearl)
Try to remove nosharecache in /etc/fstab
grep: /etc/fstab: No such file or directory
Done. NFS-root directories are mounted.
Let original init take over...
INIT: version 2.86 booting
INIT: no inittab file found
INIT: Entering runlevel: 1
INIT no more processes left in this runlevel
At this point, the client just sits there for a while and then goes to a black screen. Do I need to give clonezilla access to my fstab file?
Doing a fresh install took care of all the problems. I think there was a permissions issue somewhere that a fresh install took care of.