Not imaging - image exists - client size 0?
-
Hello, I’m very new to using this wonderful tool so please forgive any ignorance.
The image I am trying to write to my Optiplex 755 (successful in the past) is now not working. I’ve since added a new hdd for a rather large image, mounted it to /images, extracted the image, then removed the hdd and restored the previous files to the /images directory.
I’m wondering if this 0 imagesize in the db is having an effect on the writing of it? If so is there any way to accurately populate this data? (looking at the size of the actual files in the directory, it isn’t 100% with the size of the image as stored in the db)
Please let me know what other information I can provide that will help.
Thanks!
[ATTACH=full]1569[/ATTACH]
[ATTACH=full]1570[/ATTACH]
[url=“/_imported_xf_attachments/1/1569_image.png?:”]image.png[/url][url=“/_imported_xf_attachments/1/1570_imagedb.png?:”]imagedb.png[/url]
-
that 0.00ib just means that you haven’t deployed the image yet. My best guess is this is an image coming from a 0.32 server?
-
[quote=“Tom Elliott, post: 40284, member: 7271”]that 0.00ib just means that you haven’t deployed the image yet. My best guess is this is an image coming from a 0.32 server?[/quote]
Thanks for your reply, here is some more information:
Fog Version - 1.2.0
OS - Ubuntu 12.04 (32bit)Uploaded installation log, appache log is clean
[url=“/_imported_xf_attachments/1/1571_foginstall.txt?:”]foginstall.txt[/url]
-
Was the image you’re not seeing performed an a pre-1.0.0 release?
-
Nope,
Sorry for leaving this bit out, I’m installing it on a vbox vm for testing purposes right now (although I get the same issue with the optiplex). Here is a couple snapshots of the screens I see when trying to download the image if it helps:
Thanks again
![ATTACH=full]1572[/ATTACH][ATTACH=full]1573[/ATTACH][url=“/_imported_xf_attachments/1/1572_screen1.png?:”]screen1.png[/url][url=“/_imported_xf_attachments/1/1573_screen2.png?:”]screen2.png[/url]
-
what is the output of [CODE]ls -al[/CODE] in your /images directory?
-
drwxrwxrwx 7 root root 4096 Dec 12 02:18 .
drwxr-xr-x 26 root root 4096 Dec 19 07:21 …
drwxrwxrwx 2 root root 4096 Dec 1 07:24 WITHHELD
drwxrwxrwx 3 root root 4096 Dec 12 06:11 dev
drwxrwxrwx 2 root root 4096 Dec 10 01:11 WITHHELD
-rwxrwxrwx 1 root root 0 Dec 1 04:27 .mntcheck
drwxrwxrwx 2 root root 4096 Dec 1 04:27 WITHHELD
drwxrwxrwx 2 root root 4096 Dec 4 01:46 Windows7sysprep -
what is the output of
Code:
ls -al
in your /images/Windows7sysprep directory? -
[quote=“Junkhacker, post: 40300, member: 21583”]what is the output of
Code:
ls -al
in your /images/Windows7sysprep directory?[/quote]drwxrwxrwx 2 root root 4096 Dec 4 01:46 .
drwxrwxrwx 7 root root 4096 Dec 12 02:18 …
-rwxrwxrwx 1 root root 512 Dec 4 00:51 d1.mbr
-rwxrwxrwx 1 root root 168088334 Dec 4 00:51 d1p1.img
-rwxrwxrwx 1 root root 14303046206 Dec 4 01:46 d1p2.img
-rwxrwxrwx 1 root root 3741299251 Dec 4 01:52 d1p3.img -
If you’re running windows7sysprep, but this is setup for Multi-Partition (Non-resizable), I only have one guess as to why your image isn’t deploying. That guess is the disk you’re attempting to push to is smaller than the disk this image was created from.
