Re: no shutdown at all in fedora 24 Again!

2017-01-22 Thread Ralf Corsepius 

On 01/22/2017 02:26 AM, Chris Murphy wrote:

I think you're going to have to put logs up somewhere and
configuration information somewhere to get an answer. I can tell you
that mdadm raid and lvm being used do not themselves result in an
inability to shutdown Fedora. Fedora by default uses LVM, and mdadm
raid0/1/5 tests are done on pre-release versions of Fedora; if any of
that resulted in an inability to restart or shutdown, it'd likely be a
release blocking bug. So the mere fact systemd itself does not
directly support md raid or lvm doesn't really translate into a cause
of your problem.


I am also facing these shutdown probs and have come to the conclusion, 
that there is "no single cause", but that they are the result of a 
combination of several causes, probably related to systemd, 
NetworkManager, SELinux and other, networking related packages.


Isolating them seems to be difficult, because almost each update changes 
and breaks something else.


E.g. right now, rpcbind/nfs/yp/nis's integration into systemd seems to 
be "mash" in fc25 - It has "bricked" one of my machines, today!


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

Re: no shutdown at all in fedora 24 Again!

2017-01-22 Thread François Patte 
Le 22/01/2017 02:26, Chris Murphy a écrit :
> I think you're going to have to put logs up somewhere and
> configuration information somewhere to get an answer. I can tell you
> that mdadm raid and lvm being used do not themselves result in an
> inability to shutdown Fedora. Fedora by default uses LVM, and mdadm
> raid0/1/5 tests are done on pre-release versions of Fedora; if any of
> that resulted in an inability to restart or shutdown, it'd likely be a
> release blocking bug. So the mere fact systemd itself does not
> directly support md raid or lvm doesn't really translate into a cause
> of your problem.

I submitted a bug report to Redhat-bugzilla with a 3750 lines file
attached (result of lsblk command, dmesg result, and logwatch report
concerning systemd log after a shutdown failure.

But I am a little bit pessimistic if you consider that (for instance)
since f22, you can see that journalctl or watchdog are not stopped
before unmounting /  /var and /usr and you can see while you shutdown
your system (f23, f24) that unmounting these partitions systematically
fails This kind of small bugs remain after 4/5 years

I am wondering why it is claimed that systemd has been introduced to
increase fastness: I could see that it is not the case at boot time (10s
with systemv while it is now about 30s when no "start job .."
appears during the boot sequence!) the last update I made on a f23
system blocks change of user (I have to beboot) and shutdown is very
long (no raid on this system), and now, endless shutdown on my f24 system!

You say that fedora uses LVM by default, but on my f24 system (raid)
there are no LVM at all: pvscan, lvscan etc. return nothing while some
lvm services are enabled and running (lvm2-lvmetad.socket,
lvm2-monitor and lvm2-lvmpolld) what for?

Hope that someone could help!


-- 
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)1 8394 5849
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: Spectacular F24 to F25 dnf Upgrade Failure

2017-01-22 Thread Brian Hanks 



Date: Sat, 21 Jan 2017 14:10:43 -0700
From: stan 
Subject: Re: Spectacular F24 to F25 dnf Upgrade Failure
To: users@lists.fedoraproject.org
Message-ID: <20170121141043.3a363...@vfemail.net>
Content-Type: text/plain; charset=UTF-8


What was the command you used to do the upgrade?  Is there anything
unusual about your installation?
I used 'dnf system-upgrade download --releasever=25' follow by 'dnf 
system-upgrade reboot'.  Nothing terribly unusual.  Typical dual boot 
Win10 & Fedora on a 3 year old HP Envy 15t laptop with two SSDs.




Does windows still boot properly?

Yes, Win10 still running fine.


You should open a bugzilla against dnf to document your experiences
and allow the potential to get this fixed for the future.
https://bugzilla.redhat.com/
Agreed.  Unfortunately, I didn't save enough detail before moving on.  I 
will try to recreate and capture what I need.



Whew, that's a bad experience.

I'm not knowledgeable enough to help you, but there are some experts
on the list, so maybe they'll be able to help you recover.

It is because of potential experiences like yours that I always do my
upgrades to new versions while leaving my old version intact.  You
could just create the new partitions, and rsync your old version to the
new partitions before doing the upgrade.  Then, if disaster strikes,
you have a fallback position of a working system.
I usually use this laptop as my test machine.  If it works here, then 
I'll run it on my other Fedora machines.  For my main workstation, 
that's always done with a very cautious approach.


Maybe it's just me but I tend to have more issues with the odd numbered 
releases.  Call my superstitious.


