public inbox for developer@lists.illumos.org (since 2011-08)
 help / color / mirror / Atom feed
From: maurilio.longo@libero.it
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] panic inside lmrc driver
Date: Fri, 16 Feb 2024 10:20:14 -0500	[thread overview]
Message-ID: <17080968140.8E4FDDaFb.18650@composer.illumos.topicbox-beta.com> (raw)
In-Reply-To: <17080941690.9036dc2b.53726@composer.illumos.topicbox-beta.com>

[-- Attachment #1: Type: text/plain, Size: 4614 bytes --]

The system reboots, I can see all the disks spinning, on the console appears

reading ZFS configuration
mounting filesystems (n/m)

Then a new 
     Creating /etc/devices/retire_store

appears on /var/adm/messages and the pool is marked as unavailable and the disks become invisible to format.

I've power-cycled the system several times now, without changes, it seems that the controller cannot be used anymore.

modinfo | grep lmrc
194 fffffffff3fb1000   a388 123   1  lmrc (Broadcom MegaRAID 12G SAS RAID)

During boot disks seem to be ok

dmesg | grep lmrc
Feb 16 15:57:20 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:21 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:21 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:21 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:21 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:21 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:21 pg-1 scsi: [ID 583861 kern.info] sd3 at lmrc1: target-port 5000cca85ee5ecb0 lun 0
Feb 16 15:57:23 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:23 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:23 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:23 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:23 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:23 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:24 pg-1 scsi: [ID 583861 kern.info] sd2 at lmrc1: target-port 50014ee6b2513c38 lun 0
Feb 16 15:57:25 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:25 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:25 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:25 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:25 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:26 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:26 pg-1 scsi: [ID 583861 kern.info] sd4 at lmrc1: target-port 5000c500aaf9b0c3 lun 0
Feb 16 15:57:27 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:27 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:27 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:27 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:28 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:28 pg-1 lmrc: [ID 934365 kern.warning] WARNING: lmrc0: command failed, status = 76, ex_status = 0, cdb[0] = 1b
Feb 16 15:57:28 pg-1 scsi: [ID 583861 kern.info] sd5 at lmrc1: target-port 5000c500aaf9bf2f lun 0
Feb 16 15:57:33 pg-1 genunix: [ID 408114 kern.info] /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@p0 (lmrc2) online
Feb 16 15:57:35 pg-1 scsi: [ID 583861 kern.info] ses0 at lmrc2: target-port w300162b20dde3640 lun 0

and

dmesg | grep sd4
Feb 16 15:57:26 pg-1 scsi: [ID 583861 kern.info] sd4 at lmrc1: target-port 5000c500aaf9b0c3 lun 0
Feb 16 15:57:26 pg-1 genunix: [ID 936769 kern.info] sd4 is /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@v0/disk@5000c500aaf9b0c3,0
Feb 16 15:57:27 pg-1 genunix: [ID 408114 kern.info] /pci@0,0/pci8086,43b8@1c/pci1590,32b@0/iport@v0/disk@5000c500aaf9b0c3,0 (sd4) online

Maurilio.



[-- Attachment #2: Type: text/html, Size: 11872 bytes --]

  reply	other threads:[~2024-02-16 15:20 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-07 10:31 maurilio.longo
2024-02-07 11:14 ` [developer] " Peter Tribble
2024-02-07 11:16 ` Hans Rosenfeld
2024-02-07 11:46   ` maurilio.longo
2024-02-07 12:04     ` maurilio.longo
2024-02-07 12:29     ` Hans Rosenfeld
2024-02-07 13:01     ` maurilio.longo
2024-02-07 16:47       ` maurilio.longo
2024-02-07 17:01         ` Hans Rosenfeld
2024-02-07 21:35         ` Hans Rosenfeld
2024-02-08  7:59           ` maurilio.longo
2024-02-08 10:42             ` Hans Rosenfeld
2024-02-08 11:01               ` maurilio.longo
2024-02-09  8:06                 ` maurilio.longo
2024-02-09 19:55                   ` Hans Rosenfeld
2024-02-09 20:36                     ` maurilio.longo
2024-02-12  8:11                       ` maurilio.longo
2024-02-13 19:32                         ` Hans Rosenfeld
2024-02-13 20:55                           ` maurilio.longo
2024-02-13 21:03                           ` maurilio.longo
2024-02-15  6:50                             ` maurilio.longo
2024-02-15  7:38                               ` Carsten Grzemba
2024-02-15  8:11                                 ` Toomas Soome
2024-02-15  9:44                                   ` maurilio.longo
2024-02-16 14:36                                     ` maurilio.longo
2024-02-16 15:20                                       ` maurilio.longo [this message]
2024-02-16 15:27                                         ` maurilio.longo
2024-02-16 15:42                                           ` Robert Mustacchi
2024-02-16 20:41                                             ` maurilio.longo
2024-02-19 21:14                                               ` maurilio.longo
2024-02-20  8:58                                                 ` maurilio.longo
2024-02-22 17:44                                                   ` maurilio.longo
2024-02-26  8:59                                                     ` maurilio.longo
2024-02-26  9:30                                                       ` Carsten Grzemba
2024-08-26 12:30                                                         ` manipm
2024-08-26 15:23                                                           ` Hans Rosenfeld
2024-02-13 19:23                       ` Hans Rosenfeld

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=17080968140.8E4FDDaFb.18650@composer.illumos.topicbox-beta.com \
    --to=maurilio.longo@libero.it \
    --cc=developer@lists.illumos.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).