This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
My (GRUB) boot loader has suddenly started giving me an �Error 17�. I�ve found out that this means that the loader cannot recognise the file system type, so I�ll need to change the grub.conf file. Problem is all I get is the error message, and the machine hangs � I don�t have my distribution CD, or even a recovery floppy. Any Ideas?
My concern is that I don�t know why, or how this has happened � I don�t recall changing anything in the BIOS, or the Linux / Windows partitions. It just started crashing � at the worst time possible � of course!
I was just about to post a very similar question - the commenst about BIOS and drive types sounds like me.
I'm preparing a home machine as an Ubuntu server (ie minimal install, headless etc) but I cannot boot from CD on the target machine. What I did was move the drive to my primary machine, disconnecting all of the other drives except CDROM and target drive, installed and setup the various bits (eg ssl for remote admin) then moved the drive back to the machine where it will live.
After restarting, I was able to ping the box and ssh to it, then tried CVS and... nothing. I then tried ssh and ping again and... nothing. I plugged in a monitor and keyboard and restarted, then found that the BIOS had reset. After doing the minimal amount to get the BIOS started, I got the GRUB Error 17.
I had considered the filesystem type problem and was about the reinstall and make the /boot partition ext2 rather than ext3 (I was also using the virual drive manager thingy, I forget the name) but I'll try putting the drive settings in BIOS first and see how I go.