Anyway, last night I did a full re-install over this mess with a F25 net 
install USB image and that failed as well.  With this latest attempt I 
deleted and recreated all partitions except for the shared efi 
partition.  I used a basic ext4 partitioning scheme (/boot; /boot/efi; 
/; swap).  It seemed like the install was going well but on reboot it 
failed.  From the logs, it appears the new grub config written by the 
installer is looking for a device UUID that doesn't exist.


Maybe I should clear out the /boot/efi/EFI/fedora directory before 
re-install?


This morning I ran one additional test.  I did a fresh install from a 
F25 XFCE Live USB. This was successful, but it leaves me with a ton of 
reconfiguration and restoration work.  Once I get everything up and 
running again I will do some additional tests with the F25 net installer 
to see if I can accurately document what happened.



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

Re: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0

2017-01-22 Thread poma 
On 21.01.2017 21:00, poma wrote:
> On 17.01.2017 22:12, Stephen Morris wrote:
> [...]
>> The lsusb output for that device is also below.
>>
>> Bus 010 Device 002: ID 2001:331a D-Link Corp.
>>
> [...]
> 
> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
> 
> https://wikidevi.com/wiki/D-Link_DWA-192
> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
> ftp://files.dlink.com.au/products/DWA-192
> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
> 
> https://wikidevi.com/wiki/Edimax_EW-7833UAC
> http://www.edimax.com/edimax/download/download/data/edimax/global/download/for_home/wireless_adapters/wireless_adapters_ac1750_dual-band/ew-7833uac
> http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
> 
> https://github.com/pld-linux/rtl8812au
> https://github.com/diederikdehaas/rtl8812AU
> 
> ~~~
> 
> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
> $ cd 
> EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
> 
> $ curl -s 
> https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debug.patch
>  | patch -p1
> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch | 
> patch -p1
> $ curl -s 
> https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch 
> | patch -p1
> $ curl -s 
> https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch 
> | patch -p1
> 
> $ make -j3
> $ su
> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
> # depmod
> # modinfo 8814au | grep 2001
> 
> # modprobe -v 8814au
> # dmesg:
> ...
> RTL871X: module init start
> RTL871X: rtl8814au v4.3.21_17997.20160531
> RTL871X: build time: Jan 21 2017 20:04:38
> usbcore: registered new interface driver rtl8814au
> RTL871X: module init ret=0
> ...
> # modprobe -rv 8814au
> # dmesg:
> ...
> RTL871X: module exit start
> usbcore: deregistering interface driver rtl8814au
> RTL871X: module exit success
> ...
> 
> 
> Wifi ball works now?
> 
> 
> HW add.
> https://wikidevi.com/wiki/ASUS_USB-AC68
> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
> 
> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
> http://www.tp-link.com/en/download/Archer-T9UH.html
> 
> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
> https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
> 
> SW add.
> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
> https://github.com/austinmarton/rtl8812au_linux
> 
> 
> 

OR
according to "rtl8814au? #10"
https://github.com/diederikdehaas/rtl8812AU/issues/10

$ git clone -b driver-4.3.21 https://github.com/uminokoe/rtl8812AU.git 
RTL8814AU-uminokoe
$ cd RTL8814AU-uminokoe/
$ git revert -n 9260f77 8d33100
// "Disabled debugging code."
$ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch | 
patch -p1
// Enables CONFIG_MP_VHT_HW_TX_MODE
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile

OR
$ git clone https://github.com/diederikdehaas/rtl8814AU.git 
RTL8814AU-diederikdehaas
$ cd RTL8814AU-diederikdehaas/
// Adds missing Vendor/Product ID
$ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info = RTL8814A}, 
/* Edimax - Edimax */' os_dep/linux/usb_intf.c
// "Added VHT capabilities."
$ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch | patch -p1
// Enables CONFIG_MP_VHT_HW_TX_MODE
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile


$ make -j3
$ su
# cp 8814au.ko /lib/modules/$(uname -r)/updates/
# depmod
# modinfo 8814au

# modprobe -v 8814au
# dmesg:
...
RTL871X: module init start
RTL871X: rtl8814au v4.3.21_17997.20160531
usbcore: registered new interface driver rtl8814au
RTL871X: module init ret=0
...
# modprobe -rv 8814au
# dmesg:
...
RTL871X: module exit start
usbcore: deregistering interface driver rtl8814au
RTL871X: module exit success
...


Hello Diederik,
it seems there are only two Linux RTL8814AU users, so far.

Morris, when you catch some time, would you mind to run a couple iperf tests 
with DWA-192,
to see real network throughput results.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0

