Re: post-mortem: f24 boot fails; need help.

2017-06-03 Thread William Mattison
The smartctl long test took about 4 hours (I think!).  I wish it would notify 
me when it was actually finished!  As best as I could tell (by using "smartctl 
-l error /dev/sda", it found no problems.

thanks,
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: post-mortem: f24 boot fails; need help.

2017-06-03 Thread William Mattison
While changing the motherboard battery yesterday (Friday), most cables were 
disconnected and then later re-connected.  That included the hard drive 
connection to the motherboard.  I also disconnected and reconnected both the 
power cable and the data cable where they plug in to the hard drive itself.  
The hard drive was removed, vacuumed, and put back into its place.

No problems since, but I haven't done a "dnf upgrade" since then.

thanks,
Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: post-mortem: f24 boot fails; need help.

2017-06-03 Thread William Mattison
According to the man page, the "-n" option is non-destructive; the "-w" option 
is what you described.

Regardless, it's too long.

Bill.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: Fw: Systemd keeps trying to re-open an already active LUKS volume

2017-06-03 Thread Andrej Podzimek

Thanks for forwarding this. Just FYI, I have just filed a bug report, because 
it looks mire like a bug rather than a misconfiguration on my system: 
https://bugzilla.redhat.com/show_bug.cgi?id=1458524 If anyone happens to know 
what the problem could be, please update the bug report rather than the mailing 
list threads.

Cheers,
Andrej



smime.p7s
Description: Elektronicky podpis S/MIME
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


kernel errors after updating to 4.11.3-200.fc25.x86_64

2017-06-03 Thread François Patte
What is the meaning of these error messages:

WARNING:  Kernel Errors Present
WARNING: CPU: 1 PID: 3538 at drivers/net/wireles ...:  1 Time(s)
iwlwifi :0c:00.0: FH_TSSR_TX_ERROR_REG:
0X ...:  1 Time(s)
iwlwifi :0c:00.0: FW error in SYNC CMD REPL ...:  1 Time(s)
iwlwifi :0c:00.0: Microcode SW error detected.  Resta ...:  1
Time(s)
iwlwifi :0c:00.0: Start IWL Error Log Dump: ...:  1 Time(s)

Thank you.

-- 
François Patte
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)6 7892 5822
http://www.math-info.univ-paris5.fr/~patte



signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: VPN l2tp+ipsec: not work with last kernel 4.11.3-200

2017-06-03 Thread Dario Lesca
Il giorno ven, 02/06/2017 alle 18.06 +, Kseniya Blashchuk ha
scritto:
> Do you use dnsmasq? I had the same issue until I set dns=dnsmasq in
> NetworkManager.conf. I don't remember exactly why it's needed, found
> somewhere at GitHub.
> 
> 

No, I do not use dnsmasq.
Resolve remote name using remote DNS work (UDP) and also ping to remote
IP work (ICMP)
I have try last kojo kernel but the problem persist.https://bugzilla.re
dhat.com/show_bug.cgi?id=1458222#c2 id="-x-evo-selection-start-marker">
Thanks 
-- 
Dario Lesca
(inviato dal mio Linux Fedora 25 Workstation)___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org


Re: post-mortem: f24 boot fails; need help.

2017-06-03 Thread Louis Lagendijk
On Sat, 2017-06-03 at 01:32 +, William Mattison wrote:
> I tried badblocks last night.  I didn't realize how long it would
> take.  After over 3 hours, I had to abort it to do something else.
> 
> This morning, I retried it, this time with options to show its
> progress.  It took between 3 1/2 and 3 3/4 hours.  Here are the
> results:
> ===
> bash.3[~]: badblocks -s -v /dev/sda
> Checking blocks 0 to 1953514583
> Checking for bad blocks (read-only test):
> done 
> Pass completed, 0 bad blocks found. (0/0/0 errors)
> bash.4[~]:
> ===
> I don't think this completely rules out the hard drive as the
> villain, but it's now less of a suspect.  Am I correct in guessing
> that the non-destructive read-write option (option "-n") would take
> over twice as long (7 1/2 or more hours)?
> 
> Thanks,
> Bill.
> ___
> users mailing list -- users@lists.fedoraproject.org
> To unsubscribe send an email to users-le...@lists.fedoraproject.org
I have not followed this thread closely, but did you check the harddisk
cable. They are often a source for problems...

Louis
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org