fedup F18 => F20 failed, can't find (encrypted) partitions
by Dave Mitchell
I just tried doing a fedup F18 to F20; the fedup itself worked fine
(apart from from a few warnings about GPG keys), but booting from the
'System Upgrade' grub entry failed early on, not being able to find
any of my system's filesystems. I suspect this is due to them being LUKS
encrypted (these filesystems were all created by the F18 anaconda
installer using the defaults and ticking 'Encrypt').
Under F18:
# rpm -q fedup
fedup-0.8.0-3.fc18.noarch
# hostname
robin
# df -h
Filesystem Size Used Avail Use% Mounted on
devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs 3.9G 196K 3.9G 1% /dev/shm
tmpfs 3.9G 5.3M 3.9G 1% /run
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/mapper/fedora_robin-root 50G 8.7G 38G 19% /
tmpfs 3.9G 44K 3.9G 1% /tmp
/dev/sda2 477M 248M 200M 56% /boot
/dev/sda1 200M 7.9M 192M 4% /boot/efi
/dev/mapper/fedora_robin-home 178G 54G 116G 32% /home
# cat /etc/crypttab
luks-ffa7256c-bd83-40f6-ba54-40db40e60cf2 UUID=ffa7256c-bd83-40f6-ba54-40db40e60cf2 none
When booting from the 'System Upgrade' boot entry, the screen clears, then
(in text mode) I get the following (this is hand-typed):
[ 4.797465] dracut-initqueue[426]: Failed to issue method call: Access denied
[ OK ] Started Show Plymouth Boot Screen
[ OK ] Reached target paths
It then sat doing nothing for a few minutes; I then pressed ESC, and the
following extra appeared:
[ 4.797465] dracut-initqueue[426]: Failed to issue method call: Access denied
[ OK ] Started Show Plymouth Boot Screen
[ OK ] Reached target paths
[ 197.600895] dracut-initqueue[426]: Warning: Could not boot.
[ 4.797465] dracut-initqueue[426]: Failed to issue method call: Access denied
[ OK ] Started Show Plymouth Boot Screen
[ OK ] Reached target paths
[ 197.600895] dracut-initqueue[426]: Warning: Could not boot.
[ 197.604308] dracut-initqueue[426]: Warning: /dev/fedora_robin/root does not exist
[ 197.604902] dracut-initqueue[426]: Warning: /dev/fedora_robin/swap does not exist
[ 197.605328] dracut-initqueue[426]: Warning: /dev/mapper/fedora_robin-root does not exist
Starting Dracut Emergency Shell...
Warning: /dev/fedora_robin/root does not exist
Warning: /dev/fedora_robin/swap does not exist
Warning: /dev/mapper/fedora_robin-root does not exist
Generating "/run/initramfs/rdsosreport.txt"
Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or
/boot
after mounting them and attach it to a bug report.
The "/run/initramfs/rdsosreport.txt" file is 1400 lines long, so I haven't
attached it here; however, perusing it, this line stands out:
[ 4.797399] localhost systemd[1]: Failed to get security context on /etc/crypttab: No such file or directory
Anyone got any ideas what I should do next?
--
Red sky at night - gerroff my land!
Red sky at morning - gerroff my land!
-- old farmers' sayings #14
10 years, 5 months
Re: selinux=0
by Patrick Dupre
Thank,
It works.
>
> On Sun, 29 Dec 2013 14:40:26 +0100, Patrick Dupre wrote:
>
> > Hello,
> >
> > After cloning a distribution fedora 19, I have to set selinux=0
> > to be able to boot.
> > How can I do to avoid this option?
> > I tried:
> > fixfiles relabel
> > system-config-selinux
> >
> > But I never get a relabelling!
> >
> > What should I do?
>
> Have you tried booting with "enforcing=0" instead of "selinux=0" yet?
> If you disable SELinux completing, you cannot hope that anything will
> work related to file labelling.
> --
> users mailing list
> users(a)lists.fedoraproject.org
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
> Have a question? Ask away: http://ask.fedoraproject.org
===========================================================================
Patrick DUPRÉ | | email: pdupre(a)gmx.com
Laboratoire de Physico-Chimie de l'Atmosphère | |
Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44
189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===========================================================================
10 years, 5 months
New external harddrive and 106Mb unallocated - why
by Robert Moskowitz
I just got a Toshiba Canvio Desk 2TB external HD that my plans are to
delete the NTFS partition and put on an EXT4 one.
Thing is the first 106MB are unallocated. Why?
If this was a Chinese product, I would be worried. I actually found a
'call home' USB stick once. One MIGHT think that Toshiba has decent
quality control. But why the unallocated space; is this for sector
replacement?
Actually, I probably would not delete the partition, but only reformat
it as EXT4.
Seems to be a rather nice unit. Drive did not power up until I
connected the USB; very convient not to have to unplug it to save on
power usage.
10 years, 5 months
Updated to 19; now kernel panic on boot. No log
by sean darcy
Updated to F19, kernel-3.12.5-200.fc19.x86_64.
On boot I get a kernel panic around [2.2]. The trace that's on the
screen is about smp, timers, hpet. Can't read quickly enough to see what
actually happened.
/var/log/messages has no log of the kernel boot. Shouldn't there be one?
rsyslogd.conf seems to be set to put it all in syslog:
# Log anything (except mail) of level info or higher.
# Don't log private authentication messages!
*.info;mail.none;authpriv.none;cron.none /var/log/messages
I can boot with the F18 kernel. syslog there shows logging started right
at boot:
Dec 29 18:04:06 new-gateway rsyslogd: [origin software="rsyslogd"
swVersion="7.2.6" x-pid="424" x-info="http://www.rsyslog.com"] start
Dec 29 18:04:06 new-gateway systemd-cgroups-agent[226]: Failed to get
D-Bus connection: Failed to connect to socket
/org/freedesktop/systemd1/private: Conn
ection refused
Dec 29 18:04:06 new-gateway systemd[1]: systemd 204 running in system
mode. (+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP
+GCRYPT +ACL +XZ)
Dec 29 18:04:06 new-gateway systemd[1]: Set hostname to
<new-gateway.11hidden>.
Dec 29 18:04:06 new-gateway systemd[1]: Starting LVM2 metadata daemon...
Dec 29 18:04:06 new-gateway systemd-sysctl[248]: Overwriting earlier
assignment of kernel/sysrq in file '/etc/sysctl.conf'.
Dec 29 18:04:06 new-gateway systemd[1]: Started Apply Kernel Variables.
Dec 29 18:04:06 new-gateway systemd[1]: Started Setup Virtual Console.
Dec 29 18:04:06 new-gateway systemd[1]: Started Create static device
nodes in /dev.
Dec 29 18:04:06 new-gateway systemd[1]: Started LVM2 metadata daemon.
Dec 29 18:04:06 new-gateway systemd[1]: Starting udev Kernel Device
Manager...
Dec 29 18:04:06 new-gateway systemd[1]: Mounted POSIX Message Queue File
System.
Dec 29 18:04:06 new-gateway kernel: [ 0.000000] Initializing cgroup
subsys cpuset
Dec 29 18:04:06 new-gateway kernel: [ 0.000000] Initializing cgroup
subsys cpu
Dec 29 18:04:06 new-gateway kernel: [ 0.000000] Initializing cgroup
subsys cpuacct
Dec 29 18:04:06 new-gateway kernel: [ 0.000000] Linux version
3.11.10-100.fc18.x86_64 (mockbuild@bkernel02) (gcc version 4.7.2
20121109 (Red Hat 4.7.2-8
) (GCC) ) #1 SMP Mon Dec 2 20:28:38 UTC 2013
Or does the error about the D-Bus connection cause logging to fail?
Any help appreciated.
sean
10 years, 5 months
CentOS HowTos
by Timothy Murphy
The document <http://wiki.centos.org/HowTos> says
"This page contains some longer HowTos
for achieving different tasks on CentOS systems".
Unfortunately, the document consists of a single page,
and does not seem to contain any links to the HowTos it refers to.
I'm looking in particular for the HowTo on E-Mail.
(I'm looking for advice on the best way to filter out spam email
already marked as such by SpamAssassin, called by amavis.
I assume there must be a standard way of doing this,
but have been unable to find it in the documentation I have looked at,
eg <<http://wiki.centos.org/HowTos/Amavisd>.)
--
Timothy Murphy
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland
10 years, 5 months
Re: CentOS HowTos
by Peter Skensved
>
> No, I'm not trying to build a proper mail-server.
> I collect email on my server from various (remote) mail-servers.
> This is then processed by postfix/amavis/clamav/spamassassin .
> Spam is marked by addition of [SPAM] or ***Spam*** to the Subject header,
> as well as addition of several other headers.
>
> As I understand it, the email is then passed through dovecot(?),
> to ~/Maildir/cur/ .
Dovecot just does pop/imap _after_ the mail is delivered to mbox or Maildir/...
A simple way to do things is postfix->procmail->spamassassin . It works on a per
user basis the . And you can tweak spamassassin to sort by score :
spam
almost-certainly-spam
probably-spam
mbox
With a bit of training ( sa-learn --ham mbox / sa-learn --spam spam say
once a month ) you quickly get down to a few false positive/negative per year.
All the configuration is done in .forward and .procmailrc
Not sure how to do it with Maildir though ...
>
> This must be a standard setup.
> So how normally is spam dealt with, at this stage?
> You seemed to be suggesting that it could be dealt with earlier, by amavis?
> Or it could be left to the client MUA, KMail in my case?
> What is the norm?
>
Ah - but there are so many "standards" .......
peter
10 years, 5 months
gnome, gnome-terminal desktop icon oddity
by Ed Greshko
The thread with the subject of "gnome-terminal in F20 defaults to / for the initial directory" prompted me to do some testing and I've found an oddity.
The desktop file is as follows...
[egreshko@f20f ]$ cat Desktop/gnome-terminal.desktop
[Desktop Entry]
Comment[en_US]=
Comment=
Exec=/usr/bin/gnome-terminal --working-directory=$HOME/Desktop
GenericName[en_US]=Gnome Terminal
GenericName=Gnome Terminal
Icon=utilities-terminal
MimeType=
Name[en_US]=gnome-terminal
Name=gnome-terminal
StartupNotify=true
Terminal=false
TerminalOptions=
Type=Application
X-DBUS-ServiceName=
X-DBUS-StartupType=
X-KDE-SubstituteUID=false
X-KDE-Username=
If I click on the desktop icon in KDE the --working-directory option is honored.
However, if I double click on the desktop icon in GNOME that parameter has no effect unless I replace $HOME with the actual path name. So, for some reason GNOME is not expanding the $HOME variable.
Also, if I execute "/usr/bin/gnome-terminal --working-directory=$HOME/Desktop" from within an existing terminal session $HOME will be expanded.
https://bugzilla.redhat.com/show_bug.cgi?id=1047116
Ed
--
Getting tired of non-Fedora discussions and self-serving posts
10 years, 5 months
balsa is unthemed
by Tony Nelson
The balsa email program draws unthemed on my system after upgrading to
F20. Actually, the adwaita theme works, but none of the other themes
do. I get no complaints from Gtk in .xsession-errors or journalctl when
changing themes. Other programs are OK.
Does anyone else see this or know what it is?
How to debug it?
--
____________________________________________________________________
TonyN.:' <mailto:tonynelson@georgeanelson.com>
' <http://www.georgeanelson.com/>
10 years, 5 months
My fedup upgrade from F18 to F20, or "When Sendmail won't start"
by Tony Nelson
I have upgraded my system from F18 to F20 with fedup. Last year I
upgraded from F16 to F18 with preupgrade and fedup, and it did not go
well. This time was much better.
The boot option to upgrade did not appear until I rebuilt the grub2 menu
with:
grub2-mkconfig -o /boot/grub2/grub.cfg
I should note that grub2 was not properly configured to its current
set//
of modules, even though all packages were up to date (including grub2
and grub2-tools), and:
grub2-install /dev/sda
was needed to fix that.
After the upgrade, sendmail would not start. (Actually it would start
but was then stopped.) This turned out to be a problem with usrmove
from the F16 to F18 upgrade. All of it had been done except the move of
/var/run/ to /run/ and /var/lock/ to /run/lock/. Systemd was OK with
this on F18 (I don't know why) but not on F20. Booting single-user
(append 1 to kernel command line) and then:
cp -an /var/run /run # probably unneeded
cp -an /var/lock /run/lock # probably unneeded
rm -rf /var/run ; ln -s /run /var/run
rm -rf /var/lock ; ln -s /run/lock /var/lock
reboot
fixed the problem and sendmail started properly after that.
It all didn't go quite this smoothly, and next time I will burn a live
cd before upgrading. (I did eventually get the xfce spin. The Midori
web browser really doesn't work, so I had to get elinks in order to
search and browse the web from the live cd.)
--
____________________________________________________________________
TonyN.:' <mailto:tonynelson@georgeanelson.com>
' <http://www.georgeanelson.com/>
10 years, 5 months
