Bug#380049: debian-installer/etch bug report
Package: installation-reports
Boot method: netinst iso, cdrom boot
Image version: etch beta2 & daily July 26, 2006
Date: July 26th evening.
Machine: AMD CPU, NForce2 mobo Chipset.
Processor: AMD Athlon XP 2500+
Memory: 512 MB
Partitions:
this is typed in by hand since I can't boot the system:
hda, hdc both 120 GB disks:
hda1: 50 MB ext3 mounted to /boot
hda2: 650 MB swap
hda5: (rest) raid autodetect
hdc1: 700 swap
hdc5: (test) raid autodetect
hdf/hdg: exists but dont take part of the installation in any way.
Output of lspci and lspci -n:
(missing)
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: [ O]
Comments/Problems:
The machine is set to install on /dev/md0 raid1. The installer worked
like a charm, and on reboot into the live system I end up with major
failure, the scripts try to start the raid system with mdrun but I end
up with the error;
"mdadm: cannon open device /dev/hda5: Device or resource busy"
When I attempt to mount /dev/hda1 I end up with the same error.
An installation using guided partition onto hda only succeeds, and the
system boots up fine.
The hardware I have installed is:
- PVR-250 capture card
- Ethernet card
- GForce2 MX
- PATA IDE interface providing hdf/hdg
I was going to try installs without various cards, but considering the
base install works fine, it didn't look like a hardware
conflict/issue.
If you _need_ any of the above, I'll see what I can do, generally
rescue doesnt work for me because it doesnt seem to detect the raid1
and offer that as a 'root' option.
Reply to: