Bug#320660: INSTALL REPORT
Frans Pop wrote: Would connecting the external drive to another box be an option? Just did that for some quick testing. Note however that my laptop doesn't have FireWire so I used the USB interface. Started up the standard install. It did create a /dev/cdroms/cdrom0 for the IDE cdrom and a /dev/cdroms/cdrom1 for the USB cdrom. If I remove the disk from the IDE cdrom it will just use the disk from the USB drive. So the installation system finds the second drive, it just doesn't ask you if you want to use it. When I have some more time I will check if this is true for the FireWire interface as well, but for this I'll have to open the case and reinsert the cdrom drive since I took it out. Hope this helps, Remko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320660: INSTALL REPORT
Package: installation-reports INSTALL REPORT Debian-installer-version: Made the first 5 CD's with Jigdo, http://cdimage.debian.org/pub/cdimage-testing/cd/jigdo-area/i386/ with ftp.nl.debian.org mirror and some old .deb's. uname -a: Linux twins 2.4.27-2-686-smp #1 SMP Mon May 16 16:55:31 JST 2005 i686 GNU/Linux Date: 2005-07-25 Method: Installed only the base system from 1st CD on hda1 and hdc1. Booted from ATAPI CD-rom. Used expert install because I wanted LILO. Then made the md's and the lv's manually and used apt to install the rest of the packages. Machine: Dual MSI 694D Pro @AIR Processor: 2x Pentium III 1 GHz Memory: 640MB Kingston Root Device: Western Digital WD1600JB-00GVA0, ATA UDMA/100 DISK drive Root Size/partition table: Disk /dev/hd[ac]: 160.0 GB, 160041885696 bytes 255 heads, 63 sectors/track, 19457 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 128 1028128+ 83 Linux /dev/hda2 129256219551105 fd Linux raid autodetect /dev/hda32563 1101067858560 fd Linux raid autodetect /dev/hda4 11011 1945767850527+ 83 Linux Disk /dev/hd[eg]: 20.0 GB, 20020396032 bytes 16 heads, 63 sectors/track, 38792 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System (Whole disks for RAID) # /etc/fstab: static file system information. # # file system mount point typeoptions proc /proc proc defaults /dev/hda1/ ext3 defaults,errors=remount-ro /dev/md0_vg/tmp_lv /tmpreiserfs defaults /dev/md0_vg/usr_lv /usrreiserfs defaults /dev/md0_vg/var_lv /varreiserfs defaults /dev/md0_vg/home_lv /home reiserfs defaults /dev/md1 /backup ext3 defaults #/dev/hdd/media/cdrom0 iso9660 ro,user,noauto /dev/scd0/media/cdrom0 iso9660 ro,user,noauto /dev/fd0 /media/floppy0 auto rw,user,noauto Output of /etc/mdadm/mdadm.conf: DEVICE partitions DEVICE /dev/hda2 /dev/hdc2 /dev/hde /dev/hdg DEVICE /dev/hda3 /dev/hdc3 ARRAY /dev/md0 level=raid0 num-devices=4 UUID=8d261ac1:896ece7a:01460e0b:5b447bd1 devices=/dev/hda2,/dev/hdc2,/dev/hde,/dev/hdg ARRAY /dev/md1 level=raid1 num-devices=2 UUID=e5ad67f3:810709aa:becf1202:98fa32d9 devices=/dev/hda3,/dev/hdc3 Output of lspci and lspci -n: :00:00.0 Host bridge: VIA Technologies, Inc. VT82C693A/694x [Apollo PRO133x] (rev c4) :00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP] :00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) :00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:07.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 16) :00:07.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 16) :00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) :00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50) :00:0c.0 RAID bus controller: Promise Technology, Inc. PDC20265 (FastTrak100 Lite/Ultra100) (rev 02) :00:0d.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link) :00:0e.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :00:0f.0 Multimedia video controller: Brooktree Corporation Bt848 Video Capture (rev 12) :00:11.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus Controller (rev 01) :01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1) :00:00.0 0600: 1106:0691 (rev c4) :00:01.0 0604: 1106:8598 :00:07.0 0601: 1106:0686 (rev 40) :00:07.1 0101: 1106:0571 (rev 06) :00:07.2 0c03: 1106:3038 (rev 16) :00:07.3 0c03: 1106:3038 (rev 16) :00:07.4 0600: 1106:3057 (rev 40) :00:07.5 0401: 1106:3058 (rev 50) :00:0c.0 0104: 105a:0d30 (rev 02) :00:0d.0 0c00: 104c:8020 :00:0e.0 0200: 10ec:8139 (rev 10) :00:0f.0 0400: 109e:0350 (rev 12) :00:11.0 0607: 104c:ac50 (rev 01) :01:00.0 0300: 10de:0110 (rev a1) 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: [ ] 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: I wanted quite a complicated setup wich I had read wasn't supported (and didn't expect it to be). Allthough both MD and LVM were
Bug#320660: INSTALL REPORT
retitle 320660 Problems using external firewire Plextor CD/DVD thanks On Sunday 31 July 2005 11:27, Remko Bolt wrote: I wanted quite a complicated setup wich I had read wasn't supported (and didn't expect it to be). Allthough both MD and LVM were supported but not LVM on MD. That _is_ supported and should not give any problems, especially with / (or /boot) on a separated partition. Even / and /boot on LVM over RAID will work although you may need to set up your bootloader manually. During CD detection my external firewire Plextor CD/DVD `DVDR PX-504A' was not found. Allthough with the 2.4 kernel it could be manually loaded with `echo scsi add-single-device 0 0 0 0 /proc/scsi/scsi' and with the 2.6 kernel it could be mounted straight away. The 2.6 kernel would freeze during use of the plextor. I'll leave the report open for this issue, although I don't expect we will be able to do much about it. It would be nice if you could research this further and provide additional information. Are you able to use the drive with 2.6 from the installed system? Any differences in loaded modules or settings in /proc? It looks like you used an older image that has 2.4.27 as default and 2.6.8 as alternative. Could you also try a daily netinst CD which has 2.6.11 (and in a few days 2.6.12) as default? Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320660: INSTALL REPORT
Frans Pop wrote: retitle 320660 Problems using external firewire Plextor CD/DVD thanks On Sunday 31 July 2005 11:27, Remko Bolt wrote: I wanted quite a complicated setup wich I had read wasn't supported (and didn't expect it to be). Allthough both MD and LVM were supported but not LVM on MD. That _is_ supported and should not give any problems, especially with / (or /boot) on a separated partition. Even / and /boot on LVM over RAID will work although you may need to set up your bootloader manually. I read http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=251905 and I didn't want to go through all that, especially because I'm not familiar with grub. Only tried it on the side, after I had the md's set up I couldn't get back to set up the lvm's. Take note however that I didn't use the latest and greatest installer. One thing that might be a (small) new bug, I just thought about, I noticed that I could only select partitions for use with md's, not whole disks, like I did with hd[eg] During CD detection my external firewire Plextor CD/DVD `DVDR PX-504A' was not found. Allthough with the 2.4 kernel it could be manually loaded with `echo scsi add-single-device 0 0 0 0 /proc/scsi/scsi' and with the 2.6 kernel it could be mounted straight away. The 2.6 kernel would freeze during use of the plextor. I'll leave the report open for this issue, although I don't expect we will be able to do much about it. The only thing that's relevant for the installation, to my humble opinion, is that with a 2.6 install, I would expect it to show up during the `probe for CD players', since I could mount it without any problems with `mount /dev/scd0 /mnt'. I wouldn't dare to blame the fact that the kernel freezes on the installer. I'll play with 2.6 and see if I can give any helpful feedback to the driver developers. It looks like you used an older image that has 2.4.27 as default and 2.6.8 as alternative. Could you also try a daily netinst CD which has 2.6.11 (and in a few days 2.6.12) as default? I'm pretty glad I have things up and running again, and not looking forward to any more downtime :-) sorry. Good to see people are really jumping this stuff, I love Debian! Cheers, Remko -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320660: INSTALL REPORT
reassign 320660 cdrom-detect thanks The only thing that's relevant for the installation, to my humble opinion, is that with a 2.6 install, I would expect it to show up during the `probe for CD players', since I could mount it without any problems with `mount /dev/scd0 /mnt'. I wouldn't dare to blame the fact that the kernel freezes on the installer. I'll play with 2.6 and see if I can give any helpful feedback to the driver developers. Can we support this? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#320660: INSTALL REPORT
On Sunday 31 July 2005 22:49, Remko Bolt wrote: The only thing that's relevant for the installation, to my humble opinion, is that with a 2.6 install, I would expect it to show up during the `probe for CD players', since I could mount it without any problems with `mount /dev/scd0 /mnt'. I wouldn't dare to blame the fact that the kernel freezes on the installer. I'll play with 2.6 and see if I can give any helpful feedback to the driver developers. I've looked a bit further at this and it looks like there are two reasons why you could not use the external drive. - The installer uses devfs and checks for CD drives by checking what is in /dev/cdroms. The kernel is responsible for creating symlinks in that directory to the real device (like /dev/ide/...) for cdrom devices. Is a link like that created for your external drive [1]. - If no cdrom drive is located, the installer will offer to load extra modules from floppy and/or ask for a device that should be mounted as cdrom. I think this does not happen in your case because, looking at your report, you _do_ have another CD drive at /dev/hdd; correct? The syslog from the installation may provide us some information about what happened. Could you send the /var/log/installer/syslog (gzipped!). I'm pretty glad I have things up and running again, and not looking forward to any more downtime :-) sorry. You would not have to complete the installation to provide additional information. As long as you stop before disk partitioning, the existing installation will be unaffected. So you would have only minor downtime: only the time it takes to boot the installer, do some testing, and reboot. In most cases less than 15 minutes. We can not solve problems or add new functionality if users are unwilling to provide additional information or test patches (we need someone who actually has the hardware). So, if that is the case, I'm going to close your installation report. Would connecting the external drive to another box be an option? Cheers, FJP [1] It is no use looking for this in the installed system as that does not use devfs. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
