I've read the bug page which is interesting but while the drive is multiboot it only boots it is a LINUX system only and was created as a LINUX system. The standard choices of LINUX, floppy, and Failsafe are the only boot choices. The bug page says: "The problem occurs if 1.the BIOS and Linux "see" different disk geometries AND 2.the Windows partition is larger than about 8 GB (more precisely: if the first hard disk partition ends on cylinder 1024 or beyond this point). [The first partition is the /boot filesystem and is 250 MB. When the system is booted, Windows may use the values in the partition table, which causes a failure. Currently, this problem also occurs on other Linux distributions using kernel 2.6." Still my system meets the first criteria, seeing different geometries. I did set the disk BIOS to LBA and still received the error. This disk is a near to production setup and I'm rightly concerned not to trash it by making partition table changes. Further, I have been using Partition Commander(PC) to copy as checkpoints during this process. Each drive image takes 5 hours, slowing the integration process. PC appears to me to be a mostly Windows oriented product. That may imply when partition copies are made they follow some yet undiscovered aspect of Windows partitioning practices. Wait. Since my last check point has the same problem and the current drive is working just fine, I could use that last check point to test this parted fix. Bad parted, bad!
[ prior discussions omitted ]
Be sure also to read this page:
http://portal.suse.com/sdb/en/2004/05/fhassel_windows_not_booting91.html
Basically, there is a bug in the GNU parted that comes with SuSE 9.1 that may cause problems if you are doing multi-boot on the same disk with SuSE and Windows.
-Ti
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com