Bug#308236: Debian Installer: After successful install system doesnt recognise /dev/ida devices
tags 308236 - patch thanks On Monday 09 May 2005 00:45, Patrick Donker wrote: I have installed from the 10 may 2005 daily build on a generic P3-866 system with a Compaq 3200 Disk Array controller. Everything went well, until the system booted into the newly installed Deb. While starting rcS.d it got to S30checkfs.sh. The check returned /dev/ida/c0d0p1 is not a valid block device. [...] I have renamed S40hotplug to S29hotplug and rebooted, to find that everything ran smoothly; the error as above didnt occur any longer. The better short term solution would be to add the module(s) needed for that drive in your /etc/modules instead of waiting for hotplug to load it. I think the real problem is that the initrd is supposed to load all modules needed to mount partitions used for your system. However, I may be wrong about that and in that case discover should take care of it. So the bug is either in initrd-tools or discover1-data. Could you please send us the output of 'lspci' and 'lspci -n' for your system so we may check if your controller is listed in discover's hardware database? Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308236: Debian Installer: After successful install system doesnt recognise /dev/ida devices
Frans Pop wrote: tags 308236 - patch thanks On Monday 09 May 2005 00:45, Patrick Donker wrote: I have installed from the 10 may 2005 daily build on a generic P3-866 system with a Compaq 3200 Disk Array controller. Everything went well, until the system booted into the newly installed Deb. While starting rcS.d it got to S30checkfs.sh. The check returned /dev/ida/c0d0p1 is not a valid block device. [...] I have renamed S40hotplug to S29hotplug and rebooted, to find that everything ran smoothly; the error as above didnt occur any longer. The better short term solution would be to add the module(s) needed for that drive in your /etc/modules instead of waiting for hotplug to load it. I think the real problem is that the initrd is supposed to load all modules needed to mount partitions used for your system. However, I may be wrong about that and in that case discover should take care of it. So the bug is either in initrd-tools or discover1-data. Could you please send us the output of 'lspci' and 'lspci -n' for your system so we may check if your controller is listed in discover's hardware database? Cheers, FJP Hi Joris, Herewith the lspci and lspci -n output you requested. There must have been a radical change in the installer between D-I rc2 and rc3 because I had this exact hardware installed and running using some daily rc2 build. Problem is that I cant remember which one. I moved the hardware to another casing that could hold more disks, so I did a reinstall. Now, using the build I filed the bug report against, I run into this problem. If you need more info, pls let me know. Cheers, Patrick lspci: :00:00.0 Host bridge: Intel Corp. 82815 815 Chipset Host Bridge and Memory Controller Hub (rev 02) :00:02.0 VGA compatible controller: Intel Corp. 82815 CGC [Chipset GraphicsController] (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev 11) :00:1f.0 ISA bridge: Intel Corp. 82801BA ISA Bridge (LPC) (rev 11) :00:1f.1 IDE interface: Intel Corp. 82801BA IDE U100 (rev 11) :00:1f.2 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #1) (rev 11) :00:1f.3 SMBus: Intel Corp. 82801BA/BAM SMBus (rev 11) :00:1f.4 USB Controller: Intel Corp. 82801BA/BAM USB (Hub #2) (rev 11) :01:08.0 Ethernet controller: Intel Corp. 82801BA/BAM/CA/CAM Ethernet Controller (rev 03) :01:0b.0 PCI bridge: IBM IBM27-82351 (rev 07) :02:00.0 Unknown mass storage controller: Compaq Computer Corporation Smart-2/P RAID Controller (rev 04) lspci -n: :00:00.0 0600: 8086:1130 (rev 02) :00:02.0 0300: 8086:1132 (rev 02) :00:1e.0 0604: 8086:244e (rev 11) :00:1f.0 0601: 8086:2440 (rev 11) :00:1f.1 0101: 8086:244b (rev 11) :00:1f.2 0c03: 8086:2442 (rev 11) :00:1f.3 0c05: 8086:2443 (rev 11) :00:1f.4 0c03: 8086:2444 (rev 11) :01:08.0 0200: 8086:2449 (rev 03) :01:0b.0 0604: 1014:0022 (rev 07) :02:00.0 0180: 0e11:ae10 (rev 04) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#308236: Debian Installer: After successful install system doesnt recognise /dev/ida devices
Package: Debian Installer Severity: important Tags: patch I have installed from the 10 may 2005 daily build on a generic P3-866 system with a Compaq 3200 Disk Array controller. Everything went well, until the system booted into the newly installed Deb. While starting rcS.d it got to S30checkfs.sh. The check returned /dev/ida/c0d0p1 is not a valid block device. After getting into the shell I noticed that if I ran /etc/rcS.d/S40hotplug, followed by mount -a, the devices mounted without problems. If I tried mount -a without first loading hotplug, the invalid block device error came up. I have renamed S40hotplug to S29hotplug and rebooted, to find that everything ran smoothly; the error as above didnt occur any longer. Maybe it is a good idea to place hotplug *before* checkfs, as it appears that some devices, such as the Compaq 3200 Disk Array, need to be detected before a fsck can be succesfully started. If there are any serious reasons of why hotplug is placed after checkfs, please let me know because I have planned to leave the rcS.d as it is right now. Thanks -Patrick -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
