probably change /etc/dnf/dnf.conf
such that installonly_limit is set to something like 10, just to make
sure dnf doesn't start deleting kernels. You can clean this up later,
which is a bit tedious, but that's another matter.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.or
On Tue, Jun 30, 2015 at 5:59 PM, Chris Murphy wrote:
> Actually, another option is to put the legacy OS into a VM where it
> can then inherit some of the features of Linux, including LVM support.
> Then you can LVM this external drive instead of partitioning it, and
> then make an L
Actually, another option is to put the legacy OS into a VM where it
can then inherit some of the features of Linux, including LVM support.
Then you can LVM this external drive instead of partitioning it, and
then make an LV (or two or three or whatever) to use as backing for
the VM, and then those
said :) :)
>
Full circle. Now you know that you will just have to keep on doing
what you've been doing: use the one time boot menu, or change the BIOS
boot order.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https
On Tue, Jun 30, 2015 at 5:38 PM, jd1008 wrote:
>
>
> On 06/30/2015 05:33 PM, Chris Murphy wrote:
>>
>> On Tue, Jun 30, 2015 at 5:26 PM, Gordon Messmer
>> wrote:
>>
>>> So you could dd 512 bytes of /dev/zero to the drive, or use "wipefs -a
>>
you don't do that.
--
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/
es gdisk.
wipefs -a after parted or gdisk will cause both PMBR and GPT primary
and backup headers to be invalidated. So to wipe or invalidate the
PMBR has to be done with dd.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https
o not understand GPT partition structures."
Also as a matter if trivia, the UEFI spec defines the boot code region
of the PMBR as 440 bytes. Table 15. Naturally GRUB's code length
differs from the UEFI spec.
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubs
validate the MBR's signature.
--
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://fedor
On Tue, Jun 30, 2015 at 5:13 PM, Gordon Messmer
wrote:
> On 06/30/2015 03:18 PM, Chris Murphy wrote:
>>
>> 2. The most likely explanation for the problem, as someone else
>> alluded to, is the USB drive has stale bootloader code on it that
>> points to no where a
e one time boot order change menu when you
want to boot off an external, otherwise leave the first device as the
internal drive.
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
T and b) you need to boot
> from the drive under BIOS. I don't think either of those apply to you.
If you have such a BIOS, the work around is to not partition it either
MBR or GPT. If it needs partitioning, use LVM on the whole block
device. It has a signature the BIOS won't know ab
IOS is also
ignoring/skipping the HD when bootloader code in the first 440 bytes
is absent but otherwise has a valid signature and partition
information.
If I partition a new blank VDI with parted, boot hangs indefinitely
with no error message.
Chris Murphy
--
users mailing list
us
in the form of an EFI CSM. If the first 440 bytes
are zeros, it doesn't consider that device bootable, and thus it's
skipped. But I don't recall SeaBIOS or vbox's BIOS behavior, even
though I've gotten bit by this confusion many times...
--
Chris Murphy
--
users mailing l
ped. However, fdisk will not erase existing code. So this only
applies going forward. Same for gdisk. And same for their variants.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
at wipefs is for. It also has a backup facility that makes
it easy to reverse mistakes.
http://man7.org/linux/man-pages/man8/wipefs.8.html
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/lis
nd backup header signatures, and the PMBR
signature, making all three of them invalid and thus not a partitioned
drive.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedor
or by parted developers. [1]
The solution is to do one of two things: change the boot order in
BIOS; or zero the first 440 bytes of LBA 0 with this:
# dd if=/dev/zero of=/dev/sdX bs=440 count=1
##where X is the letter for the USB drive
---
Chris Murphy
[1] Which I've complained abou
There is also:
dnf group list hidden
--
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/
t very recent
kernel versions.
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-cond
of
which is it saves a ton of compile time, not so much creating a lean
kernel (as anything not needed wouldn't be loaded anyway). Correct?
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mail
On Tue, Jun 30, 2015 at 9:36 AM, Chris Murphy wrote:
> If that solves the problem then it's likely related to gdm on Wayland
> and you can search for a bug to me too, or file a new one.
Actually best to file a new one because these problems all seem to be
GPU specific. So include a
and you can search for a bug to me too, or file a new one.
--
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
https://bugzilla.redhat.com/show_bug.cgi?id=1197419
--
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://fedorapr
ora's GRUB. But video stuff is kind hard in that
early boot environment.
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.o
bug where for some reason in certain instances
root=/dev/ is used instead of root=UUID= and I'm spacing out why
this happens. But the usual fix is to get it to boot manually somehow,
and then recreate the grub.cfg from scratch with grub2-mkconfig - and
invariably that one will have all entries
't have those
kernels. So you'll want to make sure you have both /etc/yum.conf and
/etc/dnf/dnf.conf set to preserve more than 3 kernels to make sure
neither one starts deleting kernels you might need.
Of course, then the problem is ext4 /boot can become full which is why
we really
r backup, but
there are still cases where btrfs check cannot fix the problem.
And it's still mostly advisable to not run btrfs check --repair
without first posting the complete results of btrfs check to the
btrfs@ list.
So if this all sounds overly complicated and daunting th
ux/isolinux/extlinux configuration files). Sadly, grub2-mkconfig
doesn't create menu entries using these commands by default so it's
not the most user friendly thing.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://a
the DEK in favor of
a new one.
--
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
o a reserve
sector. A write error happens when there are no more reserve sectors.
--
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/c
On Sun, Mar 29, 2015 at 7:39 PM, Joe Zeff wrote:
> On 03/16/2015 04:43 PM, Chris Murphy wrote:
>>
>> That should get you more than one line. What's probably happening is
>> there's an early "Not Tainted" line which is the one to file as a bug.
>
>
&
atever was missing previously.
Ahh. That sorta sounds like possibly a dracut bug affected the
original initramfs you had. So then dracut gets updated, and kernel
update causes a new initramfs to be generated with updated dracut, and
so the problem seems magically fixed.
--
Chris Murphy
--
users
ost-install created raid1 to
be picked up and activated automatically at boot. It's only activated,
not mounted, and the boot didn't fail. So without more information
it's difficult to help.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
irmware setup access from
Windows, and reboot, at which point now the user must learn how to
change the boot order using efibootmgr via CLI since there isn't a GUI
boot manager.
Kinda, ick. But shortly after Windows 10 is released, we'll see Fedora
23 which should have the bug fixed at the
On Tue, Mar 24, 2015 at 5:57 PM, Patrick O'Callaghan
wrote:
> On Tue, 2015-03-24 at 11:40 -0600, Chris Murphy wrote:
>> On Tue, Mar 24, 2015 at 5:14 AM, Patrick O'Callaghan
>> wrote:
>> > On Mon, 2015-03-23 at 17:50 -0600, Chris Murphy wrote:
>> &
On Tue, Mar 24, 2015 at 5:14 AM, Patrick O'Callaghan
wrote:
> On Mon, 2015-03-23 at 17:50 -0600, Chris Murphy wrote:
>> OK I'm going to display some total KDE ignorance here, hopefully a KDE
>> user can answer this.
>
> Note that there's a Fedora-KDE list
apped means using dd or badblocks with the proper blocksize
(a multiple of 4096 bytes).
--
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://fedorapr
ering what the equivalent is on KDE, with about that much detail.
Thanks,
--
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/c
# ls -lZ /
root should have label
dr-xr-x---. 3 root root system_u:object_r:admin_home_t:s0 4096 Mar
21 11:44 root
If it doesn't.
restorecon -rv /
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraprojec
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 i
13dd1d / xfs
defaults0 0
UUID=9f5d6b34-7c6f-4e6c-996e-122f5b68e1f8 /boot xfs
defaults0 0
UUID=2e2ef4de-13df-41d2-9e2e-593dfd42fb64 /home
nilfs2 defaults 0 0
#UUID=0bc7066a-b8f1-4949-b480-3775dd5efec4 /home
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 opti
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
Not applicable. I advise staying on the rails.
On Mar 20, 2015 3:22 PM, "jd1008" wrote:
>
>
> On 03/20/2015 03:19 PM, Chris Murphy wrote:
>
>> sudo hdparm --user-master u --security-set-pass Eins /dev/sdX
>>
>> sudo time hdparm --user-master u --securit
sudo hdparm --user-master u --security-set-pass Eins /dev/sdX
sudo time hdparm --user-master u --security-erase Eins /dev/sdX
OR
sudo time hdparm --user-master u --security-erase-enhanced Eins /dev/sdX
Just copy and paste it. Two commands are needed. Just two. Not three. Not one.
--
users maili
> http://mackonsti.wordpress.com/2011/11/22/ssd-secure-erase-ata-command
And just to quality that source, I use it all the time, so I know it
works. Both SSD and HDD.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
ht
e-ata-command
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
blkid.
It might also be useful to see the output from journalctl -b -l -o
short monotonic, from a boot that fails, that also has kernel
parameter rd.debug set.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedorapr
two drives in the simplest way
possible, this is certainly very simple, and it's also dual boot
compatible.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Cod
fter the upgrade, reboot normally and see if the problem is
solved.
>
> The /var/log/messages file is very extensive;
Fedora 21 Workstation doesn't come with rsyslogd, so there shoudn't be
a /var/log/messages. Fedora 21 Server does.
--
Chris Murphy
--
users m
On Wed, Mar 18, 2015 at 11:18 AM, jd1008 wrote:
>
>
> On 03/17/2015 10:59 PM, Chris Murphy wrote:
>>
>> Taint is always caused by out of tree kernel modules. If you haven't
>> installed anything that installs kernel modules, most typically that's
>> vide
On Tue, Mar 17, 2015 at 10:57 PM, Tim wrote:
> On Tue, 2015-03-17 at 21:22 -0600, Chris Murphy wrote:
>> Sounds like a UI bug.
>
> Agreed. And, it would appear, that becomes a "don't really care about
> fixing it" issue, as sound still works, even if the contr
On Tue, Mar 17, 2015 at 10:42 PM, Joe Zeff wrote:
> On 03/17/2015 08:22 PM, Chris Murphy wrote:
>>
>> 2. how to provide useful debugging info - if the user will not test a
>> non-tainted kernel I see no possible way for an automated system to
>> know where to file the
On Tue, Mar 17, 2015 at 8:14 PM, Tim wrote:
> On Tue, 2015-03-17 at 14:51 -0600, Chris Murphy wrote:
>> If you know the site already, why not just file the bug directly on
>> that bugzilla? Why does it need to be automated?
>
> As a general response, I'd say that:
>
n the MBR, which
doesn't at all depend on active bit (boot flag), it directly forwards
to an LBA. So as long as the firmware can address that LBA, the GRUB
stage2/core.img can be essentially anywhere hence fewer limitations.
--
Chris Murphy
--
users mailing list
users@lists.fe
On Tue, Mar 17, 2015 at 6:28 PM, jd1008 wrote:
>
>
> On 03/17/2015 06:19 PM, Chris Murphy wrote:
>>
>> dd if=/dev/sdX count=1 2>/dev/null | hexdump -C
>
> # dd if=/dev/sdb bs=440 count=1 2>/dev/null | hexdump -C
> 00 00 00 00
On Tue, Mar 17, 2015 at 6:08 PM, jd1008 wrote:
>
>
> On 03/17/2015 05:58 PM, Chris Murphy wrote:
>>
>> The solution is to go to firmware setup and define a different drive
>> as primary. Or zero the first 440 bytes of the external drive e.g. dd
>> if=/de
are setup and define a different drive
as primary. Or zero the first 440 bytes of the external drive e.g. dd
if=/dev/zero of=/dev/sdX bs=440 count=1
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/
x27;t know. But it seems like it's the wrong list to ask. And as Fedora
is community driven, I'd ask if those third parties would pitch in on the
work needed that they'd benefit from, if they value these reports being
automated.
Chris Murphy
--
users mailing list
users@lists.fed
On Tue, Mar 17, 2015 at 2:41 PM, Rick Stevens wrote:
> On 03/17/2015 01:26 PM, Chris Murphy wrote:
>> a. It actually has to communicate with a server, so whose hosting this
>> "other" bugzilla?
>
>
> I think the point here is that a user could configure ADDITIO
On Tue, Mar 17, 2015 at 2:32 PM, Joe Zeff wrote:
> On 03/17/2015 01:26 PM, Chris Murphy wrote:
>>
>> Why bother with this infrastructure if no one is going to look at the
>> reports or do anything about them?
>
>
> Why do you assume that nobody's going to
On Tue, Mar 17, 2015 at 2:15 PM, jd1008 wrote:
>
>
> On 03/16/2015 02:58 PM, Joe Zeff wrote:
>>
>> On 03/16/2015 12:37 PM, Chris Murphy wrote:
>>>
>>>
>>> Just because the crash doesn't occur in an out of tree module, doesn't
>>
On Tue, Mar 17, 2015 at 2:11 PM, jd1008 wrote:
>
>
> On 03/16/2015 01:37 PM, Chris Murphy wrote:
>>
>> On Mon, Mar 16, 2015 at 10:44 AM, jd1008 wrote:
>>
>>> Since none of the crashes occur in the modules
>>> inserted via akmods, why is the fed
that is always considered tainted
because of the first one. If the first oops (for a boot) is tainted,
then there's a letter code that indicates why, but Fedora kernels
don't ever do this on their own, but if they did that itself would be
a bug.
--
Chris Murphy
--
users
On Mon, Mar 16, 2015 at 2:58 PM, Joe Zeff wrote:
> On 03/16/2015 12:37 PM, Chris Murphy wrote:
>>
>>
>> Just because the crash doesn't occur in an out of tree module, doesn't
>> mean that the out of tree module isn't instigating the problem though.
>
On Mon, Mar 16, 2015 at 3:19 PM, Chris Murphy wrote:
> out of tree kernel affects kernel behavior.
tree kernel ^module
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/us
ross-post (explicitly mentioned from the outset
it's a crosspost).
Just because the crash doesn't occur in an out of tree module, doesn't
mean that the out of tree module isn't instigating the problem though.
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsub
Yet power on hours is 1800+. That's funny. If I could lie about my
lifetime age on every test, that would be awesome. How old are you?
Today, hmm, I'm feeling 6 years old, that work for you? No? OK 19?
That's age of majority at least. Oh you don't like that either, OK
fine ba
On Sun, Mar 15, 2015 at 9:40 AM, Robert Nichols
wrote:
> On 03/15/2015 10:23 AM, Chris Murphy wrote:
>>
>> On Sun, Mar 15, 2015 at 8:54 AM, Robert Nichols
>> wrote:
>>
>>> One thing I noticed in there is:
>>>
>>>193 Load_Cycle_Count
it was designed for. The less time the
heads are flying over platter surface, the better. Even though this
attribute value is 001 and the threshold is 000, it's not a pre-fail
attribute, just an age attribute. It's probably instigated at least as
much by something that's fsyncin
size..
> but I can find inside it if you say me what to look for.
> -
This is the bug I filed before I realized my problem was hardware
related. Under "Additional info" you'll see the lines that are missing
from dmesg when the problem happens.
https://bugzilla.re
thing is triggered with the backup, try a non-destructive
badblocks or dd read of the drive. Any error reported by either of
those that's not triggered by the backup is probably safe to just
write over. Just make sure to get the block conversion right.
--
Chris Murphy
--
users mailing list
u
On Sat, Mar 14, 2015 at 5:56 PM, Tom Horsley wrote:
> On Sat, 14 Mar 2015 16:42:37 -0600
> Chris Murphy wrote:
>
>> If there's a definite latent sector error, this shows up with a
>> 'smarctl -t long' which will be aborted at the first error found
On Sat, Mar 14, 2015 at 5:29 PM, Tom Horsley wrote:
> On Sat, 14 Mar 2015 17:13:15 -0600
> Chris Murphy wrote:
>
>> The top post here is a good example of a URE due to media error.
>> http://ubuntuforums.org/archive/index.php/t-1034762.html
>
> Yep, that the sort of thi
a, like from torn writes or
something) or you get some write errors with reallocations on the
first pass. And no errors for subsequent passes. If any subsequent
passes have errors, especially corruption errors, then get rid of the
drive or turn it into a play thing or send it to me :-D
--
Chris Murp
verable. Fedora actually has smartd running by default and
it'll report some things into the journal; if it's minimally
configured it can do smart -t long on a schedule and report more
things.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or chan
27;s instigating
this? Or if it's just coincidence. I guess the sample size isn't big
enough to know.
What happens if you boot from install media, and capture both
dmesg
efiboomgr -v
?
In my case, dmesg clearly showed the lack of proper ACPI
initialization, no drive was found at all.
--
C
scratch again but
> would prefer not.
This looks most likely, unless you can find out what's consuming so
much space on /.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/u
fixed. This is a problem for
md, LVM, ZFS and Btrfs raid. So configuration has to be correct. This
is a monthly event on linux-raid@ (or even more often sometimes
several per week), and a high percent of the time all data on the raid
is lost in the ensuing recovery.
Backups!
--
Chris M
On Thu, Mar 12, 2015 at 3:58 PM, Chris Murphy wrote:
> Anyway, seeing as this happens on an fsck, that means filesystem
> metadata is affected and if e2fsck -f doesn't fix it then, the fs is
> toast. I honestly would just immediately remount it ro, and back it up
> though befor
On Thu, Mar 12, 2015 at 3:37 PM, jd1008 wrote:
>
>
> On 03/12/2015 03:28 PM, Chris Murphy wrote:
>>
>> smarctl -l scterc /dev/sdb
>
> # smartctl -l scterc /dev/sdb
> smartctl 6.2 2014-07-16 r3952 [x86_64-linux-3.18.8-201.fc21.x86_64] (local
> build)
>
On Thu, Mar 12, 2015 at 3:28 PM, Chris Murphy wrote:
> What do you get for:
> smarctl -l scterc /dev/sdb
smartctl -l scterc /dev/sdb
Helps to not have typos, and this command likes that additional t.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscr
unctioning normally - so
far. But you're right, it's brand new and to have a sector read error
on a brand new drive is unexpected.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject
On Thu, Mar 12, 2015 at 9:56 AM, Chris Murphy wrote:
> If you go to:
> admin.fedoraproject.org/updates
> and type in kernel, you'll see kernel-3.18.9-200.fc21 is in "testing"
> which translates into
>
> # su -c 'yum update --enablerepo=updates-testing kerne
el-3.18.9-200.fc21 is in "testing"
which translates into
# su -c 'yum update --enablerepo=updates-testing kernel-3.18.9-200.fc21'
If that doesn't work I usually clobber it with 'yum clean all' and then retry.
--
Chris Murphy
--
users mailing list
users@lists.fe
On Tue, Mar 10, 2015 at 2:55 PM, Chris Murphy wrote:
> Amazon Glacier is fairly inexpensive
Google announced Nearline option for Google Cloud Storage, priced
similar to Amazon Glacier but with faster retrieval. Storage price is
the same, but retrieval is more expensive from the looks of
or
more surviving drives have one or more bad sectors and md can't
recover from that automatically.
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: ht
That's slow. There is a feature idea to get
rsync some Btrfs awareness so that this can be optimized, taking
advantage of work Btrfs has already done, rather than separately
compute additional checksums.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.or
id0 is mainly for size, of course it totally dies
if anyone device dies. But in the meantime, I still get notifications
of any corrupt files (by full filename path) should that happen.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change s
ted or
corrupted file) it can be expensive. There are 3rd party calculators
for computing this, it's not exactly obvious what things will cost
just based on their rather convoluted pricing page.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To un
d destination are the same
independent of drives' ECC.
--
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:
an experimental, but
raid56 is still a gray area. I can't suggest enough having more than
one backup, but that's emphasized more if the primary one is on Btrfs.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://
meout
And don't forget period scrubs:
echo check > /sys/block/mdX/md/sync_action
cat /sys/block/mdX/mismatch_cnt
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedo
here any NAS projects that may be beneficial?
lwn.net has recent reviews of Rockstor, EasyNAS, OpenMediaVault,
FreeNAS (BSD ZFS based).
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraprojec
It think you need to do:
systemctl enable gdm
There might be some other services that need to be enabled. This is
the enabled list for a recent installation of Fedora 21 Workstation:
http://ur1.ca/jvh4d
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change
But still you really should have
poked the thing right in front of you, the Troubleshooting menu, with
a stick, before poking people on a mailing list. It's really that
basic.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
ht
uestions and a how to, and to actually do that effectively
I'd probably need to run through it myself and I don't have the
hardware to do that at the moment.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://adm
from some other image,
but it'll take one early reboot after changing the last partition
size, or adding another partition, to capture the extra space from
qemu-img resize.
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://adm
On Fri, Mar 6, 2015 at 9:35 PM, Chris Murphy wrote:
> There is an absolute minimum of 5 clicks to do a Fedora installation,
Correction, 7. Root password & Quit/Reboot.
--
Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options
801 - 900 of 1528 matches
Mail list logo