If this is the wrong area for bug reports Please let me know where I can post this. Thank You.
This is my first time using this version / disk. Opened up the option below Clonezilla at the beginning of the boot process to get to the CLI.
used fsck -f on all disks involved - mounted all disks involved - used rsync to copy and delete files sudo umounted all mounted partitions and exited.
The next screen showed the following,
"
mktemp: failed to create file via template
'/tmp/cmdtemp.xxxxxx: Read-only file system
/usr/share/drbl/sbin/drbl-functions:
line 2424: $parse_tmp: ambiguous redirect
-i used with no filenames on the command line,
reading from STDIN.
"
Then nothing - dead!
Rebooted - went directly into CloneZilla and no apparent problems backing up two partitions.
Hope this helps.
Anything else let me know.
Thanks
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have never encounter this issue here.
How about your RAM size? Is it too small? Or I can not find any possibilities which will cause Clonezilla to crash like that.
Steven.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry to bother you again but I have isolated the problem and it is a change that 'you' have made recently.
I use the shell to do some file copying prior to a backup. I sudo mount 8 partitions prior to copying. When I am finished I sudo umount -a before EXITing.
This is the cause of the crash. Up until now sudo umount -a has done its job and I continue to clone but not with Clonezila 2.4.2-10 downloaded on 15 June. After EXIT I crash.
After a number of different trial scenarios I found that sudo umount -a causes a crash but
sudo umount part1 part2 part3 part4 part5 . . .
doesn't.
Apparently you have mounted a filesystem probably /tmp somewhere where a user can umount it in the shell.
Anyway, I hope this helps.
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If this is the wrong area for bug reports Please let me know where I can post this. Thank You.
This is my first time using this version / disk. Opened up the option below Clonezilla at the beginning of the boot process to get to the CLI.
used fsck -f on all disks involved - mounted all disks involved - used rsync to copy and delete files sudo umounted all mounted partitions and exited.
The next screen showed the following,
"
mktemp: failed to create file via template
'/tmp/cmdtemp.xxxxxx: Read-only file system
/usr/share/drbl/sbin/drbl-functions:
line 2424: $parse_tmp: ambiguous redirect
-i used with no filenames on the command line,
reading from STDIN.
"
Then nothing - dead!
Rebooted - went directly into CloneZilla and no apparent problems backing up two partitions.
Hope this helps.
Anything else let me know.
Thanks
Sorry for the delay but I was unable to find where I lodged this issue.
This issue is 100% reproducible. I have about 12mb of memory and I have never used more than 1/3 of it.
What I do is (fsck -f) a number of ext4 partitions, (mount) them, use (rsync -auv) to update the filelist, (umount -a) them and (EXIT).
Upon exit the issue pops up as stated 100% of the time.
Hope this late message helps.
some help
the initial step was I got in was 'enter shell > cmd'
I tried just entering the shell and back out and everything was normal
I tried it again but with mkdir and mounting a partition then umounting then the same error message.
Hope this helps
I have never encounter this issue here.
How about your RAM size? Is it too small? Or I can not find any possibilities which will cause Clonezilla to crash like that.
Steven.
"12mb of memory"?
The basic requirements for Clonezilla live is 196 MB, as described here:
http://clonezilla.org/
Steven.
I wrote down where this was lodged so now I can read the replies.
Typo!
should be "12gb of memory"
Does anyone have 12mb of memory?
The issue is persistent.
Hope this helps.
Sorry to bother you again but I have isolated the problem and it is a change that 'you' have made recently.
I use the shell to do some file copying prior to a backup. I sudo mount 8 partitions prior to copying. When I am finished I sudo umount -a before EXITing.
This is the cause of the crash. Up until now sudo umount -a has done its job and I continue to clone but not with Clonezila 2.4.2-10 downloaded on 15 June. After EXIT I crash.
After a number of different trial scenarios I found that sudo umount -a causes a crash but
sudo umount part1 part2 part3 part4 part5 . . .
doesn't.
Apparently you have mounted a filesystem probably /tmp somewhere where a user can umount it in the shell.
Anyway, I hope this helps.
Thanks.
Got it. Yes, due to the live system limitation, sometimes we have to use the dir in /tmp/ as the mount point.
Thanks for sharing that.
Steven.