Re: OT: SSD or not to SSD, that is the question

Rick Stevens wrote: >> SSDs are fast, but when they die, it's typically sudden, with no >> warning, catastrophic and irrecoverable. Tom Horsley: > You mean just like every "normal" hard disk I've ever had die? (OK, > one did get smart errors first, but all the others just went kaput > with no

Re: dracut fails to build bootable initramfs on fc22

On 09.09.2015, Alex wrote: > I have a fc22 system that's been working fine and now for some reason > kernel updates result in an unbootable system. It appears to be > related to dracut failing to build a proper initramfs image. I've never used any distribution kernel, and on my F22, there is no

Trouble with nfs4 mount

Since I upgraded my system (new CPU, motherboard, and power supply on system amito) nfs mounts have failed; they were working fine till the upgrade. Here's the situation; all the commands were run on amito: $ cat /etc/fstab ... # NFS Mounts weather:/

Re: NTP synchronized: no

Hello, According to the domain administrator, the port is open. Could it be an issue with the firewall? iptables -L |grep udp ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns ctstate NEW ACCEPT udp -- anywhere anywhere udp dpt:ipp ctstate

Re: dracut fails to build bootable initramfs on fc22

I have the same problem. All 4.1 kernels have broken on one particular machine (Dell Precision T7400 with a RAID1 configuration). At this point, I am just waiting for a 4.2 kernel to see if that will fix it. Otherwise, I guess I will have to reinstall. Ranjan On Wed, 9 Sep 2015 10:51:05 -0400

dracut fails to build bootable initramfs on fc22

Hi, I have a fc22 system that's been working fine and now for some reason kernel updates result in an unbootable system. It appears to be related to dracut failing to build a proper initramfs image. I have a default initramfs from 4.0.4-300 that works fine, but using dracut to build a new

Re: After a power cut my machine cannot boot

Paul Smith writes: On Wed, Sep 9, 2015 at 7:26 PM, Joe Zeff wrote: >> >> on a F21 machine, there occured a power cut. And now I cannot boot the >> machine, and when I use the rescue mode and try to run again >> >> yum update > > > I know I'm coming in late, and judging from other

Re: NTP synchronized: no

On 09/10/15 06:18, John Pilkington wrote: > ... and (on my SL7 box) # tcpdump port 123 > shows the outgoing probe and the response, for calculation of the transit > time: > > 23:01:55.706587 IP HP_Box.home.ntp > vpn.webersheim.de.ntp: NTPv3, Client, > length 48 > 23:01:55.741872 IP

Re: NTP synchronized: no

On 09/09/15 23:43, Ed Greshko wrote: On 09/10/15 06:18, John Pilkington wrote: ... and (on my SL7 box) # tcpdump port 123 shows the outgoing probe and the response, for calculation of the transit time: 23:01:55.706587 IP HP_Box.home.ntp > vpn.webersheim.de.ntp: NTPv3, Client, length 48

Re: NTP synchronized: no

> On Sep 9, 2015, at 3:47 PM, John Pilkington wrote: > > On 09/09/15 23:43, Ed Greshko wrote: >> On 09/10/15 06:18, John Pilkington wrote: >>> ... and (on my SL7 box) # tcpdump port 123 >>> shows the outgoing probe and the response, for calculation of the transit >>> time:

Re: After a power cut my machine cannot boot

On 09/09/2015 03:45 PM, Paul Smith wrote: I will try sysresccd, as Heinz advises. In case that does not work, I will reinstall the system. Fortunately, I have a backup of my home directory and all important files! If you have /home on its own partition, you can just reuse it without

Re: After a power cut my machine cannot boot

On 09/09/2015 04:00 PM, Paul Smith wrote: Thanks, Patrick. The default clean installation of F21 does not already install a journaling filesystem? I think that the default is ext4, which is journalling. LVM is also the default, and I've no idea how that handles these things. My advice is,

Re: After a power cut my machine cannot boot

On Wed, Sep 9, 2015 at 11:09 PM, Sam Varshavchik wrote: >> >> >> >> on a F21 machine, there occured a power cut. And now I cannot boot the >> >> machine, and when I use the rescue mode and try to run again >> >> >> >> yum update >> > >> > I know I'm coming in late, and

Re: NTP synchronized: no

On 09/09/2015 03:43 PM, Ed Greshko wrote: Nice to know Yet you really should consider trimming. Otherwise you'll start to prove top-posters right. :-) :-) Indeed. One of my pet peeves is people who respond to something in the middle of a message and then quote the remainder,

Re: NTP synchronized: no

On 09/09/15 22:31, Shaheen Bakhtiar wrote: On Sep 9, 2015, at 12:17 PM, Shaheen Bakhtiar > wrote: On Sep 9, 2015, at 11:00 AM, Rick Stevens > wrote: On 09/09/2015 10:37 AM, Patrick

Re: After a power cut my machine cannot boot

On Wed, 2015-09-09 at 23:45 +0100, Paul Smith wrote: > Is there something, apart buying a UPS, that one can do in order to > minimize the severity of the damage that a power outage can cause? Use a journaling filesystem. poc -- users mailing list users@lists.fedoraproject.org To unsubscribe or

Re: After a power cut my machine cannot boot

On Wed, Sep 9, 2015 at 11:51 PM, Patrick O'Callaghan wrote: > >> Is there something, apart buying a UPS, that one can do in order to >> minimize the severity of the damage that a power outage can cause? > > Use a journaling filesystem. Thanks, Patrick. The default clean

Re: dracut fails to build bootable initramfs on fc22

On Wed, Sep 9, 2015 at 8:51 AM, Alex wrote: > Hi, > > I have a fc22 system that's been working fine and now for some reason > kernel updates result in an unbootable system. It appears to be > related to dracut failing to build a proper initramfs image. > > I have a default

Re: After a power cut my machine cannot boot

Paul Smith writes: Is there something, apart buying a UPS, that one can do in order to minimize the severity of the damage that a power outage can cause? A UPS, paired with auto-shutdown software is the best possible defense against damage due to unexpected power loss. But that's merely a

Accessing Android files from the command line

Xfce's Thundar has no problem accessing my Android phone; as long as I wait a bit. The location information is: mtp://[usb:001,012]/Phone/ But when I copy a file from the phone, I loose the date it was created. I want to copy my audio recordings and keep the date using something like 'cp

VPN: "Necessary secrets were not provided"

Hello, I had my VPN working on my F22 laptop until I changed my institutional password. When I try to edit the connection, the dialog opens initially with the name of the connection being the only field, and it takes half a minute until the rest appears. I entered the new password and

Re: After a power cut my machine cannot boot

On Wed, Sep 9, 2015 at 7:08 PM, Dave Stevens wrote: >> > >> >> "/lib64/libidn.so.11: file too short". >> > >> > Have you repaired your crashed filesystems already? >> > If you have, try "dnf reinstall libidn libidn2". >> >> Thanks for your reply, Heinz. >> >> What can I do to

Re: After a power cut my machine cannot boot

On Wed, Sep 9, 2015 at 7:26 PM, Joe Zeff wrote: >> >> on a F21 machine, there occured a power cut. And now I cannot boot the >> machine, and when I use the rescue mode and try to run again >> >> yum update > > > I know I'm coming in late, and judging from other replies this probably

Re: dracut fails to build bootable initramfs on fc22

Not sure if this is related…. But I had the same problem… it was actually because /etc/fstab used device names (which look like they changed) vs. the UUID of the drive. What is the exact error message(s) you are getting?? Where in the boot process is it failing? > On Sep 9, 2015, at 8:39

After a power cut my machine cannot boot

Dear All, While doing yum update on a F21 machine, there occured a power cut. And now I cannot boot the machine, and when I use the rescue mode and try to run again yum update I get the following error: "/lib64/libidn.so.11: file too short". Any ideas? I have already tried to get the libidn

Re: NTP synchronized: no

On 09/09/2015 10:37 AM, Patrick Dupre wrote: Still the same (always as root) journalctl -u chrony -b -- Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 19:34:53 CEST. -- after systemctl restart chronyd systemctl list-unit-files | grep chrony chrony-wait.service

Re: After a power cut my machine cannot boot

On Sep 9, 2015 1:58 PM, "Paul Smith" wrote: > > On Wed, Sep 9, 2015 at 7:26 PM, Joe Zeff wrote: > >> > >> on a F21 machine, there occured a power cut. And now I cannot boot the > >> machine, and when I use the rescue mode and try to run again > >> > >> yum update

Re: After a power cut my machine cannot boot

On 09/09/2015 01:58 PM, Paul Smith wrote: On Wed, Sep 9, 2015 at 7:26 PM, Joe Zeff wrote: on a F21 machine, there occured a power cut. And now I cannot boot the machine, and when I use the rescue mode and try to run again yum update I know I'm coming in late, and judging from

Print with password

Hello, How can I print a document when the printer requires a password? The printer shows up with cups, but I do not see any option to provide a password? Thank. === Patrick DUPRÉ | | email:

Re: NTP synchronized: no

> On 09/09/2015 08:17 AM, Patrick Dupre wrote: > > Hello, > > > > According to the domain administrator, the port is open. > > Could it be an issue with the firewall? > > > > iptables -L |grep udp > > ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns > > ctstate NEW > >

Re: NTP synchronized: no

On 09/09/2015 10:04 AM, Patrick Dupre wrote: On 09/09/2015 08:17 AM, Patrick Dupre wrote: Hello, According to the domain administrator, the port is open. Could it be an issue with the firewall? iptables -L |grep udp ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns

Re: dracut fails to build bootable initramfs on fc22

OK, for me it is failing right at the very beginning, after it starts booting. I get a bunch of stuff (similar to floating exception, with several 00x333 -- I am making this up, but just to give you an idea). I have graphical boot off (no rhgb quiet) but I get this without much additional

Re: After a power cut my machine cannot boot

On 09.09.2015, Paul Smith wrote: > "/lib64/libidn.so.11: file too short". Have you repaired your crashed filesystems already? If you have, try "dnf reinstall libidn libidn2". -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options:

Re: NTP synchronized: no

Still the same (always as root) journalctl -u chrony -b -- Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 19:34:53 CEST. -- after systemctl restart chronyd systemctl list-unit-files | grep chrony chrony-wait.service disabled chronyd.service

Re: After a power cut my machine cannot boot

On Wed, Sep 9, 2015 at 6:43 PM, Heinz Diehl wrote: > >> "/lib64/libidn.so.11: file too short". > > Have you repaired your crashed filesystems already? > If you have, try "dnf reinstall libidn libidn2". Thanks for your reply, Heinz. What can I do to repair the filesystem? I

Re: After a power cut my machine cannot boot

On Wed, 9 Sep 2015 18:46:59 +0100 Paul Smith wrote: > On Wed, Sep 9, 2015 at 6:43 PM, Heinz Diehl wrote: > > > >> "/lib64/libidn.so.11: file too short". > > > > Have you repaired your crashed filesystems already? > > If you have, try "dnf reinstall libidn

Re: After a power cut my machine cannot boot

On 09/09/2015 10:36 AM, Paul Smith wrote: on a F21 machine, there occured a power cut. And now I cannot boot the machine, and when I use the rescue mode and try to run again yum update I know I'm coming in late, and judging from other replies this probably won't work, but have you tried

Re: NTP synchronized: no

On 09/09/2015 08:17 AM, Patrick Dupre wrote: Hello, According to the domain administrator, the port is open. Could it be an issue with the firewall? iptables -L |grep udp ACCEPT udp -- anywhere 224.0.0.251 udp dpt:mdns ctstate NEW ACCEPT udp -- anywhere

Re: dracut fails to build bootable initramfs on fc22

On 09.09.2015, Shaheen Bakhtiar wrote: > What is the exact error message(s) you are getting?? Where in the boot > process is it failing? It's not me having problems.. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options:

Re: NTP synchronized: no

> On Sep 9, 2015, at 11:00 AM, Rick Stevens wrote: > > On 09/09/2015 10:37 AM, Patrick Dupre wrote: >> Still the same (always as root) >> >> journalctl -u chrony -b >> -- Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 >> 19:34:53 CEST. -- >> >> >>

Re: After a power cut my machine cannot boot

On 09/09/2015 11:58 AM, Paul Smith wrote: Thanks, Joe. I have just tried yum-complete-transaction but with no success: the error message ("/lib64/libidn.so.11: file too short"). I kind of thought so, but I figured that it was worth a try. -- users mailing list users@lists.fedoraproject.org

Re: After a power cut my machine cannot boot

On 09/09/2015 11:56 AM, Paul Smith wrote: Thanks, Dave. Unfortunately, I cannot paste any output here, as I do not have a graphical console on the problematic machine -- it cannot boot in graphical mode. Use this, then: fdisk -l | tee fdisk.txt That will both show you the results of fdisk

Re: NTP synchronized: no

On 9 September 2015 at 21:40, Patrick Dupre wrote: > > On 09/09/2015 10:37 AM, Patrick Dupre wrote: > I do not see any ntpd running, ntp is not installed! > > "NTP client/server" _is_ chronyd; this is just systemd's weird habit of showing a service "description" and not the

Re: After a power cut my machine cannot boot

On Wed, 9 Sep 2015 19:56:02 +0100 Paul Smith wrote: > On Wed, Sep 9, 2015 at 7:08 PM, Dave Stevens > wrote: > >> > > >> >> "/lib64/libidn.so.11: file too short". > >> > > >> > Have you repaired your crashed filesystems already? > >> > If you have, try "dnf

Re: After a power cut my machine cannot boot

On 9/9/2015 13:36, Paul Smith wrote: I have already tried to get the libidn rpm from a repo, but again I get the same error with wget ("/lib64/libidn.so.11: file too short"). Have you tried downloading the file from another system and transferring it using a USB flash drive? You may also be

Re: NTP synchronized: no

On 09/10/15 01:00, Rick Stevens wrote: > > journalctl -u chrony -b You want journalctl -u chronyd -b -- It seems most people that say they are "done talking about it" never really are until given the last word. -- users mailing list users@lists.fedoraproject.org To unsubscribe or

Re: NTP synchronized: no

journalctl -u chronyd -b - Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 21:30:01 CE Sep 08 11:48:18 Homere chronyd[940]: chronyd version 1.31.1 starting Sep 08 11:48:18 Homere chronyd[940]: Frequency -15.841 +/- 0.025 ppm read from / Sep 08 12:08:01 Homere systemd[1]:

Re: NTP synchronized: no

> On 09/09/2015 10:37 AM, Patrick Dupre wrote: > > Still the same (always as root) > > > > journalctl -u chrony -b > > -- Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 > > 19:34:53 CEST. -- > > > > > > after systemctl restart chronyd > > > > systemctl list-unit-files | grep

Re: NTP synchronized: no

On 09/10/15 03:36, Patrick Dupre wrote: > journalctl -u chronyd -b > > - Logs begin at Fri 2014-05-02 02:14:24 CEST, end at Wed 2015-09-09 21:30:01 > CE > Sep 08 11:48:18 Homere chronyd[940]: chronyd version 1.31.1 starting > Sep 08 11:48:18 Homere chronyd[940]: Frequency -15.841 +/- 0.025 ppm

Re: NTP synchronized: no

> On Sep 9, 2015, at 12:17 PM, Shaheen Bakhtiar wrote: > > > >> On Sep 9, 2015, at 11:00 AM, Rick Stevens > > wrote: >> >> On 09/09/2015 10:37 AM, Patrick Dupre wrote: >>> Still the same (always as root) >>> >>>

Re: After a power cut my machine cannot boot

On 09.09.2015, Paul Smith wrote: > What can I do to repair the filesystem? Go to http://www.sysresccd.org and download the sysresccd image to another machine. Then burn in onto a CD and boot from it. If you have the syslinux tools installed, you can run isohybrid sysresccd.iso and then copy