Bug#325149: installation-reports
On Fri, Aug 26, 2005 at 07:19:13AM -0500, Renato Alarcon wrote:
> Package: installation-reports
>
> Debian-installer-version:
> http://cdimage.debian.org/pub/cdimage-testing/daily/i386/20050825/debian-testing-i386-netinst.iso
> uname -a: unavailable
> Date: 05/26/2005
> Method: netinst CD image
>
> Machine: SUPERMICRO P8SAA mobo
> Processor: P4 3.0 MHZ
> Memory: 1GB
> Root Device: SATA DRIVES BOTH IN RAID AND NON RAID MODE
> Root Size/partition table: 160GB , 1GB swap
> Output of lspci and lspci -n:
>
> Base System Installation Checklist:
> [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
>
> Initial boot worked: [O ]
> Configure network HW: [O ]
> Config network: [O ]
> Detect CD: [O ]
> Load installer modules: [O ]
> Detect hard drives: [O ]
> Partition hard drives: [O ]
> Create file systems: [O ]
> Mount partitions: [O ]
> Install base system: [O ]
> Install boot loader: [O ]
> Reboot: [E ]
>
> Comments/Problems:
>
> ok, this one got me.
>
> I tried the following:
>
> installed cdimage-testing under the following conditions:
>
> -. SATA HD configured as PATA: initial installation succeeds, computer
> restarts and continues with netinst part of install. Once system is
> installed, I switch disks to SATA mode, no RAID. System won't boot. I
> get GRUB to start linux, detects devices but kernel panics due to
> dev/console not found???? If I change it back to PATA, it boots. Same
> thing happens if I try with the stable installer with linux26, initial &
> post succeed as long as I stay in PATA. In brief, It does detect my
> drives in SATA mode, but kernel panics.
>
> -. SATA HD configured as SATA no raid: initial installation succeeds, at
> restart no boot partitions are detected, won't even get LILO/GRUB
> prompts (I tried both loaders). It feels like boot loader didn't get
> installed properly in MBR
>
> -. SATA HD configured as SATA raid 1: initial installation succeeds, at
> restart no boot partitions are detected, won't even get LILO/GRUB
> prompts (I tried both loaders). It feels like boot loader didn't get
> installed properly in MBR
Switching to true sata mode almost always uses scsi interface in current
linux kernels, while pata uses the old ide interface. Hence the kernel
panics because it can't find the disk anymore (the name changed).
If you set it to true sata mode (enhanced or native or whatever the bios
calls it), do a 2.6 install, it should kxajust detect the disks as scsi
devices and work. At least it has on all my sata machines. The pata
emulation never did anything but cause trouble.
If you switch the grub boot line from /dev/hda1 to /dev/sda1 (substitute
your actualy pata device name) and then see if it boots further. It
should. It should also work great that way in the installer using
linux26.
Len Sorensen
Reply to: