From: maurilio.longo@libero.it
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] panic inside lmrc driver
Date: Tue, 13 Feb 2024 15:55:27 -0500 [thread overview]
Message-ID: <17078577270.33f4F.487809@composer.illumos.topicbox.com> (raw)
In-Reply-To: <ZcvDyakyRsd_6CR0@grumpf.hope-2000.org>
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
Hi Hans,
> Thanks! I've filed bug for this: https://www.illumos.org/issues/16277
reguarding your bug report, I had just plugged in a new disk before expanding my pool from two disks to four, and I did this as soon as the system reached the login: prompt after a reboot.
When I inserted the second one, nothing happened.
Thursday I'll be able to try to add a new disk right after a reboot to see if I can cause the problem again.
Btw,
> char [128] evt_descr = [ "Inserted: Drive 02(e252/Port 1I Box 0 Bay 0)" ]
My unit has a single SFF disk cage which can hold 8 disks, I did insert mine into slot 5 or 6, but as you can see it shows Bay 0, which is wrong; the cage has disks numbered from 1 to 8, from left to right.
This is the cage: https://www.servershop24.de/en/hpe-sff-gen9-gen10-cage/a-117573/
Thanks, I'll let you know if I can break it again ;-)
Maurilio.
[-- Attachment #2: Type: text/html, Size: 1459 bytes --]
next prev parent reply other threads:[~2024-02-13 20:55 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 [this message]
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
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=17078577270.33f4F.487809@composer.illumos.topicbox.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).