2017-01-22 Thread Stephen Morris 

On 23/01/2017 00:43, poma wrote:

On 21.01.2017 21:00, poma wrote:

On 17.01.2017 22:12, Stephen Morris wrote:
[...]

The lsusb output for that device is also below.

Bus 010 Device 002: ID 2001:331a D-Link Corp.


[...]

D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0

https://wikidevi.com/wiki/D-Link_DWA-192
http://support.dlink.com/ProductInfo.aspx?m=DWA-192
ftp://files.dlink.com.au/products/DWA-192
https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225

https://wikidevi.com/wiki/Edimax_EW-7833UAC
http://www.edimax.com/edimax/download/download/data/edimax/global/download/for_home/wireless_adapters/wireless_adapters_ac1750_dual-band/ew-7833uac
http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip

https://github.com/pld-linux/rtl8812au
https://github.com/diederikdehaas/rtl8812AU

~~~

$ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
$ cd 
EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/

$ curl -s 
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debug.patch
 | patch -p1
$ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch | 
patch -p1
$ curl -s 
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch | 
patch -p1
$ curl -s 
https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch | 
patch -p1

$ make -j3
$ su
# cp 8814au.ko /lib/modules/$(uname -r)/updates/
# depmod
# modinfo 8814au | grep 2001

# modprobe -v 8814au
# dmesg:
...
RTL871X: module init start
RTL871X: rtl8814au v4.3.21_17997.20160531
RTL871X: build time: Jan 21 2017 20:04:38
usbcore: registered new interface driver rtl8814au
RTL871X: module init ret=0
...
# modprobe -rv 8814au
# dmesg:
...
RTL871X: module exit start
usbcore: deregistering interface driver rtl8814au
RTL871X: module exit success
...


Wifi ball works now?


HW add.
https://wikidevi.com/wiki/ASUS_USB-AC68
https://www.asus.com/Networking/USB-AC68/HelpDesk_Download

https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
http://www.tp-link.com/en/download/Archer-T9UH.html

https://wikidevi.com/wiki/TRENDnet_TEW-809UB
https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB

SW add.
https://github.com/abperiasamy/rtl8812AU_8821AU_linux
https://github.com/austinmarton/rtl8812au_linux




OR
according to "rtl8814au? #10"
https://github.com/diederikdehaas/rtl8812AU/issues/10

$ git clone -b driver-4.3.21 https://github.com/uminokoe/rtl8812AU.git 
RTL8814AU-uminokoe
$ cd RTL8814AU-uminokoe/
$ git revert -n 9260f77 8d33100
// "Disabled debugging code."
$ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch | 
patch -p1
// Enables CONFIG_MP_VHT_HW_TX_MODE
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile

OR
$ git clone https://github.com/diederikdehaas/rtl8814AU.git 
RTL8814AU-diederikdehaas
$ cd RTL8814AU-diederikdehaas/
// Adds missing Vendor/Product ID
$ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info = RTL8814A}, 
/* Edimax - Edimax */' os_dep/linux/usb_intf.c
// "Added VHT capabilities."
$ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch | patch -p1
// Enables CONFIG_MP_VHT_HW_TX_MODE
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
$ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile


$ make -j3
$ su
# cp 8814au.ko /lib/modules/$(uname -r)/updates/
# depmod
# modinfo 8814au

# modprobe -v 8814au
# dmesg:
...
RTL871X: module init start
RTL871X: rtl8814au v4.3.21_17997.20160531
usbcore: registered new interface driver rtl8814au
RTL871X: module init ret=0
...
# modprobe -rv 8814au
# dmesg:
...
RTL871X: module exit start
usbcore: deregistering interface driver rtl8814au
RTL871X: module exit success
...


Hello Diederik,
it seems there are only two Linux RTL8814AU users, so far.

Morris, when you catch some time, would you mind to run a couple iperf tests 
with DWA-192,
to see real network throughput results.
I can't run any at the moment because Fedora is refusing to actually use 
the device at all.


I have also just upgraded to F25 and nothing has changed.

The last time I used this device was on 08/10/2016 and it was using the 
ATH9K driver. The main reason I upgraded to this USB device was that I 
upgraded my router to a faster version, and I found that unlike the 
DWA182 I didn't have to compile my own driver, the kernel had inbuilt 
support for the DWA192.


It is possible that I have managed to Blacklist the device in some way, 
not by the conventional Blacklist.conf, and I have forgotten how so I 
can't find where I've done it to reverse it.


Also, having never done it before, I also don't know how to run iperf tests.

regards,
Steve





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

Re: [...] D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0

