Re: SOLVED mdadm: Cannot get exclusive access to /dev/md127
by Rich Emberson
Thanks for the help!
cryptsetup luksClose luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9
did the trick.
Steps
Remove entry from /etc/fstab
# vi /etc/fstab
then following sequence of commands:
# lsof +d /raid1/
<nothing>
# lsof +D /raid1/
<nothing>
# df
</raid1 does not show up>
# mount
</raid1 does not show up>
# cryptsetup luksClose luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9
<nothing>
# cryptsetup luksClose luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9
<Device luks-ab8911f9-b3a4-4f33-8b10-7e52c7217ae9 is not active.>
# wipefs -a /dev/md127
<nothing>
# mdadm -S /dev/md127
<nothing>
# mdadm --misc --zero-superblock /dev/sdd1
<nothing>
# mdadm --misc --zero-superblock /dev/sdc1
<nothing>
# ls /raid1/
<nothing>
# touch /raid1/foo
<nothing>
# ls /raid1/
<foo>
# rm /raid1/foo
# lsof +d /home
<lots of entries>
# lsof +d /raid1/
<nothing>
# umount /raid1/
<nothing>
# umount -f /raid1/
<nothing>
# /bin/rm -rf /raid1/
<nothing>
# lsof | grep md127
<nothing>
Now fdisk, partprobe, mkfs.ext4, fsck, mkdir /mountpoint, mount for each
disk that was part of the raid group.
Again, thanks
9 years, 2 months
Blocking POODLE
by Matthew Saltzman
SSLLabs reports a couple of servers of mine have SSL v3 enabled and are
vulnerable to POODLE. I followed instructions for Apache httpd at
https://scotthelme.co.uk/sslv3-goes-to-the-dogs-poodle-kills-off-protocol/, but that does not seem to cure the problem. SSLLabs still reports the servers as vulnerable. Does anyone know what I'm missing?
The server also runs Trac and Subversion servers and a separate vhost
runs Jenkins. Does something special need to be done for those
services?
(These are, in fact, RHEL 7 servers running httpd-2.2.15-39.el6.x86_64,
but I hope someone here will know what's going on.)
Thanks in advance.
--
Matthew Saltzman
Clemson University Math Sciences
mjs AT clemson DOT edu
9 years, 2 months
Fedora 21 shutting down after logging in?
by Richard Shaw
I'm troubleshooting some video problems with a used laptop I got for cheap.
For the day is was pretty nice, Dell Latitude D620 with Nvidia Quadro
graphics (the problem I'm troubleshooting).
I was looking through the journal when I saw this shortly after logging in:
Feb 03 17:47:15 localhost.localdomain systemd-logind[676]: Removed session
c1.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Default.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Default.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Basic System.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Basic
System.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Paths.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Paths.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Timers.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Timers.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Sockets.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Sockets.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Starting Shutdown.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Reached target
Shutdown.
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Starting Exit the
Session...
Feb 03 17:47:15 localhost.localdomain systemd[1364]: Received SIGRTMIN+24
from PID 2173 (kill).
Why does systemd think I'm trying to shut down the computer right after
logging in?
The computer doesn't actually shut down and I'll get a usable desktop after
what I assumed was a hard lock but it takes well over 5 minutes, I haven't
put a stopwatch to it.
Thanks,
Richard
9 years, 2 months
Re: NETDEV WATCHDOG: internal(r8152): transmit queue 0 timed out
by poma
On 16.01.2015 10:37, Hayes Wang wrote:
> poma [mailto:pomidorabelisima@gmail.com]
>> Sent: Friday, January 16, 2015 4:25 PM
> [...]
>>> This looks like a USB problem. Is there a way to get usb (or
>>> NetworkManager) to reinitialize the driver when this happens?
>>
>> I would ask these people for advice, therefore.
>
> Our hw engineers need to analyse the behavior of the device.
> However, I don't think you have such instrument to provide
> the required information. If we don't know the reason, we
> couldn't give you the proper solution. Besides, your solution
> would work if and only if reloading the driver is helpful.
>
> The issue have to debug from the hardware, and I have no idea
> about what the software could do before analysing the hw. Maybe
> you could try the following driver first to check if it is useful.
>
> http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=2&PNid=13&P...
>
> Best Regards,
> Hayes
>
Thanks for your response, Mr. Hayes.
Mr. Sean, please download and check if "timeout" is still present with built RTL8153 module from REALTEK site, as Mr. Hayes proposed.
http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=2&PNid=13&P...
r8152.53-2.03.0.tar.bz2
Procedure - should be equal for both, Fedora 21 & 20:
$ uname -r
3.17.8-300.fc21.x86_64
$ su -c 'yum install kernel-devel'
$ tar xf r8152.53-2.03.0.tar.bz2
$ cd r8152-2.03.0/
$ make
$ su
# cp 50-usb-realtek-net.rules /etc/udev/rules.d/
# udevadm trigger --action=add
# modprobe -rv r8152
# cp r8152.ko /lib/modules/$(uname -r)/updates/
# depmod
# modprobe -v r8152
poma
9 years, 2 months
yum update errors wine-core
by Paul Cartwright
Is this just me, or should I wait for package updates??
updated fedora21 x86_64 ..
when I try to update I get:
--> Finished Dependency Resolution
Error: Package: wine-core-1.7.35-3.1.i686 (@home_DarkPlayer_Pipelight)
Requires: libgphoto2_port.so.10(LIBGPHOTO2_5_0)
Removing: libgphoto2-2.5.3-9.fc21.i686 (@fedora)
libgphoto2_port.so.10(LIBGPHOTO2_5_0)
Updated By: libgphoto2-2.5.7-1.fc21.i686 (updates)
~libgphoto2_port.so.12(LIBGPHOTO2_5_0)
Error: Package: wine-core-1.7.35-3.1.x86_64 (@home_DarkPlayer_Pipelight)
Requires: libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit)
Removing: libgphoto2-2.5.3-9.fc21.x86_64
(@koji-override-0/$releasever)
libgphoto2_port.so.10(LIBGPHOTO2_5_0)(64bit)
Updated By: libgphoto2-2.5.7-1.fc21.x86_64 (updates)
~libgphoto2_port.so.12(LIBGPHOTO2_5_0)(64bit)
Error: Package: wine-core-1.7.35-3.1.i686 (@home_DarkPlayer_Pipelight)
Requires: libgphoto2_port.so.10
Removing: libgphoto2-2.5.3-9.fc21.i686 (@fedora)
libgphoto2_port.so.10
Updated By: libgphoto2-2.5.7-1.fc21.i686 (updates)
~libgphoto2_port.so.12
Error: Package: wine-core-1.7.35-3.1.x86_64 (@home_DarkPlayer_Pipelight)
Requires: libgphoto2_port.so.10()(64bit)
Removing: libgphoto2-2.5.3-9.fc21.x86_64
(@koji-override-0/$releasever)
libgphoto2_port.so.10()(64bit)
Updated By: libgphoto2-2.5.7-1.fc21.x86_64 (updates)
~libgphoto2_port.so.12()(64bit)
You could try using --skip-broken to work around the problem
whats wrong?
--
Paul Cartwright
Registered Linux User #367800 and new counter #561587
9 years, 2 months
What are *.xz compressed kernel modules for (Fedora 21)
by Kevin Wilson
Hi,
I have Fedora 21 (x86_64).
Under /usr/lib/modules/3.17.4-302.fc21.x86_64/kernel, all the kernel
module are in compressed form.
(xz files).
Under
/usr/lib/modules/3.17.4-302.fc21.x86_64/kernel, the kernel modules
are in the *.ko form
What are the *.xz compressed kernel modules for ? In fedora 20 we had
only *.ko files under /lib/modules.
It seems to me that after booting, when running modprobe, only the
*.ko modules are used.
Just wonder what would happen If I would (accidentally or by purpose)
delete the /lib/modules folder in fedora 21 (I don't intend to do it
before getting an answer here...)
Regards,
Kevin
9 years, 2 months
F20: No sound unless root ??
by sean darcy
I'm trying to play some sound as a user. But pulseaudio can't find any
outputs:
$ aplay -l
aplay: device_list:268: no soundcards found...
But, as root, aplay sees the integrated sound card:
# aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: SB [HDA ATI SB], device 0: VT2020 Analog [VT2020 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 1: VT2020 Digital [VT2020 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: SB [HDA ATI SB], device 2: VT2020 Alt Analog [VT2020 Alt Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
I'd just use root if I could, by pulseaudio doesn't like that.
sean
9 years, 2 months
Re: mdadm: Cannot get exclusive access to /dev/md127
by Rich Emberson
Tried:
# wipefs -a /dev/md127
which did not word, so I next tried:
# wipefs -f -a /dev/md127
/dev/md127: 6 bytes were erased at offset 0x00000000 (crypto_LUKS): 4c 55
4b 53 ba be
and then
# mdadm -S /dev/md127
mdadm: Cannot get exclusive access to /dev/md127:Perhaps a running process,
mounted filesystem or active volume group?
but the filesystem is still mounted.
curious, that creating an encrypted raid system on fedora seems to be an
irreversible action.
Now, with part of the raid file system "wipefs"-ed, above, I fear rebooting
and hanging when it does not come up.
Richard
9 years, 2 months
Adding a file share service to Thunderbird
by JD
Often I want to attach a file that is larger than what google will allow,
a limit I configured in TB. And TB will prompt me to use a file share
service.
The problem is I do not want to use the 2 file share services that TB is
showing,
and none of the add-on have my preferred file share server.
Has anyone somehow overcome this "apparent" limitation of TB, and configured
TB to use a file share service other than what TB and the plugins (add-ons)
provide?
9 years, 2 months
Re: Mediacast to TV - MiracleCast - Open-Source Miracast - Wifi-Display on linux
by poma
On 02.02.2015 19:58, David Herrmann wrote:
> Hi
>
> On Sun, Feb 1, 2015 at 10:50 AM, poma <pomidorabelisima(a)gmail.com> wrote:
>> MiracleCast - Howto
>> "Current State"
>
> [snip]
>
>> Can folks from the NetworkManager team & systemd-networkd team answer regarding the current status in this matter?
>
> As people continuously ask me about this, I'll just try to answer it
> on the public ML:
>
> To make Miracast work, we need access to a Wifi P2P API. The kernel
> implements Wifi P2P and wpa_supplicant provides access to it via it's
> ctrl-interface (and I think recently even gained a dbus API). In
> MiracleCast I wrote a miracle-wifid daemon that wraps wpa_supplicant
> and provides P2P to MircaleCast. However, this does not work well in
> parallel to NetworkManager/wicd/connman/... running. You really cannot
> run wpa_supplicant multiple times on the same interface. Hence,
> MiracleCast development is currently stalled until the different
> network-managers provide a P2P API.
>
Are you for to make the request for improvement towards NetworkManager?
> Intel recently added such an API to ConnMan and provides a WFD
> implementation on its own [1]. I highly recommend looking into it.
> It's now up to NetworkManager to catch up. systemd-networkd doesn't do
> L2 setup, so it's not really related. wicd is kinda dead [2], so I
> doubt they'll come up with something.
>
> Furthermore, P2P support is pretty "limited" right now. Officially,
> almost all recent devices support it, but it's particularly annoying
> to set it up, due to major bugs across all the stacks (in no way
> limited to linux drivers). I mean, 3 of 4 of my connection attempts
> between Android and Windows devices fails.. not even talking about my
> wpa_supplicant hacks.
>
Thank you for your comprehensive explanation!
> As I'm not really interested in hacking on network-managers, I've
> decided to stop working on MiracleCast. If, some day, there's a
> working P2P stack on linux, I might resurrect it. But it sounds more
> likely that I'll refer to the Intel solution (WYSIWIDI) instead.
> There're also gstreamer plugins for WFD now, so maybe give them a try?
>
gst-rtsp-server-wfd
https://github.com/Samsung/gst-rtsp-server-wfd/blob/master/README.md
Pre-conditions:
This module is running on established p2p connection with wifi direct, which means that you have to setup this network environment to run this module. I hope this link would be very helpful. ( http://cgit.freedesktop.org/~dvdhrm/miracle )
You are referring to them, they are referring to you. :)
> Thanks
> David
>
> [1] https://github.com/01org/wysiwidi
> [2] https://answers.launchpad.net/wicd/+question/227789
>
9 years, 2 months