Processed: Re: Bug#497110: boot loader installation failed when dmraid=true
Processing commands for [EMAIL PROTECTED]: > reassign 497110 partman-dmraid Bug#497110: boot loader installation failed when dmraid=true Bug reassigned from package `installation-reports' to `partman-dmraid'. > severity 497110 serious Bug#497110: boot loader installation failed when dmraid=true Severity set to `serious' from `normal' > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#497110: boot loader installation failed when dmraid=true
reassign 497110 partman-dmraid severity 497110 serious thanks On Saturday 30 August 2008, Giuseppe Iuculano wrote: > Comments/Problems: > I used a set of fakeraid qcow2 format disk images > (http://www.themuso.id.au/ubuntu/dmraid-empty-disks.tar.bz2), but boot > loader installation failed. > It seems that installer recognize /dev/mapper/* as an lvm volume, and > so disable grub installation. That should not happen. There is an exception for dmraid devices, which apparently no longer works. From the output you provide the reason seems to be that partitions are now created as p. The problem is the "p" between the device and the partition number which AFAICT did not use to be there before. This makes the "isinstallable" test fail for grub-instaoller. I would not be surprised if this would make other changes necessary too. First thing that needs to be determined is what exactly has changed to add this "p". Is it a change in dmraid, or in libparted, or elsewhere? When we know that we can check where changes are needed. Do you have any idea yourself where this "p" comes from? > lilo-installaer wants to install lilo in a bad partition, > /dev/mapper/sil_aiahbgbgaaajp1 , but the correct is > /dev/mapper/sil_aiahbgbgaaaj1 dmraid has never been tested with lilo, so this is not very surprising. I'm reassigning this issue to partman-dmraid as that is the most specific component for dmraid support, even though most needed changes will probably be in grub-installer. Cheers, FJP -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#497110: boot loader installation failed when dmraid=true
Frans Pop ha scritto: > First thing that needs to be determined is what exactly has changed to add > this "p". Is it a change in dmraid, or in libparted, or elsewhere? > When we know that we can check where changes are needed. > Do you have any idea yourself where this "p" comes from? I don't know where this "p" comes from, this is an ls -la after partitions (from network shell installer) # ls -la /dev/mapper drwxr-xr-x2 root root 140 Aug 30 11:05 . drwxr-xr-x 10 root root 2820 Aug 30 11:05 .. crw-rw1 root root 10, 60 Aug 30 11:01 control brw---1 root root 254, 0 Aug 30 11:06 sil_aiahbgbgaaaj brw---1 root root 254, 1 Aug 30 11:10 sil_aiahbgbgaaajp1 brw---1 root root 254, 2 Aug 30 11:05 sil_aiahbgbgaaajp2 brw---1 root root 254, 3 Aug 30 11:05 sil_aiahbgbgaaajp5 But in the next reboot , from network shell installer: ~ # ls -la /dev/mapper drwxr-xr-x2 root root 120 Aug 30 11:27 . drwxr-xr-x9 root root 2900 Aug 30 11:27 .. crw-rw1 root root 10, 60 Aug 30 11:27 control brw---1 root root 254, 0 Aug 30 11:27 sil_aiahbgbgaaaj brw---1 root root 254, 1 Aug 30 11:27 sil_aiahbgbgaaaj1 brw---1 root root 254, 2 Aug 30 11:27 sil_aiahbgbgaaaj5 Giuseppe Iuculano signature.asc Description: OpenPGP digital signature
Bug#497110: boot loader installation failed when dmraid=true
(No need to CC me on replies.) On Saturday 30 August 2008, Giuseppe Iuculano wrote: > Frans Pop ha scritto: > > First thing that needs to be determined is what exactly has changed > > to add this "p". Is it a change in dmraid, or in libparted, or > > elsewhere? When we know that we can check where changes are needed. > > Do you have any idea yourself where this "p" comes from? > > I don't know where this "p" comes from, Well, I assume that the "p" stands for "partition". It is a somewhat common separator. The question is why it is showing up suddenly now and what is responsible for adding it. > this is an ls -la after partitions (from network shell installer) [...] > But in the next reboot , from network shell installer: What exactly do you mean by "network shell installer"? That is not really a meaningfull term for us. If this is some Debian Installer image, then please specify exactly what image you were using (full URL of the image you downloaded is good). I guess the two boots were with the exact same version of the installer and the same boot options? If that is the case then something is really broken. Exactly at what point of the installation did you do the 'ls -la'? Was this before or after partitioning? The best point to do it would be after hardware (disk) detection, but before partitioning. Obviously we cannot really support something that is so unpredictable. From the info so far I would say that the problem is either in dmraid or maybe in the device-mapper (either user space or kernel). I suggest that you try to determine what causes the difference by saving and carefully comparing the output of dmesg, various dmraid commands, maybe info available in /proc/, the output of fdisk -l for the underlying real devices, etc. What is also suspicious is the missing partition 2, which I suspect is an extended partition. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#497168: grub-installer cant change grub settings
Package: grub-installer Version: 1.32 Severity: grave When I install Debian on computer with other operation system, and want to setup grub not on main boot section but only on Linux partition (hd0,4) to use bootmanager from other OS, If user mistakenly choose wrong partition (in my case it was (hd0,3) ) he will get error message, after it will be possible to go back to menu and try again steps, But it will be not possible to install grub at all (on right partition). I suggest that grub-installer should detect possible Linux partitions for installing and show them to user. Or at least show partition list on page where user must enter partition number. And the best if it will also allow to reset grub partition if its not possible to install to what user enter. I am using expert install from 28.08.2008 debian-testing-i386-netinst.iso in Graphic and Text modes, tried both grub and grub2. System was successfully installed only after reboot and new install with correct (hd0,4) settings. Ubuntu also have this problem. I can try again to re-install system if it will be needed for testing. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#496981: Case sensitive path name in windows based installer
On Fri, Aug 29, 2008 at 10:32:19PM +0200, Robert Millan wrote: > On Fri, Aug 29, 2008 at 12:39:56AM +0100, peter green wrote: > > [EMAIL PROTECTED] wrote: > > >I run the windows based installer but after reboot grub won't boot and > > >shown his prompt. > > > > > >After a little investigation I discovered grub was asked to look for image > > >files to load from a "debian" directory in the Windows disk but they were > > >in "Debian" directory instead. > > >This probably happened because there was already a "Debian" directory on > > >that disk created by me for some reasons in the past. The windows based > > >installer program then copied image files to that directory without being > > >aware it was already existing but was having a different case in his name. > > > > > >To solve the problem I booted into Windows then renamed the "Debian" > > >directory to "debian" using the Windows file manager, then I rebooted the > > >system the installation process started and completed successfully. > > > > > It seems like the proper way to fix this is to find out from windows > > what the file is actually called (including case) and use that > > information when writing the grub config. Maybe GetLongPathName will do > > what is required. > > Sounds fine, although I'd prefer if you can use NSIS for that, since accessing > win32 API from the script is quite ugly. Actually, it seems that GRUB is getting support for case insensitive namespaces in NTFS, so if files are not in the POSIX namespace they will be accessible via case insensitive match. This will be much simpler and require no changes in win32-loader. -- Robert Millan The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#406971: DEAR ACCOUNT OWNER
Dear Subscriber, Important Note - We have temporarily limited access to sensitive account features, to all arcor.de (webmail) Account Owners. We are currently upgrading our data base and e-mail account center. To restore your account access, please you must reply to this email immediately and enter your password here () and Check out your new features and enhancements with your new and improved arcor.de webmail account. To prevent your account from closing you will have to re-login to know it's status as a currently used account. Thank You! The arcor.de Team This message was sent using IMP, the Internet Messaging Program. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#497110: boot loader installation failed when dmraid=true
On Saturday 30 August 2008, Giuseppe Iuculano wrote: > after partitioning: > > ~ # ls -la /dev/mapper > drwxr-xr-x2 root root 140 Aug 30 13:17 . > drwxr-xr-x 10 root root 2820 Aug 30 13:17 .. > crw-rw1 root root 10, 60 Aug 30 13:11 control > brw---1 root root 254, 0 Aug 30 13:17 sil_aiahbgbgaaaj > brw---1 root root 254, 1 Aug 30 13:17 sil_aiahbgbgaaajp1 > brw---1 root root 254, 2 Aug 30 13:17 sil_aiahbgbgaaajp2 > brw---1 root root 254, 3 Aug 30 13:17 sil_aiahbgbgaaajp5 OK, so it is the partitioning step that is causing the problem. I suspect now that libparted is most likely to be the cause of the problem, especially as after a reboot existing partitions are by dmraid detected as you would expect (without the "p"). But another possibility is that you are just not following the correct procedure. Support for dmraid is far from perfect and things will *only* work if you follow the documented procedure. How did you do the partitioning? Did you *exactly* follow the instructions that are given in the "Partitioning" section of the SataRAID wiki page [1]? Did the partman screens look like the examples that are given there? Screenshots before and after doing the "Write changes in SATA RAID partitioning to disk" step would be nice too. Please send the /var/log/partman (gzipped!) after you do the partitioning. > I selected the first ext3 entry, below serial ata raid (mirror), I had an > out of memory: The out of memory should not happen, but selecting the "first" partition is *wrong*. It is not conform the procedure on the wiki page! > Installation terminated, in the next reboot grub started, but there is > an issue. Installer set root (sil_aiahbgbgaaaj). > > Replacing with root (hd0,0) fixes it. We can look at this later. Let's concentrate first on the partitioning problem. Cheers, FJP [1] http://wiki.debian.org/DebianInstaller/SataRaid -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Please unblock pango1.0/1.20.5-2
Josselin Mouette wrote: > Hi, > > please consider pango1.0/1.20.5-2 for lenny. There is only one > significant change, which was requested by Malayalam speakers: > >* 20_indic_rendering.patch: patch from upstream SVN. Fixes rendering > of Malayalam fonts. Closes: #493975. >* 60_link-pangoxft-to-fontconfig.patch: make the patch apply with -p1. Cc-ing debian-boot as it contains a udeb Cheers Luk -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Bug#497198: grub-pc: detects wrong partition for other OS (winXP)
Processing commands for [EMAIL PROTECTED]: > reassign 497198 grub-installer Bug#497198: grub-pc: detects wrong partition for other OS (winXP) Bug reassigned from package `grub-pc' to `grub-installer'. > forcemerge 473401 497198 Bug#473401: grub-installer: grub2 config for Windows partition does not boot Bug#497198: grub-pc: detects wrong partition for other OS (winXP) Bug#488294: grub-pc: defaults existing windows installation on first partition of first hd to (hd0, 0) Bug#492717: debian-installer: choosing grub2 created hd(0, 0) and not hd(0, 1) for windows chainload Forcibly Merged 473401 488294 492717 497198. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 497168 is normal
Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.35 > severity 497168 normal Bug#497168: grub-installer cant change grub settings Severity set to `normal' from `grave' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#497110: boot loader installation failed when dmraid=true
Frans Pop ha scritto: > But another possibility is that you are just not following the correct > procedure. Support for dmraid is far from perfect and things will *only* > work if you follow the documented procedure. > > How did you do the partitioning? Did you *exactly* follow the instructions > that are given in the "Partitioning" section of the SataRAID wiki page [1]? > > Did the partman screens look like the examples that are given there? > Screenshots before and after doing the "Write changes in SATA RAID > partitioning to disk" step would be nice too. > > Please send the /var/log/partman (gzipped!) after you do the partitioning. Ok, some other test. - First test Partition disk: http://sd6.iuculano.it/dmraid-testing/partman1-1.png Choose free space and create a new partition: http://sd6.iuculano.it/dmraid-testing/partman1-2.png http://sd6.iuculano.it/dmraid-testing/partman1-3.png Unfortunately I got an out of memory. You can find partman and sylog log here: http://sd6.iuculano.it/dmraid-testing/log1.tar.gz - Second test Partition disk: This time I choose "Automatically partition the free space", "all files in one partition" and I got: http://sd6.iuculano.it/dmraid-testing/partman2-1.png http://sd6.iuculano.it/dmraid-testing/partman2-2.png I selected "finish partitioning and write changes to disk and I got the bad device with "p", and no grub support. brw---1 root root 254, 0 Aug 30 18:14 sil_aiahbgbgaaaj brw---1 root root 254, 1 Aug 30 18:16 sil_aiahbgbgaaajp1 brw---1 root root 254, 2 Aug 30 18:14 sil_aiahbgbgaaajp2 brw---1 root root 254, 3 Aug 30 18:14 sil_aiahbgbgaaajp5 the second test log is here: http://sd6.iuculano.it/dmraid-testing/log2.tar.gz - Third test (as wiki procedure but with "Automatically partition the free space") As the second, but this time I selected "Write changes in SATA RAID partitioning to disk", and I got: http://sd6.iuculano.it/dmraid-testing/partman3-1.png # ls -la /dev/mapper drwxr-xr-x2 root root 180 Aug 30 18:50 . drwxr-xr-x 10 root root 2860 Aug 30 18:50 .. crw-rw1 root root 10, 60 Aug 30 18:42 control brw---1 root root 254, 0 Aug 30 18:43 sil_aiahbgbgaaaj brw---1 root root 254, 4 Aug 30 18:56 sil_aiahbgbgaaaj1 brw---1 root root 254, 5 Aug 30 18:56 sil_aiahbgbgaaaj5 brw---1 root root 254, 1 Aug 30 19:02 sil_aiahbgbgaaajp1 brw---1 root root 254, 2 Aug 30 19:02 sil_aiahbgbgaaajp2 brw---1 root root 254, 3 Aug 30 18:43 sil_aiahbgbgaaajp5 I selected partition #1 below sil_aiahbgbgaaaj1 (partion #1) and I set it for ext3 / : http://sd6.iuculano.it/dmraid-testing/partman3-2.png Now I selected sil_aiahbgbgaaaj5 (partition #5) and pressed enter: http://sd6.iuculano.it/dmraid-testing/partman3-3.png http://sd6.iuculano.it/dmraid-testing/partman3-4.png Now I got: http://sd6.iuculano.it/dmraid-testing/partman3-5.png I selected Free space and create a new partition, set it as swap area: http://sd6.iuculano.it/dmraid-testing/partman3-6.png Now I selected "finish partitioning and write changes to disk http://sd6.iuculano.it/dmraid-testing/partman3-7.png Installed base system: OK This time, I can install grub. Installation terminated successfully - Fourth test As the first, but I increased virtual machine memory to 512MB (In first test was 256MB). Same out of memory. In conclusion, If I try to follow wiki procedure I can't create new partition, but only "Automatically partition the free space", otherwise I got an out of memory Giuseppe. signature.asc Description: OpenPGP digital signature
Bug#497207: installation-report: successful installation report
Package: installation-reports Version: 2.35 Severity: minor -- Package-specific info: Boot method: CD Image version: debian-LennyBeta2-amd64-netinst.iso (downloaded Aug 29, 2008) Date: August 29th 2008 Machine: Dell PowerEdge T105 Partitions: FilesystemType 1K-blocks Used Available Use% Mounted on /dev/mapper/ocelot-root ext3 273674194683 64860 76% / tmpfstmpfs 514232 0514232 0% /lib/init/rw udev tmpfs 1024072 10168 1% /dev tmpfstmpfs 514232 0514232 0% /dev/shm /dev/sda1 ext3 241116 31725196943 14% /boot /dev/mapper/ocelot-home ext3 228474148207560 216660780 1% /home /dev/mapper/ocelot-tmp ext3 388741 10311358360 3% /tmp /dev/mapper/ocelot-usr ext3 4922684766036 3906588 17% /usr /dev/mapper/ocelot-var ext3 2955216246080 2559020 9% /var Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[)] Comments/Problems: Extremely smooth and fast overall. The only issue I encountered was that it wasn't clear to me how to partition the second disk after the partition table for the first was written. I had to choose one disk or the other to partition and when I accepted the installer's suggestions, all of the mountpoints that I wanted were taken care of. Since I was using LVM, though, I decided just to leave the matter to fix later, if I really wanted to. A really good experience all in all. Thanks for all of your work. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to [EMAIL PROTECTED] == Installer lsb-release: == DISTRIB_ID=Debian DISTRIB_DESCRIPTION="Debian GNU/Linux installer" DISTRIB_RELEASE="5.0 (lenny) - installer build 20080522" X_INSTALLATION_MEDIUM=cdrom == Installer hardware-summary: == umame -a: Linux ocelot 2.6.24-1-amd64 #1 SMP Sat May 10 09:28:10 UTC 2008 x86_64 unknown lspci -knn: 00:00.0 Memory controller [0580]: nVidia Corporation CK804 Memory Controller [10de:005e] (rev a4) lspci -knn: 00:01.0 ISA bridge [0601]: nVidia Corporation CK804 ISA Bridge [10de:0051] (rev f1) lspci -knn: 00:01.1 SMBus [0c05]: nVidia Corporation CK804 SMBus [10de:0052] (rev a2) lspci -knn: 00:02.0 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005a] (rev a2) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: Kernel modules: ohci-hcd lspci -knn: 00:02.1 USB Controller [0c03]: nVidia Corporation CK804 USB Controller [10de:005b] (rev a4) lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:07.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0054] (rev f3) lspci -knn: Kernel driver in use: sata_nv lspci -knn: Kernel modules: sata_nv, generic lspci -knn: 00:08.0 IDE interface [0101]: nVidia Corporation CK804 Serial ATA Controller [10de:0055] (rev f3) lspci -knn: Kernel driver in use: sata_nv lspci -knn: Kernel modules: sata_nv, generic lspci -knn: 00:09.0 PCI bridge [0604]: nVidia Corporation CK804 PCI Bridge [10de:005c] (rev f2) lspci -knn: 00:0b.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev f3) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:0c.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev f3) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:0d.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev f3) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:0e.0 PCI bridge [0604]: nVidia Corporation CK804 PCIE Bridge [10de:005d] (rev a3) lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] HyperTransport Technology Configuration [1022:1100] lspci -knn: 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] Address Map [1022:1101] lspci -knn: 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opteron] DRAM Controller [1022:1102] lspci -knn: 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] K8 [Athlon64/Opt
Bug#497212: installation-reports: booting the lenny installer via pxe leeds to a black screen
Package: installation-reports Severity: important Tags: patch It seems that debian-installer/i386/pxelinux.cfg/default is broken. If I replace it with the etch version the installer boots and leads to a normal installation. -- Package-specific info: Boot method: network Image version: http://http.us.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/netboot.tar.gz 2008/08/30 (timestamp of file: 2008/05/22) Date: Machine: celeron 220 Partitions: Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [ ] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Booting the lenny installer via pxe leads to a black screen. -- Please make sure that the hardware-summary log file, and any other installation logs that you think would be useful are attached to this report. Please compress large files using gzip. Once you have filled out this report, mail it to [EMAIL PROTECTED] This is the same hardware, but an other installation... == Installer hardware-summary: == umame -a: Linux vm-host 2.6.25-2-486 #1 Fri Jul 18 17:03:35 UTC 2008 i686 unknown lspci -knn: 00:00.0 Host bridge [0600]: Silicon Integrated Systems [SiS] 662 Host [1039:0662] (rev 01) lspci -knn: 00:01.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] SiS AGP Port (virtual PCI-to-PCI bridge) [1039:0003] lspci -knn: 00:02.0 ISA bridge [0601]: Silicon Integrated Systems [SiS] SiS964 [MuTIOL Media IO] [1039:0964] (rev 36) lspci -knn: 00:02.5 IDE interface [0101]: Silicon Integrated Systems [SiS] 5513 [IDE] [1039:5513] (rev 01) lspci -knn: Kernel driver in use: SIS_IDE lspci -knn: Kernel modules: sis5513, pata_sis lspci -knn: 00:02.7 Multimedia audio controller [0401]: Silicon Integrated Systems [SiS] AC'97 Sound Controller [1039:7012] (rev a0) lspci -knn: 00:03.0 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: Kernel modules: ohci-hcd lspci -knn: 00:03.1 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: Kernel modules: ohci-hcd lspci -knn: 00:03.2 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 1.1 Controller [1039:7001] (rev 0f) lspci -knn: Kernel driver in use: ohci_hcd lspci -knn: Kernel modules: ohci-hcd lspci -knn: 00:03.3 USB Controller [0c03]: Silicon Integrated Systems [SiS] USB 2.0 Controller [1039:7002] lspci -knn: Kernel driver in use: ehci_hcd lspci -knn: Kernel modules: ehci-hcd lspci -knn: 00:04.0 Ethernet controller [0200]: Silicon Integrated Systems [SiS] SiS900 PCI Fast Ethernet [1039:0900] (rev 91) lspci -knn: Kernel driver in use: sis900 lspci -knn: Kernel modules: sis900 lspci -knn: 00:05.0 IDE interface [0101]: Silicon Integrated Systems [SiS] SATA [1039:0181] (rev 01) lspci -knn: Kernel driver in use: sata_sis lspci -knn: Kernel modules: sata_sis lspci -knn: 00:1f.0 PCI bridge [0604]: Silicon Integrated Systems [SiS] PCI-to-PCI bridge [1039:0004] lspci -knn: Kernel driver in use: pcieport-driver lspci -knn: 01:00.0 VGA compatible controller [0300]: Silicon Integrated Systems [SiS] 661/741/760 PCI/AGP or 662/761Gx PCIE VGA Display Adapter [1039:6330] (rev 04) lsmod: Module Size Used by lsmod: ufs69764 0 lsmod: qnx4 10628 0 lsmod: ntfs 189760 0 lsmod: dm_mod 54500 5 lsmod: md_mod 72724 0 lsmod: xfs 462836 0 lsmod: reiserfs 199936 0 lsmod: jfs 159452 0 lsmod: ext3 117640 2 lsmod: jbd38932 1 ext3 lsmod: vfat 11648 0 lsmod: fat45852 1 vfat lsmod: ext2 62216 0 lsmod: mbcache 7680 2 ext3,ext2 lsmod: sata_sis8580 0 lsmod: pata_sis 13700 1 sata_sis lsmod: libata142352 2 sata_sis,pata_sis lsmod: dock 10124 1 libata lsmod: sis900 20736 0 lsmod: mii 5248 1 sis900 lsmod: nls_utf82048 0 lsmod: isofs 31908 0 lsmod: nls_base6784 6 ntfs,jfs,vfat,fat,nls_utf8,isofs lsmod: zlib_inflate 14208 1 isofs lsmod: rsrc_nonstatic 11520 0 lsmod: pcmcia_core36112 1 rsrc_nonstatic lsmod: ide_generic
Bug#497223: Package: installation-reports
Package: installation-reports Boot method: CDROM Image version: http://cdimage.debian.org/cdimage/daily-builds/daily/20080829-2/amd64/iso-cd/debian-testing-amd64-netinst.iso Date: Sat Aug 30 15:50:43 2008 Eastern Daylight Time Machine: Intel DX38BT Processor: Intel Q6600 2.4 GHz Memory: DDR3 6 GB Partitions: $ sudo fdisk -l Disk /dev/sda: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0002e972 Device Boot Start End Blocks Id System /dev/sda1 * 1 36 289138+ fd Linux raid autodetect /dev/sda2 371009 7815622+ fd Linux raid autodetect /dev/sda31010 60801 480279240 fd Linux raid autodetect Disk /dev/sdb: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000d8d2c Device Boot Start End Blocks Id System /dev/sdb1 * 1 36 289138+ fd Linux raid autodetect /dev/sdb2 371009 7815622+ fd Linux raid autodetect /dev/sdb31010 60801 480279240 fd Linux raid autodetect Disk /dev/sdc: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x0002f6f7 Device Boot Start End Blocks Id System /dev/sdc1 * 1 36 289138+ fd Linux raid autodetect /dev/sdc2 371009 7815622+ fd Linux raid autodetect /dev/sdc31010 60801 480279240 fd Linux raid autodetect Disk /dev/sdd: 500.1 GB, 500107862016 bytes 255 heads, 63 sectors/track, 60801 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x000680c9 Device Boot Start End Blocks Id System /dev/sdd1 * 1 36 289138+ fd Linux raid autodetect /dev/sdd2 371009 7815622+ fd Linux raid autodetect /dev/sdd31010 60801 480279240 fd Linux raid autodetect Disk /dev/md0: 295 MB, 295960576 bytes 2 heads, 4 sectors/track, 72256 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x Disk /dev/md0 doesn't contain a valid partition table Disk /dev/md1: 16.0 GB, 16006250496 bytes 2 heads, 4 sectors/track, 3907776 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x Disk /dev/md1 doesn't contain a valid partition table Disk /dev/md2: 983.6 GB, 983611736064 bytes 2 heads, 4 sectors/track, 240139584 cylinders Units = cylinders of 8 * 512 = 4096 bytes Disk identifier: 0x Disk /dev/md2 doesn't contain a valid partition table == $ df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/md2 ext3 945485428 4253508 893204004 1% / tmpfstmpfs 3063624 0 3063624 0% /lib/init/rw udev tmpfs 10240 140 10100 2% /dev tmpfstmpfs 3063624 0 3063624 0% /dev/shm /dev/md0 ext3 279891 27381238059 11% /boot $ sudo mdadm --detail /dev/md0 /dev/md0: Version : 00.90 Creation Time : Sat Aug 30 15:50:43 2008 Raid Level : raid1 Array Size : 289024 (282.30 MiB 295.96 MB) Used Dev Size : 289024 (282.30 MiB 295.96 MB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 0 Persistence : Superblock is persistent Update Time : Sat Aug 30 19:33:13 2008 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 UUID : c19445a9:303f164a:396882e2:50829acb Events : 0.6 Number Major Minor RaidDevice State 0 810 active sync /dev/sda1 1 8 171 active sync /dev/sdb1 2 8 332 active sync /dev/sdc1 3 8 493 active sync /dev/sdd1 $ sudo mdadm --detail /dev/md1 /dev/md1: Version : 00.90 Creation Time : Sat Aug 30 15:51:19 2008 Raid Level : raid10 Array Size : 15631104 (14.91 GiB 16.01 GB) Used Dev Size : 7815552 (7.45 GiB 8.00 GB) Raid Devices : 4 Total Devices : 4 Preferred Minor : 1 Persistence : Superblock is persistent Update Time : Sat Aug 30 19:33:33 2008 State : clean Active Devices : 4 Working Devices : 4 Failed Devices : 0 Spare Devices : 0 Layout : near=2, far=1 Chunk Size : 64K UUID : ce605113:eb5a8a7e:7f9e8100:e6679ef7 Events : 0.4 Number Major Minor RaidDevice State 0 820 active sync /dev/sda2 1 8 181 active sync /dev/sdb2 2 8 342 active sync /dev/sdc2 3
