[opensuse] Bitness upgrade of 13.2 impossible due to reiserfs partitions?
Some older machine (32bit opensuse) advanced to 13.2 32bit and came a long way over the past years. I think most of the recent years and opensuse versions it advanced via zypper dup. Some places recently say that machines should be moved over to 64bit opensuse if possible by hw. So I try to upgrade via usb drive to boot the 64bit opensuse 13.2 installer. It takes really many minutes to look my hard drive but doesnt offer me upgrade 32bit opensuse nor find partitions, but offers to create new partition on free space of hard disk and wants to install everything to this new partition or format other existing partitions to xfs and btrfs and crazy stuff. Only parition it cared for was the swap (first partition). I go into manual partitioning graphical interface and try to show various partitions and tell each one what actual mount point it is on the 32bit 13.2 opensuse. I have boot and root and var I think. At the end I was scared of kinda to make it try to install as I was uncertain if it would then take a look at the already existing 32bit suse and rpm datrabases and all the config and all and an additional pop up complained that yast was very low quality and no guarantees if one had especially reiser partitons and some other aspects were listed I can not remember any more. Is this really state of the art that perfectly fine working and booting reiserfs partitions in 32bit opensuse 13.2 are unsupported or not being recognised or considered an adequate situation for 64bit opensuse 13.2? Opensuse linux kind of seems very weird to me the recent years. More stuff gets abandoned and I wonder why it is even important what fileysystem a user has available if the kernel already supports it why does a userland install program complain about it? Isnt this what software layers are supposed to be for? If kernel can talk to disk and partitions why scare the user away or why make setup application fail to find the existing 32bit opensuse 13.2? I think that complaint box didnt even list ext2 as valid only spoke about btrfs or ext3 I think. Why abandon all the proven and existing stuff that lower layers of open source and gnu-linux world brings along as support? Seemingly every day, I understand less and less of the weird path and road and opensuse is heading down to and the choices made by the project. Maybe I am better off with a different distribution after all. c -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 2015-02-13 00:34, cagsm wrote:
So I try to upgrade via usb drive to boot the 64bit opensuse 13.2 installer.
Upgrade of openSUSE 32 bit to 64 is possible via the boot-dvd-choose-upgrade-method. But it is not supported, and the installer will not even offer the possibility. You have to force it to do it, and then will then give a big warning of danger. You have to know what you are doing, and have a lot of manual work to do after the procedure. I and many others have done it, successfully.
Is this really state of the art that perfectly fine working and booting reiserfs partitions in 32bit opensuse 13.2 are unsupported or not being recognised or considered an adequate situation for 64bit opensuse 13.2?
Reiserfs is going out, and the fact has been known for years, like it or not. You can still use reiserfs partitions, but yast will not create one. I don't know if you can boot from it, though. I would not try.
Seemingly every day, I understand less and less of the weird path and road and opensuse is heading down to and the choices made by the project. Maybe I am better off with a different distribution after all.
Use whatever works for you. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlTf/moACgkQja8UbcUWM1zTZQD/ZFAQDaJPlBqNB21t1pqt9uKk M0VnDpesceLvAn9LPIsA/183Q6GkKyoX4+tCAyaGLOzxL8I6gZvJk0MHAXUFp5UQ =K4sw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Thanks for reply. My current 32bit 13.2 works fine. It boots fine. Everything okay. I do wonder why the install procedure and components need to deprecate components deliberately or at will or by accident, that the actual linux/suse actually supports just fine. As I said it doesnt find or recognize the partitions meaning which to select for root partition and for it to display that there is a 13.2 installed already. I am doing the dvd/iso upgrade method offline. But just most likely because of reiser partitions or some obscure logic it doesnt want to display and find the existing 13.2. I did this many times in the past (staying within bitness), and 13.2 upgraded 13.1 fine (32bits) and it was the same reiser partitions and all back then. The suse installer now behaves for example coparable to it decides on itself to say hey i dont like your keyboard or i dont like your video please get lost, although the linux itself just takes your keyboard or video just fine. This doesnt make any sense to me. This is hindering and bothering the user. Why can 32bit 13.2 installer upgrade my old 13.1 system just fine, but why can the same 13.2 installer not upgrade the bitness of already existing 13.2. Does these processes or places in the source code of the installer detect the partitions or the system itself differently? can the one subroutines detect the reiser partitions and the other choses to block or just disregard the partitions? or the rpm database or where and how it identifies an existing opensuse system and then lists it as an entry that 13.1 root is on /dev/sda2 or similar it used to show in the years before and still when going from 13.1 to 13.2 on 32bit. A 13.2 just boots reiser fine and the partition tools in those expert modes and advanced modus during install also lists the partitions and identifies them as reiser and all, only the installer apparently never gets into that sage where it prints out that little table where it says, yes I have found an opensuse x on partition p and do you wana select that to upgrade or to install and so forth. That is what this thread is about. Thanks. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2/16/2015 2:06 AM, cagsm wrote:
Thanks for reply. My current 32bit 13.2 works fine. It boots fine. Everything okay. I do wonder why the install procedure and components need to deprecate components deliberately or at will or by accident, that the actual linux/suse actually supports just fine. As I said it doesnt find or recognize the partitions meaning which to select for root partition and for it to display that there is a 13.2 installed already. I am doing the dvd/iso upgrade method offline. But just most likely because of reiser partitions or some obscure logic it doesnt want to display and find the existing 13.2. I did this many times in the past (staying within bitness), and 13.2 upgraded 13.1 fine (32bits) and it was the same reiser partitions and all back then. The suse installer now behaves for example coparable to it decides on itself to say hey i dont like your keyboard or i dont like your video please get lost, although the linux itself just takes your keyboard or video just fine. This doesnt make any sense to me. This is hindering and bothering the user. Why can 32bit 13.2 installer upgrade my old 13.1 system just fine, but why can the same 13.2 installer not upgrade the bitness of already existing 13.2. Does these processes or places in the source code of the installer detect the partitions or the system itself differently? can the one subroutines detect the reiser partitions and the other choses to block or just disregard the partitions? or the rpm database or where and how it identifies an existing opensuse system and then lists it as an entry that 13.1 root is on /dev/sda2 or similar it used to show in the years before and still when going from 13.1 to 13.2 on 32bit. A 13.2 just boots reiser fine and the partition tools in those expert modes and advanced modus during install also lists the partitions and identifies them as reiser and all, only the installer apparently never gets into that sage where it prints out that little table where it says, yes I have found an opensuse x on partition p and do you wana select that to upgrade or to install and so forth. That is what this thread is about. Thanks.
There are no shortage of Paragraphs on the internet. Please feel free to use a few. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Turns out the 13.2 media boot menu contains an additional entry "upgrade" which I never noticed so far. I remember the old days when booting the "installation" entry would give you choice of new install or upgrade install and it then would look on local disk for older opensuse. Now only booting the "upgrade" entry gives that functionality that it does find an older opensuse or current opensuse i386 that it then can upgrade to x86-64. Mybad but never noticed so far. What opensuse version did this get introduced by? Also this is not explained in F1 help function screen in that boot menu. There are still historic things mentioned there. But no upgrade entry. Thank you. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
cagsm -
Carlos E. R. -
John Andersen