Bug#380049: debian-installer/etch bug report
I removed the second controller and nothing changes. Something is gimped up with debian on my system. I'll try another daily installer, but I might have to switch distros here. On 7/28/06, Frans Pop [EMAIL PROTECTED] wrote: On Friday 28 July 2006 19:06, Ryan Rawson wrote: no, the md doesn't exist at all. Only physical disks, using paths in /dev/discs. What I did is to use alt-f2 before I hit that portion of the rescue and tried to start the md array, which then failed with the device or resource busy error. Seems to me that your RAID setup is either to some extend broken or at least does not conform to what current code in Debian expects. Looks like rescue isn't really designed to rescue a root part on a md Then please explain the function of the code below that I've taken from the postinst of the rescue-mode udeb. snip # RAID support try_load_module md try_load_module raid0 try_load_module raid1 try_load_module raid5 log-output -t rescue mdrun || true # LVM support try_load_module dm-mod try_load_module lvm-mod log-output -t rescue pvscan || true log-output -t rescue vgscan || true /snip (We are currently switching from using mdrun to using mdadm as mdrun is being deprecated.) device - it doesn't seem to be trying to start the md device. I had to modprobe raid1 and mdrun by hand, but I still ended up with the busy error. The installer's rescue mode _does_ support RAID and also LVM over RAID. I have used it in my own installation tests. You mentioned in your initial mail that your system also has a second controller (hdf/hdg) that is not relevant. However, it may be relevant if the order in which the drivers for the controllers changes. Check console messages or dmesg to see in what order modules are being loaded. See the first item in the errata for the Etch Beta 2 release of the installer for further info [1]. [1] http://www.debian.org/devel/debian-installer/errata -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380049: debian-installer/etch bug report
On Thu, Jul 27, 2006 at 12:21:48PM -0700, Ryan Rawson wrote: Rescue mode doesn't work for me. When I try to start the md array I end up with the same device or resource busy error. Which device was detected/suggested by rescue? The md? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380049: debian-installer/etch bug report
no, the md doesn't exist at all. Only physical disks, using paths in /dev/discs. What I did is to use alt-f2 before I hit that portion of the rescue and tried to start the md array, which then failed with the device or resource busy error. Looks like rescue isn't really designed to rescue a root part on a md device - it doesn't seem to be trying to start the md device. I had to modprobe raid1 and mdrun by hand, but I still ended up with the busy error. On 7/28/06, Geert Stappers [EMAIL PROTECTED] wrote: On Thu, Jul 27, 2006 at 12:21:48PM -0700, Ryan Rawson wrote: Rescue mode doesn't work for me. When I try to start the md array I end up with the same device or resource busy error. Which device was detected/suggested by rescue? The md? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380049: debian-installer/etch bug report
On Friday 28 July 2006 19:06, Ryan Rawson wrote: no, the md doesn't exist at all. Only physical disks, using paths in /dev/discs. What I did is to use alt-f2 before I hit that portion of the rescue and tried to start the md array, which then failed with the device or resource busy error. Seems to me that your RAID setup is either to some extend broken or at least does not conform to what current code in Debian expects. Looks like rescue isn't really designed to rescue a root part on a md Then please explain the function of the code below that I've taken from the postinst of the rescue-mode udeb. snip # RAID support try_load_module md try_load_module raid0 try_load_module raid1 try_load_module raid5 log-output -t rescue mdrun || true # LVM support try_load_module dm-mod try_load_module lvm-mod log-output -t rescue pvscan || true log-output -t rescue vgscan || true /snip (We are currently switching from using mdrun to using mdadm as mdrun is being deprecated.) device - it doesn't seem to be trying to start the md device. I had to modprobe raid1 and mdrun by hand, but I still ended up with the busy error. The installer's rescue mode _does_ support RAID and also LVM over RAID. I have used it in my own installation tests. You mentioned in your initial mail that your system also has a second controller (hdf/hdg) that is not relevant. However, it may be relevant if the order in which the drivers for the controllers changes. Check console messages or dmesg to see in what order modules are being loaded. See the first item in the errata for the Etch Beta 2 release of the installer for further info [1]. [1] http://www.debian.org/devel/debian-installer/errata pgpek8C7riaFa.pgp Description: PGP signature
Bug#380049: debian-installer/etch bug report
In-Reply-To=[EMAIL PROTECTED] hello, 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. that is a known problem of the mdrun initramfs boot script. it got dropped for proper hook scripts, you need newer initramfs-tools 0.70 and mdadm from unstable. try to fetch those before reboot. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380049: debian-installer/etch bug report
Thanks for that. So I assume I would just get the debs to some machine on the network and scp them over right after the installation and perform a dpkg -i on that... or is there a different/easier strategy? -ryan On 7/27/06, maximilian attems [EMAIL PROTECTED] wrote: In-Reply-To=[EMAIL PROTECTED] hello, 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. that is a known problem of the mdrun initramfs boot script. it got dropped for proper hook scripts, you need newer initramfs-tools 0.70 and mdadm from unstable. try to fetch those before reboot. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380049: debian-installer/etch bug report
On Thursday 27 July 2006 20:18, Ryan Rawson wrote: So I assume I would just get the debs to some machine on the network and scp them over right after the installation and perform a dpkg -i on that... or is there a different/easier strategy? You don't need to reinstall. Just use the rescue mode of the installer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380049: debian-installer/etch bug report
Rescue mode doesn't work for me. When I try to start the md array I end up with the same device or resource busy error. Luckly the system is more or less scratch so reinstalling is not a big deal. -ryan On 7/27/06, Frans Pop [EMAIL PROTECTED] wrote: On Thursday 27 July 2006 20:18, Ryan Rawson wrote: So I assume I would just get the debs to some machine on the network and scp them over right after the installation and perform a dpkg -i on that... or is there a different/easier strategy? You don't need to reinstall. Just use the rescue mode of the installer. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
