Perfect! Then I just need to add an alias to my profile and can use nslookup :-)
On 21.10.23 17:58, David Wright wrote:
On Sat 21 Oct 2023 at 17:35:21 (+0200), Reiner Buehl wrote:
> is there a DNS lookup command that is installed by default on any
> Debian Bullseye or Bookworm i
Hi all,
is there a DNS lookup command that is installed by default on any Debian
Bullseye or Bookworm install? Something that doesn't require as much
dependencies as bind9-utils (which provides dig and nslookup) or bind9-host?
Best regards,
Reiner
Hi,
I am trying to setup lm_sensors for an older Zotac IONITX-U-E mainboard.
The values I get from the w83667hg-isa-0a10 are all looking good and are in
line with what I see in the BIOS. But the values I get from
coretemp-isa- are way off. They are around +9/+10°C for both cores
while the ambi
On 27.03.2022 18:12, Nicholas Geovanis wrote:
On Sun, Mar 27, 2022, 7:31 AM Reiner Buehl wrote:
Hi all!
I am trying to build an amd64 Debian package from sources but the
command dpkg-buildpackage -us -uc fails with a number of the
following
error messages:
ERROR
Hi all!
I am trying to build an amd64 Debian package from sources but the
command dpkg-buildpackage -us -uc fails with a number of the following
error messages:
ERROR: ld.so: object 'libfakeroot-sysv.so' from LD_PRELOAD cannot be
preloaded (wrong ELF class: ELFCLASS64): ignored.
I have ins
It seems that the command /sbin/lvm pvscan --cache --activate ay 9:0 from
the Systemd unit lvm2-pvscan@9:0.service is hanging and blocks all
subsequent lvm activities.
Am Fr., 25. März 2022 um 20:40 Uhr schrieb Reiner Buehl <
reiner.bu...@gmail.com>:
> Hi all,
>
> I am crossgr
Hi all,
I am crossgrading my Debian Buster system from i386 to amd64 following the
guide from the Debian Wiki (https://wiki.debian.org/CrossGrading). After
the apt full-upgrade I rebooted but now my LVM volumes are not activated
again.
The LVM event activation by systemd times out after 90s. I can
On 04.10.2021 03:41, Joe Pfeiffer wrote:
That's not it then... googling "md127" I found a *bunch* of possible
causes.
I tried already updating the name attribute, setting the homehost to
none and a few others. Unfortunately none helped.
On 02.10.2021 01:32, Joe Pfeiffer wrote:
Is it possible you need to update your init ramdisk? Maybe your changes
to your mdadm.conf aren't being seen?
I do run update-initramfs -u after each change. Shouldn't that be enough
to to update the mdadm.conf in the init ramdisk?
On 01.10.2021 16:11, Felix Miata wrote:
Mine (old) is like so:
# head -n3 /etc/mdadm.conf
HOMEHOST
DEVICE containers partitions
ARRAY /dev/md0 metadata=1.0 name=msi85:0tmp UUID=...
I tried changing the HOMEHOST from to but that did not
help.
On 01.10.2021 15:50, Linux-Fan wrote:
I have observed this in the past, too and do not know how to "fix" it.
Why is it necessary for the volume to appear under /dev/md3? Might it
be possible to use its UUID instead, i.e. check the output of
ls -l /dev/disk/by-uuid
to find out if your m
I created a new mdadm RAID 1 as /dev/md3. But after each reboot, it gets
activated as md127. How can I fix this - preferably without haveing to
delete the whole array again...
The array is defined like this in /etc/mdadm:
ARRAY /dev/md3 metadata=1.2 level=raid1 num-devices=1
UUID=41e0a87f:22a2205
/ and /home are fine on the system. The data on the affected filesystem is
a collection of data from different remote sites, so it could be restored
but that would take a lot of time. That's why I would like to fix the
filesystem so that I can then use more intelligent recovery methods that do
not
schrieb Thomas Schmitt :
> Hi,
>
> Reiner Buehl wrote:
> > Is there a quick way to enlarge the swap space
>
> According to old memories of mine you may create a large, non-sparse file
> as you would do for a virtual disk. E.g. by mkfile (which seems not to be
> in Debian) o
Hi all,
I have a corrupt EXT4 filesystem where fsck.ext4 fails with the error
message:
Error storing directory block information (inode=366740508, block=0,
num=406081): Memory allocation failed
/dev/vg_data/lv_mpg: * FILE SYSTEM WAS MODIFIED *
e2fsck: aborted
/dev/vg_data/lv_mpg: *
,
> code=exited, status=32/n/a
> Jul 02 19:26:02 vdr systemd[1]: video.mount: Failed with result
> 'exit-code'.
> Jul 02 19:26:02 vdr systemd[1]: Failed to mount /video.
>
> Best regards,
> Reiner
>
> Am Fr., 2. Juli 2021 um 19:15 Uhr schrieb Reco :
>
>>
exited,
code=exited, status=32/n/a
Jul 02 19:26:02 vdr systemd[1]: video.mount: Failed with result 'exit-code'.
Jul 02 19:26:02 vdr systemd[1]: Failed to mount /video.
Best regards,
Reiner
Am Fr., 2. Juli 2021 um 19:15 Uhr schrieb Reco :
> Hi.
>
> On Fri, Jul 02, 2021
Hi all,
I have a directory that is mounted via NFS from a remote server. The mount
is done via an /etc/fstab entry like this:
192.168.1.2:/video /video nfs
defaults,x-systemd.automount,x-systemd.requires=network-online.target,x-systemd.device-timeout=10,rsize=8192,wsize=8192,soft,nolock,noa
That seems perfect. Many thanks!
Am Fr., 4. Juni 2021 um 15:10 Uhr schrieb Dan Ritter :
> Reiner Buehl wrote:
> > Hello all,
> >
> > I have setup mdadm to email me when disks in one of my RAID arrays fail.
> > Unfortunately the email messages only contain the device as
Hello all,
I have setup mdadm to email me when disks in one of my RAID arrays fail.
Unfortunately the email messages only contain the device as /dev/sdb1 which
does not give any hint which of the four identical disks in the array is
the affected one.
As /dev/sdb1 is only a symbolic link to a devic
Hi all,
after upgrading from Debian Stretch (cacti 0.8.x) to Buster (cacti 1.2.x),
I can't access the cacti web ui anymore. I only get a message "System log
file is not available for writing, please enable write access Log:
/usr/share/cacti/site/log/cacti.log" in the browser.
Am I missing some up
key "cdrom" not found in map
source(s).
Jul 7 18:23:37 bilbo automount[31697]: key "cdrom" not found in map
source(s).
Best regards,
Reiner
Am Mo., 6. Juli 2020 um 08:05 Uhr schrieb Andrei POPESCU <
andreimpope...@gmail.com>:
> On Lu, 06 iul 20, 07:49:09, Reiner B
Hello,
I keep getting messages from syslog "key "cdrom" not found in map
source(s)." on the console of my Debian Stretch system but I don't even
have a cd rom installed in this system.
I already checked /etc/fstab, /etc/samba/smb.conf, /etc/autofs.conf and all
the /etc/auto.* files as this messag
Many thanks, Floris! With your expression I now see the other options:
bilbo:~# awk -F"'" '/menuentry/ {print $2}' /boot/grub/grub.cfg
Debian GNU/Linux
Advanced options for Debian GNU/Linux
Debian GNU/Linux, with Linux 4.9.0-7-686-pae
Debian GNU/Linux, with Linux 4.9.0-7-686-pae (sysvinit)
On 10.12.2010 21:15, David Gaudine wrote:
The system works, but I still have some questions about whether what
I've already done is OK.
1) Is it OK to use 4 MD arrays like this, or should I use just one and
LVM like the jerryweb link? I got a bit confused reading about LVM
and I don't need a
fix this?
Regards,
Reiner Buehl.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4cfa3a84.2070...@buehl.net
Hi all,
I have a Debian Etch system that runs on a RAID 1 software raid system.
now I would like to upgrade it to Lenny by splitting the mirror off and
keep one mirror as a backup. Alternatively I could add a third disk as a
second mirror and split off this one.
If the upgrade works, I then ad
27 matches
Mail list logo
