Supermicro provided a workaround: boot with the kernel command line
parameter pci=realloc=off.
As an side, Rocky 9.2 does not have this issue even though it boots
without that kernel command line parameter.
Jeff (http://engineering.purdue.edu/~qobi)
I purchased a new server: Supermicro AS-8125GS-TNHR. It has 17 NVME
drives installed:
1x Micron 7450
12x Micron 9300
4x Micron 9400
Upon boot, /dev/nvme* only shows 10 drives: the Micron 7450, 8 of the
Micron 9300s, and 1 of the Micron 9400s. Before I plugged in the 12x
Micron 9300, /d
I purchased a new server based on the Supermicro AS-8125GS-TNHR. It
has two EPYC 9654 processors. Each processor has 96 cores and 192 hyperthreads.
Thus the system as a whole has 192 cores and 384 hyperthreads. I run
Debian stable bookworm. When first installed, it ran kernel
6.1.0.12. That kernel
> I just changed /etc/mailname on all of my machines to contain:
>
> qobi@upplysingaoflun>cat /etc/mailname
> purdue.edu
You know it makes sense to do this. :)
I had never manually edited /etc/mailname. I took whatever what put there by
the debian installer perhaps as modified by
I would bet you do not recall what you answered to the questions regarding
mail config when installing wheezy.
I kept records of what I answered to those questions when installing sarge,
etch, lenny, squeeze, and wheezy.
If you have a backup copy of /etc/exim4 you could diff and see.
Al
y upplysingaoflun with local (Exim 4.84_2)
(envelope-from )
id 1ba92P-0002nV-R3
for q...@upplysingaoflun.ecn.purdue.edu; Wed, 17 Aug 2016 18:10:17 -0400
To: q...@upplysingaoflun.ecn.purdue.edu
Subject: to qobi from qobi
Message-Id:
From: Jeffrey Mark Siskind
Date: Wed, 17
> qobi@upplysingaoflun>all+n cat /etc/mailname
> tlamachilistli:
> tlamachilistli.ecn.purdue.edu
> zhineng:
> zhineng.ecn.purdue.edu
This "all+n" intrigues me. What is it ?
One of several simple scripts I wrote that run a command on different subsets
of the machines I maintain.
> What it does under jessie:
>
> (1) and (3) still work. (2) does not. I have never seen any mail to
root but
> the people who maintain smtp.ecn.purdue.edu claim that mail to root
on my
> machines gets sent to root@empty.
^
Thanks for your help.
> # mail sent by smarthost; received via SMTP or fetchmail
> # default hostname
> # default 127.0.0.1 ; ::1
> # blank
> # blank
> # smtp.ecn.purdue.edu
> # yes
> # purdue.edu
> # no
> # mbox format in
Appologies for the repost. I sent this yesterday and it hasn't yet appeared.
It may have been filtered out for some reason.
I would appreciate some help configuring exim4.
What I want:
I have multiple machines that I maintain and have root access on. They have
domain ecn.purdue.edu and names lik
From: Ritesh Raj Sarraf
I (still) have MCE errors on my new laptop [1]. But so far, hasn't created
any problem.
It causes my servers to halt.
Jeff (http://engineering.purdue.edu/~qobi)
I upgraded four Dell R815s from wheezy to jessie a few weeks ago. Prior to the
upgrade, they were running reliably for about 5 years. Since the upgrade, two
machines have been getting periodic machine checks. The machines boot fine and
run for a day or more. The machine checks appear to happen spor
I have installed jessie. Among other packages installed, I have
apt-get -y install gnome
apt-get -y install xorg
apt-get -y install xserver-xorg-dev
apt-get -y install afni
apt-get -y -t jessie-backports install nvidia-driver
apt-get -y -t jessie-backports install nvidia-cuda-too
I had big issues with mptsas and 3.16 in jessie, so I am still using
3.2.0-4-rt-amd64
Will jessie run with 3.2.0-4-rt-amd64? If so, where do I get it and how do I
install it on a fresh jessie install that wasn't dist-upgraded from wheezy?
Jeff (http://engineering.purdue.edu/~qobi)
The non-determinism in which identifiers are shown might be a bug in the
installer, or it might be caused by failure of ID commands to the
drives.
I think most of the problems you're still having must be caused by a
bug in the RAID driver, mpt2sas (or its firmware, if that's not
I'd like to thank everyone for helping out.
Here is an update on installing jessie on R815s.
I succeeded in installing on three of my four R815s. But I am holding off on
the last because it is my file server and there are still issues. Please read
on. I don't believe that the problem is solved an
Please note that bootint with rootdelay=20 does not solve the problem. It only
masks it.
1. If I attempt a fresh USB install of jessie, when md0 is correctly built
before the install, the process of doing the fresh install breaks
md0. When it gets to grub install, components of md0 are mi
>Are you certain that there isn't a PERC H700 in this machine? [Sort of
>odd that mpt2sas is triggering a state error in your screenshot if there
>actually isn't one.]
>
> There could be one. But I probably don't use it. I use software RAID. Dell
> wouldn't sell an R8
I conjecture that there may be two to five separate issues.
1. Setting up md0 upon boot takes a long time. rootdelay=20 fixes this.
2. There is a problem writing to disk. Perhaps just writing to certain blocks.
Because even when the machine boots with rootdelay=20, and md0 has all 6
comp
> and attempted
>
>mdadm /dev/md0 --add /dev/sda1
>mdadm /dev/md0 --add /dev/sdb1
>mdadm /dev/md0 --add /dev/sdc1
>mdadm /dev/md0 --add /dev/sdd1
>mdadm /dev/md0 --add /dev/sde1
>mdadm /dev/md0 --add /dev/sdf1
>
> but these all failed.
Thi
Are you certain that there isn't a PERC H700 in this machine? [Sort of
odd that mpt2sas is triggering a state error in your screenshot if there
actually isn't one.]
There could be one. But I probably don't use it. I use software RAID. Dell
wouldn't sell an R815 without an OS. I think I pu
Thanks for your help.
> Here is a screen picture.
Could you upload this to an image paste site or send it along (or use a
serial console to get it as text?)
http://upplysingaoflun.ecn.purdue.edu/~qobi/20160619_140357.jpg
(The other screen picture of a machine (not an R815) that does bo
-
default Install
default English
default United States
default American English
Go Back
default Configure network manually
128.46.115.211
default netmask
default gateway
128.210.11.57 128.210.11.5 128.46.154.76
default hostname
default domain name
root password
root password
Jeffrey
I am attempting to install jessie on a Dell Poweredge R815. It has been
running wheezy reliably for years. And running squeeze reliably for years
before that. But no matter what I try it won't install or boot.
I have tried two ways.
1. I attempt a fresh install from a USB dongle. It gets all the
> I'd like to make a live wheezy USB dongle. I followed the
> instructions on
>
>https://www.debian.org/CD/faq/#write-usb
>
> to make a live USB from
>
>
http://cdimage.debian.org/mirror/cdimage/archive/7.11.0-live/amd64/iso-hybrid/debian-live-7.11.0-amd64-standar
> I'd like to make a live wheezy USB dongle. I followed the instructions on
Why wheezy ... it's old.
I have been running wheezy for about 5 years without any problem. The machine
has two partitions / and /aux. I attempted a fresh install of jessie in /.
But the install failed and the machin
I'd like to make a live wheezy USB dongle. I followed the instructions on
https://www.debian.org/CD/faq/#write-usb
to make a live USB from
http://cdimage.debian.org/mirror/cdimage/archive/7.11.0-live/amd64/iso-hybrid/debian-live-7.11.0-amd64-standard.iso
but apparently my machine, an old
I have a Debian farm of 24 machines running wheezy that I am upgrading to
jessie. Four of the machines are identical Dell R815 servers, each with 6
disks. (The others are Dell T5500 with 4 disks each (12 machines), Dell C6145
with 4 disks each (4 machines), or HP Proliant DL165 G5p with 3 disks eac
I'm running Etch i386 2.6.15-1-k7-smp on a Shuttle SN25P with an FX-60. As of
last night, I did an apt-get update and an apt-get upgrade so I am current.
The module snd_ice1724 and its dependents are loaded. alsamixer reports that
the hardware is an SN25P with a VIA Technologies VIA1617A.
Audio ou
29 matches
Mail list logo
