diff -Nru initramfs-tools-0.85eubuntu36/debian/changelog initramfs-tools-0.85eubuntu38/debian/changelog
--- initramfs-tools-0.85eubuntu36/debian/changelog	2008-04-10 09:00:50.000000000 -0400
+++ initramfs-tools-0.85eubuntu38/debian/changelog	2008-05-29 11:15:12.000000000 -0400
@@ -1,3 +1,10 @@
+initramfs-tools (0.85eubuntu38) hardy-proposed; urgency=low
+
+  * Provide a clearer error on mount failure of the Windows host
+    filesystem (LP: #226622)
+
+ -- Agostino Russo <agostino.russo@gmail.com>  Tue, 06 May 2008 23:55:47 +0100
+
 initramfs-tools (0.85eubuntu36) hardy; urgency=low
 
   * Drop dependency on volumeid, it's shipped by udev again.
diff -Nru initramfs-tools-0.85eubuntu36/scripts/local initramfs-tools-0.85eubuntu38/scripts/local
--- initramfs-tools-0.85eubuntu36/scripts/local	2008-04-09 10:18:14.000000000 -0400
+++ initramfs-tools-0.85eubuntu38/scripts/local	2008-05-27 12:50:22.000000000 -0400
@@ -74,8 +74,23 @@
 	# FIXME This has no error checking
 	# Mount root
 	mount ${roflag} -t ${FSTYPE} ${ROOTFLAGS} ${ROOT} ${rootmnt}
-
+	mountroot_status="$?"
 	if [ "$LOOP" ]; then
+		if [ "$mountroot_status" != 0 ]; then
+			if [ ${FSTYPE} = ntfs ] || [ ${FSTYPE} = vfat ]; then
+				panic "
+Could not mount the partition ${ROOT}.
+This could also happen if the file system is not clean because of an operating
+system crash, an interrupted boot process, an improper shutdown, or unplugging
+of a removable device without first unmounting or ejecting it.  To fix this,
+simply reboot into Windows, let it fully start, log in, run 'chkdsk /r', then
+gracefully shut down and reboot back into Windows. After this you should be
+able to reboot again and resume the installation.
+(filesystem = ${FSTYPE}, error code = $mountroot_status)
+"
+			fi
+		fi
+	
 		mkdir -p /host
 		mount -o move ${rootmnt} /host