On Tue, 2 Feb 2021 12:31:45 -0800 John Jason Jordan <[email protected]> dijo:
>nvme0 >nvme0n1 >nvme1 >nvme1n1 >nvme2 >nvme2n1 >nvme3 >nvme3n1 >nvme4 >nvme4n1 >nvme4n1p1 >nvme4n1p2 > >And scrolling up a bit I see md127 and md127p1. > >Everything is back to normal. My only problem is what happens when the >md127 and md127p1 suddenly become read-only again. It happened during >the night of February 1, so I can assume that eventually it's going to >happen again. It worked fine for a couple weeks, and now it has stopped working again. The contents of /dev now include: md127 md127p1 nvme0n2 #was nvme0n1 nvme1n2 #was nvme1n1 nvme2n2 #was nvme2n1 nvme3n2 #was nvme3n1 nvme4 nvme4n1 nvme4n1p1 nvme4n1p2 nvme5 nvme6 nvme7 nvme8 And nvme5-8 do not exist. Things are all screwed up again. I am unable to access any of the files on md127p1 (the array). The array is (supposed to be) made up of nvme0-3, and nvme4 is inside my Thinkpad for / and /home. I pulled the TB3 cable out of the enclosure (which automatically shuts it down) and then plugged it back in again. Nothing changed. From past experience the only way to restore things is to completely reboot. I really need to figure out what is causing this. Is it a defective drive? Is it one of the two PCI cards that the four drives are plugged into? Is it the enclosure that the two PCI cards are plugged into? Why does it work for a couple weeks and then go south? The only thing that I can rule out is the TB3 cable, because I bought three of them and they have been swapped, with no change. This is driving me nuts. _______________________________________________ PLUG: https://pdxlinux.org PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
