Dear All,
I have a K8S-MX Asus Athlon 64 Motherboard with a 754 pin 3000+ CPU, which I cam trying to install 4.1 Centos 64 bit.
The problem seems to arise when installing onto Mirrored disks, I have noticed that from Centos 4 onwards it tries to rebuild the arrays as it installs which slows the whole process right down across all platforms I have tried it on.
In addition, the install process bails out at random times with random errors eg. "Disk Full", "error loading this package or that package", Error reading DVD etc... now I have burnt several copies of the DVD, tested them fully, tried installing from CD, even changed the hardware to a twin Opteron system, changed the RAM changed this disks and tried everything but it still seems really touch and go as to wether the install will complete.
I haven't managed it yet on the Asus platform it took about 12 goes on the opteron platform. Yet Centos 3.4 installs no problem.
Finally the last straw was the boot loader problem with occurs either immediately after reboot after install or on one of the boots soon after, and I have to do this to fix it: -------------------------------------- grub> root (hd0,0) Filesystem type is ext2fs, partition type 0xfd
grub> setup (hd0) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 16 sectors are embedded. succeeded Running "install /boot/grub/stage1 (hd0) (hd0)1+16 p (hd0,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded Done.
grub> root (hd1,0) Filesystem type is ext2fs, partition type 0xfd
grub> setup (hd1) Checking if "/boot/grub/stage1" exists... yes Checking if "/boot/grub/stage2" exists... yes Checking if "/boot/grub/e2fs_stage1_5" exists... yes Running "embed /boot/grub/e2fs_stage1_5 (hd1)"... 16 sectors are embedded. succeeded Running "install /boot/grub/stage1 (hd1) (hd1)1+16 p (hd1,0)/boot/grub/stage2 /boot/grub/grub.conf"... succeeded Done.
grub> quit ------------------
Has anyone else seen these tedious unpredicatble errors on install that seems to have arrived with version 4 onwards...?
Regards
Pete