I am about to lose my mind and my job! I made a clonezilla image of a windows machine over the network and have spent more then a week trying to install it back across the same network.
I have given up trying to restore the image across the network and have resorted to putting the image on a usb disk and installing it locally.
But now clonezilla pops up an error when it tries to mount the WRONG disk parttion and I cannot mount the god damn usb drive because every time I try to execute sudo fdisk -l I get a error message: unable to execute /usr/sbin/fdisk: input/output error.
Clonezilla is trying to mount sda1 to /home/partimag and that is NOT the where the usb disk and image folder is!
The usb drive is sdd1. But if I try to mount it using mount -t ntfs /dev/sdd1 /home/partimag I can see the damn led on the usb device flicker but when I go to the /home/partimag folder it is just an empty folder!!
It is maddening! I am about ready to get a baseball bat and just beat the machine into bits!!!
What the hell am I doing wrong???
I am not a unix guy! I used to be years ago but years of using windows has withered my ability to do anything in unix any more. I have to get this image installed on a dozen machines or I am going to lose my job!!!!!!!
Why is clonezilla refusing to see the usb drive so I can point to the image folder and get the image installed.
Please for the love of god can someone lend me a hand?
Last edit: Logan Abbott 2024-09-01
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When I use local storage I alway use storage with a linux filesystem on it, for example ext3. I never had problems mounting such filesystems and don't have experience mounting a NTFS filesystem. However, I found the following note on http://clonezilla.org/clonezilla-usage/general-live-use.php concering mounting a NTFS filesystem:
If the file system of /dev/hdb1 is ntfs, you have to use "ntfs-3g /dev/hdb1 /home/partimag" to mount it so that it's writable.
You could try that. Hope it helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am about to lose my mind and my job! I made a clonezilla image of a windows machine over the network and have spent more then a week trying to install it back across the same network.
I have given up trying to restore the image across the network and have resorted to putting the image on a usb disk and installing it locally.
But now clonezilla pops up an error when it tries to mount the WRONG disk parttion and I cannot mount the god damn usb drive because every time I try to execute sudo fdisk -l I get a error message: unable to execute /usr/sbin/fdisk: input/output error.
Clonezilla is trying to mount sda1 to /home/partimag and that is NOT the where the usb disk and image folder is!
The usb drive is sdd1. But if I try to mount it using mount -t ntfs /dev/sdd1 /home/partimag I can see the damn led on the usb device flicker but when I go to the /home/partimag folder it is just an empty folder!!
It is maddening! I am about ready to get a baseball bat and just beat the machine into bits!!!
What the hell am I doing wrong???
I am not a unix guy! I used to be years ago but years of using windows has withered my ability to do anything in unix any more. I have to get this image installed on a dozen machines or I am going to lose my job!!!!!!!
Why is clonezilla refusing to see the usb drive so I can point to the image folder and get the image installed.
Please for the love of god can someone lend me a hand?
Last edit: Logan Abbott 2024-09-01
" a error message: unable to execute /usr/sbin/fdisk: input/output error." -> Normally this is hardware issue. You can try to use different hardware.
Steven
When I use local storage I alway use storage with a linux filesystem on it, for example ext3. I never had problems mounting such filesystems and don't have experience mounting a NTFS filesystem. However, I found the following note on http://clonezilla.org/clonezilla-usage/general-live-use.php concering mounting a NTFS filesystem:
You could try that. Hope it helps.