Re: fedup - luks encrypted system

2014-12-12 Thread Chris Murphy 
On Fri, Dec 12, 2014 at 12:29 AM, Joe Zeff  wrote:

> On 12/11/2014 06:21 PM, Sam Varshavchik wrote:
>
>> We're talking about fedup doing its thing after rebooting into the
>> upgrade kernel. It appears that the sysrq is enabled in the upgrade
>> kernel, and I do believe that I accurately explained that sysrq did
>> produce a response; unfortunately the response did not solve the problem
>> the sysrq key was intended to solve.
>>
>
> Sysrq key did produce an effect, but not, if memory serves, the effect
> it's supposed to.  Rather similar to a lock-up issue I had before swapping
> in a new mobo, where it worked reliably when I tested it, but not when I
> needed it because of hardware trouble.  No, I don't think that's what's
> going on with your system, but the responses you describe just don't sound
> right.  (And, if you're using the Magic Sysrq Key, it's ^Alt-Sysrq that's
> needed, not just sysrq.)


Only sync is enabled by default on Fedora.

https://www.kernel.org/doc/Documentation/sysrq.txt

# cat /proc/sys/kernel/sysrq
16

So you have to do:

echo 1 > /proc/sys/kernel/sysrq

Now the other commands will work. I usually just echo the letter to
/proc/sysrq-trigger.

Chris Murphy



-- 
Chris Murphy
-- 
users mailing list
users@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

Re: fedup - luks encrypted system

2014-12-12 Thread Gordon Messmer 

On 12/11/2014 03:30 PM, Sam Varshavchik wrote:
So… Has anyone been able to update a LUKS-encrypted system, without 
getting stuck at the end? I couldn't find anything in Bugzilla. 


Yes.  I've updated two F20 systems with LUKS-encrypted LVM backed 
filesystems using fedup.


Felix already reported success using LUKS and no LVM.

--
users mailing list
users@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

Re: fedup - luks encrypted system

2014-12-11 Thread Joe Zeff 

On 12/11/2014 06:21 PM, Sam Varshavchik wrote:

We're talking about fedup doing its thing after rebooting into the
upgrade kernel. It appears that the sysrq is enabled in the upgrade
kernel, and I do believe that I accurately explained that sysrq did
produce a response; unfortunately the response did not solve the problem
the sysrq key was intended to solve.


Sysrq key did produce an effect, but not, if memory serves, the effect 
it's supposed to.  Rather similar to a lock-up issue I had before 
swapping in a new mobo, where it worked reliably when I tested it, but 
not when I needed it because of hardware trouble.  No, I don't think 
that's what's going on with your system, but the responses you describe 
just don't sound right.  (And, if you're using the Magic Sysrq Key, it's 
^Alt-Sysrq that's needed, not just sysrq.)

--
users mailing list
users@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

Re: fedup - luks encrypted system

2014-12-11 Thread Sam Varshavchik 

Joe Zeff writes:


On 12/11/2014 03:30 PM, Sam Varshavchik wrote:

I forgot about reboot -f. sysrq+s did not do anything; sysrq+u made the
entire console output from the entire installation process, from start
to finish, scroll through the console at warp speed, looping 3-4 times,
which was highly amusing to watch; sysrq+b did not do anything.


In order for sysrq to do any good, you have to activate the Magic Sysrq  
Key.  (Details can be found in Wikipedia.)


We're talking about fedup doing its thing after rebooting into the upgrade  
kernel. It appears that the sysrq is enabled in the upgrade kernel, and I do  
believe that I accurately explained that sysrq did produce a response;  
unfortunately the response did not solve the problem the sysrq key was  
intended to solve.




pgpZ7FWHvQLVp.pgp
Description: PGP signature
-- 
users mailing list
users@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

Re: fedup - luks encrypted system

2014-12-11 Thread Joe Zeff 

On 12/11/2014 03:30 PM, Sam Varshavchik wrote:

I forgot about reboot -f. sysrq+s did not do anything; sysrq+u made the
entire console output from the entire installation process, from start
to finish, scroll through the console at warp speed, looping 3-4 times,
which was highly amusing to watch; sysrq+b did not do anything.


In order for sysrq to do any good, you have to activate the Magic Sysrq 
Key.  (Details can be found in Wikipedia.)

--
users mailing list
users@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

Re: fedup - luks encrypted system

2014-12-11 Thread Sam Varshavchik 

