[oS-EN] 15.5 Upgrade thoughts.
Hi, I have upgraded two machines to 15.5, using the DVD image on usb stick, choosing upgrade. On a modern laptop, I noticed that it erased "GRUB_DISTRIBUTOR=" in "/etc/default/grub". This can cause crashes (collisions) on machines with multiboots. On an old desktop (classic BIOS) I noticed two things. It did not recognize the partition to upgrade, maybe because this machine uses a separate /usr partition. I managed to reboot and restart the procedure, and it seems to be working. I'm typing on it. -- Cheers / Saludos, Carlos E. R. (from Elesar, using openSUSE Leap 15.5)
* Carlos E. R. <robin.listas@telefonica.net> [06-14-23 16:07]:
Hi,
I have upgraded two machines to 15.5, using the DVD image on usb stick, choosing upgrade.
On a modern laptop, I noticed that it erased "GRUB_DISTRIBUTOR=" in "/etc/default/grub". This can cause crashes (collisions) on machines with multiboots.
On an old desktop (classic BIOS) I noticed two things. It did not recognize the partition to upgrade, maybe because this machine uses a separate /usr partition. I managed to reboot and restart the procedure, and it seems to be working. I'm typing on it.
I would think that worthy of a bug report. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 15/06/2023 00.04, Patrick Shanahan wrote:
* Carlos E. R. <...> [06-14-23 16:07]:
Hi,
I have upgraded two machines to 15.5, using the DVD image on usb stick, choosing upgrade.
On a modern laptop, I noticed that it erased "GRUB_DISTRIBUTOR=" in "/etc/default/grub". This can cause crashes (collisions) on machines with multiboots.
On an old desktop (classic BIOS) I noticed two things. It did not recognize the partition to upgrade, maybe because this machine uses a separate /usr partition.
Oh, I forgot the most important part of it: the machine locked hard when it had updated maybe a hundred or two packages. Not even the mouse would move. First time I see this happen in more than twenty years of upgrades with SuSE, or openSUSE. That's why I had to hard reboot.
I managed to reboot and restart the procedure, and it seems to be
working. I'm typing on it.
I would think that worthy of a bug report.
I have the feeling this was reported years ago. I will have to check. Erasure of the grub variables is more important, I think. -- Cheers / Saludos, Carlos E. R. (from openSUSE 15.4 (Legolas))
On 2023-06-14 20:55:13 Carlos E. R. wrote:
On 15/06/2023 00.04, Patrick Shanahan wrote:
* Carlos E. R. <...> [06-14-23 16:07]:
Hi,
I have upgraded two machines to 15.5, using the DVD image on usb stick, choosing upgrade.
On a modern laptop, I noticed that it erased "GRUB_DISTRIBUTOR=" in "/etc/default/grub". This can cause crashes (collisions) on machines with multiboots.
On an old desktop (classic BIOS) I noticed two things. It did not recognize the partition to upgrade, maybe because this machine uses a separate /usr partition.
Oh, I forgot the most important part of it: the machine locked hard when it had updated maybe a hundred or two packages. Not even the mouse would move. First time I see this happen in more than twenty years of upgrades with SuSE, or openSUSE. That's why I had to hard reboot.
I managed to reboot and restart the procedure, and it seems to be
working. I'm typing on it.
I would think that worthy of a bug report.
I have the feeling this was reported years ago. I will have to check.
Erasure of the grub variables is more important, I think.
They both sound very important to me, one for multi-boot systems, the other for multi-partition systems; such systems can't be very scarce. Leslie -- Platform: Linux Distribution: openSUSE Leap 15.4 (x86_64)
I've done the upgrade on 5 computers now. The only thing that's caused problems is... I have 2 computers with external/USB 8TB drives on them. When the upgrade process starts to mount existing file systems they went into la-la land. I was forced to turn them off, disconnect the USB drive, and start all over again. This happened using a DvD to do the upgrade on one computer, and using a USB stick on the other computer (no DvD drive on the computer).
Am 17.06.23 um 21:12 schrieb Bill Swisher:
I've done the upgrade on 5 computers now. The only thing that's caused problems is... I have 2 computers with external/USB 8TB drives on them. When the upgrade process starts to mount existing file systems they went into la-la land. I was forced to turn them off, disconnect the USB drive, and start all over again. This happened using a DvD to do the upgrade on one computer, and using a USB stick on the other computer (no DvD drive on the computer).
Obvious: The upgrade process probes all connected devices, I suppose, if you had waited long enough it would simply timeout that device and continue with the next. I learnt this lesson long ago: Disconnect/switch of everything which is not needed while upgrading. Peter
On 2023-06-17 22:05, Peter McD wrote:
Am 17.06.23 um 21:12 schrieb Bill Swisher:
I've done the upgrade on 5 computers now. The only thing that's caused problems is... I have 2 computers with external/USB 8TB drives on them. When the upgrade process starts to mount existing file systems they went into la-la land. I was forced to turn them off, disconnect the USB drive, and start all over again. This happened using a DvD to do the upgrade on one computer, and using a USB stick on the other computer (no DvD drive on the computer).
Obvious: The upgrade process probes all connected devices, I suppose, if you had waited long enough it would simply timeout that device and continue with the next.
I learnt this lesson long ago: Disconnect/switch of everything which is not needed while upgrading.
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2023-06-18 00:38, Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-06-18 01:37, Carlos E. R. wrote:
On 2023-06-18 00:38, Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Or you could write a text file named something like "notes for version upgrade".... ;)
Am 18.06.23 um 10:06 schrieb Darryl Gregorash:
On 2023-06-18 01:37, Carlos E. R. wrote:
On 2023-06-18 00:38, Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Or you could write a text file named something like "notes for version upgrade".... ;)
Also learnt: A local archive, .txt files only. It is astonishing how many additional notes accumulate for a smooth running Linux. Peter
On 2023-06-18 10:30, Peter McD wrote:
Am 18.06.23 um 10:06 schrieb Darryl Gregorash:
On 2023-06-18 01:37, Carlos E. R. wrote:
On 2023-06-18 00:38, Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Or you could write a text file named something like "notes for version upgrade".... ;)
Also learnt: A local archive, .txt files only. It is astonishing how many additional notes accumulate for a smooth running Linux.
You bet. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-06-18 10:51, Carlos E. R. wrote:
On 2023-06-18 10:30, Peter McD wrote:
Am 18.06.23 um 10:06 schrieb Darryl Gregorash:
On 2023-06-18 01:37, Carlos E. R. wrote:
On 2023-06-18 00:38, Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Or you could write a text file named something like "notes for version upgrade".... ;)
Also learnt: A local archive, .txt files only. It is astonishing how many additional notes accumulate for a smooth running Linux.
You bet.
Yep. Been down this road since 1998 (when I switched from FreeBSD to Linux). Calling my files a bit silly "fungerande_" (working_) in Swedish. And I have a little function that just greps for keywords in the files. Has been a real lifesaver many, many times when memory doesn't serve me well enough. $ ls ~/doc/fungerande_* | wc -l 369 $ LANG=C stat ~/doc/fungerande_* | grep Modify: | sort | head -1 Modify: 1998-11-23 03:41:28.000000000 +0100 -- /bengan
On 2023-06-18 11:19, Bengt Gördén wrote:
On 2023-06-18 10:51, Carlos E. R. wrote:
On 2023-06-18 10:30, Peter McD wrote:
Am 18.06.23 um 10:06 schrieb Darryl Gregorash:
On 2023-06-18 01:37, Carlos E. R. wrote:
On 2023-06-18 00:38, Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
> It even probes the floppy drive. maybe ten times. And not only while > starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Or you could write a text file named something like "notes for version upgrade".... ;)
Also learnt: A local archive, .txt files only. It is astonishing how many additional notes accumulate for a smooth running Linux.
You bet.
Yep. Been down this road since 1998 (when I switched from FreeBSD to Linux). Calling my files a bit silly "fungerande_" (working_) in Swedish. And I have a little function that just greps for keywords in the files. Has been a real lifesaver many, many times when memory doesn't serve me well enough.
$ ls ~/doc/fungerande_* | wc -l 369 $ LANG=C stat ~/doc/fungerande_* | grep Modify: | sort | head -1 Modify: 1998-11-23 03:41:28.000000000 +0100
I have dir ~/howto :-) Talking of that, a proper note taking software with automatic indexing/TOC, and a resulting file that can be merged across several machines, would be nice ;-) If multi-os, even better. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
On 2023-06-18 02:30, Peter McD wrote:
Am 18.06.23 um 10:06 schrieb Darryl Gregorash:
On 2023-06-18 01:37, Carlos E. R. wrote:
On 2023-06-18 00:38, Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Or you could write a text file named something like "notes for version upgrade".... ;)
Also learnt: A local archive, .txt files only. It is astonishing how many additional notes accumulate for a smooth running Linux.
Peter A small price to pay, if the alternative is to ask the same questions over and over again, every time there is a new release.
On 2023-06-18 10:06, Darryl Gregorash wrote:
On 2023-06-18 01:37, Carlos E. R. wrote:
On 2023-06-18 00:38, Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Or you could write a text file named something like "notes for version upgrade".... ;)
Yeah, well. The machine is on another location, 30 Km away. I have to remember to type it when I get there :-P -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
* Carlos E. R. <robin.listas@telefonica.net> [06-18-23 08:12]:
On 2023-06-18 10:06, Darryl Gregorash wrote:
On 2023-06-18 01:37, Carlos E. R. wrote:
On 2023-06-18 00:38, Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Or you could write a text file named something like "notes for version upgrade".... ;)
Yeah, well. The machine is on another location, 30 Km away. I have to remember to type it when I get there :-P
you mean when you forget that ssh is just a step away? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
On 2023-06-18 14:55, Patrick Shanahan wrote:
* Carlos E. R. <...> [06-18-23 08:12]:
On 2023-06-18 10:06, Darryl Gregorash wrote:
On 2023-06-18 01:37, Carlos E. R. wrote:
On 2023-06-18 00:38, Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Or you could write a text file named something like "notes for version upgrade".... ;)
Yeah, well. The machine is on another location, 30 Km away. I have to remember to type it when I get there :-P
you mean when you forget that ssh is just a step away? There is no ssh to the site.
Two reasons: 1. I power off everything when I leave 2. The ISP there is using CGNAT, ie, the address is a 10.*.*.*, non routable on internet, not reachable from outside. https://en.wikipedia.org/wiki/Carrier-grade_NAT -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. composed on 2023-06-18 09:37 (UTC+0200):
Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Reading https://en.opensuse.org/SDB:Linuxrc as a matter of course before upgrading might help the memory. So could including it in your current grub.cfg & /etc/default/grub. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2023-06-18 11:28, Felix Miata wrote:
Carlos E. R. composed on 2023-06-18 09:37 (UTC+0200):
Felix Miata wrote:
Carlos E. R. composed on 2023-06-17 17:23 (UTC+0200)
It even probes the floppy drive. maybe ten times. And not only while starting, also while upgrading grub or the kernel.
Cmdline option BrokenModules=floppy will prevent that.
Too late. And I will forget the next year.
Reading https://en.opensuse.org/SDB:Linuxrc as a matter of course before upgrading might help the memory. So could including it in your current grub.cfg & /etc/default/grub.
I only need it for the DVD install image. The problem is remembering that I should better disable the floppy, not really how to do it ;-) Anyhow, that particular machine is USB-2, just booting the image from USB takes half an hour, and the floppy isn't the only hurdle. Just reading the initrd takes over 10 minutes (guessing, didn't occur to me to time it, and anyway, I went to do things meanwhile). And I had to do 4 boots... 1. Boot rescue to edit log files to add an entry "upgraded to 15.5 here" 2. Boot install media (upgrade). It crashed, locked after 300 rpm installed. 3. Boot rescue to consider whether I should recover from backup. 4. Boot install media (upgrade). -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. composed on 2023-06-18 13:46 (UTC+0200):
Felix Miata wrote:
Reading https://en.opensuse.org/SDB:Linuxrc as a matter of course before upgrading might help the memory. So could including it in your current grub.cfg & /etc/default/grub.
I only need it for the DVD install image. The problem is remembering that I should better disable the floppy, not really how to do it ;-)
Disable floppy in BIOS for normal use. If and when you actually need to use floppy, reboot into BIOS to enable, and when done with floppy, reboot into BIOS to again disable. My OS/2 box is the only one on which I keep floppy enabled in BIOS. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2023-06-18 14:03, Felix Miata wrote:
Carlos E. R. composed on 2023-06-18 13:46 (UTC+0200):
Felix Miata wrote:
Reading https://en.opensuse.org/SDB:Linuxrc as a matter of course before upgrading might help the memory. So could including it in your current grub.cfg & /etc/default/grub.
I only need it for the DVD install image. The problem is remembering that I should better disable the floppy, not really how to do it ;-)
Disable floppy in BIOS for normal use. If and when you actually need to use floppy, reboot into BIOS to enable, and when done with floppy, reboot into BIOS to again disable. My OS/2 box is the only one on which I keep floppy enabled in BIOS.
I know how to do that, but again, the problem is remembering after waiting half an hour for the machine to boot and start yast that I should have disabled the floppy. Rebooting to disable the floppy is _another_ half an hour. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. composed on 2023-06-18 14:06 (UTC+0200):
Felix Miata wrote: ...
Disable floppy in BIOS for normal use.... ^^^^^^ I know how to do that, but again, the problem is remembering after waiting half an hour for the machine to boot and start yast that I should have disabled the floppy. Rebooting to disable the floppy is _another_ half an hour.
On next boot, disable floppy in BIOS. Leave it that way. If and when floppy is actually needed, reboot to turn on, use floppy, then reboot to turn it back off. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On 2023-06-18 14:22, Felix Miata wrote:
Carlos E. R. composed on 2023-06-18 14:06 (UTC+0200):
Felix Miata wrote: ...
Disable floppy in BIOS for normal use.... ^^^^^^ I know how to do that, but again, the problem is remembering after waiting half an hour for the machine to boot and start yast that I should have disabled the floppy. Rebooting to disable the floppy is _another_ half an hour.
On next boot, disable floppy in BIOS. Leave it that way. If and when floppy is actually needed, reboot to turn on, use floppy, then reboot to turn it back off.
Nah... :-) -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
participants (8)
-
Bengt Gördén -
Bill Swisher -
Carlos E. R. -
Darryl Gregorash -
Felix Miata -
J Leslie Turriff -
Patrick Shanahan -
Peter McD