Why would a new 300G hard drive format and run Windows 2000 fine, load and run Trustix Linux 2.2 and 3.0.5 fine, load CentOS 4.4 and Ubuntu 6.06 TLS fine but when it comes time to boot them give a "Buffer I/O error on device hda, logical sector 0" and then fail to recognize any of the partitions?
On Monday 26 March 2007 01:10:08 pm James Sissel wrote:
Why would a new 300G hard drive format and run Windows 2000 fine, load and run Trustix Linux 2.2 and 3.0.5 fine, load CentOS 4.4 and Ubuntu 6.06 TLS fine but when it comes time to boot them give a "Buffer I/O error on device hda, logical sector 0" and then fail to recognize any of the partitions?
Game over, dude. On-board controller probably failed. Should at lest be under warranty.
(Of course, you could try just wiggling the wires...)
But Winblows 2000 and 2 versions of Trustix Linux worked. Fedora Core 3 also worked with the non-SMP kernel and no graphics (It couldn't detect my graphics card and I didn't have time to play).
Jonathan Hutchins hutchins@tarcanfel.org wrote: On Monday 26 March 2007 01:10:08 pm James Sissel wrote:
Why would a new 300G hard drive format and run Windows 2000 fine, load and run Trustix Linux 2.2 and 3.0.5 fine, load CentOS 4.4 and Ubuntu 6.06 TLS fine but when it comes time to boot them give a "Buffer I/O error on device hda, logical sector 0" and then fail to recognize any of the partitions?
Game over, dude. On-board controller probably failed. Should at lest be under warranty.
(Of course, you could try just wiggling the wires...)
_______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
On Monday 26 March 2007 03:07:27 pm James Sissel wrote:
But Winblows 2000 and 2 versions of Trustix Linux worked. Fedora Core 3 also worked with the non-SMP kernel and no graphics (It couldn't detect my graphics card and I didn't have time to play).
Past tense. "Worked." They don't now, do they?
Oh, yes. If I load them they work. If I load CentOS or Ubuntu they don't. I can do it many times back and forth. Trustix and Winblows work, CentOS and Ubunto don't.
Jonathan Hutchins hutchins@tarcanfel.org wrote: On Monday 26 March 2007 03:07:27 pm James Sissel wrote:
But Winblows 2000 and 2 versions of Trustix Linux worked. Fedora Core 3 also worked with the non-SMP kernel and no graphics (It couldn't detect my graphics card and I didn't have time to play).
Past tense. "Worked." They don't now, do they? _______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
On Monday 26 March 2007 03:31:08 pm James Sissel wrote:
Oh, yes. If I load them they work. If I load CentOS or Ubuntu they don't. I can do it many times back and forth. Trustix and Winblows work, CentOS and Ubunto don't.
Ah. Are you using a different bootloader for the ones that work?
Hmmm... A couple ideas are rattling around in my head.
First, can you boot a Knoppix Live CD and then read the contents of the 300 GB drive with one of your non-booting Linux installations? This would indicate that the file system is ok and that you could have a bootloader issue. Lilo has to access all of its boot files from the first 1024 cylinders of your hard drive. This may be a problem if you have chosen Lilo.
Second, if you are using GRUB with each of your installations, you may want to check to see if the GRUB versions are the same. An interesting and perhaps helpful technical article on GRUB can be found here:
http://www.uruk.org/orig-grub/technical.html
Third, Could it be the way the bootloaders are looking at the hardware? In the BIOS, I am assuming that you are using Linear ( or Logical) Block Addressing. Sometimes, you can have mixed results with the Drive jumper being set to "Cable Select" instead of "Master" or "Master mode with a Slave"
Fourth, perhaps you have an incompatible IDE Interface for the IDE Controller on the drive. Some OSes can compensate for certain incompatiblities with modified drivers. Often, drive manufacturers release firmware updates to resolve compatibility issues. Although I am not familiar with your particular brand of system board, System board manufacturers often provide BIOS updates that can can fix compatibility and performance issues as well. I am making alot of assumptions here, such as the system board having integrated IDE adapters.
Fifth, you mentioned that you replaced the 300 GB IDE drive with a SATA drive and yout problems went away. Certain system boards, especially early implementations of integrated IDE and SATA controllers on the same system board, have had mixed results. Try reconnecting the 300 GB drive on your IDE interface and the go into BIOS and disable the SATA controllers and see if your problem clears up. I have resolved several Boot issues this way.
Good Luck and best wishes!
Thanks,
Jeffrey A. McCright, A+ 816-210-3107 jmccright@hotmail.com
From: James Sissel jimsissel@yahoo.com To: Kclug@kclug.org Subject: Re: OK, if it is too quiet Date: Mon, 26 Mar 2007 13:31:08 -0700 (PDT)
Oh, yes. If I load them they work. If I load CentOS or Ubuntu they don't. I can do it many times back and forth. Trustix and Winblows work, CentOS and Ubunto don't.
Jonathan Hutchins hutchins@tarcanfel.org wrote: On Monday 26 March 2007 03:07:27 pm James Sissel wrote:
But Winblows 2000 and 2 versions of Trustix Linux worked. Fedora Core 3 also worked with the non-SMP kernel and no graphics (It couldn't detect my graphics card and I didn't have time to play).
Past tense. "Worked." They don't now, do they? _______________________________________________ Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
Kclug mailing list Kclug@kclug.org http://kclug.org/mailman/listinfo/kclug
_________________________________________________________________ The average US Credit Score is 675. The cost to see yours: $0 by Experian. http://www.freecreditreport.com/pm/default.aspx?sc=660600&bcd=EMAILFOOTE...
If it's saying "Buffer I/O error on device hd*a*", then this is Linux speaking, not GRUB. If Trustix works and CentOS does not, that means there is probably either a bugfix in a newer version of Linux, or a regression, depending on which OS has a more recent version of Linux.
Try copying the kernel and modules from Trustix to the CentOS/Ubuntu system and see if it will boot. (assuming they're both similar versions; eg, both 2.6)