|
Bugzilla – Full Text Bug Listing |
| Summary: | System does not boot on HP DL380 G5 Server | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Ulrich Windl <Ulrich.Windl> |
| Component: | Installation | Assignee: | E-mail List <yast2-maintainers> |
| Status: | RESOLVED NORESPONSE | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | ancor, jreidinger, Ulrich.Windl |
| Version: | Leap 42.1 | Flags: | ancor:
needinfo?
(Ulrich.Windl) |
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 42.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | Output of "fdisk -l" | ||
|
Description
Ulrich Windl
2015-12-15 12:34:24 UTC
I think I found the problem: The Array had three logical disks defined, but only the first being scanned for boot code. The installation used the largest logical disk to install everything (it seems). After a new installation with manual disk partitioning, the system booted. Ulrich, if I got it right, it was not Grub or YaST fault then. Grub was installed only in a logical disk and the BIOS didn't consider that disk for booting. Right? I guess there is no much we can fix about this. As I wasn't patient enough to collect the installation state before doing another installation, it's a bit hard to guess was had happened. Fact is that there was Windows/2003 on the first logical disk and that booted. So I guess that partition was marked active. As installation wiped the NTFS filesystem, I guess the boot sector on logical drive remained intact, while the new boot loader was written to another logical drive. So naturally when booting the boot sector on the first logical drive had a small chance to succeed. So the primary error of installation was to use the largest drive instead of the first drive for installing the system boot area. (In reply to my comment #3) > (...) the boot sector on the first logical drive had a small chance to succeed. That's the polite version of: "the boot sector had no chance to succeed" ;-) Josef, what's your view here? For me it looks like problem with "boot" flag on disks. I need logs to check where it is set. Choosing the biggest drive should not be problem for bootloader as long as boot flag is properly set and as long as disk boot order in bios is correct (something installer cannot change). But as I said I need logs. Created attachment 659542 [details]
Output of "fdisk -l"
The logical drives look like this:
/dev/cciss/c0d0: 100 GiB
/dev/cciss/c0d0p1: 100 GiB, bootable
/dev/cciss/c0d1: 5 GiB
/dev/cciss/c0d1p1: 5 GiB, NTFS (some recovery partition)
/dev/cciss/c0d2: 174.4 GiB, unpartitioned!
So if /dev/cciss/c0d2 is unpartitioned now, I guess it was unpartitioned all the time. These are the facts I can get from the system as it's running now.
Ulrich, Josef was referring to the YaST logs generated during installation. https://en.opensuse.org/openSUSE:Report_a_YaST_bug Requested information not provided within 4 weeks. Feel free to reopen the bug once the information is provided. |