opensuse 12.1 to 12.3 update: video refresh rate, system to upgrade not found

I was running openSUSE 12.1 on a Supermicro 1U server. I took openSUSE-12.3-DVD-x86_64.iso and burned it to a USB flash drive and booted from it. I got the Welcome screen and then the choices screen. These looked fine. I picked installation. After a long time of hardware detection I got the Preparation > Welcome Screen, which was being displayed at 640x480x87 with a lot of jitter. I don’t know why it chose the 87 Hz refresh rate; that seems too fast for my Dell LCD panel. I hit enter for the license agreement, and it moved to the System Analysis page, and seemed to hang on the “Searching for Linux partitions…” (60%) step. I powered off the system and powered on again. This time I picked 1600x1200 from the Video menu, but on proceeding to Preparation > Welcome I got the same 87Hz refresh. I also let it search for a really long time for Linux partitions, and it did eventually make further progress, but I’ve never seen an openSUSE upgrade be so slow and never had the video trouble before. Right now “Partition or System to Update” it is showing no choices until I checked Show All Partitions. This is definitely not working as smoothly as it once did.

The 1U system has four 750 GB drives with /boot and / being mirrored RAID1 arrays (there are also RAID6 and RAID5 partitions if this matters).

Any suggestions on how to manage the video for the install process would be most appreciated. Any comments on why the upgrade is not as smooth as it once was would be interesting.

To make matters worse, at the end of the upgrade, it said Error occurred while installing GRUB. GNU GRUB version 0.97. [Minimal BASH-like line…] grub> setup --stage2 /boot/grub/stage2 --force-lba (hd0) (hd0,1)
Checking if “/boot/grub/stage1” exists… no
Checking if “/grub/stage1” exists… no
Error 15: File not found
grub> quit

To the long pause. It is reported the if the BIOS has set a active floppy but it does not exist can cause a lengthy hang

To the rest I cam’t say but since you chose old grub intead of grub2 you do need to be careful how thing are set

On 2013-04-12 03:56, gogalthorp wrote:
> To the rest I cam’t say but since you chose old grub intead of grub2
> you do need to be careful how thing are set

If he selected “upgrade” the choice of grub 1 would be automatic.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

He is also jumping from 12.1 to 12.3 which may be a factor. Personally I’s be very sure that the the installer was doing what I expect it to do.

On 2013-04-12 06:36, gogalthorp wrote:
>
> He is also jumping from 12.1 to 12.3 which may be a factor. Personally
> I’s be very sure that the the installer was doing what I expect it to
> do.

Yes, it is a factor. The upgrade is possible, but a DVD upgrade can not
upgrade what is not in the DVD. The rest of the packages are either left
not upgraded or uninstalled, so you have things to do afterwards, and
with a jump the leftovers are from more different version than normal.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

On 2013-04-12 19:58, Carlos E. R. wrote:
> On 2013-04-12 06:36, gogalthorp wrote:
>>
>> He is also jumping from 12.1 to 12.3 which may be a factor. Personally
>> I’s be very sure that the the installer was doing what I expect it to
>> do.
>
> Yes, it is a factor. The upgrade is possible, but a DVD upgrade can not
> upgrade what is not in the DVD. The rest of the packages are either left
> not upgraded or uninstalled, so you have things to do afterwards, and
> with a jump the leftovers are from more different version than normal.

I forgot to say:

Online upgrade
method

Offline upgrade
method

Chapter 16. Upgrading the System and System Changes

Number 2 and 3 apply.


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

Thank you for the note about the floppy. That may be it, as the machine lacks a floppy drive. I will check the BIOS.

As someone else pointed out, GRUB was picked by the upgrade process. I have since attempted a fresh install (leaving the data partitions, and reformatting /boot and /) with GRUB2. That did not work either, as I ran into GRUB2 needing a “BIOS boot partition” with GPT. Apparently GPT worked with openSUSE 12.1 on my old system (a Tyan K8S, about vintage 2005), but no longer does. I am going to attempt to tar my data partitions to a USB disk and then revert to MBR, as I don’t know how to create a BIOS boot partition without disturbing the existing data partitions.

I do have a suggestion for the developers: how about checking if a BIOS boot partition is required and non-existant earlier in the process? It is unfortunate to go through a long install to have it fail at the last step.

Thank you again all for your suggestions. If you have any further suggestions, they will be appreciated.

I guess we need more info on that hardware.

video card?

BIOS/UEFI?

Disk partitioning?

fdisk -l

etc

Unfortunately the upgrade attempt the system non-bootable, so some of that is hard to get at the moment. I also tried running both the LIVE GNOME and LIVE KDE systems to help backup the system, but both failed. I am currently running a Live Fedora 18 and running tar of each of the 4 partitions before starting over with a MBR setup (if you have other suggestions, let me know).

I think this is the mobo: tomcatK8S_spec and I am using the integrated graphics (ATI® RAGE™ XL 8MB PCI graphics controller).

