On Sun, Jun 9, 2024 at 7:47 AM Klaus-Peter Schrage via users
wrote:
> What I don't understand: What produced the entry "resume=UUID=8e895..."
> in the file /etc/default/grub which was created on the install date, May
> 3rd?
Do you have a /etc/kernel/cmdline file? I was tripped-up recently
becaus
> On 9 Jun 2024, at 13:06, Klaus-Peter Schrage via users
> wrote:
>
> What I already mentioned: It doesn't hang on kernel 6.8.9, only on more
> recent ones, with everything else left constant (e. g. no boot partition).
> --
The latest kernels require that resume= refers to an existing partit
Am 09.06.2024 um 15:22 schrieb Felix Miata:
Klaus-Peter Schrage via users composed on 2024-06-09 13:47 (UTC+0200):
What I don't understand: What produced the entry "resume=UUID=8e895..."
in the file /etc/default/grub which was created on the install date, May
3rd
Does your fstab or installati
Klaus-Peter Schrage via users composed on 2024-06-09 13:47 (UTC+0200):
> What I don't understand: What produced the entry "resume=UUID=8e895..."
> in the file /etc/default/grub which was created on the install date, May
> 3rd
Does your fstab or installation media or any other media used during or
Am 08.06.24 um 22:27 schrieb Jeffrey Walton:
On Sat, Jun 8, 2024 at 12:20 PM Klaus-Peter Schrage via users
wrote:
Since kernel 6.8.10-300.fc40.x86_64, boot hangs on KDE Plasma (kernel
6.8.9-300.fc40.x86_64 was the last good one).
I found that there is a job running infinitely:
'Job dev-disk-b
Am 08.06.24 um 22:04 schrieb Samuel Sieb:
On 6/8/24 9:20 AM, Klaus-Peter Schrage via users wrote:
This is a rather fresh install of fedora 40 (running on ext4):
da 8:0 0 232,9G 0 disk
├─sda1 8:1 0 1,1G 0 part /boot
├─sda2 8:2 0 49,1G 0 part /
├─sda3 8:3 0 31,7G 0
Am 08.06.24 um 19:52 schrieb Michael D. Setzer II:
On 8 Jun 2024 at 18:20, Klaus-Peter Schrage via users wrote:
might want to run blkid and see what it reports.
The output is similar to yours, but
# blkid | grep -i 8e8952
#
shows that there isnt any device with an UUID containing 8e8952... (t
Am 08.06.24 um 19:04 schrieb Felix Miata:
Klaus-Peter Schrage composed on 2024-06-08 18:20 (UTC+0200):
Does any device within your system actually include 8e895whatever within it?
No, there isn't any block device with an UUID (or PARTUUID) that
includes 8e895
Did you previously have a swap par
George,
On 2024-06-09 20:36, George N. White III wrote:
On Sat, Jun 8, 2024 at 4:35 PM Philip Rhoades via users
wrote:
[...]
What I don't understand is that when creating the snapshots
originally,
the time to create them is almost zero but when using btrfs send to
the
other partition the tim
On Sat, Jun 8, 2024 at 4:35 PM Philip Rhoades via users <
users@lists.fedoraproject.org> wrote:
> [...]
> What I don't understand is that when creating the snapshots originally,
> the time to create them is almost zero but when using btrfs send to the
> other partition the times are _much_ longer.
ok, I will take this back.
I just logged into cockpit with Administrative access and it is not
complaining at all about things not being mounted.
Weird.
On Sun, Jun 9, 2024 at 3:10 AM Javier Perez wrote:
> Hi.
>
> I just finished a new build to replace my current build. After installing
> cockp
Hi.
I just finished a new build to replace my current build. After installing
cockpit, and checking Storage, i noticed some warnings about the disks. It
claims that /root, /home and /var are not mounted. I think they are. I just
wonder if I am doing something wrong or weird here and I'd appreciate
12 matches
Mail list logo
