Page 1 of 1

Problem with CMD line syntax to begin imaging

Posted: Sat Feb 27, 2010 12:47 pm
by RonC
I am running FSArchiver from a System Rescue CD and am in Terminal mode, and entered at the prompt:

fsarchiver savefs /dev/sdc1/Leeenux-img.fsa /dev/sda1

where the first is is destination, an external USB hard drive (NTFS format), and the second is the source, the SSD (Ext4 format) in an L701 netbook. The CD was booted through an external USB optical drive.

Please help explain the error that results, and how to correct it:

[errno=20, Not a directory]" archwriter.c#114,archwriter_create(): cannot create archive /dev/sdc1/Leeenux-img.fsa

All drives and partitions are visible in GParted, and the menu selection Mount for each drive is grayed-out, so would this mean it's already mounted, or does it have to be mounted from the command line, and if so, suggestions please, as I see one way of mounting will cause a crash.

fsarchiver probe gives a nice display. I don't know if anything that displays there would explain the above -- but I can access this.

Re: Problem with CMD line syntax to begin imaging

Posted: Sat Feb 27, 2010 12:56 pm
by admin
The problem is that /dev/sdc1 is a block device. It has to be mounted first:

Code: Select all

mount /dev/sdc1 /mnt/backup
fsarchiver savefs /mnt/backup/Leeenux-img.fsa /dev/sda1
umount /mnt/backup

Re: Problem with CMD line syntax to begin imaging

Posted: Sat Feb 27, 2010 2:59 pm
by RonC
Great, I'm going to try it right away.
admin wrote:umount /mnt/backup
And, just out of curiosity, since I'm running this from a "live" disk, what's the significance of the unmount? Would the source or target be damaged in any way, if one were just to exit terminal and reboot?

I'm really a Linux newbie, and I ask to help my understanding of what one has to be careful of, and what makes no difference, as I continue to work with the command line.

Re: Problem with CMD line syntax to begin imaging

Posted: Sat Feb 27, 2010 4:35 pm
by RonC
RonC wrote:Great, I'm going to try it right away.
Great, once again, as the system booted normally after the restore.

This is working much better than Clonezilla, that was really unusable because it wouldn't replace one critical component, GRUB. [edit: I now think it did replace it, but not with the original.] The backup and restore seemed to work properly, but each time the system was booted after that, it would hang at the GRUB prompt. Not a satisfactory outcome.

Seems a minority of users experience this and no one knows why, for sure. Some say that Clonezilla "replaces" an existing copy GRUB with one of its own. Other than that, no explanation.

So, I am very appreciative of your program, given the scarcity of utilities that work with Ext4. Even users of the latest Semantec/Norton Ghost are complaining of this deficiency.

Now I am looking at learning scripting, with the idea of placing a script on the USB drive, that would automate this, but that would have to be a new thread.