From: Uwe Sauter <uwe.sauter.de@gmail.com>
To: Ralf Storm <ralf.storm@konzept-is.de>,
Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] OS Error after upgrade to 7.1
Date: Tue, 23 Nov 2021 14:37:07 +0100 [thread overview]
Message-ID: <37bf83e6-a9f8-fa22-ae56-b9e704ea5003@gmail.com> (raw)
In-Reply-To: <737e7b21-85e0-f7a8-9dff-a6e0a3470951@konzept-is.de>
Am 23.11.21 um 14:34 schrieb Ralf Storm:
> Hello,
>
>
> yes - I have a problem, as mentioned in my first mail, the system is stuck at boot with this message
> and then after a few minutes reboots...
Can you reboot with the previous kernel and check the firmware of the controller?
dmesg | grep mpt | grep -i fw
should show the firmware version.
>
>
> Am 23/11/2021 um 14:14 schrieb Uwe Sauter:
>> Am 23.11.21 um 14:04 schrieb Ralf Storm:
>>> Hello,
>>>
>>> I´m currently upgrading my 7-node Cluster, 1 node without problems, 2 nodes had renamed NICs to be
>>> corrected,
>>>
>>> but the last Node stucks at boot with this message: "mpt2sas_cm0: overiding NVDATA EEDPTagMode
>>> setting"
>>>
>>> Anybody had this error before?
>> Yes, unrelated to Proxmox. But the SAS controller works fine even with this message.
>>
>> Do you have issues accessing your storage?
>>
>>> Best regards
>>>
>>
>> _______________________________________________
>> pve-user mailing list
>> pve-user@lists.proxmox.com
>> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
next prev parent reply other threads:[~2021-11-23 13:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 13:04 Ralf Storm
2021-11-23 13:14 ` Uwe Sauter
[not found] ` <737e7b21-85e0-f7a8-9dff-a6e0a3470951@konzept-is.de>
2021-11-23 13:37 ` Uwe Sauter [this message]
2021-11-24 10:24 ` Ralf Storm
[not found] ` <mailman.713.1637764284.15957.pve-user@lists.proxmox.com>
2021-11-24 14:45 ` Ralf Storm
2021-11-24 15:36 ` Uwe Sauter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37bf83e6-a9f8-fa22-ae56-b9e704ea5003@gmail.com \
--to=uwe.sauter.de@gmail.com \
--cc=pve-user@lists.proxmox.com \
--cc=ralf.storm@konzept-is.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.