2017-01-22 Thread poma 
On 22.01.2017 21:49, Stephen Morris wrote:
> On 23/01/2017 00:43, poma wrote:
>> On 21.01.2017 21:00, poma wrote:
>>> On 17.01.2017 22:12, Stephen Morris wrote:
>>> [...]
 The lsusb output for that device is also below.

 Bus 010 Device 002: ID 2001:331a D-Link Corp.

>>> [...]
>>>
>>> D-Link DWA-192 - Realtek RTL8814AU WiFi USB 3.0
>>>
>>> https://wikidevi.com/wiki/D-Link_DWA-192
>>> http://support.dlink.com/ProductInfo.aspx?m=DWA-192
>>> ftp://files.dlink.com.au/products/DWA-192
>>> https://openitforum.pl/index/recenzje/karty/d-link-dwa-192-r225
>>>
>>> https://wikidevi.com/wiki/Edimax_EW-7833UAC
>>> http://www.edimax.com/edimax/download/download/data/edimax/global/download/for_home/wireless_adapters/wireless_adapters_ac1750_dual-band/ew-7833uac
>>> http://www.edimax.com/edimax/mw/cufiles/files/download/Driver_Utility/EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>>
>>> https://github.com/pld-linux/rtl8812au
>>> https://github.com/diederikdehaas/rtl8812AU
>>>
>>> ~~~
>>>
>>> $ unzip EW-7833UAC_linux_4.3.21_kernel_3.16-4.4.zip
>>> $ cd 
>>> EW7833UAC_linux_4.3.21_kernel_3.16-4.4/EW7833UAC_linux_v4.3.21_17997.20160531/
>>>
>>> $ curl -s 
>>> https://raw.githubusercontent.com/pld-linux/rtl8812au/master/disable-debug.patch
>>>  | patch -p1
>>> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/e6d6beb.patch 
>>> | patch -p1
>>> $ curl -s 
>>> https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.7.patch
>>>  | patch -p1
>>> $ curl -s 
>>> https://raw.githubusercontent.com/pld-linux/rtl8812au/master/linux-4.8.patch
>>>  | patch -p1
>>>
>>> $ make -j3
>>> $ su
>>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>>> # depmod
>>> # modinfo 8814au | grep 2001
>>>
>>> # modprobe -v 8814au
>>> # dmesg:
>>> ...
>>> RTL871X: module init start
>>> RTL871X: rtl8814au v4.3.21_17997.20160531
>>> RTL871X: build time: Jan 21 2017 20:04:38
>>> usbcore: registered new interface driver rtl8814au
>>> RTL871X: module init ret=0
>>> ...
>>> # modprobe -rv 8814au
>>> # dmesg:
>>> ...
>>> RTL871X: module exit start
>>> usbcore: deregistering interface driver rtl8814au
>>> RTL871X: module exit success
>>> ...
>>> 
>>>
>>> Wifi ball works now?
>>>
>>>
>>> HW add.
>>> https://wikidevi.com/wiki/ASUS_USB-AC68
>>> https://www.asus.com/Networking/USB-AC68/HelpDesk_Download
>>>
>>> https://wikidevi.com/wiki/TP-LINK_Archer_T9UH
>>> http://www.tp-link.com/en/download/Archer-T9UH.html
>>>
>>> https://wikidevi.com/wiki/TRENDnet_TEW-809UB
>>> https://www.trendnet.com/support/supportdetail.asp?prod=100_TEW-809UB
>>>
>>> SW add.
>>> https://github.com/abperiasamy/rtl8812AU_8821AU_linux
>>> https://github.com/austinmarton/rtl8812au_linux
>>>
>>>
>>>
>> OR
>> according to "rtl8814au? #10"
>> https://github.com/diederikdehaas/rtl8812AU/issues/10
>>
>> $ git clone -b driver-4.3.21 https://github.com/uminokoe/rtl8812AU.git 
>> RTL8814AU-uminokoe
>> $ cd RTL8814AU-uminokoe/
>> $ git revert -n 9260f77 8d33100
>> // "Disabled debugging code."
>> $ curl -s https://github.com/diederikdehaas/rtl8812AU/commit/3e80ebc.patch | 
>> patch -p1
>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>
>> OR
>> $ git clone https://github.com/diederikdehaas/rtl8814AU.git 
>> RTL8814AU-diederikdehaas
>> $ cd RTL8814AU-diederikdehaas/
>> // Adds missing Vendor/Product ID
>> $ sed -i '/0xA834/ a\\t{USB_DEVICE(0x7392, 0xA833), .driver_info = 
>> RTL8814A}, /* Edimax - Edimax */' os_dep/linux/usb_intf.c
>> // "Added VHT capabilities."
>> $ curl -s https://github.com/uminokoe/rtl8812AU/commit/5f75242.patch | patch 
>> -p1
>> // Enables CONFIG_MP_VHT_HW_TX_MODE
>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/n/y/' Makefile
>> $ sed -i '/CONFIG_MP_VHT_HW_TX_MODE/s/#//' Makefile
>>
>>
>> $ make -j3
>> $ su
>> # cp 8814au.ko /lib/modules/$(uname -r)/updates/
>> # depmod
>> # modinfo 8814au
>>
>> # modprobe -v 8814au
>> # dmesg:
>> ...
>> RTL871X: module init start
>> RTL871X: rtl8814au v4.3.21_17997.20160531
>> usbcore: registered new interface driver rtl8814au
>> RTL871X: module init ret=0
>> ...
>> # modprobe -rv 8814au
>> # dmesg:
>> ...
>> RTL871X: module exit start
>> usbcore: deregistering interface driver rtl8814au
>> RTL871X: module exit success
>> ...
>>
>>
>> Hello Diederik,
>> it seems there are only two Linux RTL8814AU users, so far.
>>
>> Morris, when you catch some time, would you mind to run a couple iperf tests 
>> with DWA-192,
>> to see real network throughput results.
> I can't run any at the moment because Fedora is refusing to actually use 
> the device at all.
> 
> I have also just upgraded to F25 and nothing has changed.
> 
> The last time I used this device was on 08/10/2016 and it was using the 
> ATH9K driver. The main reason I upgraded to this USB device was that I 
> upgraded my router to a faster version, and I found that unlike the 
> DWA182 I

