<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Greets,<br></div><div><br></div><div>I have a client who has been plagued by Grub 17 errors for the longest time. I'm using grub 0.97 ("legacy") on a version 0.6 version of Voyage. Please don't tell me to upgrade -- it takes months to verify that a change of that nature is going to be safe.<br></div><div><br></div><div>I've done everything I can to debug the problem, but the error path in fsys_ext2fs.c doesn't seem applicable -- the partition sizes have been verified to be correct, there are no errors from fsck (other than the expected ones because the ALIX.3D2 was power cycled just before it happened) indicating the superblock had a bad magic number.</div><div><br></div><div>I'm not able to recreate the problem here, and updating the filesystem so it has a debugging version of grub fixes the problem.</div><div><br></div><div>The systems are cloned from an image using "dd", but grub is then re-installed manually. All of the system I have in house, and all of the tests that I perform on systems I ship, are successful. When they receive the systems they perform the exact same test, which is also successful. It isn't until the systems are installed in the field that they fail.</div><div><br></div><div>I'm using Kingston "Elite Pro" 8GB compact flash for the O/S image and application. Although it isn't "industrial" grade flash, the application was written so it minimizes the number of modified filesystem blocks as much as possible.</div><div><br></div><div>Help?<br></div><div>--<br>Julie Haugh<br>Senior Design Engineer<br>greenHouse Computers, LLC // jfh at <a href="http://greenhousepc.com">greenhousepc.com</a> // greenHousePC on Skype</div></span></body></html>