To make a long story short, my laptop screen died, so I bought a new laptop.
I installed Fedora 25. Then I wanted to copy my old stuff off of the old
(Fedora 23) so I took the drive out and put it into a USB container and
The first problem is that its got a logical volume,
and its name is duplicated with the current name ('fedora').
Searching the web I find that I have to rename the old volume to something
a) I used 'pvs' to determine the device names and to see the sizes,
b) I then used 'vgs -d vg_all' to find the UUID that matched the sizes
of the device I needed to alter.
c) Having the UUID, I then used 'vgrename UUID fedora_old'
d) Then I needed 'ls /dev/fedora_old' to see the 'sub-device' called
e) That let me 'mount /dev/fedora_old/root00 mydir'
That was good enough to allow me to copy some of my data off,
but it wasn't showing anything in /home/fulko.
My next step was to plug an external monitor into that old laptop
and reboot, and try to FTP the remainder of my data from /home/fulko.
That didn't work because the volume name was now changed.
So I had to change it back.
I booted an F23 live CD, used 'vgs' to find the UUID, and the 'vgrename'
to rename it back to 'fedora'.
Rebooting with the drive, now fails with the following error messages:
Failed to start File System Check on /dev/mapper/fedora-root00
See 'systemctl status systemd-fsck-root.service' for details.
Dependency failed for /sysroot.
Dependency failed for Initrd Root File System
Dependency failed for Reload Configuration from the Real Root.
and then goes into emergency mode.
Following the instructions in those error messages, I used 'sytemctl'
to see what I could see, and it says:
/dev/mapper/fedora-root00: Inode 1317765, end of extent exceeds allowed
(logical block 128, physical block 7479168, len 15)
/dev/mapper/fedora-root00: UNEXPECTED INCONSISTENCY: run FsCK manually.
(i.e. without -a or -p options) fsck failed with error code 4.
Running request emergency.target/start/replace
I'm afraid of running fsck on it to resolve whatever problems it may have,
(because I'm afraid of screwing it up even more)
and on the other hand, what did I do wrong to get problems in the place?
Comments and suggestions will be more than welcome.
Thanks in advance.
----- Original Message -----
From: Cheng Rk [mailto:email@example.com]
Sent: Mon, 20 Feb 2017 23:08:32 +0000 (UTC)
Subject: Re: question about packages
then a question is why don't you (Fedora) make a a vim package since `dnf install vim` is such a high demand?
It is available to install quite easily if you look for it.
[root@hostname ~]# dnf list vim\*
Last metadata expiration check: 0:32:16 ago on Tue Feb 21 04:50:08 2017.
vim-common.x86_64 2:8.0.329-1.fc25 @updates
vim-enhanced.x86_64 2:8.0.329-1.fc25 @updates
vim-filesystem.x86_64 2:8.0.329-1.fc25 @updates
vim-minimal.x86_64 2:8.0.329-1.fc25 @updates
Running Fedora 25 with a Mate desktop environment. I ran
the same on F24 and still do on another system. I would
prefer to use compiz as my window manager. However it is
unusable. If I move a window, images trail the movement
and remain when I stop. Popup menus don't disappear when
I make a selection. Killing a window does not cause its
image to disappear.
All the residual garbage is cleaned up if I change
workspaces and change back again. But the desktop
wallpaper is gone too.
I don't run any of compiz' fancy features, wobbly
Any idea what might cause this problem?
Jon H. LaBadie jonfu(a)jgcomp.com
i can install the package 'vim' via `sudo dnf install vim` but there is no package called vim in the list returned by `dnf search vim`.
is there a way to get the real package name given the name vim? (i want a generic way to resolve such a name).
I have a fairly embarrassing problem : just upgraded from F24 to F25
using 'dnf system-upgrade'. Everything works as smooth as expected...
except... when I close Remmina OR when I lock my screen while Remmina is
running, Gnome-Shell crashes and gets me back to the login screen,
losing everything I had on screen.
Have you experienced this ? What could I provide to help solve this ?
I frequently get bitten by bug *1401166*
The author closed the bug as WONTFIX because of some personal issues he
had/has with the original reporter.
Could somebody with the permissions please reopen the bug, so other users
who run into this problem can report?
To test out dkms compiling and installing my wifi driver I have
uninstalled the driver from the kernel with dkms, removed the driver
from dkms and re-added the driver to dkms.
When I boot Fedora dkms compiles and installs the driver into the
kernel but it does not issue a modprobe to actually load the driver, how
do I force dkms to do so, or alternatively am I missing the package that
would provide that functionality?
my computer boot only in emergency mode ...
Looking the journalctl (command journalctl -xb), I found (in thejournalctl
) these lines in red color :
ATA2:00: link is slow to respond....
ATA200: SRST failed (erro 16)
That seem indicate that it is a problem to access the HDs..
I found a possible solution to the problem in this post:
There is wrote that :...the problem can depend by the physic set up of the
HD (as "master", "slave", "single drive", ...): this set up can be done by
changing the position of a jumper on the HD...
I know that, in the past time, the HDs had to be set physically in this
way.., but recently I never heart anymore that the modern HD need this
So actually I don't care anymore of the configuration of the HDs
(my HD is Toshiba 1 TB that I bought few mounts ago).
I would like to have a confirmation that what I read in the post is only an
obsolete information and, in any case, I would like to know also what I can
do to go around in my problem..
>From the command line: ls /dev/sd* I get:
give me this input :
/dev/sda /dev/sda1 /dev/sda2 /dev/sda5 /dev/sdb /dev/sdb1
I'm not sure where I ought to post this; if there's still a
Mailman list, it's not carried by Gmane. And even if there is, this may be
a Fedora question.
On my own domain (not Comcast) I've been running three lists under
Mailman for a good many years and Fedora releases. Two of them are still
The third went into abeyance five years back. I want to resume it,
or maybe start a replacement, with at least some of the former
subscribers. But I never wrote the listowner password down, and of course
I've forgotten it.
I have both user access and root access to my domain, but no GUI,
and the only way I've ever done anything with Mailman is through the GUI.
Is there some way to use the CLI to find the list and set a dummy
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.
Every so often, when I run "dnf -y update" in a terminal,
these messages will show up:
[root@zooty ~]# dnf -y update
BDB2053 Freeing read locks for locker 0x7a: 5771/139940940851008
BDB2053 Freeing read locks for locker 0x7c: 5771/139940940851008
BDB2053 Freeing read locks for locker 0x7d: 5771/139940940851008
BDB2053 Freeing read locks for locker 0x7e: 5771/139940940851008
Anyone know what that's about? The only way I ever update
the system is with the dnf update command. No weird
installing rpms behind dnf's back or anything, so why
are there sometimes readlocks?
Just curiosity here, they don't seem to hurt anything.