Re: Spectacular F24 to F25 dnf Upgrade Failure

2017-01-22 Thread EGO-II.1 



On 01/22/2017 09:31 AM, Brian Hanks wrote:


Date: Sat, 21 Jan 2017 14:10:43 -0700 From: stan
 Subject: Re: Spectacular F24 to F25
dnf Upgrade Failure To: users@lists.fedoraproject.org Message-ID:
<20170121141043.3a363...@vfemail.net> Content-Type: text/plain;
charset=UTF-8

What was the command you used to do the upgrade? Is there anything
unusual about your installation?

I used ‘dnf system-upgrade download --releasever=25’ follow by ‘dnf 
system-upgrade reboot’. Nothing terribly unusual. Typical dual boot 
Win10 & Fedora on a 3 year old HP Envy 15t laptop with two SSDs.


Does windows still boot properly?

Yes, Win10 still running fine.

You should open a bugzilla against dnf to document your
experiences and allow the potential to get this fixed for the
future. https://bugzilla.redhat.com/

Agreed. Unfortunately, I didn't save enough detail before moving on. I 
will try to recreate and capture what I need.


Whew, that's a bad experience.

I'm not knowledgeable enough to help you, but there are some
experts on the list, so maybe they'll be able to help you recover.

It is because of potential experiences like yours that I always do
my upgrades to new versions while leaving my old version intact.
You could just create the new partitions, and rsync your old
version to the new partitions before doing the upgrade. Then, if
disaster strikes, you have a fallback position of a working system.

I usually use this laptop as my test machine. If it works here, then 
I'll run it on my other Fedora machines. For my main workstation, 
that's always done with a very cautious approach.


Maybe it's just me but I tend to have more issues with the odd 
numbered releases. Call my superstitious.


Anyway, last night I did a full re-install over this mess with a F25 
net install USB image and that failed as well. With this latest 
attempt I deleted and recreated all partitions except for the shared 
efi partition. I used a basic ext4 partitioning scheme (/boot; 
/boot/efi; /; swap). It seemed like the install was going well but on 
reboot it failed. From the logs, it appears the new grub config 
written by the installer is looking for a device UUID that doesn't exist.


Maybe I should clear out the /boot/efi/EFI/fedora directory before 
re-install?


This morning I ran one additional test. I did a fresh install from a 
F25 XFCE Live USB. This was successful, but it leaves me with a ton of 
reconfiguration and restoration work. Once I get everything up and 
running again I will do some additional tests with the F25 net 
installer to see if I can accurately document what happened.


-Brian



___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
I once remember a situation something like that happening to me way back 
when the latest version was F19. I had to take a more drastic approach, 
I completely backed up the entire system onto my external 2TB HDD, and 
blew away the drive completely with DBAN (D-arik's B-oot A-nd N-uke) 
then tried a fresh install of F19 and it WORKED!...I wouldn't suggest 
that now of course,...but I was tired and I was angry so I went Ninja on 
itLoL!



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