While digging around here I saw that update-grub will lead to a lockup
every time. So I simply changed /usr/sbin/grub-mkconfig script to
allow me to see everything that happens.
That gets me to :
/usr/sbin/grub-probe --device /dev/sda2 --target=fs_uuid
which falls to pieces perfectly :
On 3/14/21 5:52 PM, John Paul Adrian Glaubitz wrote:
> On 3/14/21 6:48 PM, Frank Scheiner wrote:
>>> So, if, for example, you want to verify that the memory is okay, you should
>>> run
>>> a memtest program.
>>
>> ...the built-in (memory) diagnostics of Sun machines are pretty
>> thorough. This
On 3/14/21 6:48 PM, Frank Scheiner wrote:
>> So, if, for example, you want to verify that the memory is okay, you should
>> run
>> a memtest program.
>
> ...the built-in (memory) diagnostics of Sun machines are pretty
> thorough. This is not a PC. :-)
I doubt that the hardware runs a thorough
On 14.03.21 18:21, John Paul Adrian Glaubitz wrote:
On 3/14/21 5:55 PM, Mike Tremaine wrote:
Let’s assume it’s not hardware, Dennis has posted the tests and states
the machine ran Sol10 fine.
The fact that Solaris runs fine can be an indicator the hardware is okay, but
it's not a proper
On 3/14/21 5:55 PM, Mike Tremaine wrote:
> Let’s assume it’s not hardware, Dennis has posted the tests and states
> the machine ran Sol10 fine.
The fact that Solaris runs fine can be an indicator the hardware is okay, but
it's not a proper verification that it's actually the case.
For example,
Let’s assume it’s not hardware, Dennis has posted the tests and states the
machine ran Sol10 fine. My only ideas are
1) Try using apt to update some individual packages to see if that even works.
Try dash and bash and whatever but avoid Systemd and any related libraries.
2a) If those succeed
6 matches
Mail list logo
