Troubleshoot Downloading - Unicast - Revision history

Wayne-workman.28155: /* Task is completed, computer will now restart */

2015-11-26T03:51:24Z

‎Task is completed, computer will now restart

Wayne-workman.28155 at 03:49, 26 November 2015

2015-11-26T03:49:46Z

Wayne-workman.28155: /* Task is completed, computer will now restart */

2015-11-26T03:48:39Z

‎Task is completed, computer will now restart

Wayne-workman.28155: /* Task is completed, computer will now restart */

2015-11-26T03:44:11Z

‎Task is completed, computer will now restart

Wayne-workman.28155: /* Task is completed, computer will now restart */

2015-11-26T03:43:49Z

‎Task is completed, computer will now restart

Wayne-workman.28155: /* Task is completed, computer will now restart */

2015-11-26T03:43:31Z

‎Task is completed, computer will now restart

Wayne-workman.28155 at 03:42, 26 November 2015

2015-11-26T03:42:41Z

Wayne-workman.28155: Created page with "Article under construction. Below, you will find notes / jibberish that I'm collecting to make into an article."

2015-06-03T02:27:50Z

Created page with "Article under construction. Below, you will find notes / jibberish that I'm collecting to make into an article."

New page

Article under construction. Below, you will find notes / jibberish that I'm collecting to make into an article.

@@ Line 7: / Line 7: @@
 == Task is completed, computer will now restart ==
