Re: TW slow to process "post trans script" grub2-i386????
"post trans script of grub2-i386 xxxx" for what turned out to be roughly 35 minutes . . . .
Only a tiny part of grub2 is written such that the to be performed task is done in the most efficient way.
Try to run 'ps fax' a few times to see what this posttrans script is doing. Most likely something will hang in D state.
Olaf
Only a tiny part of grub2 is written such that the to be performed task is done in the most efficient way.
Try to run 'ps fax' a few times to see what this posttrans script is doing. Most likely something will hang in D state.
os-probe can take very long, specially if you have many partitions. And some types makes os-prober to loose its mind.
-- Cheers / Saludos,
Carlos E. R.
Gents: Thanks for the replies on it . . . considering that most people on this list-serve would say that "code is impassionate and only does what it is told to do" . . . it sounds like "excuses for the misbehaviors of grub2" are being provided??? : - ))) Previously I thought it was the zypper processing of packages, i.e., total number of packages being processed, that was at issue . . . now it doesn't seem to have anything to do with that. TW does process the actual upgrades very quickly, as does the '12 machine. Today is "Sid" day, and Sid ran 46 packages through in roughly 1 minute. The difference there is that Sid isn't the grub handler, TW is. As far as the "os-prober loses its mind" concept . . . could be, but then we have the "it loses its mind at different places" . . . at the first post on this topic I wasn't watching where in the 1.5 hours to upgrade 150 packages the process was "hanging." Yesterday it got stuck on a dracut on a package in the middle of the packages being upgraded, and the time on Sunday it was the "post trans script" after the packages were installed . . . . There are 8 linux distros installed across three drives, with a few OSX in each; if I plug my Super Grub2 usb drive in and boot to that, it finds every system that was ever installed and every kernel in less than a minute, so why is it that os-prober needs a variable 40 minutes to 180 minutes to refreshen itself??? PS: Thanks for the link to the question asked on the **forum** about "Why i386?" . . . that does explain it; "Head_on_a_Stick" has also addressed some of my Sid issues on their forum, seems to be a reliable source of information.
Fritz Hudnut composed on 2023-03-15 09:15 (UTC-0700):
There are 8 linux distros installed across three drives, with a few OSX in each; if I plug my Super Grub2 usb drive in and boot to that, it finds every system that was ever installed and every kernel in less than a minute, so why is it that os-prober needs a variable 40 minutes to 180 minutes to refreshen itself???
Output from fdisk -l or parted -l might explain. -- 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-03-15 18:25, Felix Miata wrote:
Fritz Hudnut composed on 2023-03-15 09:15 (UTC-0700):
There are 8 linux distros installed across three drives, with a few OSX in each; if I plug my Super Grub2 usb drive in and boot to that, it finds every system that was ever installed and every kernel in less than a minute, so why is it that os-prober needs a variable 40 minutes to 180 minutes to refreshen itself???
Output from fdisk -l or parted -l might explain.
Just try to run os-prober on its own and time it. -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. composed on 2023-03-15 20:55 (UTC+0100):
Felix Miata wrote:
Fritz Hudnut composed on 2023-03-15 09:15 (UTC-0700):
...a few OSX in each...
Output from fdisk -l or parted -l might explain.
Just try to run os-prober on its own and time it.
That may place the immediate blame, but not a possibly underlying lack of support for for every type of MacOS filesystem, or who know what else MacOS puts on or does with its disks. Compatibility with competitive OSes is not an Apple strength or goal. -- 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-03-15 22:19, Felix Miata wrote:
Carlos E. R. composed on 2023-03-15 20:55 (UTC+0100):
Felix Miata wrote:
Fritz Hudnut composed on 2023-03-15 09:15 (UTC-0700):
...a few OSX in each...
Output from fdisk -l or parted -l might explain.
Just try to run os-prober on its own and time it.
That may place the immediate blame, but not a possibly underlying lack of support for for every type of MacOS filesystem, or who know what else MacOS puts on or does with its disks. Compatibility with competitive OSes is not an Apple strength or goal.
Is he using Apple hardware? I didn't notice. Then of course, that's the cause of the problem. Yes, now I notice "OSX" above; it is not "OSes". -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Carlos E. R. composed on 2023-03-15 20:55 (UTC+0100):
Felix Miata wrote:
Fritz Hudnut composed on 2023-03-15 09:15 (UTC-0700):
...a few OSX in each...
Output from fdisk -l or parted -l might explain.
Just try to run os-prober on its own and time it.
That may place the immediate blame, but not a possibly underlying lack of support for for every type of MacOS filesystem, or who know what else MacOS puts on or does with its disks. Compatibility with competitive OSes is not an Apple strength or goal.
Is he using Apple hardware? I didn't notice. Then of course, that's the cause of the problem. Yes, now I notice "OSX" above; it is not "OSes". et al: The scourge of using linux on Apple hardware . . . !!! Mr Miata has pointed out the "apple" problem before, but I have been running grub on this machine for years without the level of slowness in the processing that seems to have crept in recently . . . to an extent that is diffficult to provide the time for. I don't use grub to boot OSX, so nothing in OSX is connected back into grub . . . . But, indeed it might be interesting to just run "os-prober" and see how long that takes . . . or, when I get a minute flip grub2 out of TW and into Leap or some other system and see how that goes . . . that way I can see whether something specific to TW is taking its time to process, or whether "everybody" is confused while running grub in this Macintosh? F
On 2023-03-15 22:47, Fritz Hudnut wrote:
Carlos E. R. composed on 2023-03-15 20:55 (UTC+0100):
Felix Miata wrote:
Fritz Hudnut composed on 2023-03-15 09:15 (UTC-0700):
...a few OSX in each...
Output from fdisk -l or parted -l might explain.
Just try to run os-prober on its own and time it.
That may place the immediate blame, but not a possibly underlying lack of support for for every type of MacOS filesystem, or who know what else MacOS puts on or does with its disks. Compatibility with competitive OSes is not an Apple strength or goal.
Is he using Apple hardware? I didn't notice. Then of course, that's the cause of the problem.
Yes, now I notice "OSX" above; it is not "OSes".
et al:
The scourge of using linux on Apple hardware . . . !!! Mr Miata has pointed out the "apple" problem before, but I have been running grub on this machine for years without the level of slowness in the processing that seems to have crept in recently . . . to an extent that is diffficult to provide the time for. I don't use grub to boot OSX, so nothing in OSX is connected back into grub . . . .
AFAIK, it is not grub, it is os-prober, which is run by part of the grub installation process to find out what other bootable partitions are there. And as I recall, some types of partitions drive os-prober bonkers. AFAIK, that includes some Apple partitions. Of course, you can simply not run os-prober, ever again, and create manual entries in grub for whatever other bootable partitions you have, in /boot/grub2/custom.cfg.
But, indeed it might be interesting to just run "os-prober" and see how long that takes . . . or, when I get a minute flip grub2 out of TW and into Leap or some other system and see how that goes . . . that way I can see whether something specific to TW is taking its time to process, or whether "everybody" is confused while running grub in this Macintosh?
F
-- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
participants (3)
-
Carlos E. R. -
Felix Miata -
Fritz Hudnut