On Mon, 28 Nov 2022 11:59:14 -0800
Russell Senior dijo:
>Probably a good idea to record what /proc/mdstat looks like when
>things are working, ahead of time, too.
Done, and added to mdadm.txt file. Thanks!
Probably a good idea to record what /proc/mdstat looks like when things are
working, ahead of time, too.
On Mon, Nov 28, 2022 at 11:28 AM John Jason Jordan wrote:
> On Mon, 28 Nov 2022 11:26:01 -0500
> Tomas Kuchta dijo:
>
> >TB is hot plug interface. As such, I'd sort of expect that HW and SW
On Mon, 28 Nov 2022 11:26:01 -0500
Tomas Kuchta dijo:
>TB is hot plug interface. As such, I'd sort of expect that HW and SW
>assumes that it can safely traverse power states and that connection
>resets may be OK.
>
>If that is what is happening, it is of course pretty nasty thing to do
>to md arr
TB is hot plug interface. As such, I'd sort of expect that HW and SW
assumes that it can safely traverse power states and that connection resets
may be OK.
If that is what is happening, it is of course pretty nasty thing to do to
md arrays. Native higher level file systems btrfs/zfs may fare bette
Another good starting point is: cat /proc/mdstat
On Sun, Nov 27, 2022 at 11:03 PM John Jason Jordan wrote:
> On Sun, 27 Nov 2022 22:39:48 -0800
> Paul Goins dijo:
>
> >When this occurs, have you tried "dmesg -T" or checked
> >/var/log/kern.log or /var/log/syslog for suspicious log entries aroun
On Sun, 27 Nov 2022 22:39:48 -0800
Paul Goins dijo:
>When this occurs, have you tried "dmesg -T" or checked
>/var/log/kern.log or /var/log/syslog for suspicious log entries around
>the time of the error? Might be worth taking a peek as well.
Your suspicion was correct - I had not tried either of
When this occurs, have you tried "dmesg -T" or checked /var/log/kern.log or
/var/log/syslog for suspicious log entries around the time of the error?
Might be worth taking a peek as well.
Best Regards,
Paul Goins
On Sun, Nov 27, 2022 at 9:24 PM John Jason Jordan wrote:
> On Sun, 27 Nov 2022 19:0
On Sun, 27 Nov 2022 19:06:35 -0600
Bill Barry dijo:
>On Sun, Nov 27, 2022 at 7:02 PM Bill Barry wrote:
>>
>> On Sun, Nov 27, 2022 at 6:55 PM John Jason Jordan
>> wrote:
>> >
>> > On Sun, 27 Nov 2022 16:07:09 -0600
>> > Bill Barry dijo:
>> >
>> > >So reassembling is what was needed, but you
On Sun, Nov 27, 2022 at 7:02 PM Bill Barry wrote:
>
> On Sun, Nov 27, 2022 at 6:55 PM John Jason Jordan wrote:
> >
> > On Sun, 27 Nov 2022 16:07:09 -0600
> > Bill Barry dijo:
> >
> > >So reassembling is what was needed, but you don't need to force it.
> > >Now if you just had some way to automat
On Sun, Nov 27, 2022 at 6:55 PM John Jason Jordan wrote:
>
> On Sun, 27 Nov 2022 16:07:09 -0600
> Bill Barry dijo:
>
> >So reassembling is what was needed, but you don't need to force it.
> >Now if you just had some way to automate that. Have you connected
> >your external enclosure to the UPS s
On Sun, 27 Nov 2022 16:07:09 -0600
Bill Barry dijo:
>So reassembling is what was needed, but you don't need to force it.
>Now if you just had some way to automate that. Have you connected
>your external enclosure to the UPS so that it is protected from
>temporary power disruptions?
Yes, everyth
On Sun, Nov 27, 2022 at 3:57 PM John Jason Jordan wrote:
> On Sun, 27 Nov 2022 12:49:54 -0800 (PST)
> Rich Shepard dijo:
>
> >On Sun, 27 Nov 2022, John Jason Jordan wrote:
> >
> >> I've searched documentation on mdadm and I can't figure out if there
> >> is a way to just restart the array. Sugge
On Sun, 27 Nov 2022 12:49:54 -0800 (PST)
Rich Shepard dijo:
>On Sun, 27 Nov 2022, John Jason Jordan wrote:
>
>> I've searched documentation on mdadm and I can't figure out if there
>> is a way to just restart the array. Suggestions?
>How do I reactivate my MDADM RAID5 array? - Super User You s
13 matches
Mail list logo
