Bug#1035096: installation-report Bookworm RC2 GRUB not installed
On May 4, 2023 3:35:40 PM Pascal Hambourg wrote:
On 04/05/2023 at 16:21, Peter Ehlert wrote:
"Install the GRUB boot loader" menu ... 6 items
Enter device manually
/dev/sda (usb-SanDisk ...
/dev/sdb (ata-WL4000G ...
/dev/sdc (ata-WDC_WD300...
/dev/sdd (ata-WDC_WD300...
/dev/sde (ata-SanDisk_SDSSDA240G_162248447811)
I selected /dev/sde and pressed the Continue button
then the GUI progress bar Installing GRUB and I see Running
"grub-install /dev/sdd" ...
in this case sdd was the install location, sde is the drive that has a
bios_grub flagged partition
OK, I think I managed to reproduce the issue and it shares the root
cause with another bug I am currently chasing (GRUB is not installed at
all). Some logic in grub-installer seems to be flawed but I still need
to understand the original intent before I can submit a patch for both bugs.
Meanwhile, a workaround is to enter the boot device manually.
Thanks. Best of luck. I appreciate your assistance
setting up BIOS to boot from a drive that does not have a bios_grub
flagged partition results in:
"GPT-formatted disk.
Legacy boot not supported. Press any key to reboot."
If this is a message from the BIOS, then it is flawed. A compliant
BIOS should not care about the partition table, even less the presence
of any kind of partition. All a BIOS should care about is the presence
of the "boot signature" 0x55, 0xAA at the end of the boot sector.
Yes, that is from the BIOS
(...)
root@z820-3:~# grub-install /dev/sda && update-grub
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot
Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for
cross-disk install.
This failure has nothing to do with the above. You are trying to install
GRUB on a GPT disk which is not the one containing /boot ("cross-disk"),
and this requires a BIOS boot partition.
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
On 04/05/2023 at 16:21, Peter Ehlert wrote:
"Install the GRUB boot loader" menu ... 6 items
Enter device manually
/dev/sda (usb-SanDisk ...
/dev/sdb (ata-WL4000G ...
/dev/sdc (ata-WDC_WD300...
/dev/sdd (ata-WDC_WD300...
/dev/sde (ata-SanDisk_SDSSDA240G_162248447811)
I selected /dev/sde and pressed the Continue button
then the GUI progress bar Installing GRUB and I see Running
"grub-install /dev/sdd" ...
in this case sdd was the install location, sde is the drive that has a
bios_grub flagged partition
OK, I think I managed to reproduce the issue and it shares the root
cause with another bug I am currently chasing (GRUB is not installed at
all). Some logic in grub-installer seems to be flawed but I still need
to understand the original intent before I can submit a patch for both bugs.
Meanwhile, a workaround is to enter the boot device manually.
setting up BIOS to boot from a drive that does not have a bios_grub
flagged partition results in:
"GPT-formatted disk.
Legacy boot not supported. Press any key to reboot."
If this is a message from the BIOS, then it is flawed. A compliant
BIOS should not care about the partition table, even less the presence
of any kind of partition. All a BIOS should care about is the presence
of the "boot signature" 0x55, 0xAA at the end of the boot sector.
Yes, that is from the BIOS
(...)
root@z820-3:~# grub-install /dev/sda && update-grub
Installing for i386-pc platform.
grub-install: warning: this GPT partition label contains no BIOS Boot
Partition; embedding won't be possible.
grub-install: error: embedding is not possible, but this is required for
cross-disk install.
This failure has nothing to do with the above. You are trying to install
GRUB on a GPT disk which is not the one containing /boot ("cross-disk"),
and this requires a BIOS boot partition.
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
On 5/2/23 11:59, Pascal Hambourg wrote: On 02/05/2023 at 15:21, Peter Ehlert wrote: DI asks on which drive to install GRUB User says disk X DI attempts to install on Drive Y result ... GRUB does not get installed at all This is completely different from what I understood. The statement "GRUB does not get installed at all" is refuted by /var/log/syslog which indicates clearly that GRUB was successfully installed on /dev/sdb: Apr 28 23:55:51 grub-installer: info: Running chroot /target grub-install --force "/dev/sdb" (...) Apr 28 23:56:01 grub-installer: Installation finished. No error reported. Can you described what happened exactly ? Were you prompted to "Install the GRUB boot loader to your primary drive?" ? If yes, did you answer "yes" or "no" ? Where you then prompted to select the "Device for boot loader installation" ? If yes, what option did you select exactly ? from my initial installation-report: "when install was finished, a list of drives was displayed, asking where to install GRUB. the install drive was highlighted I selected the drive with bios_grub the display showed "installing GRUB on (...drive it was installed on...)" Pardon me for not being more clear. I will elaborate from the photos I took "Install the GRUB boot loader" menu ... 6 items Enter device manually /dev/sda (usb-SanDisk ... /dev/sdb (ata-WL4000G ... /dev/sdc (ata-WDC_WD300... /dev/sdd (ata-WDC_WD300... /dev/sde (ata-SanDisk_SDSSDA240G_162248447811) I selected /dev/sde and pressed the Continue button then the GUI progress bar Installing GRUB and I see Running "grub-install /dev/sdd" ... in this case sdd was the install location, sde is the drive that has a bios_grub flagged partition setting up BIOS to boot from a drive that does not have a bios_grub flagged partition results in: "GPT-formatted disk. Legacy boot not supported. Press any key to reboot." If this is a message from the BIOS, then it is flawed. A compliant BIOS should not care about the partition table, even less the presence of any kind of partition. All a BIOS should care about is the presence of the "boot signature" 0x55, 0xAA at the end of the boot sector. Yes, that is from the BIOS running Debian, from the terminal: peter@z820-3:~$ su - Password: root@z820-3:~# grub-install /dev/sda && update-grub Installing for i386-pc platform. grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. grub-install: error: embedding is not possible, but this is required for cross-disk install. root@z820-3:~#
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
On 02/05/2023 at 15:21, Peter Ehlert wrote: DI asks on which drive to install GRUB User says disk X DI attempts to install on Drive Y result ... GRUB does not get installed at all This is completely different from what I understood. The statement "GRUB does not get installed at all" is refuted by /var/log/syslog which indicates clearly that GRUB was successfully installed on /dev/sdb: Apr 28 23:55:51 grub-installer: info: Running chroot /target grub-install --force "/dev/sdb" (...) Apr 28 23:56:01 grub-installer: Installation finished. No error reported. Can you described what happened exactly ? Were you prompted to "Install the GRUB boot loader to your primary drive?" ? If yes, did you answer "yes" or "no" ? Where you then prompted to select the "Device for boot loader installation" ? If yes, what option did you select exactly ? setting up BIOS to boot from a drive that does not have a bios_grub flagged partition results in: "GPT-formatted disk. Legacy boot not supported. Press any key to reboot." If this is a message from the BIOS, then it is flawed. A compliant BIOS should not care about the partition table, even less the presence of any kind of partition. All a BIOS should care about is the presence of the "boot signature" 0x55, 0xAA at the end of the boot sector.
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
On 4/30/23 01:17, Pascal Hambourg wrote: On 30/04/2023 at 01:47, Peter Ehlert wrote: On 4/29/23 15:41, Pascal Hambourg wrote: On 29/04/2023 at 16:02, Peter Ehlert wrote: reboot gave me the Old GRUB menu, not including my new system. What do you mean by "old GRUB menu" ? The GRUB which was previously installed on /dev/sdb ? the GRUB that was on the only disk with a bios_grub flagged partition. Thank you for the clarification. If I understand correctly, - the machine usually boots with some GRUB on disk X, - you installed a new Debian system with GRUB on disk Y, - then the machine rebooted on disk X as usual. Correct: to reiterate the problem... DI asks on which drive to install GRUB User says disk X DI attempts to install on Drive Y result ... GRUB does not get installed at all The Debian installer will not add the newly installed system to another existing OS GRUB menu; it will only add other existing OS's to the new installed system GRUB menu, which will be displayed only if the machine boots from the disk containing the new GRUB. So what you describe is normal behaviour. "normal"? except I am not asking for the existing GRUB menu on drive X to be appended. the request is Install GRUB on drive X If you want to add the newly installed system to another OS GRUB menu, you need to run update-grub from that other OS. If you want to boot with the new installed GRUB, you need to set up the BIOS to boot from the disk which contains it. setting up BIOS to boot from a drive that does not have a bios_grub flagged partition results in: "GPT-formatted disk. Legacy boot not supported. Press any key to reboot."
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
On 30/04/2023 at 01:47, Peter Ehlert wrote: On 4/29/23 15:41, Pascal Hambourg wrote: On 29/04/2023 at 16:02, Peter Ehlert wrote: reboot gave me the Old GRUB menu, not including my new system. What do you mean by "old GRUB menu" ? The GRUB which was previously installed on /dev/sdb ? the GRUB that was on the only disk with a bios_grub flagged partition. Thank you for the clarification. If I understand correctly, - the machine usually boots with some GRUB on disk X, - you installed a new Debian system with GRUB on disk Y, - then the machine rebooted on disk X as usual. The Debian installer will not add the newly installed system to another existing OS GRUB menu; it will only add other existing OS's to the new installed system GRUB menu, which will be displayed only if the machine boots from the disk containing the new GRUB. So what you describe is normal behaviour. If you want to add the newly installed system to another OS GRUB menu, you need to run update-grub from that other OS. If you want to boot with the new installed GRUB, you need to set up the BIOS to boot from the disk which contains it.
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
On 4/29/23 15:41, Pascal Hambourg wrote: Hello Peter, On 29/04/2023 at 16:02, Peter Ehlert wrote: Legacy aka BIOS booting system has 4 physical disk drives, all GPT partition tables only one drive has a partition with bios_grub install was on a drive without bios_grub when install was finished, a list of drives was displayed, asking where to install GRUB. the install drive was highlighted I selected the drive with bios_grub the display showed "installing GRUB on (...drive it was installed on...) According to /var/log/syslog, GRUB was successfully installed on /dev/sdb although this drive has no BIOS boot partition: Apr 28 23:55:51 grub-installer: info: Installing grub on '/dev/sdb' Apr 28 23:55:51 grub-installer: info: grub-install does not support --no-floppy Apr 28 23:55:51 grub-installer: info: Running chroot /target grub-install --force "/dev/sdb" Apr 28 23:55:51 grub-installer: Installing for i386-pc platform. Apr 28 23:56:01 grub-installer: grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. Apr 28 23:56:01 grub-installer: grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. Apr 28 23:56:01 grub-installer: Installation finished. No error reported. Apr 28 23:56:01 grub-installer: info: grub-install ran successfully (several other OS's are on that drive if that matters) reboot gave me the Old GRUB menu, not including my new system. What do you mean by "old GRUB menu" ? The GRUB which was previously installed on /dev/sdb ? the GRUB that was on the only disk with a bios_grub flagged partition. That does not seem possible according to the above logs. Are you sure that the machine rebooted from this disk ? apparently so. I know of none other. GRUB menu showed all of the other systems as before the install. (note that /dev/sd* naming is not stable across reboots and does not match BIOS disk numbering/naming) I am aware of that boot from another OS: # grub-install /dev/sde && update-grub now my GRUB menu includes the new system In chroot or directly from the other OS ? directly from the other OS (also Bookworm), my default Running grub-install directly from another OS just installed that other OS's GRUB on /dev/sde and running update-grub directly just added the new Debian installation to that other OS's boot menu if os-prober is enabled. yes, I enabled os-prober
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
Hello Peter, On 29/04/2023 at 16:02, Peter Ehlert wrote: Legacy aka BIOS booting system has 4 physical disk drives, all GPT partition tables only one drive has a partition with bios_grub install was on a drive without bios_grub when install was finished, a list of drives was displayed, asking where to install GRUB. the install drive was highlighted I selected the drive with bios_grub the display showed "installing GRUB on (...drive it was installed on...) According to /var/log/syslog, GRUB was successfully installed on /dev/sdb although this drive has no BIOS boot partition: Apr 28 23:55:51 grub-installer: info: Installing grub on '/dev/sdb' Apr 28 23:55:51 grub-installer: info: grub-install does not support --no-floppy Apr 28 23:55:51 grub-installer: info: Running chroot /target grub-install --force "/dev/sdb" Apr 28 23:55:51 grub-installer: Installing for i386-pc platform. Apr 28 23:56:01 grub-installer: grub-install: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. Apr 28 23:56:01 grub-installer: grub-install: warning: Embedding is not possible. GRUB can only be installed in this setup by using blocklists. However, blocklists are UNRELIABLE and their use is discouraged.. Apr 28 23:56:01 grub-installer: Installation finished. No error reported. Apr 28 23:56:01 grub-installer: info: grub-install ran successfully (several other OS's are on that drive if that matters) reboot gave me the Old GRUB menu, not including my new system. What do you mean by "old GRUB menu" ? The GRUB which was previously installed on /dev/sdb ? That does not seem possible according to the above logs. Are you sure that the machine rebooted from this disk ? (note that /dev/sd* naming is not stable across reboots and does not match BIOS disk numbering/naming) boot from another OS: # grub-install /dev/sde && update-grub now my GRUB menu includes the new system In chroot or directly from the other OS ? Running grub-install directly from another OS just installed that other OS's GRUB on /dev/sde and running update-grub directly just added the new Debian installation to that other OS's boot menu if os-prober is enabled.
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
On 4/29/23 09:21, Steve McIntyre wrote: On Sat, Apr 29, 2023 at 08:51:48AM -0700, Peter Ehlert wrote: On 4/29/23 07:23, Steve McIntyre wrote: Hi Peter, Could you please share a copy of the installer logs? You should be able to find them in /var/log/installer on the installed system. there is no file "installer" in /var/log Right, it's a directory with multiple files in it. Could you also Mr. McIntyre: I sent several email Huge responses to the list. I copied the contents of all of the files... were they received? if not I can repeat or find a pastebin service of some sort. Thanks, Peter share the other files please? I found /var/log/installer/syslog Thanks...
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
On Sat, Apr 29, 2023 at 08:51:48AM -0700, Peter Ehlert wrote: > >On 4/29/23 07:23, Steve McIntyre wrote: >> Hi Peter, >> >> Could you please share a copy of the installer logs? You should be >> able to find them in /var/log/installer on the installed system. >there is no file "installer" in /var/log Right, it's a directory with multiple files in it. Could you also share the other files please? >I found /var/log/installer/syslog Thanks... -- Steve McIntyre, Cambridge, UK.st...@einval.com "Because heaters aren't purple!" -- Catherine Pitt
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
Hi Peter, Could you please share a copy of the installer logs? You should be able to find them in /var/log/installer on the installed system. On Sat, Apr 29, 2023 at 07:02:43AM -0700, Peter Ehlert wrote: >Package: grub-installer >Boot method: USB >Image version: debian-bookworm-DI-rc2-amd64-netinst.iso >download from Debian >Date: 2023-04-28 ~17 > >Machine: HP Z820 Workstation >Processor: 2x 8-core model: Intel Xeon E5-2687W >Memory: 47.06 GiB >Partitions: >peter@RC2net:~$ df -T >Filesystem Type 1K-blocks Used Available Use% Mounted on >udev devtmpfs 24636332 0 24636332 0% /dev >tmpfs tmpfs 4934304 1988 4932316 1% /run >/dev/sda6 ext4 28660644 4485828 22693600 17% / >tmpfs tmpfs 24671508 0 24671508 0% /dev/shm >tmpfs tmpfs 5120 12 5108 1% /run/lock >/dev/sda8 ext4 19046484 908 18052708 1% /home >tmpfs tmpfs 4934300 56 4934244 1% /run/user/1000 >peter@RC2net:~$ > >Output of lspci and lspci -n: > >peter@RC2net:~$ lspci >00:00.0 Host bridge: Intel Corporation Xeon E5/Core i7 DMI2 (rev 07) >00:01.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root >Port 1a (rev 07) >00:01.1 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root >Port 1b (rev 07) >00:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root >Port 2a (rev 07) >00:03.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root >Port 3a in PCI Express Mode (rev 07) >00:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address Map, >VTd_Misc, System Management (rev 07) >00:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control Status >and Global Errors (rev 07) >00:05.4 PIC: Intel Corporation Xeon E5/Core i7 I/O APIC (rev 07) >00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express >Virtual Root Port (rev 05) >00:16.0 Communication controller: Intel Corporation C600/X79 series chipset >MEI Controller #1 (rev 05) >00:16.2 IDE interface: Intel Corporation C600/X79 series chipset IDE-r >Controller (rev 05) >00:16.3 Serial controller: Intel Corporation C600/X79 series chipset KT >Controller (rev 05) >00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network >Connection (Lewisville) (rev 05) >00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 >Enhanced Host Controller #2 (rev 05) >00:1b.0 Audio device: Intel Corporation C600/X79 series chipset High >Definition Audio Controller (rev 05) >00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express >Root Port 2 (rev b5) >00:1c.5 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express >Root Port 5 (rev b5) >00:1c.6 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express >Root Port 3 (rev b5) >00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 >Enhanced Host Controller #1 (rev 05) >00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5) >00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller >(rev 05) >00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset SATA >RAID Controller (rev 05) >00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host >Controller (rev 05) >01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network >Connection >02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express >Fusion-MPT SAS-2 (rev 05) >04:00.0 Serial Attached SCSI controller: Intel Corporation C602 chipset >4-Port SATA Storage Control Unit (rev 05) >05:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730] >(rev a1) >05:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev >a1) >08:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI >Host Controller (rev 02) >09:01.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a >Controller (rev 70) >3f:08.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 0 (rev >07) >3f:08.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0 >(rev 07) >3f:08.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0 >(rev 07) >3f:09.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 1 (rev >07) >3f:09.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1 >(rev 07) >3f:09.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1 >(rev 07) >3f:0a.0 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control >Unit 0 (rev 07) >3f:0a.1 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control >Unit 1 (rev 07) >3f:0a.2 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control >Unit 2 (rev 07) >3f:0a.3 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control >Unit 3 (rev 07) >3f:0b.0 System peripheral: Intel Corporation Xeon E5/Core i7 Interrupt >Control Registers (rev 07) >3f:0b.3 System peripheral:
Bug#1035096: installation-report Bookworm RC2 GRUB not installed
Package: grub-installer Boot method: USB Image version: debian-bookworm-DI-rc2-amd64-netinst.iso download from Debian Date: 2023-04-28 ~17 Machine: HP Z820 Workstation Processor: 2x 8-core model: Intel Xeon E5-2687W Memory: 47.06 GiB Partitions: peter@RC2net:~$ df -T Filesystem Type 1K-blocks Used Available Use% Mounted on udev devtmpfs 24636332 0 24636332 0% /dev tmpfs tmpfs 4934304 1988 4932316 1% /run /dev/sda6 ext4 28660644 4485828 22693600 17% / tmpfs tmpfs 24671508 0 24671508 0% /dev/shm tmpfs tmpfs 5120 12 5108 1% /run/lock /dev/sda8 ext4 19046484 908 18052708 1% /home tmpfs tmpfs 4934300 56 4934244 1% /run/user/1000 peter@RC2net:~$ Output of lspci and lspci -n: peter@RC2net:~$ lspci 00:00.0 Host bridge: Intel Corporation Xeon E5/Core i7 DMI2 (rev 07) 00:01.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 1a (rev 07) 00:01.1 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 1b (rev 07) 00:02.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 2a (rev 07) 00:03.0 PCI bridge: Intel Corporation Xeon E5/Core i7 IIO PCI Express Root Port 3a in PCI Express Mode (rev 07) 00:05.0 System peripheral: Intel Corporation Xeon E5/Core i7 Address Map, VTd_Misc, System Management (rev 07) 00:05.2 System peripheral: Intel Corporation Xeon E5/Core i7 Control Status and Global Errors (rev 07) 00:05.4 PIC: Intel Corporation Xeon E5/Core i7 I/O APIC (rev 07) 00:11.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Virtual Root Port (rev 05) 00:16.0 Communication controller: Intel Corporation C600/X79 series chipset MEI Controller #1 (rev 05) 00:16.2 IDE interface: Intel Corporation C600/X79 series chipset IDE-r Controller (rev 05) 00:16.3 Serial controller: Intel Corporation C600/X79 series chipset KT Controller (rev 05) 00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network Connection (Lewisville) (rev 05) 00:1a.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #2 (rev 05) 00:1b.0 Audio device: Intel Corporation C600/X79 series chipset High Definition Audio Controller (rev 05) 00:1c.0 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 2 (rev b5) 00:1c.5 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 5 (rev b5) 00:1c.6 PCI bridge: Intel Corporation C600/X79 series chipset PCI Express Root Port 3 (rev b5) 00:1d.0 USB controller: Intel Corporation C600/X79 series chipset USB2 Enhanced Host Controller #1 (rev 05) 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev a5) 00:1f.0 ISA bridge: Intel Corporation C600/X79 series chipset LPC Controller (rev 05) 00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset SATA RAID Controller (rev 05) 00:1f.3 SMBus: Intel Corporation C600/X79 series chipset SMBus Host Controller (rev 05) 01:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection 02:00.0 Serial Attached SCSI controller: Broadcom / LSI SAS2308 PCI-Express Fusion-MPT SAS-2 (rev 05) 04:00.0 Serial Attached SCSI controller: Intel Corporation C602 chipset 4-Port SATA Storage Control Unit (rev 05) 05:00.0 VGA compatible controller: NVIDIA Corporation GK208B [GeForce GT 730] (rev a1) 05:00.1 Audio device: NVIDIA Corporation GK208 HDMI/DP Audio Controller (rev a1) 08:00.0 USB controller: Texas Instruments TUSB73x0 SuperSpeed USB 3.0 xHCI Host Controller (rev 02) 09:01.0 FireWire (IEEE 1394): LSI Corporation FW322/323 [TrueFire] 1394a Controller (rev 70) 3f:08.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 0 (rev 07) 3f:08.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0 (rev 07) 3f:08.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 0 (rev 07) 3f:09.0 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link 1 (rev 07) 3f:09.3 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1 (rev 07) 3f:09.4 System peripheral: Intel Corporation Xeon E5/Core i7 QPI Link Reut 1 (rev 07) 3f:0a.0 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 0 (rev 07) 3f:0a.1 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 1 (rev 07) 3f:0a.2 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 2 (rev 07) 3f:0a.3 System peripheral: Intel Corporation Xeon E5/Core i7 Power Control Unit 3 (rev 07) 3f:0b.0 System peripheral: Intel Corporation Xeon E5/Core i7 Interrupt Control Registers (rev 07) 3f:0b.3 System peripheral: Intel Corporation Xeon E5/Core i7 Semaphore and Scratchpad Configuration Registers (rev 07) 3f:0c.0 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07) 3f:0c.1 System peripheral: Intel Corporation Xeon E5/Core i7 Unicast Register 0 (rev 07)