Chris Murphy writes:

On Wed, Dec 10, 2014 at 7:20 AM, Michael Morgan  
mmor...@dca.net> wrote:


   I ran into a hang like BZ 1160079 while upgrading from F20 on a similar
   setup yesterday. I didn't have any issues with disk space but the reboot
   did get stuck on the LUKS container when trying to unmount sysroot.
   Power cycling at that point was a bit frightening but the system came
   back up without issue.



Best to try 'reboot -f' which should still cleanly unmount filesystems. And  
if that doesn't work then sysrq + s, u, b (in order). If that doesn't work,  
OK power cycle.


Hit the same bug here too, with a LUKS-based laptop.

I forgot about reboot -f. sysrq+s did not do anything; sysrq+u made the  
entire console output from the entire installation process, from start to  
finish, scroll through the console at warp speed, looping 3-4 times, which  
was highly amusing to watch; sysrq+b did not do anything.


The reboot was getting stuck unmounting some of the LUKS volumes. There were  
about five or six unmount tasks that systemd spawned off. All but two of  
them had the default 90 second timeout, and they were killed afterwards. Two  
of them had an unlimited timeout, and that's where the reboot gets stuck.


The three-fingered-salute produced a response, though. Unfortunately, it was  
the same reboot cycle, again. 90 seconds to time out all but the two  
remaining jobs, then spin forever.


After a reboot, the system looks ok. forcefsck didn't find anything to  
complain about.


So… Has anyone been able to update a LUKS-encrypted system, without getting  
stuck at the end? I couldn't find anything in Bugzilla.




pgp6A_XV8yM3Z.pgp
Description: PGP signature
-- 
users mailing list
users@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

Re: fedup - luks encrypted system

2014-12-10 Thread Chris Murphy 
On Wed, Dec 10, 2014 at 7:20 AM, Michael Morgan  wrote:

> I ran into a hang like BZ 1160079 while upgrading from F20 on a similar
> setup yesterday. I didn't have any issues with disk space but the reboot
> did get stuck on the LUKS container when trying to unmount sysroot.
> Power cycling at that point was a bit frightening but the system came
> back up without issue.


Best to try 'reboot -f' which should still cleanly unmount filesystems. And
if that doesn't work then sysrq + s, u, b (in order). If that doesn't work,
OK power cycle.


-- 
Chris Murphy
-- 
users mailing list
users@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

Re: fedup - luks encrypted system

2014-12-10 Thread Michael Morgan 
I ran into a hang like BZ 1160079 while upgrading from F20 on a similar
setup yesterday. I didn't have any issues with disk space but the reboot
did get stuck on the LUKS container when trying to unmount sysroot.
Power cycling at that point was a bit frightening but the system came
back up without issue.

-Mike

On Tue, Dec 09, 2014 at 08:17:06PM -0700, Robin Laing wrote:
> Hello,
> 
> In the past, using fedup was a disaster due to encrypted systems.
> 
> Is this working in F21?
> 
> Don't use LVM's and partitions are encrypted using LUKS.  This includes /tmp
> swap.  /boot isn't encrypted.
> 
> Have had issues installing in the past with encrypted partitions.
> 
> Seen many bug reports about fedup and encrypted partitions.
> 
> Will be going from F19 and F20 to F21.
> 
> Robin
> -- 
> users mailing list
> users@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
-- 
users mailing list
users@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

Re: fedup - luks encrypted system

2014-12-10 Thread Felix Schwarz 
Am 10.12.2014 um 04:17 schrieb Robin Laing:
> In the past, using fedup was a disaster due to encrypted systems.
> 
> Is this working in F21?
>
> Don't use LVM's and partitions are encrypted using LUKS.  This includes /tmp
> swap.  /boot isn't encrypted.

It worked for me, I upgraded from F20->F21 and a very similar filesystem setup
as you described (luks encrypted / + swap, no lvm).

fs

-- 
users mailing list
users@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

fedup - luks encrypted system

2014-12-09 Thread Robin Laing 

Hello,

In the past, using fedup was a disaster due to encrypted systems.

Is this working in F21?

Don't use LVM's and partitions are encrypted using LUKS.  This includes 
/tmp swap.  /boot isn't encrypted.


Have had issues installing in the past with encrypted partitions.

Seen many bug reports about fedup and encrypted partitions.

Will be going from F19 and F20 to F21.

Robin
--
users mailing list
users@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