On 21.03.2015, Chris Murphy wrote:
> OK it's a little annoying when you provide so little information from
> the very start about what you're trying to do, and what the setup is,
Here's what lsblk says before formatting:
AME FSTYPE LABEL UUID MOUNTPOINT
sda
On 03/21/2015 02:25 PM, Chris Murphy wrote:
> I found it in kernel-modules-extra (not extras as I wrote earlier) for
> both 3.19.2 and 4.0.0; I have no idea what the history is, whether
> that module has been in some other package before the kernel packaging
> changes for F21.
My F19 system has i
On 03/21/2015 02:04 PM, Heinz Diehl wrote:
My system is fine, and the phenomenon is 100% replicable.
And the behaviour is the same with the latest Fedora kernel from the Fedora
update repo.
One other thing you can do is give the partition a label, and list the
label in fstab instead. That way
On 21.03.2015, Chris Murphy wrote:
> OK it's a little annoying when you provide so little information from
> the very start about what you're trying to do, and what the setup is,
> and now you're not even using a Fedora kernel.
My original posting was kinda sort of "does this ring a bell?".
Othe
On Sat, Mar 21, 2015 at 12:11 PM, jd1008 wrote:
>
>
> On 03/21/2015 11:51 AM, Chris Murphy wrote:
>>
>> OK I think I found the problem. The Fedora kernel doesn't come with
>> nilfs2 kernel module. At least, a default Fedora 22 installation
>> doesn't include it.
>>
>>
>> Chris Murphy
>
> Did it ev
On 03/21/2015 11:51 AM, Chris Murphy wrote:
OK I think I found the problem. The Fedora kernel doesn't come with
nilfs2 kernel module. At least, a default Fedora 22 installation
doesn't include it.
Chris Murphy
Did it ever??
Which was the last release that had it?
--
users mailing list
users@
On Sat, Mar 21, 2015 at 11:52 AM, Heinz Diehl wrote:
> I don't use any distribution kernel. My kernel has nilfs2 - definitely.
> A manual mount works perfectly, just on boot /home doesn't get mounted and the
> system boots into emergency shell.
OK it's a little annoying when you provide so little
On 21.03.2015, Chris Murphy wrote:
> OK I think I found the problem. The Fedora kernel doesn't come with
> nilfs2 kernel module. At least, a default Fedora 22 installation
> doesn't include it.
I don't use any distribution kernel. My kernel has nilfs2 - definitely.
A manual mount works perfectly
On 21.03.2015, Chris Murphy wrote:
> I don't think systemd has any concept of filesystems (volume formats).
> It gets all of this from libblkid, udev, and the kernel. So I'd say
> one of those three things is confused, and then confuses everything
> else.
Didn't have much time today to further d
OK I think I found the problem. The Fedora kernel doesn't come with
nilfs2 kernel module. At least, a default Fedora 22 installation
doesn't include it.
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org
On Fri, Mar 20, 2015 at 11:59 PM, Heinz Diehl wrote:
> On 20.03.2015, Chris Murphy wrote:
>
>> If /dev/sda uses MBR, it doesn't really have a UUID, it might have a
>> serial number.
>
> It's MBR, and it didn't have a UUID before.
>
>> I think think needs more troubleshooting, rather
>> than bringi
On 20.03.2015, Chris Murphy wrote:
> If /dev/sda uses MBR, it doesn't really have a UUID, it might have a
> serial number.
It's MBR, and it didn't have a UUID before.
> I think think needs more troubleshooting, rather
> than bringing out the hammer before the problem is identified.
> Feel free
On Fri, Mar 20, 2015 at 10:49 AM, Heinz Diehl wrote:
> Hi,
>
> F21, fully updated, no longer boots cleanly. After to tries, I found the
> culprit:
>
> suddenly, the physical device (/dev/sda) has got a UUID, and it's the same as
> the one /home has. So no wonder that /home can't be mounted. I have
On 20.03.2015, Heinz Diehl wrote:
> Looks like a serious problem with nilfs-tools.
s/tools/utils;
--
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://fedoraproje
On 20.03.2015, jd1008 wrote:
> uuid is the way to go!!!
But not on the top-level physical device. No way in h*ll should /dev/sda have
any UUID. What happened was that systemd tried to mount /dev/sda on /home
rather than /dev/sda4, which of course can't work..
--
users mailing list
users@list
On 20.03.2015, Ron Morse wrote:
> I don't know about removing a UUID, but you can assign a new one with
> GParted.
Yes. But I was curious what could have assigned a UUID to /dev/sda. And I found
it. Making a nilfs2 partition on /home the evening before, lsblk -f reported
the same UUID for /de
On 03/20/2015 12:49 PM, Heinz Diehl wrote:
> Hi,
>
> F21, fully updated, no longer boots cleanly. After to tries, I found the
> culprit:
>
> suddenly, the physical device (/dev/sda) has got a UUID, and it's the same as
> the one /home has. So no wonder that /home can't be mounted. I have not the
>
On 03/20/2015 10:49 AM, Heinz Diehl wrote:
Hi,
F21, fully updated, no longer boots cleanly. After to tries, I found the
culprit:
suddenly, the physical device (/dev/sda) has got a UUID, and it's the same as
the one /home has. So no wonder that /home can't be mounted. I have not the
slightest
I don't know about removing a UUID, but you can assign a new one with GParted.
Sent from my iPhone
> On Mar 20, 2015, at 10:49 AM, Heinz Diehl wrote:
>
> Hi,
>
> F21, fully updated, no longer boots cleanly. After to tries, I found the
> culprit:
>
> suddenly, the physical device (/dev/sda)
Hi,
F21, fully updated, no longer boots cleanly. After to tries, I found the
culprit:
suddenly, the physical device (/dev/sda) has got a UUID, and it's the same as
the one /home has. So no wonder that /home can't be mounted. I have not the
slightest clue what could have given /dev/sda a UUID.
So
20 matches
Mail list logo