-The task completes but did not image, did not actually complete the task, did not really deploy the image.
+The task completes but did not image, did not actually complete the task, did not really deploy the image. You receive the below (pictured) error when deploying an image.
-You receive the below (pictured) error when deploying an image. This is ''normally'' caused by a non-resizable image that has been deployed to a host with a hard drive that is too small to hold the image.
+[[File:Image Too Big For Destination Drive.jpg]]
 In order to deploy a non-resizable image, the destination HDD '''must''' be the same size or larger than the HDD the image was taken from. If the source HDD was 80GB and destination HDD is 80GB but the HDDs are different brands, it is possible that the image deployment can fail. This is because the destination HDD '''MUST''' be at least as large as the source. Even 4 sectors less, or even 16KB smaller and the image deployment '''will''' fail.
 Generally, to fix this you would use the resizeable image type.
 Another time you might recieve this error is if you're trying to deploy to an HDD that is '''absolutely blank''' - with no pre-existing partitions. In such case, you might try the fix in this thread: [https://forums.fogproject.org/topic/6117/svn-image-doesnt-push svn image doesnt push]. The user in this thread followed this: [https://wiki.fogproject.org/wiki/index.php/Modifying_the_Init_Image Modifying_the_Init] and added this code:
@@ Line 42: / Line 48: @@
   echo "checked $testdisk for partitions (no need to kill partition table yet)";
 fi</pre>

← Older revision		Revision as of 03:49, 26 November 2015
Line 16:		Line 16:

	Another time you might recieve this error is if you're trying to deploy to an HDD that is '''absolutely blank''' - with no pre-existing partitions. In such case, you might try the fix in this thread: [https://forums.fogproject.org/topic/6117/svn-image-doesnt-push svn image doesnt push]. The user in this thread followed this: [https://wiki.fogproject.org/wiki/index.php/Modifying_the_Init_Image Modifying_the_Init] and added this code:		Another time you might recieve this error is if you're trying to deploy to an HDD that is '''absolutely blank''' - with no pre-existing partitions. In such case, you might try the fix in this thread: [https://forums.fogproject.org/topic/6117/svn-image-doesnt-push svn image doesnt push]. The user in this thread followed this: [https://wiki.fogproject.org/wiki/index.php/Modifying_the_Init_Image Modifying_the_Init] and added this code:
		+
		+	Just before the image check types:
		+
		+	<pre># Generates the partitions. If singledisk resizeable, it generates
		+	# based on default normal values.
		+	# Otherwise it uses MBR/GPT to generate the partition table(s).</pre>
		+
		+	Add this code:

	<pre>#fix for possible dodgy partitions on the disk		<pre>#fix for possible dodgy partitions on the disk

@@ Line 15: / Line 15: @@
 Generally, to fix this you would use the resizeable image type.
-Another time you might recieve this error is if you're trying to deploy to an HDD that is '''absolutely blank''' - with no pre-existing partitions. In such case, you might try the fix in this thread: [https://forums.fogproject.org/topic/6117/svn-image-doesnt-push svn image doesnt push]
+Another time you might recieve this error is if you're trying to deploy to an HDD that is '''absolutely blank''' - with no pre-existing partitions. In such case, you might try the fix in this thread: [https://forums.fogproject.org/topic/6117/svn-image-doesnt-push svn image doesnt push]. The user in this thread followed this: [https://wiki.fogproject.org/wiki/index.php/Modifying_the_Init_Image Modifying_the_Init] and added this code:
 [[File:Image Too Big For Destination Drive.jpg]]

@@ Line 15: / Line 15: @@
 Generally, to fix this you would use the resizeable image type.
-Another time you might recieve this error is if you're trying to deploy to an HDD that is a'''bsolutely blank''' - with no pre-existing partitions. In such case, you might try the fix in this thread: [https://forums.fogproject.org/topic/6117/svn-image-doesnt-push svn image doesnt push]
+Another time you might recieve this error is if you're trying to deploy to an HDD that is '''absolutely blank''' - with no pre-existing partitions. In such case, you might try the fix in this thread: [https://forums.fogproject.org/topic/6117/svn-image-doesnt-push svn image doesnt push]
 [[File:Image Too Big For Destination Drive.jpg]]

@@ Line 9: / Line 9: @@
 The task completes but did not image, did not actually complete the task, did not really deploy the image.
-You receive the below error when deploying an image. This is ''normally'' caused by a non-resizable image that has been deployed to a host with a hard drive that is too small to hold the image.
+You receive the below (pictured) error when deploying an image. This is ''normally'' caused by a non-resizable image that has been deployed to a host with a hard drive that is too small to hold the image.
 In order to deploy a non-resizable image, the destination HDD '''must''' be the same size or larger than the HDD the image was taken from. If the source HDD was 80GB and destination HDD is 80GB but the HDDs are different brands, it is possible that the image deployment can fail. This is because the destination HDD '''MUST''' be at least as large as the source. Even 4 sectors less, or even 16KB smaller and the image deployment '''will''' fail.

← Older revision		Revision as of 03:43, 26 November 2015
Line 6:		Line 6:

	== Task is completed, computer will now restart ==		== Task is completed, computer will now restart ==
		+
		+	The task completes but did not image, did not actually complete the task, did not really deploy the image.

	You receive the below error when deploying an image. This is ''normally'' caused by a non-resizable image that has been deployed to a host with a hard drive that is too small to hold the image.		You receive the below error when deploying an image. This is ''normally'' caused by a non-resizable image that has been deployed to a host with a hard drive that is too small to hold the image.

← Older revision		Revision as of 03:42, 26 November 2015
Line 1:		Line 1:
	Article under construction. Below, you will find notes / jibberish that I'm collecting to make into an article.		Article under construction. Below, you will find notes / jibberish that I'm collecting to make into an article.
		+
		+
		+
		+	= Common Problems =
		+
		+	== Task is completed, computer will now restart ==
		+
		+	You receive the below error when deploying an image. This is ''normally'' caused by a non-resizable image that has been deployed to a host with a hard drive that is too small to hold the image.
		+
		+	In order to deploy a non-resizable image, the destination HDD '''must''' be the same size or larger than the HDD the image was taken from. If the source HDD was 80GB and destination HDD is 80GB but the HDDs are different brands, it is possible that the image deployment can fail. This is because the destination HDD '''MUST''' be at least as large as the source. Even 4 sectors less, or even 16KB smaller and the image deployment '''will''' fail.
		+
		+	Generally, to fix this you would use the resizeable image type.
		+
		+	Another time you might recieve this error is if you're trying to deploy to an HDD that is a'''bsolutely blank''' - with no pre-existing partitions. In such case, you might try the fix in this thread: [https://forums.fogproject.org/topic/6117/svn-image-doesnt-push svn image doesnt push]
		+
		+
		+	[[File:Image Too Big For Destination Drive.jpg]]