I too have the problem reported by rdchin so am trying cifs instead of smbfs. I have created the image on the server OK but during the restore process I am having the error "can't read the following volume file: /stdin.001"
I'm asked to enter a new file name but the screen is locked up :-(
Any idea ?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We need more info, so please post the details about the steps you start the restoration.
Also post the file info in the images by:
1. After you mount samba server public folder to /home/partimag, run
a. df > debug.log
b. ls -alF /home/partimag >> debug.log
c. ls -alF /home/partimag/$IMAGENAME >> debug.log
$IMAGENAME with yours)
Then post debug.log here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thankyou. I performed standard steps for image restore, accepting default settings. First partition (FAT32) seemed to be OK, error occured with second partition (ReiserFS).
mount -t cifs -o username=images //172.16.15.4/images/smb /home/partimag
Interesting. The image looks fine. reiserfs in clonezilla does not have any problem here.
Now please do more testing in Clonezilla live with //172.16.15.4/images is mounted as /home/partimag:
1. run
file /home/partimag/$IMAGENAME/sda3.aa > file.log
please post file.log here
2. use verbose mode to run ocs-sr as root (sudo su -) by:
a. cp /etc/screenrc ~/.screenrc
b. edit ~/.screenrc, find
defscrollback 1000
make it larger, like:
defscrollback 100000
c. run "screen" to enter screen
d. bash -x /opt/drbl/sbin/ocs-sr -x
remember to choose "-v" and "-nogui"
e. wait for the error, then use "ctrl-a [" (press ctrl-a, release them, then press [), this will enter screen copy/scrollback mode. You can use ctrl-b (pageup), ctrl-f pagedown), j(down), k(up), h(left), l(right) to scrollback the screen. Find the beginning of "ocs-sr -x", then use "space bar" key to mark the beginning of the copy, then move to the end of the ocs-sr error, and use "space bar" key to mark the end of the copy.
f. In the same screen terminal, use vim, jove or whatever editor you are familiar with. For example, vim
vim ocs-err.log
enter edit mode in vim (i.e. press i), then use "ctrl-a ]" to paste the one you put in the buffer of screen.
enter command mode in vim (i.e. press esc), save the file by ":wq".
g. post ocs-err.log here.
Sorry for such a long procedure. However, with this, it's easier for us to know why it fails.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Please, for clarification... after I press spacebar to mark end of ocs-sr error I seem to be still in "screen", do I need to exit this in some way to then vim ocs-err.log ?
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Clonezilla is nothing to do with .screenrc. No idea where went wrong there. But at least now it's working for you. Good.
If you use PXEboot clonezilla with gigabits NIC, the speed will be faster, I think. Someone reported that the restoring speed is about 1.6-2.0 GB/min. Here it's about 1.5 GB/min.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The problem has returned again, this time using a different image file. It failed the first time, succeeded the second time, failed the third time. On the 2 occasions of failure it failed at a different stage/partition but the error "can't read the following volume file: /stdin.001" was the same (also says "LZOP: <stdin>: checksum error".
can you advise on my earlier question "... after I press spacebar to mark end of ocs-sr error I seem to be still in "screen", do I need to exit this in some way to then vim ocs-err.log ?"
Many thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
About ".. after I press spacebar to mark end of ocs-sr error I seem to be still in "screen", do I need to exit this in some way to then vim ocs-err.log ?", no, you have to be in the same screen terminal.
If you see "LZOP: <stdin>: checksum error", I guess it's the network problem. This also explains that why you saw "can't read the following volume file: /stdin.001", since lzop is complaining the source image has checksum error. The network quality might not be good. Maybe you can replace the network cable or switch. Or if you have USB disk, you can try to mount it as /home/partimag if the free space is large enough.
Good luck.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think you are correct in saying it may be a network quality issue. I have just performed the image restore process again (same image file, same client PC, same options), this time the client PC has booted correctly into both the Win2k and SUSE Linux partitions.
I'll need to check all the networking components, maybe make a direct link from PC to Server without hub/switch and use quality cable.
Again, many thanks for this superb application and many thanks for your support.
Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
No problem, do our best. If you replace hardware, yet the problem still remains, please let us know.
BTW, just got an email from sf.net about donation you made. We'd like to say thank you very much. Appreciate that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm still having problems relating to the network, I think it's mainly the on-board NICs in these cheap PCs ! The image restore process works most of the time but occasionally I get the Win2k blue screen when trying to boot (corrupted .dll file in Win2k). Restoring the image again seems to either fix it or the Win2k blue screen reports a different .dll fault. The SUSE Linux partition is always OK :-) Sadly I built the server from one of these cheap machines so I think I'll install a PCI NIC.
Would optional error checking be possible in a future release of Clonezilla-Live. Along with a little more GUI to cover the sudo su, mounting the cifs/smbfs etc. ?
Thanks again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Did you use partimage or ntfsclone (option -q) when saving the image ? By default clonezilla will use ntfsclone to save the NTFS image, it's compatibility is better than partimage. For ntfsclone, as I remember, it will verify the data. Here we never has such problem when clone NTFS, and no one ever reported this problem in the past few years.
BTW, maybe you should do a memory test in your client machine, sometimes those weird problems are due to bad RAM. You can do it by booting Clonezilla live CD, and in the boot menu, check the 3rd choice.
As for the GUI about sudo su -, mouting samba server... We will try it. Maybe it will be added in the next release if we make it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I used the default (ntfsclone), if fact I used all default settings. I'll run a memory check on one of the client machines today. They are very cheap systems so maybe my problems lie there :-( I have 59 of them to set up so finding a cloning system is important. I have used Norton Ghost 2003 in the past but can't get it to work now and their new version is, in my opinion, useless.
Regards
Mike
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You have 59 clients ? I think you need multicast clone, so I suggest you to use pxe-boot clonezilla instead of clonezilla live.
For more info about pxeboot clonezilla, check http://clonezilla.sf.net
Basically what you need is to setup a DRBL server, then pxeboot clonezilla is ready. For the time being, I suggest you to use clonezilla 2.1, now it's in testing branch. Since the image format is same with that in clonezilla live. The one in the stable branch is still clonezilla 1.x, so its format is not compatible with clonezilla live, which uses clonezilla 2.x format.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Basically all the function in Clonezilla live is same with pxeboot Clonezilla, except multicast is not available in Clonezilla live.
As for Slackware... well, maybe in the future, pxeboot Clonezilla will be ready on that. Sorry for that.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have the same problem as above.
I created a hard disk image with clonezilla live(1.7) and saved it to a samba share, with default settings.
I boot the target machine with clonezilla live, follow the instructions on screen and get
std001 file not found.
I ran it again this time "checking"
turning off the partimage gui and
set verbose options
now I see... check sum error, file not found stdin.001...
I'll try to create a new image with gzip instead of lzo.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If possible, maybe you can try to use the version 20070406 in http://opensource.nchc.org.tw/clonezilla-live/testing/
The lzop program in that version is recompiled with LZO 2, maybe it will work better.
Please let us know the results if you do such a comparison test.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I too have the problem reported by rdchin so am trying cifs instead of smbfs. I have created the image on the server OK but during the restore process I am having the error "can't read the following volume file: /stdin.001"
I'm asked to enter a new file name but the screen is locked up :-(
Any idea ?
We need more info, so please post the details about the steps you start the restoration.
Also post the file info in the images by:
1. After you mount samba server public folder to /home/partimag, run
a. df > debug.log
b. ls -alF /home/partimag >> debug.log
c. ls -alF /home/partimag/$IMAGENAME >> debug.log
$IMAGENAME with yours)
Then post debug.log here.
Thankyou. I performed standard steps for image restore, accepting default settings. First partition (FAT32) seemed to be OK, error occured with second partition (ReiserFS).
mount -t cifs -o username=images //172.16.15.4/images/smb /home/partimag
debug.log is:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 242136 0 242136 0% /lib/init/rw
udev 10240 52 10188 1% /dev
tmpfs 242136 4 242132 1% /dev/shm
rootfs 302616 77648 224968 26% /
/dev/hdc 75172 75172 0 100% /live_media
tmpfs 242136 17168 224968 8% /cow
tmpfs 242136 0 242136 0% /tmp
//172.16.15.4/images 74750656 10973152 63777504 15% /home/partimag
total 1012
drwx--x--x 4 1001 users 0 Feb 21 2007 ./
drwxr-xr-x 4 root root 80 Feb 21 03:40 ../
drwxr-xr-x 2 1001 users 0 Feb 21 2007 basic_dual/
-rwxr--r-- 1 1001 users 581 Feb 21 2007 debug.log*
drwxr-xr-x 2 1001 users 0 Feb 21 2007 test/
basic_dual
debug.log
test
is this information of use ? Content of test (name I assigend to the image).
drwxr-xr-x 2 images users 4096 2007-02-21 16:29 ./
drwx--x--x 4 images users 4096 2007-02-21 16:28 ../
-rwxr--r-- 1 images users 259 2007-02-21 15:35 cifs1b*
-rwxr--r-- 1 images users 259 2007-02-21 15:35 cifs2b*
-rwxr--r-- 1 images users 80 2007-02-21 16:26 debug.log*
-rwxr--r-- 1 images users 4 2007-02-21 15:41 disk*
-rw-r--r-- 1 root root 0 2007-02-21 16:29 files.log
-rwxr--r-- 1 images users 10 2007-02-21 15:41 parts*
-rwxr--r-- 1 images users 36 2007-02-21 15:35 sda-chs.sf*
-rwxr--r-- 1 images users 512 2007-02-21 15:35 sda-mbr*
-rwxr--r-- 1 images users 259 2007-02-21 15:35 sda-pt.sf*
-rw------- 1 images users 409507485 2007-02-21 15:39 sda1.aa
-rw------- 1 images users 1116988559 2007-02-21 15:41 sda3.aa
Interesting. The image looks fine. reiserfs in clonezilla does not have any problem here.
Now please do more testing in Clonezilla live with //172.16.15.4/images is mounted as /home/partimag:
1. run
file /home/partimag/$IMAGENAME/sda3.aa > file.log
please post file.log here
2. use verbose mode to run ocs-sr as root (sudo su -) by:
a. cp /etc/screenrc ~/.screenrc
b. edit ~/.screenrc, find
defscrollback 1000
make it larger, like:
defscrollback 100000
c. run "screen" to enter screen
d. bash -x /opt/drbl/sbin/ocs-sr -x
remember to choose "-v" and "-nogui"
e. wait for the error, then use "ctrl-a [" (press ctrl-a, release them, then press [), this will enter screen copy/scrollback mode. You can use ctrl-b (pageup), ctrl-f pagedown), j(down), k(up), h(left), l(right) to scrollback the screen. Find the beginning of "ocs-sr -x", then use "space bar" key to mark the beginning of the copy, then move to the end of the ocs-sr error, and use "space bar" key to mark the end of the copy.
f. In the same screen terminal, use vim, jove or whatever editor you are familiar with. For example, vim
vim ocs-err.log
enter edit mode in vim (i.e. press i), then use "ctrl-a ]" to paste the one you put in the buffer of screen.
enter command mode in vim (i.e. press esc), save the file by ":wq".
g. post ocs-err.log here.
Sorry for such a long procedure. However, with this, it's easier for us to know why it fails.
Please bear with me... I'm struggling with the vi editor at the moment (I am new to Linux) but will reply soon.
Please, for clarification... after I press spacebar to mark end of ocs-sr error I seem to be still in "screen", do I need to exit this in some way to then vim ocs-err.log ?
Thanks
Oh,
I tried yet again (4th attempt), after managing to edit screenrc.
This time it all worked perfectly ! I had moved the PC on to a different network connection so I wonder if this had been a problem somewhow. ???
So far I am very pleased with the speed of this application.
Thankyou
Mike
Clonezilla is nothing to do with .screenrc. No idea where went wrong there. But at least now it's working for you. Good.
If you use PXEboot clonezilla with gigabits NIC, the speed will be faster, I think. Someone reported that the restoring speed is about 1.6-2.0 GB/min. Here it's about 1.5 GB/min.
Oh,
The problem has returned again, this time using a different image file. It failed the first time, succeeded the second time, failed the third time. On the 2 occasions of failure it failed at a different stage/partition but the error "can't read the following volume file: /stdin.001" was the same (also says "LZOP: <stdin>: checksum error".
can you advise on my earlier question "... after I press spacebar to mark end of ocs-sr error I seem to be still in "screen", do I need to exit this in some way to then vim ocs-err.log ?"
Many thanks
About ".. after I press spacebar to mark end of ocs-sr error I seem to be still in "screen", do I need to exit this in some way to then vim ocs-err.log ?", no, you have to be in the same screen terminal.
If you see "LZOP: <stdin>: checksum error", I guess it's the network problem. This also explains that why you saw "can't read the following volume file: /stdin.001", since lzop is complaining the source image has checksum error. The network quality might not be good. Maybe you can replace the network cable or switch. Or if you have USB disk, you can try to mount it as /home/partimag if the free space is large enough.
Good luck.
Many many thanks,
I think you are correct in saying it may be a network quality issue. I have just performed the image restore process again (same image file, same client PC, same options), this time the client PC has booted correctly into both the Win2k and SUSE Linux partitions.
I'll need to check all the networking components, maybe make a direct link from PC to Server without hub/switch and use quality cable.
Again, many thanks for this superb application and many thanks for your support.
Mike
No problem, do our best. If you replace hardware, yet the problem still remains, please let us know.
BTW, just got an email from sf.net about donation you made. We'd like to say thank you very much. Appreciate that.
My pleasure,
I'm still having problems relating to the network, I think it's mainly the on-board NICs in these cheap PCs ! The image restore process works most of the time but occasionally I get the Win2k blue screen when trying to boot (corrupted .dll file in Win2k). Restoring the image again seems to either fix it or the Win2k blue screen reports a different .dll fault. The SUSE Linux partition is always OK :-) Sadly I built the server from one of these cheap machines so I think I'll install a PCI NIC.
Would optional error checking be possible in a future release of Clonezilla-Live. Along with a little more GUI to cover the sudo su, mounting the cifs/smbfs etc. ?
Thanks again.
Did you use partimage or ntfsclone (option -q) when saving the image ? By default clonezilla will use ntfsclone to save the NTFS image, it's compatibility is better than partimage. For ntfsclone, as I remember, it will verify the data. Here we never has such problem when clone NTFS, and no one ever reported this problem in the past few years.
BTW, maybe you should do a memory test in your client machine, sometimes those weird problems are due to bad RAM. You can do it by booting Clonezilla live CD, and in the boot menu, check the 3rd choice.
As for the GUI about sudo su -, mouting samba server... We will try it. Maybe it will be added in the next release if we make it.
Hi Steven,
I used the default (ntfsclone), if fact I used all default settings. I'll run a memory check on one of the client machines today. They are very cheap systems so maybe my problems lie there :-( I have 59 of them to set up so finding a cloning system is important. I have used Norton Ghost 2003 in the past but can't get it to work now and their new version is, in my opinion, useless.
Regards
Mike
You have 59 clients ? I think you need multicast clone, so I suggest you to use pxe-boot clonezilla instead of clonezilla live.
For more info about pxeboot clonezilla, check http://clonezilla.sf.net
Basically what you need is to setup a DRBL server, then pxeboot clonezilla is ready. For the time being, I suggest you to use clonezilla 2.1, now it's in testing branch. Since the image format is same with that in clonezilla live. The one in the stable branch is still clonezilla 1.x, so its format is not compatible with clonezilla live, which uses clonezilla 2.x format.
Basically all the function in Clonezilla live is same with pxeboot Clonezilla, except multicast is not available in Clonezilla live.
As for Slackware... well, maybe in the future, pxeboot Clonezilla will be ready on that. Sorry for that.
Thanks Steven,
My DHCP/FTP server is running Slackware Linux, which is not one of the distributions listed on the Clonzilla site.
"Sorry but it will NOT work in other distributions or versions." :-(
I'm trying a few more options here but if all fail then I'll set up SUSE 10 or 10.1 on a system and try Clonezilla 2.1
Regards
Mike
Just to follow-up on this a little...
I see the same issues on my GigE network occasionally. The main problem seems to be the use of the LZOP compression tool instead of gzip or bzip2.
I wonder if the LZOP compression tool is a little less forgiving with network latency that the other tools?
So you mean when you use gzip or bzip2, you never has this problem ?
I have the same problem as above.
I created a hard disk image with clonezilla live(1.7) and saved it to a samba share, with default settings.
I boot the target machine with clonezilla live, follow the instructions on screen and get
std001 file not found.
I ran it again this time "checking"
turning off the partimage gui and
set verbose options
now I see... check sum error, file not found stdin.001...
I'll try to create a new image with gzip instead of lzo.
We had similar issue before, most of the cases are the network quality problem, either the network cable or network switch.
If possible, maybe you can try to use the version 20070406 in
http://opensource.nchc.org.tw/clonezilla-live/testing/
The lzop program in that version is recompiled with LZO 2, maybe it will work better.
Please let us know the results if you do such a comparison test.