Problem description: As soon as S-ATA discs are connected to the motherboard VIA EN15000G the iMedia Linux 5.0.3 blocks after post with its message ". ..."! Once the drives disconnected again, the system will boot as expected." System components are: Motherboard: VIA EN15000G with 1GB DDR2/533 installed DELOCK 54115 8GB for OS 2 * S-ATA 250GB (Maxtor 7V250F0) Optical drive: CD-RW/DVD-ROM SD-R2102 I tried the following: -different templates of installation -a manual package install -configure the "grub.conf" file in another manner than produced by those templates I observed the following: 1)during the OS installation the S-ATA disk are listed as followed HDD 0 IDE /dev/hda HDD 1 S-ATA /dev/sda HDD 2 S-ATA /dev/sdb 2) Even if in BIOS "RAID" as S-ATA option has been chosen during install procedure, the mirrored drives are listed separately. The logical array unit (not important which type) is not addressed as defined in the controller’s BIOS. 3)it is not important if the OS is installed onto S-ATA or ATA disks. Install procedure is able to write to both S-ATA and ATA hard disks. 4) Once in BIOS the “RAID” option switched back to IDE the OS is able to startup correctly. 5) The partition manager used with the installation routine is not able to change to another disk unit as the first one (at least didn't find any option). So there stays no possibility to modify any partition if you need so! - The only thing the user may change is the location where the OS is going to be installed but with fixed options as boot, maximized and ext3 partition. I suppose: for 1) this should be correct for 2) the install procedure chooses a non RAID driver and bypasses on this way the configuration in the controller's BIOS. for 3) same as for 2) for 4) same as for 2) for 5) used "GRUB" boot loader is not compatible with the VIA VT8732R RAID hardware OR the system needs an adapted driver for this configuration loaded. ***** What possibility do I have here, please? Thanks for your help in advance.

I suspect GRUB is having a problem with your setup. You might try various changes to the grub.conf as a workaround. See my own "Booting 5.0.1 from on Geode LX results in ". ..." and the recent "Problem booting 5.0.3 / 5.0.4 from Intel d201GLY" threads.