The original disk partitioning was done with the openSUSE 12.1 installation DVD using GPT and creating four type 83 and one type 82 partitions, so I think parted output is more appropriate than fdisk output. I will try to get that to you when I am finished with the backup. I have it on the screen, but I doubt I could type it here without errors, so it will have to wait until cut-and-paste is possible (many hours). Basically the first partition (/boot) is 525MB (RAID1,ext4), the second (/) is 64GB (RAID1,ext4), the third is 16GB of swap, the fourth is 268G (RAID6,ext4), and the fifth is 400GB (RAID5,ext4). The first partition starts at 1049kB according to parted. The first and second partitions have both the boot and legacy_boot flags shown in parted.

The BIOS says it is Phoenix on boot. I very much doubt that it is UEFI.

Hardware or software RAID? I Assume it is not BIOS assisted or fake RAID.

The backup finally finished and I was able to upload the information you requested:

% cat /Volumes/homes/earl/fdisk-l.out 

Disk /dev/sda: 750.2 GB, 750156374016 bytes, 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1028095      513024   83  Linux
/dev/sda2         1028096   126865407    62918656   83  Linux
/dev/sda3       126865408   160425983    16780288   82  Linux swap / Solaris
/dev/sda4               1           1           0+  ee  GPT


Partition table entries are not in disk order


Disk /dev/sdd: 750.2 GB, 750156374016 bytes, 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdd1   *        2048     1028095      513024   83  Linux
/dev/sdd2         1028096   126865407    62918656   83  Linux
/dev/sdd3       126865408   160425983    16780288   82  Linux swap / Solaris
/dev/sdd4               1           1           0+  ee  GPT


Partition table entries are not in disk order


Disk /dev/sde: 750.2 GB, 750156374016 bytes, 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sde1   *        2048     1028095      513024   83  Linux
/dev/sde2         1028096   126865407    62918656   83  Linux
/dev/sde3       126865408   160425983    16780288   82  Linux swap / Solaris
/dev/sde4               1           1           0+  ee  GPT


Partition table entries are not in disk order


Disk /dev/sdc: 8295 MB, 8295284736 bytes, 16201728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x7b8e2b2a


   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1   *           0     1875967      937984    0  Empty
/dev/sdc2             172        9995        4912   ef  EFI (FAT-12/16/32)
/dev/sdc3           10044       49371       19664    0  Empty


Disk /dev/sdc1: 960 MB, 960495616 bytes, 1875968 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x7b8e2b2a


     Device Boot      Start         End      Blocks   Id  System
/dev/sdc1p1   *           0     1875967      937984    0  Empty
/dev/sdc1p2             172        9995        4912   ef  EFI (FAT-12/16/32)
/dev/sdc1p3           10044       49371       19664    0  Empty


Disk /dev/sdb: 4000.8 GB, 4000786149376 bytes, 976754431 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0xacf6640a


   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              63   976751999  3907007748    7  HPFS/NTFS/exFAT


Disk /dev/sdf: 750.2 GB, 750156374016 bytes, 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000


   Device Boot      Start         End      Blocks   Id  System
/dev/sdf1   *        2048     1028095      513024   83  Linux
/dev/sdf2         1028096   126881791    62926848   83  Linux
/dev/sdf3       126881792   158642175    15880192   82  Linux swap / Solaris
/dev/sdf4               1           1           0+  ee  GPT


Partition table entries are not in disk order


Disk /dev/mapper/live-rw: 4294 MB, 4294967296 bytes, 8388608 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes




Disk /dev/mapper/live-osimg-min: 4294 MB, 4294967296 bytes, 8388608 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes




Disk /dev/md127: 64.4 GB, 64428630016 bytes, 125837168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes




Disk /dev/md126: 525 MB, 525324288 bytes, 1026024 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes




Disk /dev/md125: 1198.8 GB, 1198757511168 bytes, 2341323264 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 393216 bytes




Disk /dev/md124: 536.9 GB, 536861999104 bytes, 1048558592 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 131072 bytes / 262144 bytes

% cat /Volumes/homes/earl/sda.parted 
Model: ATA ST3750330NS (scsi)
Disk /dev/sda: 750GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags: pmbr_boot


Number  Start   End     Size    File system     Name     Flags
 1      1049kB  526MB   525MB   ext4            primary  boot, legacy_boot
 2      526MB   65.0GB  64.4GB  ext4            primary  boot, legacy_boot
 3      65.0GB  82.1GB  17.2GB  linux-swap(v1)  primary
 4      82.1GB  351GB   268GB   ext4            primary  raid
 5      351GB   750GB   400GB                   primary  raid




Software RAID.

On 2013-04-19 06:36, eak9000 wrote:
> The backup finally finished and I was able to upload the information
> you requested:

Hybrid GPT/traditional partitioning?

I understand that can be a source of problems :-?


Cheers / Saludos,

Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)

All I know is that I picked GPT partitioning when installing openSUSE 12.1. Perhaps it picked hybrid on my behalf? I had never heard of hybrid partitioning until the 12.3 upgrade failed and I started reading about GPT booting.