Bugzilla – Bug 103011
On first reboot getting "No operating system"
Last modified: 2005-08-11 11:01:14 UTC
Installing from a SuSE installation server via PXE boot. Using SUSE-10.0-CD-OSS-i386-Beta1 as the source. Installation seems to finish with no errors, boot on the first reboot a message is displayed that their is "No operating system". Drive is a IDE harddisk, and is master on secondary IDE channel (/dev/hdc). CDROM is master on primary channel. A SuSE 9.3 installation works using same installation method without any problems.
*** This bug has been marked as a duplicate of 100728 ***
FYI... I switched the IDE drive from master on secondary to master on primary (now /dev/hda/), and I still get the same results. I even went as far to disconnect the CD-ROM, and it still fails. One other note, same configuration but on a Dell Optiplex GX1 works with no issues. The harddrive is a Western Digital vs. Seagate. Below is the output from hwinfo when booting to rescue mode. hwinfo --storage-ctrl 21: PCI 11.1: 0101 IDE interface [Created at pci.271] Unique ID: +Y+h.5RYrxfomH02 SysFS ID: /devices/pci0000:00/0000:00:11.1 SysFS BusID: 0000:00:11.1 Hardware Class: storage Model: "Elitegroup VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE" Vendor: pci 0x1106 "VIA Technologies, Inc." Device: pci 0x0571 "VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE" SubVendor: pci 0x1019 "Elitegroup Computer Systems" SubDevice: pci 0x1831 Revision: 0x06 Driver: "VIA_IDE" I/O Ports: 0xfc00-0xfc0f (rw) IRQ: 255 (no events) I/O Ports: 0x1f0-0x1f7 (rw) I/O Port: 0x3f6 (rw) I/O Ports: 0x170-0x177 (rw) I/O Port: 0x376 (rw) IRQ: 14 (218 events) IRQ: 15 (2629 events) Driver Info #0: Driver Status: via82cxxx is active Driver Activation Cmd: "modprobe via82cxxx" Driver Info #1: Driver Status: generic is not active Driver Activation Cmd: "modprobe generic" Config Status: cfg=new, avail=yes, need=no, active=unknown hwinfo --partition 14: None 00.0: 11300 Partition [Created at block.357] Unique ID: 0fbI.SE1wIdpsiiC Parent ID: l_yX.YJ4I4IjrkZ0 SysFS ID: /block/hda/hda1 Hardware Class: partition Model: "Partition" Device File: /dev/hda1 Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #13 (Disk) 15: None 00.0: 11300 Partition [Created at block.357] Unique ID: TqrM.SE1wIdpsiiC Parent ID: l_yX.YJ4I4IjrkZ0 SysFS ID: /block/hda/hda2 Hardware Class: partition Model: "Partition" Device File: /dev/hda2 Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #13 (Disk) hwinfo --disk 13: IDE 00.0: 10600 Disk [Created at block.188] Unique ID: l_yX.YJ4I4IjrkZ0 Parent ID: +Y+h.5RYrxfomH02 SysFS ID: /block/hda SysFS BusID: 0.0 SysFS Device Link: /devices/pci0000:00/0000:00:11.1/ide0/0.0 Hardware Class: disk Model: "ST33210A" Device: "ST33210A" Revision: "3.02" Serial ID: "7AB0XJ77" Driver: "VIA_IDE", "ide-disk", "ide-disk" Device File: /dev/hda Device Number: block 3:0-3:63 BIOS id: 0x80 Geometry (Logical): CHS 6296/16/63 Size: 6346368 sectors a 512 bytes Geometry (BIOS Legacy): CHS 786/128/63 Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #10 (IDE interface) Final comment, this configuratiion works with no problems in SuSE 9.3. I did read bug 100728, and will test beta2 when released.
Please see previous comments.
Can you attach - /var/log/YaST2/* directory - contents of MBR of your first disk Both needs to be got after the failing installation, from the rescue system, before it is fixed.
It sounds like a duplicate of 103031, it is hopefully the same, also one-disk machine. *** This bug has been marked as a duplicate of 103031 ***