<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic amsd segfault. in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/amsd-segfault/m-p/7227085#M189415</link>
    <description>&lt;P&gt;Today's toy is the ML30 gen10 broadcom model with a P408i with a load of unconfigured disks and linux running from &amp;lt;KIOXIA&amp;gt; NVMe on an adapter card in PCI4.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is debian 12.x installed today, amsd whatever is current as of today, 2024.10.13 now.&lt;/P&gt;&lt;P&gt;Linux hexagon 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux&lt;/P&gt;&lt;P&gt;Package: amsd&lt;BR /&gt;Version: 3.3.0-1772.24-debian12&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Apart from the fans being 36,18,6, presumably because the nvme card but &lt;FONT size="5"&gt;NOTHING WILL TELL YOU WHY. (dear HPE, **WHY**)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="4"&gt;If you unplug a drive, "amsd" will have a segfault.&lt;/FONT&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ 1200.952093] smartpqi 0000:0a:00.0: removed 6:0:0:0 31402ec013618e640000000000000000 Direct-Access     ATA      HP SSD S700 500G AIO+ qd=32
[ 1200.959913] amsd[1408]: segfault at 7ffc78631000 ip 00007f7104cd83ae sp 00007ffc7862c298 error 6 in libc.so.6[7f7104ba6000+155000] likely on CPU 2 (core 4, socket 0)
[ 1200.959938] Code: e8 20 76 78 c5 fe 7f 07 48 83 c7 20 48 89 fe 83 e6 1f 48 29 f7 49 01 f0 49 81 e8 80 00 00 00 72 23 c5 fd 7f 07 c5 fd 7f 47 20 &amp;lt;c5&amp;gt; fd 7f 47 40 c5 fd 7f 47 60 48 81 c7 80 00 00 00 49 81 e8 80 00
[ 1201.033542] smartpqi 0000:0a:00.0: removed 6:0:1:0 31402ec013618e650000000000000000 Direct-Access     ATA      HP SSD S700 500G AIO+ qd=32&lt;/LI-CODE&gt;&lt;P&gt;This isn't the first time either, just the first time I have actually recorded it.&lt;/P&gt;&lt;P&gt;While on the subject of amsd, -h says:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;usage: amsd [-f] [-L] [-D&amp;lt;tokens&amp;gt;] [-P&amp;lt;interval&amp;gt;]
                [-M&amp;lt;MIB list&amp;gt;] [-T&amp;lt;interval&amp;gt;] [-G&amp;lt;generic data&amp;gt;]
        -f      Do not fork() from the calling shell.
        -L      Do not open a log file; print all messages to stderr.&lt;/LI-CODE&gt;&lt;P&gt;Even without "-L" lsof shows it is not opening a log file. Strings shows some possible options but...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 18 Oct 2024 00:10:41 GMT</pubDate>
    <dc:creator>BunnyPon</dc:creator>
    <dc:date>2024-10-18T00:10:41Z</dc:date>
    <item>
      <title>amsd segfault.</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/amsd-segfault/m-p/7227085#M189415</link>
      <description>&lt;P&gt;Today's toy is the ML30 gen10 broadcom model with a P408i with a load of unconfigured disks and linux running from &amp;lt;KIOXIA&amp;gt; NVMe on an adapter card in PCI4.&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is debian 12.x installed today, amsd whatever is current as of today, 2024.10.13 now.&lt;/P&gt;&lt;P&gt;Linux hexagon 6.1.0-26-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.112-1 (2024-09-30) x86_64 GNU/Linux&lt;/P&gt;&lt;P&gt;Package: amsd&lt;BR /&gt;Version: 3.3.0-1772.24-debian12&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Apart from the fans being 36,18,6, presumably because the nvme card but &lt;FONT size="5"&gt;NOTHING WILL TELL YOU WHY. (dear HPE, **WHY**)&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&lt;FONT size="4"&gt;If you unplug a drive, "amsd" will have a segfault.&lt;/FONT&gt;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[ 1200.952093] smartpqi 0000:0a:00.0: removed 6:0:0:0 31402ec013618e640000000000000000 Direct-Access     ATA      HP SSD S700 500G AIO+ qd=32
