/Dev/sda5/ filesystem: unknown or unsupported / /home/partimag is full
A partition and disk imaging/cloning program
Brought to you by:
steven_shiau
Menu
▾
▴
I was previously using DRBL 2.1.0-12-life-i686.iso to clone PCs via CloneZilla Server Edition, and everything works fine with my older systems.
But I recently got new machines I needed to clone, and apparently the new onboard NIC doesn't have supported drivers on that older DRBL. Those systems will pick up an IP address, but never receive an image to boot from. When I upgraded to the latest version of DRBL (2.4.2.10), everything seems to work fine (It boots the source machines into DRBL to store the image) until it finishes trying to save the image. It proceeds to successfully write about 1.7gb of files to the drive, then fails, stating /dev/sda5 filesystem: unknown or unsupported.
The thumb drive I was storing the images on is a 64gb that was formatted to exfat. It has plenty of space (The source disk is 32gb with only about 8gb used, the destination has zero files and shows 59gb free, and I even tried reformatting it to be sure) I saw notes in releases that seemed to indicate that exfat support was removed from DRBL-OCS due to patent concerns (Microsoft owns the patent for exfat)... yet if I check, with sudo apt-get install exfat-utils it says exfat-utils and exfat-fuse are both installed and the latest version. And the fact that it does actually write some files successfully seem to indicate something else is awry..
So I tried formatting the disk to NTFS, but I get the same results..
Unsure what to do to try and work around this..!
Here's what's displayed on screen at the point it fails:
Cloned successfully
Checking the disk space
Finished saving /dev/sda1 as /home/partimag/mydiskimage02122016/sda1.ext4-ptcl-...
Started saving /dev/sda5 as /home/partimag/mydiskimage02122016/sda5.XXX...
/dev/sda5 filesystem: Unknown or unsupported.
Checking the disk space...
/home/partimag is full! No space left on device!
program terminated
press "enter" to continue
I tried restoring the "image" it stored, but those machines boot to a blinking cursor, indicating the file system it restored is incomplete somehow..
The source and DRBL PCs are all small embedded machines with Intel Celeron processors, 2gb DDR3 and 32GB SSD. The older ones were Intel Atom embedded machines with 1GB DDR2 and same 32GB SSD. The older OS was Linux Mint 14 32 bi tXFCE, the newer ones are using Linux Mint 17.2 32 bit XFCE
Did you try the testing one? Like DRBL live 2.4.5-6 or even newer if it's available?
http://drbl.org/download/
Steven.
I just downloaded and tried 2.4.5-6, it appears to have the same issue, but presents it in a slightly different way.
When starting Clonezilla-SE on this one, it now asks which device to save the image to (Which the original version did but the current release didn't). It even sees the "DRBL-Images" directory which I created to ensure it's seeing the right location..
During the "Calculating Bitmap" process, it got just over 55% through and gave an error saying it failed to use partclone to save the image and waited for me to press Enter to continue. On screen it says to check /var/log/partclone.log I assume this is on the host? But I checked /var/log/ and don't see the partclone.log file
It then appeared to go through saving the partition and created about 5gb of files on the USB drive, just like before, but after that completed, again said the image was not saved correctly, then proceeded to shut down the client as I selected during the clonezilla-SE setup process.
Did you run fsck to check the file system before saving it? If not, enter expert mode, and choose "-fsck-src-part" to make Clonezila do that for you.
Steven.