On Thu, Dec 21, 2023 at 10:35:45AM -0600, Chris Adams wrote:
> Once upon a time, Beniamino Galvani said:
> > network-scripts do [1]:
> >
> > /sbin/arping -c 2 -w ${ARPING_WAIT:-3} -D -I ${REALDEVICE} ${ipaddr[$idx]}
> >
> > which waits 2 seconds by default.
>
> Ahh, sorry, that's what I get fo
OLD: Fedora-Rawhide-20231226.n.0
NEW: Fedora-Rawhide-20231227.n.0
= SUMMARY =
Added images:1
Dropped images: 1
Added packages: 5
Dropped packages:0
Upgraded packages: 34
Downgraded packages: 0
Size of added packages: 167.59 KiB
Size of dropped packages:0
I could you use some help with ${SUBJECT}. I posted the details in
discussion [1], but have yet to receive a response. I thought maybe
folks on the list may have an idea.
I'm kinda lost as to where this is going wrong. Feel free to reply
either on discussion or here. I'd appreciate any help I
Once upon a time, Beniamino Galvani said:
> In practice, it's a bit more complex than that. network-online.target
> is emitted after all NM connections succeed. The meaning of "success"
> depends on properties "ipv4.may-fail" and "ipv6.may-fail" of the
> connection profile. Normally they are both
On 12/27/23 15:05, Sandro wrote:
I could you use some help with ${SUBJECT}. I posted the details in
discussion [1], but have yet to receive a response. I thought maybe
folks on the list may have an idea.
I'm kinda lost as to where this is going wrong. Feel free to reply
either on discussion or h
On 12/27/23 15:14, pgnd wrote:
what's the output of:
mdadm -Es
cat /etc/mdadm.conf
# mdadm -Es
ARRAY /dev/md/5 metadata=1.1 UUID=39295d93:e5a75797:b72287f3:51563755
name=urras.penguinpee.nl:5
ARRAY /dev/md/1 metadata=1.1 UUID=4a2c44b5:25f2a6c9:0e7f6cae:37a8a9cc
name=urras.penguinpe
On 12/27/23 16:47, pgnd wrote:
i explicitly add the
level=
num-devices
i've had issues long ago with mis-assembly that that cured.
whether it's STILL a problem, i don't know; all my array spec contain contain
these, and don't cause harm. it's now SOP here.
i'd at least conside
On 12/27/23 17:10, pgnd wrote:
If it works, I'd still wonder why md54 comes up fine. That entry is also
missing `level` and `num-devices`.
1st WAG ?
WAG?
/dev/md/54 is 'just' raid1, without an atypical spare
It's not. It's a raid5 without any spare just like md5. Only difference
between
On 12/27/23 17:03, pgnd wrote:
also make sure your drivers are in the initrd
lsinitrd | grep -Ei "kernel/drivers/md/raid"
-rw-r--r-- 1 root root10228 Nov 15 19:00
usr/lib/modules/6.6.8-200.fc39.x86_64/kernel/drivers/md/raid0.ko.xz
-rw-r--r-- 1 root root35376 Nov 15 1
On 12/27/23 17:28, pgnd wrote:
WAG?
https://www.urbandictionary.com/define.php?term=wild%20ass%20guess
;) I should have guessed...
I added `level` and `num-devices` to all entries in mdadm.conf and rebooted. It
didn't change anything. Manual assembly still freezes the system as well.
hm
On 12/27/23 17:36, Sandro wrote:
I'll try with a F39 live ISO as well. If nothing else, it could confirm
the issue to be with/in F39.
I did that. Right after boot only one of the arrays was assembled. In
/proc/mdstat is was listed as "active (auto-read-only)" and the
component devices matched
Hello!
I intend to hand over primary maintainership of the following packages
or orphan them if nobody steps up:
arpack
chemtool
cp2k
elpa
inchi
python-colorspacious
python-fypp
python-GridDataFormats
python-gsd
python-kaitaistruct
python-mmtf
python-mrcfile
python-Pympler
tachyon
wxmacmolplt
xdraw
On 12/27/23 22:48, pgnd wrote:
without seeing all the details, unfound superblocks aren't good.
But isn't the information `mdadm --examine` prints coming from the
superblock stored on the device? The magic number, that this command
reports, matches what was expected (a92b4efc). I can access t
On 12/27/23 08:20, Sandro wrote:
I added `level` and `num-devices` to all entries in mdadm.conf and
rebooted. It didn't change anything. Manual assembly still freezes the
system as well.
You need to also update the initramfs using dracut or the modified
mdadm.conf won't be available at boot.
On 12/27/23 06:05, Sandro wrote:
I could you use some help with ${SUBJECT}. I posted the details in
discussion [1], but have yet to receive a response. I thought maybe
folks on the list may have an idea.
I'm kinda lost as to where this is going wrong. Feel free to reply
either on discussion o
On 12/27/23 15:12, Samuel Sieb wrote:
On 12/27/23 06:05, Sandro wrote:
I could you use some help with ${SUBJECT}. I posted the details in
discussion [1], but have yet to receive a response. I thought maybe
folks on the list may have an idea.
I'm kinda lost as to where this is going wrong. Fee
On 12/28/23 00:04, Samuel Sieb wrote:
On 12/27/23 08:20, Sandro wrote:
I added `level` and `num-devices` to all entries in mdadm.conf and
rebooted. It didn't change anything. Manual assembly still freezes the
system as well.
You need to also update the initramfs using dracut or the modified
md
17 matches
Mail list logo
