On Fri, 06 Nov 2015 23:06:11 +
Patrick O'Callaghan wrote:
> The latest kernel update fixed it
I had something similar happen when I added a raid
to my system once. Merely doing a dracut -f
didn't make it work on one of my boot partitions.
It wasn't until I installed a new kernel in
that parti
On Fri, 2015-11-06 at 22:17 +0100, Chris Murphy wrote:
> If only /home is btrfs, it's sufficiently late that the btrfs kernel
> module doesn't need to be in the initrd. So I'd be looking at other
> failures.
>
> If by manual mount you mean the complete command:
>
> mount -t btrfs /dev/sdaX /home
If only /home is btrfs, it's sufficiently late that the btrfs kernel
module doesn't need to be in the initrd. So I'd be looking at other
failures.
If by manual mount you mean the complete command:
mount -t btrfs /dev/sdaX /home
and not
mount /home
Then that's kinda weird for it to fail. I've b
On 5 November 2015 at 11:05, Stephen Berg (Contractor) <
stephen.berg@nrlssc.navy.mil> wrote:
> How exactly did you do the downgrade? I tried by removing xorg-* and
>> running dnf install xorg* with --releasever=22, followed by dnf downgrade,
>> but it didn't work. The kmod-nvidia gave a depen
On 11/05/2015 04:59 AM, Patrick O'Callaghan wrote:
On 5 November 2015 at 10:40, Stephen Berg (Contractor) <
stephen.berg@nrlssc.navy.mil> wrote:
On 11/05/2015 04:33 AM, Patrick O'Callaghan wrote:
Now I just have to struggle with Nouveau settings to get decent screen
resolution until Nvidi
On 5 November 2015 at 10:40, Stephen Berg (Contractor) <
stephen.berg@nrlssc.navy.mil> wrote:
> On 11/05/2015 04:33 AM, Patrick O'Callaghan wrote:
>
>> Now I just have to struggle with Nouveau settings to get decent screen
>> resolution until Nvidia drivers appear. Any suggestions would be wel
On 11/05/2015 04:33 AM, Patrick O'Callaghan wrote:
Now I just have to struggle with Nouveau settings to get decent screen
resolution until Nvidia drivers appear. Any suggestions would be welcome.
poc
I downgraded Xorg to 1.17 and installed the 352.55 driver from Nvidia.
So far it's pretty stab
On 4 November 2015 at 00:28, Patrick O'Callaghan
wrote:
> I updated to F23 using the approved dnf method, with no errors. Now I have
> an unusable system because /home is not being mounted.
This just in: updating to kernel 4.2.5-300.fc23.x86_64 has fixed the btrfs
issue.
Now I just have to str
On 4 November 2015 at 22:07, Jon LaBadie wrote:
> When I upgraded to F22, all fstab entries that said mount at boot
> had to succeed or the boot went to emergency mode. For me it
> was an obscure sshfs mount that caused problems.
>
> Are any boot time mounts failing?
>
I have masked the btrfs a
On 4 November 2015 at 22:12, Rick Stevens wrote:
> As root, try:
>
> # find /lib/modules/`uname -r`/kernel/fs -name "*btrfs*"
>
> And see if you get anything like this:
>
> [root@golem4 ~]# find /lib/modules/`uname -r`/kernel/fs -name
> "*btrfs*"
> /lib/modules/4.2.3-200.f
On 11/04/2015 01:24 PM, Patrick O'Callaghan wrote:
On 4 November 2015 at 20:14, Michael Schwendt mailto:mschwe...@gmail.com>> wrote:
What kernel packages is this with? Do they verify fine?
core, tools, tools-libs, modules, modules-extra, headers and devel, all
4.2.3-300.fc23.x86_64
They a
On Wed, Nov 04, 2015 at 09:48:05PM +, Patrick O'Callaghan wrote:
> On 4 November 2015 at 21:24, Patrick O'Callaghan
> wrote:
>
> > Does "modprobe -v btrfs" print anything, or does the command fail
> >> silently?
> >>
> > Gives no output. "lsmod|grep btrfs" shows nothing.
> >
> >> Is this with
On 4 November 2015 at 21:48, Gordon Messmer
wrote:
> On 11/04/2015 01:24 PM, Patrick O'Callaghan wrote:
>
>>
>> Does "modprobe -v btrfs" print anything, or does the command fail
>> silently?
>>
>>
>> Gives no output. "lsmod|grep btrfs" shows nothing.
>>
>
> And "dmesg" after that?
>
Noth
On 4 November 2015 at 21:24, Patrick O'Callaghan
wrote:
> Does "modprobe -v btrfs" print anything, or does the command fail
>> silently?
>>
>
> Gives no output. "lsmod|grep btrfs" shows nothing.
>
>
>> Is this with SELinux enforcing? If so, have you tried with enforcing=0
>> yet? (or run "setenfo
On 11/04/2015 01:24 PM, Patrick O'Callaghan wrote:
Does "modprobe -v btrfs" print anything, or does the command fail
silently?
Gives no output. "lsmod|grep btrfs" shows nothing.
And "dmesg" after that?
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subsc
On 4 November 2015 at 20:14, Michael Schwendt wrote:
> What kernel packages is this with? Do they verify fine?
>
core, tools, tools-libs, modules, modules-extra, headers and devel, all
4.2.3-300.fc23.x86_64
They all verify correctly, i.e. give only ..T.
Does "modprobe -v btrfs" print anyth
On Wed, 4 Nov 2015 20:18:17 +0200, Alchemist wrote:
> You should search for answer in system logs, why exactly btrfs module isn't
> loaded, usually debug data is being written in kernel log. If initram, boot
> params and fstab is not tampered by you or by not so successful upgrade
> then check log
2015-11-04 19:06 GMT+02:00 Patrick O'Callaghan :
>
> On 4 November 2015 at 08:01, Patrick O'Callaghan
> wrote:
>
>> On 4 November 2015 at 11:55, Patrick O'Callaghan
>> wrote:
>>
>>> /proc/filesystems does not contain btrfs. Modprobe makes no difference.
>>>
>>> 'lsinitrd|grep btrfs' gives no out
On 4 November 2015 at 08:01, Patrick O'Callaghan
wrote:
> On 4 November 2015 at 11:55, Patrick O'Callaghan
> wrote:
>
>> /proc/filesystems does not contain btrfs. Modprobe makes no difference.
>>
>> 'lsinitrd|grep btrfs' gives no output.
>>
>
> I should also mention that I ran 'dracut -f' but no
On 4 November 2015 at 11:55, Patrick O'Callaghan
wrote:
> /proc/filesystems does not contain btrfs. Modprobe makes no difference.
>
> 'lsinitrd|grep btrfs' gives no output.
>
I should also mention that I ran 'dracut -f' but nothing changed.
poc
--
users mailing list
users@lists.fedoraproject.o
On 4 November 2015 at 11:55, Patrick O'Callaghan
wrote:
> On 4 November 2015 at 11:16, Michael Schwendt wrote:
>
>> What does "cat /proc/filesystems" say about btrfs?
>> If it's not listed there, does "modprobe btrfs ; mount /home" work then,
>> at least?
>>
>
> /proc/filesystems does not contai
On 4 November 2015 at 11:16, Michael Schwendt wrote:
> What does "cat /proc/filesystems" say about btrfs?
> If it's not listed there, does "modprobe btrfs ; mount /home" work then,
> at least?
>
/proc/filesystems does not contain btrfs. Modprobe makes no difference.
'lsinitrd|grep btrfs' gives
On 4 November 2015 at 00:37, Alchemist wrote:
> Boot F23, login console mode, check
>
> systemctl --failed
>
Failures for:
home.mount, proc-fs-nfsd.mount, several other local mounts and
var-lib-nfs-rpc_pipefs.mount
> systemctl status home.mount
>
Failed to mount /home
> rpm -qa | egrep "bt
On Wed, 4 Nov 2015 00:28:16 +, Patrick O'Callaghan wrote:
> (Repeating myself from another thread where this was somewhat OT)
>
> I updated to F23 using the approved dnf method, with no errors. Now I have
> an unusable system because /home is not being mounted. It's a btrfs
> filesystem and w
On Wed, 4 Nov 2015 00:28:16 +
Patrick O'Callaghan wrote:
> Booting F22 mounts /home correctly, but I have no desktop as the upgrade
> removed my working akmod Nvidia stuff and for some reason Nouveau doesn't
> work.
This is the sort of thing that makes me always reinstall
from scratch in a vi
2015-11-04 2:28 GMT+02:00 Patrick O'Callaghan :
> (Repeating myself from another thread where this was somewhat OT)
>
> I updated to F23 using the approved dnf method, with no errors. Now I have
> an unusable system because /home is not being mounted. It's a btrfs
> filesystem and when trying to m
(Repeating myself from another thread where this was somewhat OT)
I updated to F23 using the approved dnf method, with no errors. Now I have
an unusable system because /home is not being mounted. It's a btrfs
filesystem and when trying to mount it manually I get:
mount: unknown filesystem type 'b
27 matches
Mail list logo
