--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
We are closing this installation report for one of the following
reasons:
- it was reported with a pre-lenny version of Debian
Installer.
- indications in the installation report give the feeling that
the reported problem waslying in another software, unrelated to
D-I, which we can't easily identify.
- indications in the installation report suggest that it may have been
fixed in a more recent version of a D-I component
- it was successful and we forgot closing it..:-)
- it has no information we consider useful
The D-I team is currently in the process of cleaning out the old spool
of installation reports that haven't bene processed yet.
In case you think that the problem you reported has chances to be
still present, please reiterate your installation test with
a more recent image of D-I, if you're in position of doing this.
You'll find daily builds at
http://www.debian.org/devel/debian-installer. We recommend you choose
the netboot image, in the "daily builds section", then choose to
install "squeeze" when prompted.
If some problems are found, please report them with a new bug sent
against installation-reports.
Many thanks for your understanding and your help improving Debian,
past and present.
--- End Message ---