[ 1200.959913] amsd[1408]: segfault at 7ffc78631000 ip 00007f7104cd83ae sp 00007ffc7862c298 error 6 in libc.so.6[7f7104ba6000+155000] likely on CPU 2 (core 4, socket 0)
[ 1200.959938] Code: e8 20 76 78 c5 fe 7f 07 48 83 c7 20 48 89 fe 83 e6 1f 48 29 f7 49 01 f0 49 81 e8 80 00 00 00 72 23 c5 fd 7f 07 c5 fd 7f 47 20 &amp;lt;c5&amp;gt; fd 7f 47 40 c5 fd 7f 47 60 48 81 c7 80 00 00 00 49 81 e8 80 00
[ 1201.033542] smartpqi 0000:0a:00.0: removed 6:0:1:0 31402ec013618e650000000000000000 Direct-Access     ATA      HP SSD S700 500G AIO+ qd=32&lt;/LI-CODE&gt;&lt;P&gt;This isn't the first time either, just the first time I have actually recorded it.&lt;/P&gt;&lt;P&gt;While on the subject of amsd, -h says:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;usage: amsd [-f] [-L] [-D&amp;lt;tokens&amp;gt;] [-P&amp;lt;interval&amp;gt;]
                [-M&amp;lt;MIB list&amp;gt;] [-T&amp;lt;interval&amp;gt;] [-G&amp;lt;generic data&amp;gt;]
        -f      Do not fork() from the calling shell.
        -L      Do not open a log file; print all messages to stderr.&lt;/LI-CODE&gt;&lt;P&gt;Even without "-L" lsof shows it is not opening a log file. Strings shows some possible options but...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 00:10:41 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/amsd-segfault/m-p/7227085#M189415</guid>
      <dc:creator>BunnyPon</dc:creator>
      <dc:date>2024-10-18T00:10:41Z</dc:date>
    </item>
    <item>
      <title>Re: amsd segfault.</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/amsd-segfault/m-p/7227256#M189466</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Please download the HPE Smart Storage Administrator Diagnostic Utility (SSADU) and install it.&lt;/P&gt;&lt;P&gt;Navigate to the folder where ssadu.exe is installed. Please refer to section "13.1.5.3 Generating ADU Report" on page 116 of the &lt;A href="https://support.hpe.com/hpesc/public/docDisplay?docId=dp00002635en_us&amp;amp;docLocale=en_US" target="_blank" rel="noopener"&gt;HPE Smart Storage Administrator CLI User Guide&lt;/A&gt; for command to generate the Arrau Diagnostics Utility report.&lt;/P&gt;&lt;P&gt;If SSDs are installed, then run the command "ssaducli -ssd -f ssd-report.zip"&lt;/P&gt;&lt;P&gt;Once the reports are installed review them to identify issues with the hard drives.&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Tue, 15 Oct 2024 09:35:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/amsd-segfault/m-p/7227256#M189466</guid>
      <dc:creator>TVVJ</dc:creator>
      <dc:date>2024-10-15T09:35:11Z</dc:date>
    </item>
    <item>
      <title>Re: amsd segfault.</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/amsd-segfault/m-p/7227421#M189521</link>
      <description>&lt;P dir="auto" style="margin: 0;"&gt;If you need any further support with analyzing the logs, please feel free to log a support case with us and we would be more than happy to assist you further.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 00:08:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/amsd-segfault/m-p/7227421#M189521</guid>
      <dc:creator>ngnear</dc:creator>
      <dc:date>2024-10-18T00:08:51Z</dc:date>
    </item>
  </channel>
</rss>

